Ontario Subscription HL7® FHIR® Implementation Guide -v1.0.0-ballot1
For a full list of available versions, see the Directory of published versions
This Subscription FHIR specification defines the FHIR profiles and extensions that are used in the Publish/Subscribe project. All FHIR-based specifications rely on an underlying set of base “resources”.
FHIR version-specific MIME types (e.g., application/fhir+json; fhirVersion=4.0.1) are not prohibited, but their use is not required by this Implementation Guide.
The Implementation Guide assumes that both the Subscription Server and Subscriber conform to the same FHIR version (i.e., the version defined by this IG). Therefore, version negotiation through MIME types is not expected or supported as part of the normal exchange workflow.
The formal MIME types for FHIR resources are application/fhir+json and application/fhir+xml. The correct MIME type SHALL be used by clients and servers:
application/fhir+jsonapplication/fhir+xmlFHIR® uses UTF-8 for all request and response bodies. Since the HTTP specification defines a default character encoding of ISO-8859-1, requests and responses SHALL explicitly set the character encoding to UTF-8 using the charset parameter of the MIME-type in the Content-Type header. Requests MAY also specify this charset parameter in the Accept header and/or use the Accept-Charset header.
Accept-Language field in HTTP header will be used to set the language of the search in the future releases. The allowed values are en-CA and fr-CA. If this field is not set by the requestor, the default is en-CA. In the current release, only en-CA is supported.