Patient pull of information

Title:

Use Case Description: [Use an action verb name to describe the use case, not including the primary actor name, but identifying any subject actors. Verb modifiers may be used to refine the use case. Examples: authenticate to system with trusted identity, authenticate to system with pseudonymous identity, match names between systems, verify attributes with privacy protection]

Use Case Category:

Contributor:

[edit]

Use Case Details

A patient can direct a third party electronic health record (EHR) application to aperiodically have access to his/her personal health information via the internet. The electronic health data holder will ensure this data is made available and follow certain interoperability, security, and privacy (HIPAAHIPPA) standards Both the patient EHR and data holder application will accept interoperable, high assurance patient credentials, avoiding duplicative and burdensome new account creation by the patient and providers. Supplement (not replace) existing Direct transport protocols with authentication, RESTful transport, and content standards that provide for non-repudiation (e.g. OpenID, Oauth). Actors:

Goals:

Incorporate NSTIC principles into Health care interactions

Assumptions:

Relationships between patient, data holder and EHR have already been established

Requirements:

Authentication and authorization events

Process Flow:

Success Scenario:

Error Conditions:

[edit] Relationships Extended by: Extension of: [edit] References and Citations