This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
\n
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
+{
+ "resourceType" : "CapabilityStatement",
+ "id" : "IHE.MHDS.DocumentRegistry",
+ "text" : {
+ "status" : "extensions",
+ "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>IHE_MHDS_DocumentRegistry</h2><div><p>MHD Document Registry Actor definition</p>\n</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td><div><p>CapabilityStatement Requirements for the MHDS Document Registry Actor</p>\n<ul>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/MHD/index.html\">MHD</a> - <a href=\"https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133113-document-recipient\">Document Recipient</a></strong> supports publication requests by the <a href=\"https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133111-document-source\">MHD Document Source</a>. The Comprehensive Metadata Option is required.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/MHD/index.html\">MHD</a> - <a href=\"https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133114-document-responder\">Document Responder</a></strong> supports the discovery and retrieval of documents by <a href=\"https://profiles.ihe.net/ITI/MHD/index.html\">MHD</a> <a href=\"https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133112-document-consumer\">Document Consumer</a>.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/PMIR/index.html\">PMIR</a> - <a href=\"https://profiles.ihe.net/ITI/PMIR/CapabilityStatement-IHE.PMIR.PatientIdentityConsumer.html\">Patient Identity Consumer</a></strong> provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/SVCM/index.html\">SVCM</a> - <a href=\"https://profiles.ihe.net/ITI/SVCM/volume-1.html#1511-svcm-actorstransactions\">Terminology Consumer</a></strong> enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/mCSD/index.html\">mCSD</a> - <a href=\"https://profiles.ihe.net/ITI/mCSD/volume-1.html#146111-care-services-selective-consumer\">Care Services Selective Consumer</a></strong> enables the Registry to have access to Organization and Practitioner resources.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/IUA/index.html\">IUA</a> - <a href=\"https://profiles.ihe.net/ITI/IUA/index.html\">Authorization Server and Resource Server</a></strong> enforces access control decisions.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html\">ATNA</a> - <a href=\"https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html#9.1.1.1\">Secure Node</a></strong> enable the Document Registry to be secure, record audit records, and support secure transactions.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html\">CT</a> - <a href=\"https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html\">Time Client</a></strong> assures that all records of time done by the Document Registry are aligned with the Time Source.</li>\n<li><strong><a href=\"https://profiles.ihe.net/ITI/BALP/index.html\">BALP</a> - <a href=\"https://profiles.ihe.net/ITI/BALP/volume-1.html#152111-audit-creator\">Audit Creator</a></strong> recording rich audit log entries to ATNA.</li>\n</ul>\n</div></td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title=\"GET a resource (read interaction)\">Read</b></th><th><b title=\"GET all set of resources of the type (search interaction)\">Search</b></th><th><b title=\"PUT a new resource version (update interaction)\">Update</b></th><th><b title=\"POST a new resource (create interaction)\">Create</b></th></tr></table></div>"
+ },
+ "url" : "https://profiles.ihe.net/ITI/MHDS/CapabilityStatement/IHE.MHDS.DocumentRegistry",
+ "version" : "2.3.1",
+ "name" : "IHE_MHDS_DocumentRegistry",
+ "title" : "MHDS Document Registry",
+ "status" : "active",
+ "experimental" : false,
+ "date" : "2022-10-28",
+ "publisher" : "IHE IT Infrastructure Technical Committee",
+ "contact" : [
+ {
+ "telecom" : [
+ {
+ "system" : "url",
+ "value" : "https://www.ihe.net/ihe_domains/it_infrastructure/"
+ }
+ ]
+ },
+ {
+ "telecom" : [
+ {
+ "system" : "email",
+ "value" : "iti@ihe.net"
+ }
+ ]
+ },
+ {
+ "name" : "IHE IT Infrastructure Technical Committee",
+ "telecom" : [
+ {
+ "system" : "email",
+ "value" : "iti@ihe.net"
+ }
+ ]
+ }
+ ],
+ "description" : "MHD Document Registry Actor definition",
+ "jurisdiction" : [
+ {
+ "coding" : [
+ {
+ "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
+ "code" : "001"
+ }
+ ]
+ }
+ ],
+ "kind" : "requirements",
+ "imports" : [
+ "https://profiles.ihe.net/ITI/MHD/CapabilityStatement/IHE.MHD.DocumentRecipient",
+ "https://profiles.ihe.net/ITI/MHD/CapabilityStatement/IHE.MHD.DocumentResponder",
+ "https://profiles.ihe.net/ITI/PMIR/CapabilityStatement/IHE.PMIR.PatientIdentityConsumer",
+ "https://profiles.ihe.net/ITI/SVCM/CapabilityStatement/IHE.SVCM.TerminologyConsumer",
+ "https://profiles.ihe.net/ITI/mCSD/CapabilityStatement/IHE.mCSD.CareServicesSelectiveConsumer"
+ ],
+ "fhirVersion" : "4.0.1",
+ "format" : [
+ "application/fhir+xml",
+ "application/fhir+json"
+ ],
+ "rest" : [
+ {
+ "mode" : "server",
+ "documentation" : "CapabilityStatement Requirements for the MHDS Document Registry Actor\n\n- **[MHD](https://profiles.ihe.net/ITI/MHD/index.html) - [Document Recipient](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133113-document-recipient)** supports publication requests by the [MHD Document Source](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133111-document-source). The Comprehensive Metadata Option is required.\n- **[MHD](https://profiles.ihe.net/ITI/MHD/index.html) - [Document Responder](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133114-document-responder)** supports the discovery and retrieval of documents by [MHD](https://profiles.ihe.net/ITI/MHD/index.html) [Document Consumer](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133112-document-consumer).\n- **[PMIR](https://profiles.ihe.net/ITI/PMIR/index.html) - [Patient Identity Consumer](https://profiles.ihe.net/ITI/PMIR/CapabilityStatement-IHE.PMIR.PatientIdentityConsumer.html)** provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.\n- **[SVCM](https://profiles.ihe.net/ITI/SVCM/index.html) - [Terminology Consumer](https://profiles.ihe.net/ITI/SVCM/volume-1.html#1511-svcm-actorstransactions)** enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.\n- **[mCSD](https://profiles.ihe.net/ITI/mCSD/index.html) - [Care Services Selective Consumer](https://profiles.ihe.net/ITI/mCSD/volume-1.html#146111-care-services-selective-consumer)** enables the Registry to have access to Organization and Practitioner resources.\n- **[IUA](https://profiles.ihe.net/ITI/IUA/index.html) - [Authorization Server and Resource Server](https://profiles.ihe.net/ITI/IUA/index.html)** enforces access control decisions.\n- **[ATNA](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html) - [Secure Node](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html#9.1.1.1)** enable the Document Registry to be secure, record audit records, and support secure transactions.\n- **[CT](https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html) - [Time Client](https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html)** assures that all records of time done by the Document Registry are aligned with the Time Source.\n- **[BALP](https://profiles.ihe.net/ITI/BALP/index.html) - [Audit Creator](https://profiles.ihe.net/ITI/BALP/volume-1.html#152111-audit-creator)** recording rich audit log entries to ATNA."
+ }
+ ]
+}
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
\n
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
\n
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
\n
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
+
+<CapabilityStatement xmlns="http://hl7.org/fhir">
+ <idvalue="IHE.MHDS.DocumentRegistry"/>
+ <text>
+ <statusvalue="extensions"/>
+ <div xmlns="http://www.w3.org/1999/xhtml"><h2>IHE_MHDS_DocumentRegistry</h2><div><p>MHD Document Registry Actor definition</p>
+</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td><div><p>CapabilityStatement Requirements for the MHDS Document Registry Actor</p>
+<ul>
+<li><strong><a href="https://profiles.ihe.net/ITI/MHD/index.html">MHD</a> - <a href="https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133113-document-recipient">Document Recipient</a></strong> supports publication requests by the <a href="https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133111-document-source">MHD Document Source</a>. The Comprehensive Metadata Option is required.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/MHD/index.html">MHD</a> - <a href="https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133114-document-responder">Document Responder</a></strong> supports the discovery and retrieval of documents by <a href="https://profiles.ihe.net/ITI/MHD/index.html">MHD</a> <a href="https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133112-document-consumer">Document Consumer</a>.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/PMIR/index.html">PMIR</a> - <a href="https://profiles.ihe.net/ITI/PMIR/CapabilityStatement-IHE.PMIR.PatientIdentityConsumer.html">Patient Identity Consumer</a></strong> provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/SVCM/index.html">SVCM</a> - <a href="https://profiles.ihe.net/ITI/SVCM/volume-1.html#1511-svcm-actorstransactions">Terminology Consumer</a></strong> enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/mCSD/index.html">mCSD</a> - <a href="https://profiles.ihe.net/ITI/mCSD/volume-1.html#146111-care-services-selective-consumer">Care Services Selective Consumer</a></strong> enables the Registry to have access to Organization and Practitioner resources.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/IUA/index.html">IUA</a> - <a href="https://profiles.ihe.net/ITI/IUA/index.html">Authorization Server and Resource Server</a></strong> enforces access control decisions.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html">ATNA</a> - <a href="https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html#9.1.1.1">Secure Node</a></strong> enable the Document Registry to be secure, record audit records, and support secure transactions.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html">CT</a> - <a href="https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html">Time Client</a></strong> assures that all records of time done by the Document Registry are aligned with the Time Source.</li>
+<li><strong><a href="https://profiles.ihe.net/ITI/BALP/index.html">BALP</a> - <a href="https://profiles.ihe.net/ITI/BALP/volume-1.html#152111-audit-creator">Audit Creator</a></strong> recording rich audit log entries to ATNA.</li>
+</ul>
+</div></td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title="GET a resource (read interaction)">Read</b></th><th><b title="GET all set of resources of the type (search interaction)">Search</b></th><th><b title="PUT a new resource version (update interaction)">Update</b></th><th><b title="POST a new resource (create interaction)">Create</b></th></tr></table></div>
+ </text>
+ <url
+ value="https://profiles.ihe.net/ITI/MHDS/CapabilityStatement/IHE.MHDS.DocumentRegistry"/>
+ <versionvalue="2.3.1"/>
+ <namevalue="IHE_MHDS_DocumentRegistry"/>
+ <titlevalue="MHDS Document Registry"/>
+ <statusvalue="active"/>
+ <experimentalvalue="false"/>
+ <datevalue="2022-10-28"/>
+ <publishervalue="IHE IT Infrastructure Technical Committee"/>
+ <contact>
+ <telecom>
+ <systemvalue="url"/>
+ <valuevalue="https://www.ihe.net/ihe_domains/it_infrastructure/"/>
+ </telecom>
+ </contact>
+ <contact>
+ <telecom>
+ <systemvalue="email"/>
+ <valuevalue="iti@ihe.net"/>
+ </telecom>
+ </contact>
+ <contact>
+ <namevalue="IHE IT Infrastructure Technical Committee"/>
+ <telecom>
+ <systemvalue="email"/>
+ <valuevalue="iti@ihe.net"/>
+ </telecom>
+ </contact>
+ <descriptionvalue="MHD Document Registry Actor definition"/>
+ <jurisdiction>
+ <coding>
+ <systemvalue="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
+ <codevalue="001"/>
+ </coding>
+ </jurisdiction>
+ <kindvalue="requirements"/>
+ <imports
+ value="https://profiles.ihe.net/ITI/MHD/CapabilityStatement/IHE.MHD.DocumentRecipient"/>
+ <imports
+ value="https://profiles.ihe.net/ITI/MHD/CapabilityStatement/IHE.MHD.DocumentResponder"/>
+ <imports
+ value="https://profiles.ihe.net/ITI/PMIR/CapabilityStatement/IHE.PMIR.PatientIdentityConsumer"/>
+ <imports
+ value="https://profiles.ihe.net/ITI/SVCM/CapabilityStatement/IHE.SVCM.TerminologyConsumer"/>
+ <imports
+ value="https://profiles.ihe.net/ITI/mCSD/CapabilityStatement/IHE.mCSD.CareServicesSelectiveConsumer"/>
+ <fhirVersionvalue="4.0.1"/>
+ <formatvalue="application/fhir+xml"/>
+ <formatvalue="application/fhir+json"/>
+ <rest>
+ <modevalue="server"/>
+ <documentation
+ value="CapabilityStatement Requirements for the MHDS Document Registry Actor
+
+- **[MHD](https://profiles.ihe.net/ITI/MHD/index.html) - [Document Recipient](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133113-document-recipient)** supports publication requests by the [MHD Document Source](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133111-document-source). The Comprehensive Metadata Option is required.
+- **[MHD](https://profiles.ihe.net/ITI/MHD/index.html) - [Document Responder](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133114-document-responder)** supports the discovery and retrieval of documents by [MHD](https://profiles.ihe.net/ITI/MHD/index.html) [Document Consumer](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html#133112-document-consumer).
+- **[PMIR](https://profiles.ihe.net/ITI/PMIR/index.html) - [Patient Identity Consumer](https://profiles.ihe.net/ITI/PMIR/CapabilityStatement-IHE.PMIR.PatientIdentityConsumer.html)** provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+- **[SVCM](https://profiles.ihe.net/ITI/SVCM/index.html) - [Terminology Consumer](https://profiles.ihe.net/ITI/SVCM/volume-1.html#1511-svcm-actorstransactions)** enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
+- **[mCSD](https://profiles.ihe.net/ITI/mCSD/index.html) - [Care Services Selective Consumer](https://profiles.ihe.net/ITI/mCSD/volume-1.html#146111-care-services-selective-consumer)** enables the Registry to have access to Organization and Practitioner resources.
+- **[IUA](https://profiles.ihe.net/ITI/IUA/index.html) - [Authorization Server and Resource Server](https://profiles.ihe.net/ITI/IUA/index.html)** enforces access control decisions.
+- **[ATNA](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html) - [Secure Node](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html#9.1.1.1)** enable the Document Registry to be secure, record audit records, and support secure transactions.
+- **[CT](https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html) - [Time Client](https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html)** assures that all records of time done by the Document Registry are aligned with the Time Source.
+- **[BALP](https://profiles.ihe.net/ITI/BALP/index.html) - [Audit Creator](https://profiles.ihe.net/ITI/BALP/volume-1.html#152111-audit-creator)** recording rich audit log entries to ATNA."/>
+ </rest>
+</CapabilityStatement>
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor.
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
+
+
Behavior: Capability Statements
+
+
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
PMIR - Patient Identity Consumer provides patient identity synchronization and specifically the merge function to be applied to any data managed in the Document Registry.
+
SVCM - Terminology Consumer enables the Document Registry to gain access to ValueSets that the Registry is enforcing Metadata consistency.
This page is part of the Mobile Health Document Sharing (v2.3.1: Publication) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.iti.mhds.r4) and R4B (ihe.iti.mhds.r4b) are available.
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
+
+
Package ihe.formatcode.fhir#1.1.0
+
Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)
+
+
Package hl7.fhir.uv.extensions.r4#1.0.0
+
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
+
+
Package ihe.iti.balp#1.1.2
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Tue, Aug 1, 2023 08:40-0500-05:00)
+
+
Package hl7.fhir.uv.extensions.r4#1.0.0
+
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
+
+
Package ihe.iti.balp#1.1.2
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Tue, Aug 1, 2023 08:40-0500-05:00)
+
+
Package ihe.formatcode.fhir#1.1.0
+
Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)
+
+
Package ihe.iti.mhd#4.2.1
+
ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents (MHD) (built Wed, Aug 2, 2023 10:57-0500-05:00)
+
+
Package hl7.fhir.uv.extensions.r4#1.0.0
+
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
+
+
Package ihe.iti.balp#1.1.2
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Tue, Aug 1, 2023 08:40-0500-05:00)
+
+
Package ihe.iti.svcm#1.5.1
+
The Sharing Valuesets, Codes, and Maps (SVCM) Profile defines a lightweight interface through which healthcare systems may retrieve centrally managed uniform nomenclature and mappings between code systems based on the HL7 Fast Healthcare Interoperability Resources (FHIR) specification. (built Wed, Aug 2, 2023 12:46-0500-05:00)
+
+
Package ihe.iti.balp#1.1.0
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Wed, May 4, 2022 10:07-0500-05:00)
+
+
Package ihe.iti.mcsd#3.8.0
+
The IHE Mobile Care Services Discovery (mCSD) IG provides a transaction for mobile and lightweight browser-based applications to find and update care services resources. (built Fri, Aug 12, 2022 09:41-0500-05:00)
+
+
Package ihe.iti.pdqm#2.4.0
+
The Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications. (built Tue, Feb 22, 2022 07:42-0600-06:00)
+
+
Package hl7.fhir.uv.extensions.r4#1.0.0
+
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
+
+
Package ihe.iti.balp#1.1.2
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Tue, Aug 1, 2023 08:40-0500-05:00)
+
+
Package ihe.iti.pixm#3.0.3
+
ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Patient Identifier Cross-referencing for mobile (PIXm) (built Thu, Aug 3, 2023 15:56-0500-05:00)
+
+
Package ihe.iti.balp#1.1.0
+
The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Wed, May 4, 2022 10:07-0500-05:00)
+
+
Package ihe.iti.pmir#1.5.0
+
The Patient Master Identity Registry (PMIR) Profile supports the creating, updating and deprecating of patient master identity information about a subject of care, as well as subscribing to changes to the patient master identity, using the HL7 FHIR standard resources and RESTful transactions. (built Mon, Aug 8, 2022 16:03-0500-05:00)
+
+
+
+
Globals Table
+
+
There are no Global profiles defined
+
+
+
IP Statements
+
+
No use of external IP (other than from the FHIR specification)