Provider Registry Use Cases: Difference between revisions
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
{{:Use Case:PR-UI-3}} | {{:Use Case:PR-UI-3}} | ||
{{:Use Case:PR-UI-4}} | {{:Use Case:PR-UI-4}} | ||
==Point-of-Care Interface== | ==Point-of-Care Interface== | ||
{{:Use Case:PR-POC-1}} | {{:Use Case:PR-POC-1}} | ||
{{:Use Case:PR-POC-2}} | {{:Use Case:PR-POC-2}} |
Revision as of 09:49, 10 May 2012
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 |
|
Extensions |
|
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 |
|
Extensions |
|
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 |
|
Notes | Data fields should include these provider attributes |
Use Case: PR-UI-2 Editing a health care professional
Edit an existing health care provider to the registry
Primary Actor | Provider Registry Administrator |
Pre-Conditions | The user must be authenticated to the system. The user has searched for and found the health care professional to be edited |
Success Guarantee | A provider is successfully is edited in the system. |
Main Success Scenario |
|
Notes | Data fields should include these provider attributes |
Use Case: PR-UI-3 Searching for a health care professional
Search for 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 found in the system. |
Main Success Scenario |
|
Use Case: PR-UI-4 Deactivate a health care professional
Deactivate a health care provider from the registry
Primary Actor | Provider Registry Administrator |
Pre-Conditions | The user must be authenticated to the system, the appropriate record has been located |
Success Guarantee | A provider is successfully is added to the system and made available to be searched |
Main Success Scenario |
|