Versions Compared

Old Version 4

changes.mady.by.user Russ Buchanan

Saved on

compared with

New Version Current

changes.mady.by.user Russ Buchanan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
titleTable of Contents

Table of Contents
indent20px
stylecircle

Tip
titleSource Systems

Sources systems, such as the Alberta College of Physicians and Surgeons, provide information to the registry.

Tip
titleConsumer Systems

Consumer systems, such as electronic medical records systems used at the point of care, receive and consume information from the registry, either as notifications or in response to a query.

The PRS provides a number of business functions that require interaction with source or client systems:

UC-1 Maintain

Provider Information in PRS

provider 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

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 PRS

delete provider record

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

UC-3 Merge

Providers in PRS

provider records

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

PRS

registry then trigger notifications to distribute updated provider information to

client sytems

consumer systems UC-4.

UC-4

Distribute Provider Updates from PRS

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 PRS

Allows sources and consumers to search providers based on a range of selection criteria. Results may be returned in either summary or detail format.

UC-6 Request Transaction History from PRS

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 informationAllows sources and consumers to request a history of provider changes, selectable by date range and many other criteria.