CH EPR mHealth (R4)
0.1.3 - CI build

CH EPR mHealth (R4), published by eHealth Suisse. This is not an authorized publication; it is the continuous build for version 0.1.3). This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-mhealth/ and changes regularly. See the Directory of published versions

Artifacts Summary

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 complying with the implementation guide are expected to declare conformance to one or more of the following capability statements.

mHealth: App (client) CapabilityStatement for mHealth App (client).
PMIR Patient Identifier Cross-Reference Consumer (client) CapabilityStatement for Actor PMIR Patient Identifier Cross-reference Consumer (client).
PMIR Patient Identity Source (client) CapabilityStatement for Actor PMIR Patient Identity Source (client).
MHD Document Source (client) CapabilityStatement for Actor MHD Document Source (client).
MHD Document Consumer (client) CapabilityStatement for Actor MHD Document Consumer (client).
mHealth: Mobile Access Gateway (server) CapabilityStatement for mHealth MobileAccessGateway (server).
PMIR Patient Identity Manager (server) CapabilityStatement for Actor PMIR Patient Identity Manager (server).
MHD Document Recipient (server) CapabilityStatement for Actor MHD Document Recipient (server).
MHD Document Responder (server) CapabilityStatement for Actor MHD Document Responder (server).
IHE ITI Mobile access to Health Documents (MHD) - Document Consumer (client) This CapabilityStatement describes the Document Consumer actor in the IHE Mobile access to Health Documents (MHD) Rev. 3.1 Profile. See http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD). The IHE MHD Profile text is Normative, this conformance resource is Informative.
IHE ITI Mobile access to Health Documents (MHD) - Document Recipient This CapabilityStatement describes the Document Recipient actor in the IHE Mobile access to Health Documents (MHD) Rev. 3.1 Profile. See http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD). The IHE MHD Profile text is Normative, this conformance resource is Informative.
IHE ITI Mobile access to Health Documents (MHD) - Document Responder (server) This CapabilityStatement describes the Document Responder actor in the IHE Mobile access to Health Documents (MHD) Rev. 3.1 Profile. See http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD). The IHE MHD Profile text is Normative, this conformance resource is Informative.
IHE ITI Mobile access to Health Documents (MHD) - Document Source (publisher) This CapabilityStatement describes the Document Source actor in the IHE Mobile access to Health Documents (MHD) Rev. 2.3 Profile. See http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD). The IHE MHD Profile text is Normative, this conformance resource is Informative.
IHE ITI Patient Identity Cross-Reference for Mobile (PIXm) - Consumer (client) CapabilityStatement for Consumer Actor in the IHE IT Infrastructure Technical Framework Supplement IHE PIXm. See http://wiki.ihe.net/index.php/PIXm. The IHE Profile text is Normative, this conformance resource is Informative.
IHE ITI Patient Identity Cross-Reference for Mobile (PIXm) - Manager (server) CapabilityStatement for Manager Actor in the IHE IT Infrastructure Technical Framework Supplement IHE PIXm. See http://wiki.ihe.net/index.php/PIXm. The IHE Profile text is Normative, this conformance resource is Informative.

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems complying with this implementation guide

Find patient matches using IHE-PMIR Profile Find patient matches using IHE-PMIR Profile
Find patient matches using IHE-PIXm Profile A Master Patient Index ([MPI](http://en.wikipedia.org/wiki/Enterprise_master_patient_index) ) is a service used to manage patient identification in a context where multiple patient databases exist. Healthcare applications and middleware use the MPI to match patients between the databases, and to store new patient details as they are encountered. MPIs are highly specialized applications, often tailored extensively to the institution's particular mix of patients. MPIs can also be run on a regional and national basis. To ask an MPI to match a patient, clients use the "$match" operation, which accepts a patient resource which may be only partially complete. The data provided is interpreted as an MPI input and processed by an algorithm of some kind that uses the data to determine the most appropriate matches in the patient set. Note that different MPI matching algorithms have different required inputs. The generic $match operation does not specify any particular algorithm, nor a minimum set of information that must be provided when asking for an MPI match operation to be performed, but many implementations will have a set of minimum information, which may be declared in their definition of the $match operation by specifying a profile on the resource parameter, indicating which properties are required in the search. The patient resource submitted to the operation does not have to be complete, nor does it need to pass validation (i.e. mandatory fields don't need to be populated), but it does have to be a valid instance, as it is used as the reference data to match against.

Structures: Resource Profiles

These define constraints on FHIR resources that need to be complied with by conformant implementations

CH PIXm IN Parameters See https://wiki.ihe.net/index.php/Patient_Identifier_Cross-Reference_for_Mobile_(PIXm)
CH PIXm OUT Parameters See https://wiki.ihe.net/index.php/Patient_Identifier_Cross-Reference_for_Mobile_(PIXm)
CH PMIR Bundle Message See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
CH EPR mHealth Patient Profile for IHE PMIR Patient
CH EPR mHealth Provider Organization Profile for IHE PMIR Organization
CH PMIR Bundle Message Response See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
CH PMIR MessageHeader Response See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
CH MHD Provide Comphrensive Document Bundle IHE MHD profile on Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata.
IHE_MHD_Provide_Comprehensive_DocumentBundle IHE_MHD_Provide_Comprehensive_DocumentBundle, define URL to resolve profile in Bundle.meta.profile
CH MHD Comprehensive DocumentManifest (SubmissionSet) IHE MHD Profile on DocumentManifest for Comprehensive Metadata (SubmissionSet).
CH MHD Comprehensive DocumentReference IHE MHD Profile on DocumentReference (DocumentEntry) when used in the Provide Transaction with Comprehensive (aka XDS-on-FHIR) Metadata.
CH MHD Provide Comphrensive Document Bundle Response IHE MHD profile on Response of Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata.
CH MHD Comprehensive DocumentManifest (SubmissionSet) Bundle IHE MHD Profile on DocumentManifest for Comprehensive Metadata (SubmissionSet) in a Bundle.
CH MHD Comprehensive DocumentReference Bundle IHE MHD Profile on DocumentReference (DocumentEntry) in a Bundle from a Query with Comprehensive Metadata (aka XDS-on-FHIR).
Comprehensive DocumentManifest (SubmissionSet) Bundle IHE MHD Profile on DocumentManifest for Comprehensive Metadata (SubmissionSet) in a Bundle.
Comprehensive DocumentReference Bundle IHE MHD Profile on DocumentReference (DocumentEntry) in a Bundle from a Query with Comprehensive Metadata (aka XDS-on-FHIR).
IHE PIXm Parameters See https://wiki.ihe.net/index.php/Patient_Identifier_Cross-Reference_for_Mobile_(PIXm)
IHE PMIR Bundle Message See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR Bundle History See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR MessageHeader See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR Patient Merge See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR Patient Related Person See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR Subscription See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
IHE PMIR Subscription request See https://wiki.ihe.net/index.php/Patient_Master_Identity_Registry_(PMIR)
Comprehensive DocumentManifest (SubmissionSet) IHE MHD Profile on DocumentManifest for Comprehensive Metadata (SubmissionSet).
Comprehensive List (Folder) IHE MHD Profile on List with Comprehensive Metadata (Folder).
Minimal DocumentManifest (SubmissionSet) IHE MHD Profile on DocumentManifest for Minimal Metadata (SubmissionSet).
Minimal List Folder IHE MHD Profile on List with Minimal Metadata (Folder).
Provide Comphrensive Document Bundle IHE MHD profile on Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata.

Structures: Data Type Profiles

These define constraints on FHIR data types that need to be complied with by conformant implementations

CH EPR mHealth HumanName The humanname WITHOUT the ISO 21090 qualifier https://www.hl7.org/fhir/extension-iso21090-en-qualifier.html BR
CH EPR mHealth BirthName The birthname with the ISO 21090 qualifier https://www.hl7.org/fhir/extension-iso21090-en-qualifier.html BR

Structures: Extension Definitions

These define constraints on FHIR data types that need to be complied with by conformant implementations

CH Extension Author AuthorRole Extension Author AuthorRole for DocumentManifest
CH Extension Deletion Status Extension Deletion Status for DocumentReference

Terminology: Value Sets

These define sets of codes used by systems conforming with this implementation guide

ch-ehealth-valueset-deletionstatus Additional metadata about deletion status on the DocumentReference
CH PIXm Format Mime Type The requested format of the PIXm response from the mime-type value set. See ITI TF-2x: Appendix Z.6.

Terminology: Code Systems

These define new code systems used by systems conforming with this implementation guide

ch-ehealth-codesystem-deletionstatus Additional metadata about deletion status on the DocumentReference

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

Parameters PMIR Input Example Input Parameters PMIR Mobile Patient Identifier Corss-reference Query
Parameters PMIR Output Example Output Parameters PMIR Mobile Patient Identifier Corss-reference Query
Bundle PMIR Feed Example Bundle for a PMIR Feed
Patient PMIR Feed Example PMIR patient feed
Franz Muster Needs Absolute Url Example Patient
GruppenpraxisCH Example Organization
Bundle PMIR Response Example Bundle for a PMIR Response
MHD Provide Document Bundle for MedicationCard MHD Provide Document Bundle for MedicationCard
DocumentManifest for MedicationCard Example DocumentManifest for a MedicationCard
DocumentReference for MedicationCard Example DocumentReference for a MedicationCard
MHD Provide Document Bundle Response for MedicationCard MHD Provide Document Bundle Response for MedicationCard
MHD Find DocumentManifests MHD Find DocumentManifests - Bundle as Response
MHD Find DocumentReferences MHD Find DocumentReferences - Bundle as Response