The use cases outlined below are intended to provide context and frame which the standard must meet.
The use cases identify different activities related to a provider registry:
|
|
Data received from source systems 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:
Information updates in the registry then trigger notifications to distribute updated provider information to client systems UC-4.
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 consumer systems UC-4.
Two provider records are combined in the registry.
Information updates in the registry then trigger notifications to distribute updated provider information to consumer systems UC-4.
Events in the PR trigger notification messages which are distributed to subscribing applications.
A consumer system sends a query to the provider registry:
If the request is authorized, the PR responds with the requested information.
A source system requests a history of provider record changes by date range or other criteria.
If the request is authorized, the PR responds with the requested information.