Versions Compared

Old Version 5

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.

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
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 the PR

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.

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 PR

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

UC-3 Merge

Providers in PR

provider 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

systems of PR changes.

of information updates (passive)

Events Changes to data in the PR trigger notification messages which are distributed to subscribing applications via the provincial health information exchange..

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

UC-5

Search and Retrieve Provider Information from the PR

Consumer search for provider information (active)

A consumer system sends a query to the provider registry system to retrieve:

  • Full details for a specific provider Get provider details using HSPIDFull details for a specific
  • provider Get provider details using License and Role
  • Provider information Identify provider using License when HSPID role isn't known
  • List of Find candidate 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

A source system requests Transaction History from PRAllows 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.