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 the PRprovider information
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.
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 registry then trigger notifications to distribute updated provider information to client systems UC-4.
UC-2 Logically
Delete Provider in the PRdelete provider record
Identify and logically delete a provider added to the registry in error.
Information updates in the registry then trigger notifications to distribute updated provider information to client consumer systems UC-4.
UC-3 Merge
Providers in PRprovider records
Two provider records are combined in the registry.
Information updates in the registry then trigger notifications to distribute updated provider information to client consumer systems UC-4.
UC-4 Notify consumer
systemsof
PR changes.provider updates
Changes to data in the PR trigger notification messages which are distributed to subscribing applications via the provincial health information exchange.
UC-5
Search and Retrieve Provider Information from the PRConsumer search for provider information
A consumer system sends a query to the provider registry system to retrieverequesting:
- 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 request is authorized, the PR sends responds with the requested data to the consumer systeminformation.
UC-6 Request
Transaction History from PRtransaction history
A source system requests
Allows source systems to request a history of provider record changes by date range or other criteria.
If the request is authorized, the PR responds with the requested information.