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. Business Context
    3. Business Data

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

2.2. Business Data

2.2.1. Record Management Approach

PCR maintains client identity information received from multiple contributing organizations across Ontario's healthcare ecosystem. Each data contribution submitted to PCR represents a source-specific view of the client and is stored as an independent contributor record.

PCR uses identity resolution and matching processes to determine whether contributed records refer to an existing PCR client or represent a new individual. Records determined to belong to the same individual are associated with a single Enterprise Client Identifier (ECID), which serves as the unique provincial identifier within PCR.


2.2.2. Contributor Record Management

Contributing organizations remain the authoritative source for the identifiers and demographic information they submit to PCR. PCR preserves contributed information while maintaining the relationship between the contributor record and the associated PCR client record.

When a contributor submits a demographic update, the revised information may alter the identity resolution outcome. As a result, PCR may:

  • Maintain the existing ECID association.
  • Associate the contributor record with a different existing ECID.
  • Create a new ECID.
  • Trigger merge or unmerge processing activities.

Examples of demographic changes that may affect identity resolution include:

  • Addition or correction of an Ontario Health Card Number (HCN).
  • Changes to legal or alias names.
  • Date of birth corrections.
  • Address updates.
  • Merge and unmerge events initiated by contributing systems.

2.2.3. Identity Resolution

PCR evaluates demographic and identifier information received through FHIR contribution transactions using established matching algorithms and business rules.

The matching process determines whether a contribution represents:

  • A new PCR client.
  • An update to an existing PCR client.
  • A duplicate client requiring merge processing.
  • A previously merged client requiring unmerge processing.

The resulting ECID assignment reflects PCR's current identity resolution outcome for the contributed record.

2.2.4. PCR Client View

PCR maintains an integrated client view derived from contributor records associated with the same ECID. This allows PCR to support provincial identity management while preserving source-specific demographic history and identifiers.

PCR-Golden

The integrated client view is dynamically maintained as new contribution transactions are processed.

2.2.4.1. Example Record Lifecycle

The following scenario illustrates how PCR processes contributed demographic information over time.

Source Event Description
Source A A client record is initially contributed from a provincial source containing a valid Ontario Health Card Number and demographic information. PCR creates a new client and assigns an ECID.
Source B A hospital contributes a record containing updated address information and a preferred name. PCR determines the record belongs to the same client and associates it with the existing ECID.
Source C Another contributing organization submits additional demographic information, including a changed legal name. PCR identifies the record as representing the same individual and maintains the ECID association.
Ongoing Maintenance Subsequent demographic updates continue to refine the client identity record while preserving contributor-specific data.

2.2.5. Patient Data

PCR supports the collection and maintenance of client identifiers and demographic information contributed through FHIR transactions.

The information submitted and maintained within PCR supports:

  • Identity resolution
  • Duplicate detection
  • Demographic maintenance
  • Merge processing
  • Unmerge processing
  • Provincial client identity management

2.2.5.1. General Data Contribution Considerations

  • Multiple identifiers of the same type may be associated with a patient.
  • Identifiers may be active or inactive.
  • Not all attributes are mandatory for every contribution transaction.
  • Some demographic attributes may be unavailable depending on source system capabilities.
  • Source systems remain responsible for the quality and accuracy of contributed information.
  • The availability of attributes depends on the contributing organization and the business operation being performed.
  • PCR uses identifiers and demographic attributes collectively to support identity resolution and client record management.
  • Patient information is represented using the PCR FHIR Patient profile and associated extensions defined within this implementation guide.

2.2.6. Patient Data Attributes

The following identifiers and demographic attributes may be contributed to PCR.

2.2.6.1. Patient Identifiers

2.2.6.1.1. PCR Enterprise Client Identifier (ECID)

A PCR-assigned identifier that uniquely identifies a client within the Provincial Client Registry. The ECID is created and managed exclusively by PCR and is used to associate contributor records belonging to the same individual.

2.2.6.1.2. Ontario Health Card Number (HCN)

The provincial identifier assigned to eligible Ontario residents under the Ontario Health Insurance Plan (OHIP).

2.2.6.1.3. Out-of-Province Health Numbers

Health insurance identifiers issued by Canadian provinces and territories outside Ontario.

2.2.6.1.4. Corporate Identifier (CORPID)

An enterprise-level identifier used within an organization to uniquely identify a client across multiple facilities, sites, or identifier domains.

2.2.6.1.5. Medical Record Number (MRN)

An identifier assigned within a healthcare organization to uniquely identify a patient record.

2.2.6.1.6. Alternate Identifier (ALTID)

Any additional business identifier used by a contributing organization.

Examples include:

  • Driver's Licence Number
  • Passport Number
  • Client GUID
  • Local Application Identifier

2.2.6.2. Demographic Information

2.2.6.2.1. Names
2.2.6.2.1.1. Official

The formal name as registered in an official government registry and commonly referred to as the legal name.

2.2.6.2.1.2. Temp

A temporary name assigned at birth or in emergency situations.

2.2.6.2.1.3. Nickname

A name used to address the person in an informal manner.

2.2.6.2.1.4. Anonymous

An assigned name, alias, or pseudonym used to protect a person's identity.

2.2.6.2.1.5. Old

A historical name that is no longer used but is retained for record purposes.

2.2.6.2.1.6. Maiden

A name used before a name change associated with marriage.

2.2.6.2.2. Birth Information
  • Date of Birth

2.2.6.2.3. Administrative Sex

Administrative gender used for patient identification and registration purposes.

2.2.6.2.4. Addresses
2.2.6.2.4.1. Home

A residential communication address, including mailing and physical addresses.

2.2.6.2.4.2. Work

An office or business communication address.

2.2.6.2.4.3. Temporary

A temporary communication address used for a limited period.

2.2.6.2.5. Contact Information
  • Phone (home | work | mobile)
  • Fax (home | work)
  • Email (home | work)

2.2.6.2.6. Emergency Contact Information
  • Phone (home | work | mobile)

2.2.6.2.7. Communication Preferences
  • Communication Language

2.2.6.2.8. Vital Status
  • Deceased Indicator
  • Date of Death

2.2.7. FHIR Representation

Within the PCR FHIR Data Contribution API, these identifiers and demographic attributes are represented using the Patient resource and associated PCR-specific profiles and extensions defined within this implementation guide.

Contributing systems shall populate required identifiers and demographic attributes in accordance with profile requirements, cardinality constraints, terminology bindings, and business validation rules specified throughout this implementation guide.

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