Provincial Provider Registry
What is it?
This registry contains authoritative information about regulated health professionals and organizations in Ontario that fall within the definition of health information custodian (HIC) or are operators of a HIC pursuant to the Personal Health Information Protection Act (PHIPA). The registry is fed by regulatory colleges and the Ministry of Health and Long-Term Care’s corporate provider database. It is managed by eHealth Ontario.
The registry enhances patient care delivery by:
- Improving the accuracy of provider information including location, contact information, affiliations, and licensing status
- Reducing manual efforts related to maintaining accurate provider information within local health care solutions
Based on Ontario’s eHealth Blueprint, the PPR is a registry that contains authoritative information about health care Providers in Ontario that fall within the definition of Health Information Custodian (HIC) or agent of a HIC pursuant to the Personal Health Information and Protection of Privacy Act (PHIPA).
The target vision of the PPR is to:
1. Provide the ability to create a single unique identifier for all health care Providers in Ontario.
2. Provide the ability to link multiple Provider identifiers/sites information to a single Provider identity across multiple data sources.
3. Provide the ability for an authoritative source to add Provider data to the registry in real time.
4. Provide the ability for an authoritative source to update/provide credentials, demographics, and practice information in real time.
5. Provide the ability for health care Providers to maintain their own demographic and contact information.
6. Provide the ability to verify data integrity and quality through reporting and verification scripts.
7. Support eHealth Ontario interface specifications for access to Providers information.
8. Provide the ability to notify interested consumers when Providers’ particulars (identifiers/ status/ information) are updated or changed.
9. Enable search/link of provider individual in the registry by name (including aliases, near matches and nicknames), profession, specialty/sub-specialty, alternate identifiers, location, unique identifier, etc., and return accurate, up-to-date provider individual profile information generated from information across multiple sources.
10. Enable search/link of provider organizations in the registry by name (including aliases, near matches and nicknames), role (e.g. pharmacy, hospital, clinic etc.), LHIN, alternate identifiers, unique identifier, etc. and return accurate, up-to-date provider organization profile information across multiple sources.
11. Improve accuracy and currency of Provider information in the registry.
The PPR provides a key cornerstone service in the context of the Electronic Health Record (EHR) in Ontario.The PPR receives data/information from many sources; the Ministry of Health and Long Term Care (MOHLTC), Hospital Information Systems (HIS), Regulatory Colleges, and the Provider themselves.
The PPR Solution will support the following patterns for consuming the Provider information:
1. Real-time direct access:
a. Consumers with systems capable of interacting with the HIAL interfaces for Provider access will directly consume the Provider information through the HIAL PPR interfaces.
b. Provider individuals will access the information through a user interface that allows the individual to maintain their own information.
2. Batch Synchronization:
a. Consumers with systems that are unable to interact with the HIAL real-time interfaces (for example, a Hospital Information System) utilize a built-in local provider registry (e.g. a Provider directory) to manage Provider information relevant to their organization. These systems will have the ability to keep their Provider information synchronized with the PPR through a daily batch interface.
By providing the ability to link provider identities and identifiers to a single provider identity, the provider registry solution enables consent enforcement to ensure that patient’s consent directive against a provider person or organization is applied no matter which ID or organization a provider is accessing the information from. Without this relationship consent is applied on a provider at a one-off basis (e.g. the provider at a specific location). Managing and maintaining the current status of the provider, as provided by the Regulatory body or governing body for the profession, allows the ONE ID entitlement service to identify to the requested service whether the provider requesting access is in good standing (e.g. still an practicing Provider) to allow the service to determine if the requestor should have access to that service. The Provincial Provider Registry technology refresh, moves the Provider Registry solution from a Mainframe solution to an open system COTS implementation on IBM’s Master Data Management platform. This software, formerly known as Initiate, is the same platform, although a newer version, as the Provincial Client Registry. EMPI stands for Enterprise Master Person/Patient/Provider Index which is a concept of allowing linking of records from multiple sources for the same Entity (person/patient/provider/organization) together to show a single “enterprise” view of the entity.
Lite Service Tests
- PCR HL7 V3 end point: lite.innovation-lab.ca:7102
User of System requests the retrieval of provider summary information, using specific pre-defined combinations of provider person data items as query parameters.
This is a business transaction that is used by external systems to request and receive detail information from the Ontario Provincial Provider Registry (PPR), about a specific provider person (licensed or otherwise).
This is a business transaction that is used by external systems to request and receive summary information from the Ontario Provincial Provider Registry (PPR), about provider organizations.
The following table lists the interactions which support the Get Provider Organization Details business scenario. It lists the interaction and specifies the appropriate transmission wrapper, control event wrapper, and payload message type which, in combination, forms an entire interaction.
For the full details on these interactions, please refer to our full PPR Standards documentation.
- Improved accuracy of provider person information including location, contact information, affiliations, and licensing status.
- Reduce manual efforts related to maintaining provider information within local healthcare solutions.