Provider Registry Use Cases

Use Cases for Provider Registry

These are use cases for interacting with the provider registry. Please see the requirements

Interoperability Layer/Web Services

Use Case: PR-WS-1 Query from a provider’s enterprise ID

---

This query takes in a unique ID for a provider and returns the enterprise ID associated with the provider who matches the given ID.

Primary Actor	Interoperability Layer, potentially Point Of Care Application
Pre-Conditions	The application must be authenticated to the system
Success Guarantee	An enterprise id (EID) is returned to the requesting application
Main Success Scenario	The actor submits a request with a given ID type and ID number The system returns the EID
Extensions	2.a The system does not find the provider and returns an error code.

Other Resources: Web Service:PR-WS-1

Use Case: PR-WS-2 Query for providers

---

ueries for HC Professional’s using a variety of possible parameter. This transaction returns a list of all professionals that match the criteria specified in the query parameters. Otherwise, if an error occurred, then an error is returned.

Primary Actor	Interoperability Layer, Point Of Care Application?
Pre-Conditions	The application must be authenticated to the system
Success Guarantee	An list of enterprise ids (EIDs) is returned to the requesting application
Main Success Scenario	The actor submits a request with a given query parameters The system returns a list of matching EIDs
Extensions	2.a The system does not find the provider and returns an error code. 2.b The requested search parameters are invalid and returns an error code.
Notes	Not needed for Sept. 2012

Other Resources: Web Service:PR-WS-2 Use Case:PR-WS-3

User Interface

Use Case: PR-UI-1 Inserting a health care professional

---

Add a health care provider to the registry

Primary Actor	Provider Registry Administrator
Pre-Conditions	The user must be authenticated to the system
Success Guarantee	A provider is successfully is added to the system and made available to be searched
Main Success Scenario	The administrator enters the new health care professional data The system verifies if the data has been entered properly and performs necessary validations The system creates a unique EPID (enterprise provider ID) for the provider The system stores the health care professional data. The system returns to the previous screen
Notes	Data fields should include these provider attributes