Use Cases

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:

UC-1 Maintain provider information

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:

• 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 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 consumer systems UC-4.

UC-3 Merge provider records

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.

UC-4 Notify consumer of information updates (passive)

Events in the PR trigger notification messages which are distributed to subscribing applications.

• Add provider
• Update provider
• Merge provider
• Nullify license

UC-5 Consumer search for provider information (active)

A consumer system sends a query to the provider registry:

• Get provider details using HSPID
• Get provider details using License and Role
• Identify provider using License when HSPID role isn't known
• Find candidate providers matching a set of search criteria

If the request is authorized, the PR responds with the requested information.

UC-6 Request transaction history

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.