BC Client Registry FHIR Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Transition from V3 Provider to FHIR

Transition from V3 to FHIR

In the future stakeholders can transition from V3 to FHIR. The older specification will be supported but not extended with new features. FHIR interactions have several advantages:

• FHIR will allow users to receive and send more information than is currently within the V3 specification. Attributes such as Address Validation Status and comprehensive business dates on all Patient attributes will be available in FHIR, but not in V3.
• FHIR uses JSON which makes new implementations simpler than V3
• FHIR is being adopted throughout the health care landscape and switching to FHIR may help interoperability with other health organizations and systems

FHIR Development

This guide is a primary source of information and describes the specification in detail. Developers and the whole technical team should have access to this guide.

There are a variety of approaches one can take to develop FHIR capabilities. FHIR servers can be rented via Cloud providers (Azure has one here) or build one from scratch using libraries such as HAPI which is a Java library. One could also develop a custom implementation that integrates with an existing webservice and system.

The Client Registry team will have test Client Registry FHIR servers available to test interactions and operation validity.

Partial Implementations

As the V3 services will remain you may choose to develop some interactions with FHIR and still use other Client Registry services with V3. This allows you to avoid a complete switch-over to FHIR all at once and instead roll out your new FHIR services as required or over a longer period.

Business Rules

The FHIR interface is subject to the same rules as V3. Some examples regarding patient data:

No Browsing - Users must be providing health services or facilitating care related to the patient prior to searching for the patient in a provincial clinical repository (e.g., PharmaNet, PLIS).

No Modifications of HIE Data - Data received from a Ministry HIE service cannot be modified.

Use or Disclosure of Patient Data - Patient data received from a Ministry HIE service must not be used or disclosed for any purpose other than:

• providing care to the individual whose information is being accessed; or
• providing a patient with a copy of their own profile.

Temporary Copies of Patient Data - Temporary copies (e.g., paper forms) of patient data received from a Ministry HIE service must be securely disposed when no longer required for its intended use.

Reporting Incidents of Inappropriate Access, Use or Disclosure - Personnel (employees and contractors) must be made aware of procedures for responding to suspected and actual privacy and security incidents and breaches, including “whistle-blower” protection measures.

See British Columbia’s Health Information Exchange for details on the Client Registry system and access to Client Registry.