Information updates in the registry then trigger notifications to distribute updated provider information to client sytems UC-4.
The use cases outlined below are intended to provide additional context and frame the needs that the candidate standards must meet.
The use cases identify different activities related to a provider registry:
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
The PRS provides a number of business functions that require interaction with source or client systems:
UC-1 Maintain Provider Information in
PRSthe PR
Data received from source systems (such as information from the Alberta College of Physicians and Surgeons) is used to add or update provider information within the registry, including secondary identifiers and licensing information
Allows source systems to create and update provider information including maintenance of secondary identifiers. The capability to maintain provider information is dictated by user type and data permission profile.
Multiple business events relate to provider maintenance including:
- Addition of a new provider
- Update of provider demographic information
- Association of a license with a provider
- Nullification of a license with a provider
Information updates in the PRS registry then trigger notifications to distribute updated provider information to client sytems systems UC-4.
UC-2 Logically Delete Provider in
PRSthe PR
Identify and logically delete a provider added to the registry Allows source systems to identify provider information that was entered into the system in error.
Information updates in the PRS registry then trigger notifications to distribute updated provider information to client sytems systems UC-4.
UC-3 Merge Providers in
PRSPR
Two provider records are combined in the registryAllows source systems to identify provider information that was entered into the system in error.
Information updates in the
PRSregistry then trigger notifications to distribute updated provider information to client
sytemssystems UC-4.
UC-4
Distribute Provider Updates from PRSNotify consumer systems of PR changes.
Changes to data in the PR trigger notification messages which are distributed to subscribing applications via the provincial health information exchange.
Sources and consumers may receive distributions of changes to provider data.
Distributions are created and delivered according to the recipient’s data permissions and distribution profile. Distributions may be direct or queued.
UC-5 Search
Provider Information in PRSAllows sources and consumers to search providers based on a range of selection criteria. Results may be returned in either summary or detail formatand Retrieve Provider Information from the PR
A consumer system sends a query to the provider registry system to retrieve:
- Full details for a specific provider using HSPID
- Full details for a specific provider using License and Role
- Provider information using License when HSPID role isn't known
- List of providers matching a set of search criteria.
If the consumer is authorized, the PR sends the requested data to the consumer system.
UC-6 Request Transaction History from
PRSPR
Allows sources and consumers source systems to request a history of provider changes , selectable by date range and many or other criteria.