Scalable Consent Management
1.0.0-preview - STU 1 PReview United States of America flag

Scalable Consent Management, published by HL7 International / Community Based Collaborative Care. This guide is not an authorized publication; it is the continuous build for version 1.0.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-consent-management/ and changes regularly. See the Directory of published versions

: Technical Specification Client

Page standards status: Trial-use Maturity Level: 1

Raw ttl | Download

@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

<http://hl7.org/fhir/Requirements/technical-specification-client> a fhir:Requirements ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:Resource.id [ fhir:value "technical-specification-client"] ;
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "generated" ] ;
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: Requirements technical-specification-client</b></p><a name=\"technical-specification-client\"> </a><a name=\"hctechnical-specification-client\"> </a><p>These requirements apply to the actor <a href=\"ActorDefinition-client.html\">Client</a></p><table class=\"grid\"><tr><td><b><a name=\"67\"> </a></b>requirement-67</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>Consent Client SHALL query the consent administration service for the identifiers of the involved patients, practitioners, organizations, and related persons&lt;br/&gt;&lt;br/&gt;Not testable yet - need lots more details about the lifecycle of relates resource instances.\nQuery or match?\nImplies CAS is an MPI and similar for other resources?\nDoesn’t say what triggers these queries to occur, or what effect it has on workflows, or whether discovered identifiers are used in resources...</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=client%20systems%20SHALL%20query%20the%20consent%20administration%20service%20for%20the%20identifiers%20of%20the%20involved%20patients%2C%20practitioners%2C%20organizations%2C%20and%20related%20persons\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"1168\"> </a></b>requirement-1168</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>To search for consents by organization identifier, implementers SHOULD use the controller:identifier chained search parameter (e.g., GET [base]/Consent?controller:identifier=|1234567890) rather than a custom organization ID search parameter&lt;br/&gt;&lt;br/&gt;Because it's a SHOULD, assumes other ways; for now this is the only way we'll test.</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20search%20for%20consents%20by%20organization%20identifier%2C%20implementers%20should%20use%20the%20controller%3Aidentifier%20chained%20search%20parameter%20%28e.g.%2C%20get%20%5Bbase%5D/consent%3Fcontroller%3Aidentifier%3D%7C1234567890%29%20rather%20than%20a%20custom%20organization%20id%20search%20parameter\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"1169\"> </a></b>requirement-1169</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>To search for consents by patient identifier, implementers SHOULD use the patient:identifier chained search parameter (e.g., GET [base]/Consent?patient:identifier=http://example.org/mrn|M1230041)&lt;br/&gt;&lt;br/&gt;Because it's a SHOULD, assumes other ways; for now this is the only way we'll test.</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20search%20for%20consents%20by%20patient%20identifier%2C%20implementers%20should%20use%20the%20patient%3Aidentifier%20chained%20search%20parameter%20%28e.g.%2C%20get%20%5Bbase%5D/consent%3Fpatient%3Aidentifier%3Dhttp%3A//example.org/mrn%7Cm1230041%29\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"265\"> </a></b>requirement-265</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>This guide mandates that Subscriptions be used&lt;br/&gt;&lt;br/&gt;Need conformance words - who does this apply to? Assuming clients, but which ones? What triggering actions? Are clients required to support only, or that they positively subscribe to specific other systems? Suggest referencing section with normative workflows.</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=this%20guide%20mandates%20that%20Subscriptions%20be%20used\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"202\"> </a></b>requirement-202</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-MAY\">MAY</a></td><td><div><p>Consent Client MAY subscribe to Consent topics as defined by the FAST Subscription Topic&lt;br/&gt;&lt;br/&gt;- No conformance words \"client will...\", so not clear which actors SHALL or MAY support. For now, treating as MAY for both clients and servers - tests can be conditional.</p>\n<ul>\n<li>Nature of topic is it allows combinations of criteria. I'll call out each criterion below for traceability.</li>\n<li>TBD whether there need to be requirements for CAS to detect and fire Consent events or if implied by subs framework.</li>\n</ul>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20register%20a%20subscription%2C%20consent%20client%20systems%20will%20post%20to%20a%20consent%20server%20system%27s%20subscription%20endpoint\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"1170\"> </a></b>requirement-1170</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Systems conforming to this guide SHOULD NOT update an existing Consent resource in place using RESTful PUT or PATCH&lt;br/&gt;&lt;br/&gt;Capturing because conformance verb, but can't test a negative.</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20conforming%20to%20this%20guide%20should%20not%20update%20an%20existing%20consent%20resource%20in%20place%20using%20restful%20put%20or%20patch\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"1165\"> </a></b>requirement-1165</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>Consent Client SHALL support AuditEvent search by Consent (entity)</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20shall%20support%20searching%20for%20fast%20consent%20audit%20events%C2%A7op9%20using%20the%20following%20search%20parameters&amp;text=entity%20%E2%80%94%20use%20entity%3DConsent/%5Bid%5D%20to%20search%20for%20all%20authorization%20decisions%20made%20against%20a%20specific%20Consent%20instance\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"299\"> </a></b>requirement-299</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>Consent Client SHALL support AuditEvent search by patient&lt;br/&gt;&lt;br/&gt;Implied - need requirement</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20shall%20support%20searching%20for%20fast%20consent%20audit%20events%C2%A7op9%20using%20the%20following%20search%20parameters&amp;text=patient%20%E2%80%94%20use%20patient%3D%5Bref%5D%20to%20search%20for%20all%20authorization%20decisions%20involving%20any%20consent%20for%20a%20specific%20patient\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr><tr><td><b><a name=\"1167\"> </a></b>requirement-1167</td><td><a href=\"http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/CodeSystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>For disclosure events (cases where health information was actually shared following a permit decision), implementers SHOULD follow IHE-BALP patterns and the ITI-81 Retrieve ATNA Audit Event transaction for querying those events</p>\n</div><p>Links: </p><ul><li>Derived From: <code>HL7 FAST Consent IG</code></li><li>Satisfied By: <a href=\"https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=for%20disclosure%20events%20%28cases%20where%20health%20information%20was%20actually%20shared%20following%20a%20permit%20decision%29%2C%20implementers%20should%20follow%20ihe%2Dbalp%20patterns%20and%20the%20iti%2D81%20retrieve%20atna%20audit%20event%20transaction%20for%20querying%20those%20events\">https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html</a></li></ul></td></tr></table></div>"
  ] ;
  fhir:DomainResource.extension [
     fhir:index 0 ;
     fhir:Extension.url [ fhir:value "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg" ] ;
     fhir:Extension.valueCode [ fhir:value "cbcc" ]
  ], [
     fhir:index 1 ;
     fhir:Extension.url [ fhir:value "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm" ] ;
     fhir:Extension.valueInteger [
       fhir:value "1"^^xsd:integer ;
       fhir:Element.extension [
         fhir:index 0 ;
         fhir:Extension.url [ fhir:value "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom" ] ;
         fhir:Extension.valueCanonical [
           fhir:value "http://hl7.org/fhir/us/consent-management/ImplementationGuide/hl7.fhir.us.consent-management" ;
           fhir:link <http://hl7.org/fhir/us/consent-management/ImplementationGuide/hl7.fhir.us.consent-management>
         ]
       ]
     ]
  ], [
     fhir:index 2 ;
     fhir:Extension.url [ fhir:value "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status" ] ;
     fhir:Extension.valueCode [
       fhir:value "trial-use" ;
       fhir:Element.extension [
         fhir:index 0 ;
         fhir:Extension.url [ fhir:value "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom" ] ;
         fhir:Extension.valueCanonical [
           fhir:value "http://hl7.org/fhir/us/consent-management/ImplementationGuide/hl7.fhir.us.consent-management" ;
           fhir:link <http://hl7.org/fhir/us/consent-management/ImplementationGuide/hl7.fhir.us.consent-management>
         ]
       ]
     ]
  ] ;
  fhir:Requirements.url [ fhir:value "http://hl7.org/fhir/us/consent-management/Requirements/technical-specification-client"] ;
  fhir:Requirements.version [ fhir:value "1.0.0-preview"] ;
  fhir:Requirements.name [ fhir:value "TechnicalSpecificationClient"] ;
  fhir:Requirements.title [ fhir:value "Technical Specification Client"] ;
  fhir:Requirements.status [ fhir:value "active"] ;
  fhir:Requirements.experimental [ fhir:value "false"^^xsd:boolean] ;
  fhir:Requirements.date [ fhir:value "2026-09-02T22:40:54-04:00"^^xsd:dateTime] ;
  fhir:Requirements.publisher [ fhir:value "HL7 International / Community Based Collaborative Care"] ;
  fhir:Requirements.contact [
     fhir:index 0 ;
     fhir:ContactDetail.name [ fhir:value "HL7 International / Community Based Collaborative Care" ] ;
     fhir:ContactDetail.telecom [
       fhir:index 0 ;
       fhir:ContactPoint.system [ fhir:value "url" ] ;
       fhir:ContactPoint.value [ fhir:value "http://www.hl7.org/Special/committees/homehealth" ]
     ]
  ] ;
  fhir:Requirements.description [ fhir:value "Technical Specification Requirements for Client"] ;
  fhir:Requirements.jurisdiction [
     fhir:index 0 ;
     fhir:CodeableConcept.coding [
       fhir:index 0 ;
       fhir:Coding.system [ fhir:value "urn:iso:std:iso:3166" ] ;
       fhir:Coding.code [ fhir:value "US" ] ;
       fhir:Coding.display [ fhir:value "United States of America" ]
     ]
  ] ;
  fhir:Requirements.actor [
     fhir:value "http://hl7.org/fhir/us/consent-management/ActorDefinition/client" ;
     fhir:index 0 ;
     fhir:link <http://hl7.org/fhir/us/consent-management/ActorDefinition/client>
  ] ;
  fhir:Requirements.statement [
     fhir:index 0 ;
     fhir:Requirements.statement.key [ fhir:value "67" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-67" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHALL" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "Consent Client SHALL query the consent administration service for the identifiers of the involved patients, practitioners, organizations, and related persons<br/><br/>Not testable yet - need lots more details about the lifecycle of relates resource instances. \nQuery or match?\nImplies CAS is an MPI and similar for other resources?\nDoesn’t say what triggers these queries to occur, or what effect it has on workflows, or whether discovered identifiers are used in resources..." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=client%20systems%20SHALL%20query%20the%20consent%20administration%20service%20for%20the%20identifiers%20of%20the%20involved%20patients%2C%20practitioners%2C%20organizations%2C%20and%20related%20persons" ;
       fhir:index 0
     ]
  ], [
     fhir:index 1 ;
     fhir:Requirements.statement.key [ fhir:value "1168" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-1168" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHOULD" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "To search for consents by organization identifier, implementers SHOULD use the controller:identifier chained search parameter (e.g., GET [base]/Consent?controller:identifier=|1234567890) rather than a custom organization ID search parameter<br/><br/>Because it's a SHOULD, assumes other ways; for now this is the only way we'll test." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20search%20for%20consents%20by%20organization%20identifier%2C%20implementers%20should%20use%20the%20controller%3Aidentifier%20chained%20search%20parameter%20%28e.g.%2C%20get%20%5Bbase%5D/consent%3Fcontroller%3Aidentifier%3D%7C1234567890%29%20rather%20than%20a%20custom%20organization%20id%20search%20parameter" ;
       fhir:index 0
     ]
  ], [
     fhir:index 2 ;
     fhir:Requirements.statement.key [ fhir:value "1169" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-1169" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHOULD" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "To search for consents by patient identifier, implementers SHOULD use the patient:identifier chained search parameter (e.g., GET [base]/Consent?patient:identifier=http://example.org/mrn|M1230041)<br/><br/>Because it's a SHOULD, assumes other ways; for now this is the only way we'll test." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20search%20for%20consents%20by%20patient%20identifier%2C%20implementers%20should%20use%20the%20patient%3Aidentifier%20chained%20search%20parameter%20%28e.g.%2C%20get%20%5Bbase%5D/consent%3Fpatient%3Aidentifier%3Dhttp%3A//example.org/mrn%7Cm1230041%29" ;
       fhir:index 0
     ]
  ], [
     fhir:index 3 ;
     fhir:Requirements.statement.key [ fhir:value "265" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-265" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHALL" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "This guide mandates that Subscriptions be used<br/><br/>Need conformance words - who does this apply to? Assuming clients, but which ones? What triggering actions? Are clients required to support only, or that they positively subscribe to specific other systems? Suggest referencing section with normative workflows." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=this%20guide%20mandates%20that%20Subscriptions%20be%20used" ;
       fhir:index 0
     ]
  ], [
     fhir:index 4 ;
     fhir:Requirements.statement.key [ fhir:value "202" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-202" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "MAY" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "Consent Client MAY subscribe to Consent topics as defined by the FAST Subscription Topic<br/><br/>- No conformance words \"client will...\", so not clear which actors SHALL or MAY support. For now, treating as MAY for both clients and servers - tests can be conditional.\n- Nature of topic is it allows combinations of criteria. I'll call out each criterion below for traceability.\n- TBD whether there need to be requirements for CAS to detect and fire Consent events or if implied by subs framework." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=to%20register%20a%20subscription%2C%20consent%20client%20systems%20will%20post%20to%20a%20consent%20server%20system%27s%20subscription%20endpoint" ;
       fhir:index 0
     ]
  ], [
     fhir:index 5 ;
     fhir:Requirements.statement.key [ fhir:value "1170" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-1170" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHOULD" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "Systems conforming to this guide SHOULD NOT update an existing Consent resource in place using RESTful PUT or PATCH<br/><br/>Capturing because conformance verb, but can't test a negative." ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20conforming%20to%20this%20guide%20should%20not%20update%20an%20existing%20consent%20resource%20in%20place%20using%20restful%20put%20or%20patch" ;
       fhir:index 0
     ]
  ], [
     fhir:index 6 ;
     fhir:Requirements.statement.key [ fhir:value "1165" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-1165" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHALL" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "Consent Client SHALL support AuditEvent search by Consent (entity)" ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20shall%20support%20searching%20for%20fast%20consent%20audit%20events%C2%A7op9%20using%20the%20following%20search%20parameters&text=entity%20%E2%80%94%20use%20entity%3DConsent/%5Bid%5D%20to%20search%20for%20all%20authorization%20decisions%20made%20against%20a%20specific%20Consent%20instance" ;
       fhir:index 0
     ]
  ], [
     fhir:index 7 ;
     fhir:Requirements.statement.key [ fhir:value "299" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-299" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHALL" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "Consent Client SHALL support AuditEvent search by patient<br/><br/>Implied - need requirement" ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=systems%20shall%20support%20searching%20for%20fast%20consent%20audit%20events%C2%A7op9%20using%20the%20following%20search%20parameters&text=patient%20%E2%80%94%20use%20patient%3D%5Bref%5D%20to%20search%20for%20all%20authorization%20decisions%20involving%20any%20consent%20for%20a%20specific%20patient" ;
       fhir:index 0
     ]
  ], [
     fhir:index 8 ;
     fhir:Requirements.statement.key [ fhir:value "1167" ] ;
     fhir:Requirements.statement.label [ fhir:value "requirement-1167" ] ;
     fhir:Requirements.statement.conformance [
       fhir:value "SHOULD" ;
       fhir:index 0
     ] ;
     fhir:Requirements.statement.conditionality [ fhir:value "false"^^xsd:boolean ] ;
     fhir:Requirements.statement.requirement [ fhir:value "For disclosure events (cases where health information was actually shared following a permit decision), implementers SHOULD follow IHE-BALP patterns and the ITI-81 Retrieve ATNA Audit Event transaction for querying those events" ] ;
     fhir:Requirements.statement.derivedFrom [ fhir:value "HL7 FAST Consent IG" ] ;
     fhir:Requirements.statement.satisfiedBy [
       fhir:value "https://build.fhir.org/ig/HL7/fhir-consent-management/en/technical.html#:~:text=for%20disclosure%20events%20%28cases%20where%20health%20information%20was%20actually%20shared%20following%20a%20permit%20decision%29%2C%20implementers%20should%20follow%20ihe%2Dbalp%20patterns%20and%20the%20iti%2D81%20retrieve%20atna%20audit%20event%20transaction%20for%20querying%20those%20events" ;
       fhir:index 0
     ]
  ] .

# - ontology header ------------------------------------------------------------

<http://hl7.org/fhir/Requirements/technical-specification-client.ttl> a owl:Ontology ;
  owl:imports fhir:fhir.ttl ;
  owl:versionIRI <http://build.fhir.org/Requirements/technical-specification-client.ttl> .