B.C.-specific interoperability

Built for B.C.'s health-information architecture

The Hub's program directory and live-capacity records are exposed as FHIR R4 Location and HealthcareService resources. This makes a future provincial or EMR connection an adapter over the same model, not a second directory to rebuild and reconcile.

Directory place

Location

Every program has a Location resource declaring the Canadian Baseline Location profile mirrored by B.C. Core.

View Location bundle →
Program and access

HealthcareService

Service type, coverage area and current capacity travel together in a read-only R4 HealthcareService representation.

View service bundle →
Declared capability

CapabilityStatement

The live metadata endpoint declares the supported resources, searches, profile alignment and read-only boundary.

Open metadata →
Integration contract

Patient data stays out of this public directory

The Hub does not store or expose Patient or Encounter resources. Future authorized clinical hand-offs must use the B.C.-mirrored Canadian Baseline profiles below and add use-case-specific privacy, identity, consent and security controls.

Patient
http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-patient
Encounter
http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-encounter
Location
http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-location
Precise claim, not generic “FHIR-ready” language

B.C. states that its Core profiles mirror the Canadian Baseline and are a starting point for project-specific profiles. The Canadian artifact list does not currently publish a HealthcareService profile, so the Hub uses the base R4 resource and a documented Hub extension for current capacity. This implementation is aligned and inspectable; it is not represented as Ministry certification.

Read B.C. Core FHIR guidance ↗