Difference between Version 1.0.0 and 2.0.0

This page lists the differences for resource profile definitions between Version 1.0.0 and this Version 2.0.0 of the PCR FHIR implementation guide. The purpose is to help implementers who are supporting Version 1.0.0 understand the necessary changes required to migrate to Version 2.0.0. At this point, both versions will be supported by Ontario Health.

MustSupport:

This implementation guide introduces the "MustSupport" flag to identify elements that implementers must be aware of in order to query data from the PCR. Refer to the Implementation Guidelines for additional details on how to interpet the "MustSupport" flag.

MIME types:

MIME types used in the query parameter "_format" have changed in FHIR. The following values should now be used:

• JSON(preferred): application/fhir+json

• XML: application/fhir+xml

Refer to the Implementation Guidelines for additional details on supported Content Types and Encodings.

meta.profile value change in all resource profile definitions:

The resource.meta.profile will contain the new canonical URI for all PCR profiles. For example in pcr-patient-response, the meta.profile value will be http://ehealthontario.ca/fhir/StructureDefinition/ca-on-pcr-profile-Patient|2.0.0

Please refer to the table below for the new canonical URIs:

Bundle Response

Patient EMPI Match Request:

No change.

Patient EMPI Match Response:

12. The Patient EMPI Match response will use the patient profile instead of the patient match profile. As per business rules, the Patient EMPI Match response is a summary view of the patient profile. Therefore the patient response profile will be used with an additional Patient.meta.tag set to "SUBSETTED". Note that the following elements are not returned in a Patient EMPI Match response:

• Patient.deceased[x]
• Patient.multipleBirth[x]
• Patient.contact
• Patient.communication

The Patient.meta.tag will be populated as follows:

<meta>
    <tag>
        <system value="http://hl7.org/fhir/v3/ObservationValue" />
        <code value="SUBSETTED" />
        <display value="subsetted" />
    </tag>
</meta>

Patient Read Request:

No change.

Patient Read Response:

Patient Search Request:

Added support for the HTTP POST method (in addition to GET) on the Patient Search Operation. See Patient Search for details

Patient Search Response:

Same profile change as in the table above.

Cross-Identifier PIXm Request:

Added support for the HTTP POST method (in addition to GET) on the Cross-Identifier-PIXm Operation. See PIXm page for details.

Cross-Identifier PIXm Response:

No change.