visit the hl7 website
Provincial Client Registry (PCR) HL7 FHIR® Contribution Implementation Guide v1.0.0-draft1
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
    • Business Rules
    • Contribution Models
  • Technical Context
    • Technical Context
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Interactions
    • Operations
    • Profiles
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. FHIR Artifacts
    3. Capability Statement

For a full list of available versions, see the Directory of published versions

4.7. Capability Statement

The PCR FHIR Capability Statement describes the expected FHIR capabilities that support PCR data contribution. It identifies the contribution operations, resource profiles, interaction patterns, security expectations, and response behaviours that client systems and PCR services must support to exchange contribution transactions consistently.

For PCR contribution, the Capability Statement must be interpreted together with the FHIR profiles, operation definitions, conformance rules, connectivity requirements, privacy and security obligations, and onboarding guidance referenced in this implementation guide. The Capability Statement does not replace the detailed profile constraints or business validation rules; rather, it provides a system-level summary of the FHIR capabilities required to submit and process contribution transactions.

4.7.1. Purpose of the Capability Statement

The Capability Statement supports implementation planning, conformance assessment, and integration readiness by documenting the FHIR contribution behaviours expected from both PCR and contributing client systems. It helps implementers understand which operations are available, which resources and profiles must be supported, what security model applies, and what response patterns should be expected.

Service Description Download Link
OntarioPCRContributionCapabilityStatement Defines the capabilities of a contributor to the PCR Download

4.7.2. Supported Contribution Capabilities

Capability Area Expected Support Contribution Relevance
Patient Add Client systems submit a conformant FHIR request to create a new client record when PCR business rules allow creation. Supports initial contribution of demographic and identifier information.
Patient Update Client systems submit revised demographic or identifier information for an existing PCR client record. Supports ongoing maintenance of accurate client identity data.
Patient Merge Client systems submit a contribution request to consolidate duplicate client records according to PCR merge rules. Supports identity resolution and duplicate record management.
Patient Unmerge Client systems submit a contribution request to reverse a prior merge where records were incorrectly consolidated. Supports correction of identity linkage issues.

4.7.3. Client and Server Capability Expectations

  • Contributing client systems shall generate requests that conform to PCR FHIR profiles, required identifiers, cardinality rules, and operation-specific business rules.
  • PCR services shall validate submitted contribution requests and return appropriate response status, identifiers, and OperationOutcome details where applicable.
  • Both client and server systems shall use supported content types, UTF-8 encoding, approved security controls, and agreed connectivity patterns.
  • Client systems shall process responses meaningfully, including successful acknowledgements, validation errors, rejected requests, and accepted-for-processing outcomes.

4.7.4. Capability Statement Implementation Notes

Implementers should treat the Capability Statement as a summary of supported capabilities rather than a complete substitute for this implementation guide. Where a formal FHIR CapabilityStatement resource or related implementation artifact is published, it should be interpreted together with the PCR contribution profiles, operation definitions, business rules, and Ontario Health onboarding direction. Where there is any discrepancy, the detailed implementation guide content and Ontario Health onboarding direction should be followed.

Version: 1.0.0 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

HL7® and FHIR® are the registered trademarks of Health Level Seven International