Skip to main content
Previous section

Compliance with FHIR IHE Profile Specifications

Health Connect adheres to the PIXm, PDQm, and MHD FHIR profile specifications in most respects. Differences are noted below.

Differences from PIXm Specification

Comments below apply to both DSTU2 and STU3.

Section 41.6.1: Proxy Model, Section 41.6.2 Manager group

PIXm server-side support is a proxy, not a pure FHIR model. This means that the PIXm Manager business process does not interact with FHIR resource repositories.

The PIXm Manager can be a proxy to PIX, PIXv3 or PIXm client business operations by setting MPIOperations to point to any of those operations.

Section 3.83.4.2.2.2: Message Semantics

PIXm responses return only targetIdentifier elements, not targetId elements.

Section 3.83.5: Security Considerations

The PIXm implementation does not log ATNA audit messages.

Differences from PDQm Specification

DSTU2

Section 38.2.1 Pediatric Option

This option is supported with the exceptions below:

  • Multiple Birth Indicator and Patient Birth Order cannot both appear in a given patient record.

  • The Mother's Maiden Name extension is not supported.

  • Last Update Date/Time and Last Update Facility are not supported.

Section 3.78.5 Security Considerations

The DSTU2 PDQm implementation does not log ATNA audit messages.

STU3

Section 38.2.1 Pediatric Option

This option is supported with the exceptions below:

  • Multiple Birth Indicator and Patient Birth Order cannot both appear in a given patient record.

  • Last Update Date/Time and Last Update Facility are not supported.

3.78.4.1.2.1 Query Search Parameters

In SDA3, there is no structure analogous to the FHIR STU3 Patient resource active parameter. Therefore the following provision is made:

Section 3.78.5 Security Considerations

The STU3 PDQm implementation does not log ATNA audit messages.

Differences from MHD Specification

DSTU2

3.65.4.1.3 Expected Actions (paragraph 600), 5.4.1.3 Folder Metadata Attributes

The List resource for XDSb Folders in DSTU2 is not supported.

33.2.2 XDS on FHIR Option, 33.6.1 MHD Actor Grouped with XDS Infrastructure

This option is supported. However, this is the only mode in which MHD is supported. The other mode would be as a pure FHIR implementation, which is unverified and untested.

33.6.2 MHD Actors Grouped with XCA Infrastructure

MHD support in conjunction with XCA has not been tested.

33.6.3 MHD Actor grouped with Retrieve Information for Display (RID) Profile

MHD support in conjunction with RID has not been tested.

3.66.4.1.2.1 Query Search Parameters (Find Document Manifests)

The patient search parameter for find document manifests is not supported.

3.67.4.1.2.1 Query Search Parameters (Find Document References)

The patient search and period search parameters for find document references are not supported.

STU3

33.2.2 XDS on FHIR Option, 33.6.1 MHD Actor Grouped with XDS Infrastructure

This option is supported. However, this is the only mode in which MHD is supported. The other mode would be as a pure FHIR implementation, which is unverified and untested.

33.6.2 MHD Actors Grouped with XCA Infrastructure

MHD support in conjunction with XCA has not been tested.

33.6.3 MHD Actor grouped with Retrieve Information for Display (RID) Profile

MHD support in conjunction with RID has not been tested.

3.66.4.1.2.1 Query Search Parameters (Find Document Manifests)

The patient search parameter for find document manifests is not supported.

3.67.4.1.2.1 Query Search Parameters (Find Document References)

The patient search and period search parameters for find document references are not supported.