CH EPR mHealth (R4)
1.1.0 - DSTU 2 Informative Ballot
This page is part of the CH EPR mHealth (R4) (v1.1.0: DSTU 2) based on FHIR R4. . For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
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.
mHealth: App (client) |
CapabilityStatement for mHealth App (client). |
PIXm Patient Identifier Cross-Reference Consumer (client) |
The Patient Identifier Cross-reference Consumer Actor CapabililtyStatement expresses the requirements that can be utilized while being compliant. - using FHIR R4 - using json or xml encoding - query the $ihe-pix operation |
PIXm Patient Identity Source (client) |
The Patient Identity Source Actor CapabililtyStatement expresses the requirements that can be utilized while being compliant. - using FHIR R4 - using json or xml encoding - using conditional update for [ITI-104] - provide supported Patient profile for crosss-referencing for [ITI-104] |
MHD Document Source (client) |
CapabilityStatement for Actor MHD Document Source (client). |
MHD Document Consumer (client) |
CapabilityStatement for Actor MHD Document Consumer (client). |
mHealth: API (server) |
CapabilityStatement for mHealth API (server). |
PIXm Patient Identifier Cross-reference Manager (server) |
The Patient Identifier Cross-reference Manager CapabililtyStatement expresses the requirements that shall be provided. - using FHIR R4 - using json and xml encoding - support the $ihe-pix operation - support conditional update for [ITI-104] - support conditional delete for [ITI-104] if Remove Patient Option is supported - used with IHE-IUA |
MHD Document Recipient (server) |
CapabilityStatement for Actor MHD Document Recipient (server). |
MHD Document Responder (server) |
CapabilityStatement for Actor MHD Document Responder (server). |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide
Find patient matches using IHE-PIXm Profile |
Find patient matches using IHE-PIXm Profile |
These define constraints on FHIR resources for systems conforming to this implementation guide
CH PIXm IN Parameters |
The StructureDefinition defines the Input Parameters for the $ihe-pix operation: - Input: sourceIdentifier, targetSystem |
CH PIXm OUT Parameters |
The StructureDefinition defines the Output Parameters for the $ihe-pix operation: |
CH EPR mHealth Patient Profile for PIXm Mobile Patient Identity Feed |
The patient demographics and identifier information which can be provided in the PIXm Feed according to the EPR. If the patient is already registered in a community, the MPI-PID SHALL be provided as an identifier. The EPR-SPID as an identifier MAY be added. The birthname can be added with the ISO 21090 qualifier extension. |
CH EPR mHealth Provider Organization Profile for PIXm |
Organization |
CH MHD Provide Document Bundle Comprehensive |
IHE MHD profile on Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata for the Swiss EPR. |
CH MHD SubmissionSet Comprehensive |
CH MHD SubmissionSet Comprehensive |
CH MHD DocumentReference Comprehensive |
CH MHD Profile on CH Core DocumentReference |
CH MHD Provide Document Bundle Comphrensive Response |
IHE MHD profile on Response of Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata. |
CH MHD SubmissionSet Comprehensive Bundle |
CH MHD SubmissionSet Comprehensive Bundle response [ITI-66] |
CH MHD Find Document References Comprehensive Response message |
A profile on the Find Document References Comprehensive Response message for ITI-68 |
These define constraints on FHIR data types for systems conforming to this implementation guide
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 |
Oid Identifier |
Identifer with an oid |
These define constraints on FHIR data types for systems conforming to this implementation guide
CH Extension Author AuthorRole |
Extension Author AuthorRole for SubmissionSet and DocumentEntry |
CH Extension Deletion Status |
Extension Deletion Status for DocumentReference |
These define sets of codes used by systems conforming to this implementation guide
ch-ehealth-valueset-deletionstatus |
Additional metadata about deletion status on the DocumentReference |
These define new code systems used by systems conforming to this implementation guide
ch-ehealth-codesystem-deletionstatus |
Additional metadata about deletion status on the DocumentReference |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like
Parameters PIXm Query Input |
Example Input Parameters Mobile Patient Identifier Corss-reference Query |
Parameters PIXm Query Output |
Example Output Parameters Mobile Patient Identifier Corss-reference Query |
Patient PIXm Feed |
Example PIXm Patient for Feed |
Franz Muster Needs Absolute Url |
Example Patient |
GruppenpraxisCH |
Example Organization |
MHD Provide Document Bundle for MedicationCard |
MHD Provide Document Bundle for MedicationCard |
SubmissionSet (List) for MedicationCard |
Example SubmissionSet 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 DocumentSubmissionSet (List) |
MHD Find Document SumbmissionSet- Bundle as Response |
MHD Find DocumentReferences |
MHD Find DocumentReferences - Bundle as Response |
Audit Event for Provide Bundle Transaction at Source |
Audit Example for a Provide Bundle Transaction from source perspective |