CapabilityStatement for Client Actor in the IHE IT Infrastructure Technical Framework Supplement Add RESTful ATNA.

CapabilityStatement for Server Actor in the IHE IT Infrastructure Technical Framework Supplement Add RESTful ATNA.

The PDQm Patient Demographics Consumer Actor requirements CapabilityStatement expresses the requirements that can be utilized while being compliant.

• Query against the FHIR endpoint to the Patient Resource endpoint
• Using FHIR R4
• may request json or xml encoding
• TLS SHALL be used together with IUA basic access token

Defines the CapabilityStatement for the Patient Audit Record Repository actor of ITI-81.

CapabilityStatement for EPR API (server).

CapabilityStatement for EPR App (client).

CapabilityStatement for Actor MHD Document Consumer (client).

CapabilityStatement for Actor MHD Document Recipient (server).

CapabilityStatement for Actor MHD Document Responder (server).

CapabilityStatement for Actor MHD Document Source (client).

The PDQm Patient Demographics Supplier Actor requirements CapabilityStatement expresses the requirements that shall be provided.

• Query against the FHIR endpoint to the Patient Resource endpoint
• Using FHIR R4
• shall support both json or xml encoding
• TLS SHALL be used together with IUA basic access token
• SHALL support the PDQm $match operation
• SHALL return Patient Resources conforming to the PDQm Patient Profile

The Patient Identifier Cross-reference Consumer Actor CapabilityStatement expresses the requirements that can be utilized while being compliant. - using FHIR R4 - using json or xml encoding - query the $ihe-pix operation

The Patient Identifier Cross-reference Manager CapabilityStatement 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

The Patient Identity Source Actor CapabilityStatement 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 cross-referencing for [ITI-104]

CapabilityStatement for the Policy Repository actor in the CH:PPQm profile (server).

CapabilityStatement for the Policy Source and Policy Consumer actors in the CH:PPQm profile (client).

CapabilityStatement for Data Source Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Server Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Client Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

This operation implements the Patient Demographics Match [ITI-119] transaction. It is fully compatible with the $match Operation on Patient. The only changes are to constrain the input parameters to use the PDQm Patient Profile for $match Input profile and to constrain the output parameters to use the PDQm Patient Profile profile.

Defines the IHE RESTFul ATNA Query Parameter entity.identifier for an AuditEvent.

This profile is used to define the CH Audit Event for the [CH:MHD-1] transaction and the actor 'Document Responder'.

This profile is used to define the CH Audit Event for the [CH:MHD-1] transaction and the actor 'Document Source'.

This profile is used to define the CH Audit Event for the [ITI-104] transaction and the actor 'Patient Identifier Cross-reference Manager' when creating a patient.

This profile is used to define the CH Audit Event for the [ITI-104] transaction and the actor 'Patient Identifier Cross-reference Manager' when updating a patient.

This profile is used to define the CH Audit Event for the [ITI-104] transaction and the actor 'Patient Identity Source'.

This profile is used to define the CH Audit Event for the [ITI-119] transaction and the actor 'Patient Demographics Consumer'.

This profile is used to define the CH Audit Event for the [ITI-119] transaction and the actor 'Patient Demographics Supplier'.

This profile is used to define the CH Audit Event for the [ITI-130] transaction and the actors 'Data Source' & Directory, when adding care service resources.

This profile is used to define the CH Audit Event for the [ITI-130] transaction and the actors 'Data Source' & Directory, when deleting care service resources.

This profile is used to define the CH Audit Event for the [ITI-130] transaction and the actors 'Data Source' & Directory, when updating care service resources.

This profile is used to define the CH Audit Event for the [ITI-65] transaction and the actor 'Document Recipient'.

This profile is used to define the CH Audit Event for the [ITI-65] transaction and the actor 'Document Source'.

This profile is used to define the CH Audit Event for the [ITI-67] transaction and the actor 'Document Consumer'.

This profile is used to define the CH Audit Event for the [ITI-67] transaction and the actor 'Document Responder'.

This profile is used to define the CH Audit Event for the [ITI-68] transaction and the actor 'Document Consumer'.

This profile is used to define the CH Audit Event for the [ITI-68] transaction and the actor 'Document Responder'.

This profile is used to define the CH Audit Event for the [ITI-83] transaction and the actor 'Patient Identifier Cross-reference Consumer'.

This profile is used to define the CH Audit Event for the [ITI-83] transaction and the actor 'Patient Identifier Cross-reference Manager'.

This profile is used to define the CH Audit Event for the [ITI-90] transaction and the actors 'Query Client' & Directory, when querying care service resources.

This profile is used to define the CH Audit Event for the [ITI-90] transaction and the actors 'Query Client' & Directory, when reading care service resources.

This profile is used to define the CH Audit Event for the [PPQ-3] transaction and the actors 'Policy Source' and 'Policy Repository' when creating a privacy policy.

This profile is used to define the CH Audit Event for the [PPQ-3] transaction and the actors 'Policy Source' and 'Policy Repository' when deleting a privacy policy.

This profile is used to define the CH Audit Event for the [PPQ-3] transaction and the actors 'Policy Source' and 'Policy Repository' when updating a privacy policy.

This profile is used to define the CH Audit Event for the [PPQ-5] transaction and the actor 'Policy Consumer'.

This profile is used to define the CH Audit Event for the [PPQ-5] transaction and the actor 'Policy Repository'.

This is the profile for Swiss Audit Events when a transaction is secured with a Basic Authorization Token.

This is the profile for Swiss Audit Events when a transaction is secured with an Extended Authorization Token.

CH EPR FHIR profile on AuditEvent

CH MHD Profile on CH Core DocumentReference

A profile on the Find Document References Comprehensive Response message for ITI-68

IHE MHD profile on Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata for the Swiss EPR.

IHE MHD profile on Response of Provide Document Bundle (ITI-65) transaction with Comprehensive Metadata.

CH MHD SubmissionSet Comprehensive

The PDQm Match Input Parameters Profile describes the Parameters Resource that is to be posted to the $match endpoint when invoking ITI-119. This profile is consistent with the exceptions of the Patient-match operation in FHIR core, except the input resource SHALL be an instance of the PDQm Patient Profile for $match Input.

Note that the only REQUIRED parameter is the Patient Resource. When only the Patient is supplied, it can be POSTed directly to the $match endpoint without being wrapped in a Parameters Resource, as long as it conforms to the PDQm Patient Profile for $match Input.

A profile on the Query Patient Resource Response message for ITI-119

A profile on the OperationOutcome for indicating which additional attributes are requested to lower the results number.

The patient demographics and identifier information which can be provided in the PDQm response 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.

The PDQm Patient Profile for $match Input SHALL be provided as input to the ITI-119 transaction.

• While it is not REQUIRED that the input to $match be a valid FHIR instance, it is RECOMMENDED to supply as many elements as possible to facilitate matching.
• modifierExtension and implicitRules SHALL not be specified.
• The ChEprFhirBirthName profile is available to hold the mother's maiden name

Organization

The StructureDefinition defines the Input Parameters for the $ihe-pix operation: - Input: sourceIdentifier, targetSystem

The StructureDefinition defines the Output Parameters for the $ihe-pix operation:

The patient demographics and identifier information which can be provided in the PIXm Feed according to the EPR. The EPR-SPID as an identifier SHALL be added. The birthname can be added with the ISO 21090 qualifier extension.

Swiss EPR Policy Set as a Consent

Bundle for Mobile Privacy Policy Bundle Feed requests

Bundle for Mobile Privacy Policy Retrieve responses

CH mCSD profile on Organization

CH mCSD profile on Practitioner

CH mCSD profile on PractitionerRole

EPR policy set based on template 201 – grants the patient the full access to the their EPR. This policy set shall be created during the patient's onboarding.

EPR policy set based on template 202 – grants healthcare professionals access to the patient's EPR in emergency mode. This policy set shall be created during the patient's onboarding, but can be modified later.

EPR policy set based on template 203 – defines the minimal confidentiality level of documents. This policy set shall be created during the patient's onboarding, but can be modified later.

EPR policy set based on template 301 – gives a particular healthcare professional read access to the patient's EPR, without delegation rights.

EPR policy set based on template 302 – gives a group of healthcare professionals read access to the patient's EPR, without delegation rights.

EPR policy set based on template 303 – gives a representative full access to the patient's EPR.

EPR policy set based on template 304 – gives a particular healthcare professional read access to the patient's EPR, with delegation rights.

A profile on the Bundle transaction for ITI-130 Process Care Services Resources Request Message

This profile defines the content of the access audit trail event which a community has to provide for a patients audit trail.

This profile defines the content of the document audit events which a community has to provide for a patients audit trail.

This profile defines the content of the HPD audit events which a community has to provide for a patients audit trail.

This profile defines the content of the policy audit events which a community has to provide for a patients audit trail.

This profile defines the response to the [ITI-81] query. The response is a search set including all audit events which a community has to provide for a patients audit trail.

The birthname with the ISO 21090 qualifier https://www.hl7.org/fhir/extension-iso21090-en-qualifier.html BR

The human name WITHOUT the ISO 21090 qualifier https://www.hl7.org/fhir/extension-iso21090-en-qualifier.html BR

Identifier representation of DICOM Study Instance UID

Identifier for XDSDocumentEntry.uniqueId

Identifier with an LDAP DN

Identifier with an oid

Extension Author AuthorRole for SubmissionSet and DocumentEntry

Extension Deletion Status for DocumentReference

This CH MHD extension enables to provide homeCommunityId in an OperationOutcome

AccessAuditTrailEventType

Coded Values for indicating which additional attributes are requested to lower the results number.

Actor Identifier Types for CH:PPQm

Value Set for CH:PPQm Consent Identifier Types

HTTP methods allowed in CH:PPQm Feed requests

IDs of policy set templates

IDs of basis policy sets that may be referenced from template 203

IDs of basis policy sets that may be referenced from templates 202 and 302

IDs of basis policy sets that may be referenced from template 304

IDs of basis policy sets that may be referenced from template 301

IDs of basis policy sets that may be referenced from templates 201 and 303

DocumentAuditEventType

EprParticipant

HpdAuditEventType

PolicyAuditEventType

Value set for allowed HTTP verbs, excluding GET operations.

Codes for indicating which additional attributes are requested to lower the results number.

Code system for CH:PPQm Consent Identifier Types

Code system for Policy Set Template IDs

Codes for indicating which additional attributes are requested to lower the results number.

NamingSystem for event type code system from eHealth Suisse.

NamingSystem for event type code from IHE.

NamingSystem for uniqueId from IHE.

NamingSystem for Lightweight Directory Access Protocol (LDAP); https://www.ietf.org/rfc/rfc4514.html.

CH ATC - Access of Audit Trail Repository

CH ATC - Audit Event for Document Search

CH ATC - AuditEvent of Healthcare professional which has been added to a group and patient has been notified

CH ATC - Create Access Right for Healthcare professional

CH ATC - Create Access Right a representative

CH ATC - Creation of a Document for a patient by a representative of this patient

CH ATC - Reponse Audit Trail

CH ATC - Retrieveal of a Document from a patient by an assitant for a healthcare professional

This example shows an made by the Document Responder for a CH:MHD-1 transaction.

This example shows an made by the Document Source for a CH:MHD-1 transaction.

This example shows an AuditEvent made by the Data Source for a ITI-130 transaction that created a new PractitionerRole (relationship).

This example shows an AuditEvent made by the Directory for a ITI-130 transaction that deleted an Organization.

This example shows an AuditEvent made by the Directory for a ITI-130 transaction that updated an existing Practitioner.

This example shows an made by the Policy Source for a PPQ-3 transaction that added a new Consent.

This example shows an AuditEvent made by the Policy Source for a PPQ-3 transaction that deleted a Consent.

This example shows an made by the Policy Repository for a PPQ-3 transaction that updated an existing Consent.

This example shows an made by the Policy Consumer for a PPQ-5 transaction.

This example shows an made by the Policy Repository for a PPQ-5 transaction.

This example shows an made by the Patient Identifier Cross-reference Manager for an ITI-104 transaction that added a new Patient.

This example shows an made by the Patient Identity Source for an ITI-104 transaction.

This example shows an made by the Patient Identifier Cross-reference Manager for an ITI-104 transaction that revised an existing Patient.

This example shows an made by the Patient Demographics Consumer for an ITI-119 transaction.

This example shows an made by the Patient Demographics Supplier for an ITI-119 transaction.

This example shows an made by the Document Recipient for an ITI-65 transaction.

This example shows an made by the Document Source for an ITI-65 transaction.

This example shows an made by the Document Consumer for an ITI-67 transaction.

This example shows an made by the Document Responder for an ITI-67 transaction.

This example shows an made by the Document Consumer for an ITI-68 transaction.

This example shows an made by the Document Responder for an ITI-68 transaction.

This example shows an made by the Patient Identifier Cross-reference Consumer for an ITI-83 transaction.

This example shows an made by the Patient Identifier Cross-reference Manager for an ITI-83 transaction.

This example shows an made by the Directory for an ITI-90 transaction that searched Practitioners.

This example shows an made by the Query Client for an ITI-90 transaction that read an Organization.

This example shows a Bundle of AuditEvents made by the Policy Source for a PPQ-4 transaction.

Example DocumentReference for a MedicationCard

MHD Find DocumentReferences - Bundle as Response

Error OperationOutcome that the updated DocumentReference has not same values for the identifiers

Error OperationOutcome that the updated DocumentReference references not the same patient

Error OperationOutcome that the updated DocumentReference changed unmodifiable metadata

MHD Provide Document Bundle Response for MedicationCard

MHD Provide Document Bundle for MedicationCard

Example SubmissionSet for a MedicationCard

CH PDQm Match response message example result for Franz Muster, 27.1.1955

CH PDQm Match response message with too many results indication

An example on the OperationOutcome for indicating which additional attributes are requested to lower the results number.

Example Patient

Example Organization

Example Input Parameters Mobile Patient Identifier Cross-reference Query

Example Output Parameters Mobile Patient Identifier Cross-reference Query

Example PIXm Patient for Feed

CH:PPQm Consent for template 201 – Full access for the patient

CH:PPQm Consent for template 202 – Read access in emergency mode

CH:PPQm Consent for template 203 – Default provide level

CH:PPQm Consent for template 301 – Read access for a healthcare professional, without delegation

CH:PPQm Consent for template 302 – Read access for a group of healthcare professionals

CH:PPQm Consent for template 303 – Full access for a representative

CH:PPQm Consent for template 304 – Read access for a healthcare professional, with delegation

CH:PPQm Feed Request Bundle for HTTP method DELETE – delete policy sets

CH:PPQm Feed Request Bundle for HTTP method POST – add new policy sets

CH:PPQm Feed Request Bundle for HTTP method PUT – conditionally update policy sets

CH:PPQm Feed Response Bundle

CH:PPQm Retrieve Response Bundle

An example of ITI-90 response Bundle in the profile CH mCSD

An example of CHmCSDOrganization that contains the same information as Community A in the Swiss examples (uid=CommunityA,OU=CHCommunity,DC=CPI,O=BAG,C=ch)

An example of CHmCSDOrganization that contains the same information as Praxis P in the Swiss examples (uid=CommunityA:00000001001,OU=HCRegulatedOrganization,DC=HPD,O=BAG,C=ch)

An example of CHmCSDOrganization that contains the same information as Spital X in the Swiss examples (uid=CommunityA:00000001000,OU=HCRegulatedOrganization,DC=HPD,O=BAG,C=ch)

An example of CHmCSDOrganization that contains the same information as Spital X, Dept. 3 in the Swiss examples (uid=CommunityA:00000001004,OU=HCRegulatedOrganization,DC=HPD,O=BAG,C=ch)

An example of CHmCSDPractitioner that contains the same information as Dr. Peter Pan in the Swiss examples (uid=CommunityA:00000003002,OU=HCProfessional,DC=HPD,O=BAG,C=ch)

An example of CHmCSDPractitionerRole that contains the same information as Dr. Peter Pan - Praxis P Relationship in the Swiss examples (CN=CommunityA:00000001001,OU=Relationship,DC=HPD,O=BAG,C=ch)

An example of CHmCSDPractitionerRole that contains the same information as Dr. Peter Pan - Spital X, Dept. 3 Relationship in the Swiss examples (CN=CommunityA:00000001004,OU=Relationship,DC=HPD,O=BAG,C=ch)

Resource Organization SpitalX

Resource Practitioner DrAndrews

Resource Practitioner DrMeier

Resource Practitioner DrReynolds

Resource PractitionerRole AnnAndrewsSpitalXOsteopathie

Resource PractitionerRole HansMeierSpitalX

Resource PractitionerRole RichardReynoldsSpitalX

Resource Organization SpitalX-Osteopathie

Resource Organization Auryn-Spital

Resource Organization Fuchur-Klinik

Resource Practitioner DrBux

Resource Practitioner DrGmork

Resource Practitioner DrKoreander

Resource PractitionerRole BastianBuxAuryn-Spital

Resource PractitionerRole GisiGmorkFurchur-Klinik

Resource PractitionerRole KarlKoreanderFuchur-Klinik