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. Contribution Models

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

2.5. Contribution Models

2.5.1. Overview

PCR supports multiple source models to accommodate the different ways organizations manage patient identifiers and medical records. The source model determines how identifiers are submitted and interpreted during patient contribution processing.

2.5.2. Standard Model

Organizations that use a single Medical Record Number (MRN) namespace across their operations SHALL contribute records using the Standard Model.

Business Rules:

  • MRN SHALL be submitted as the organization's Definitional Source Identifier.
  • MRN SHALL also be retained as an Informational Identifier.
  • Each MRN SHALL uniquely identify a patient record within the contributing organization.

2.5.3. Corporate ID Model

Organizations that manage patients across multiple facilities using a shared Corporate Identifier (CORPID) SHALL contribute records using the Corporate ID Model. Business Rules:

  • CORPID SHALL be submitted as the organization's Definitional Source Identifier.
  • Associated facility-specific MRNs SHALL be submitted as Informational Identifiers.
  • The same patient MAY have multiple MRNs associated with a single CORPID.

PCR_Contribution_Models

2.5.4. Identifier Management

Identifiers are used by PCR to uniquely identify patient records and support patient identity resolution.

2.5.4.1. Definitional Source Identifier

A contributed patient record SHALL contain a Definitional Source Identifier.

The Definitional Source Identifier SHALL be one of the following:

Source Model Definitional Identifier
Standard Model Medical Record Number (MRN)
Corporate ID Model Corporate Identifier (CORPID)
MOH RPDB Ontario Health Card Number (HCN)

The Definitional Identifier SHALL uniquely identify the source record within the contributing organization.

2.5.4.2. Informational Source Identifier

PCR supports one or more Informational Identifiers associated with a patient record. Informational Identifiers may include:

  • Medical Record Number (MRN)
  • Ontario Health Card Number (HCN)
  • Other approved patient identifiers These identifiers support patient discovery, linkage, and reconciliation activities.

2.5.5. Enterprise Client Identifier (ECID)

PCR assigns or maintains a Provincial Enterprise Client Identifier (ECID) for each patient entity. The ECID represents the provincial identity associated with all linked source records for the patient.

2.5.6. Patient Matching

PCR uses deterministic and probabilistic matching methods to determine whether contributed records belong to an existing patient entity.

2.5.6.1. Deterministic Matching

PCR performs exact-match evaluation on selected attributes that are expected to remain consistent across patient records. Deterministic matching evaluates:

  • Health Card Number (HCN)
  • Administrative Sex (Gender) Matching scores will be derived based on the presence and exact agreement of values between records.

2.5.6.2. Probabilistic Matching

PCR performs probabilistic evaluation on demographic attributes including:

  • Legal Name
  • Alias Name
  • Date of Birth
  • Address
  • Telephone Number Probabilistic matching calculates match confidence based on similarity between values and established matching thresholds.

2.5.7. Data Normalization

PCR normalizes data prior to matching. Normalization may include:

  • Removal of formatting characters
  • Standardization of address and telephone formats
  • Normalization of name values
  • Character cleaning and transformation Normalized values will be used during matching evaluation.

2.5.7.1. Historical Data

PCR considers historical demographic information when evaluating patient matches. Historical information may include:

  • Previous names
  • Previous addresses
  • Previous telephone numbers Historical values may contribute to patient matching and identity resolution.

2.5.7.2. Anonymous and Placeholder Values

PCR prevents anonymous, dummy, or placeholder values from influencing matching outcomes. Examples include:

  • John Doe
  • Baby Boy
  • Baby Girl
  • Invalid dates of birth
  • Placeholder Health Card Numbers Such values will not contribute positively to patient matching decisions.

2.5.7.3. False Positive Prevention

PCR applies safeguards intended to prevent inappropriate linkages between different individuals where demographic similarities could otherwise produce incorrect matches.

2.5.7.4. Trusted Source Processing

PCR recognizes the Ministry of Health RPDB source as an authoritative source during patient identity evaluation and record linkage activities.

2.5.8. Record Linkage

PCR determines whether contributed records should be linked to existing patient entities based on calculated matching scores.

2.5.8.1. No Linkage

A record will remain separate when the calculated linkage score falls below the configured linkage threshold. In this scenario:

  • No patient linkage occurs.
  • The record remains associated with its existing entity.
  • A new entity may be maintained where appropriate.

2.5.8.2. Potential Linkage

Where the matching score falls within the clerical review threshold range:

  • PCR creates a Potential Linkage task.
  • The source record will* remain unchanged pending review.
  • Manual resolution will determine whether linkage will occur.

2.5.8.3. Automatic Linkage

Where the matching score exceeds the automatic linkage threshold:

  • PCR automatically links the source record to the identified patient entity.
  • The record will inherit the associated ECID.
  • The patient entity will be updated accordingly.
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