Emergency Contact Information Use Case

Full Title of Use Case

Any person that wants First Responders to be able to contact specific people in case of emergency.

Context

To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.

Goal

• The patient has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.
• Extendibility to provide accessibility to patient care stipulations that would help First Responders provide care.
• Provide the privacy and other considerations as described in the Health Care Profile.

1. Give the contact person ability to impact the record about their own data and availability as a contact.
2. Consent experience for patient

Actors

1. Patient
2. Provider of specialized services related to emergency contact and other information.

Preconditions

1. The patient is "known to the practice" where general health care is provided.
2. A trust registry exists which the patient knows and trusts.
3. The providers of health care and lab services present the patient with a trusted identity which confirms that they subscribe to the privacy regulations of the trust provider.
4. Different providers are unlikely to allow each other, or the patient, to write into their EHR, so it is expected that the patient will have multiple repositories, each with their own Medical Records Identifier.
5. Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent
6. The patient has the right to eliminate some individuals in a practice from seeing their data even when the practice has access.

An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.

Scenarios / User Journeys

The goal of this scenario is to test the functionality of the web site that the user access their information.

Journey 1 - the user's comes to the site to learn what emergency access really is:

1. Patient schedules an appointment with primary care physician and is authenticated at the front desk. (This might involve re-affirmation of the consent with the practice.)
2. Patient sees the doctor, is reauthenticated (this reauth will be less onerous than that at the front desk) and explains symptoms.
3. Doctor schedules a lab test for a sensitive condition (for example sexually transmitted disease) in order to test patient consent to share such information with referral.
4. The patient is given a consent receipt that tells the patient the labs trusted identity and adherence with the trust registry conditions for handling patient records.
5. The patient positively gives consent consonant with the receipt by signing a copy and returning to the doctor's practice.
6. The patient goes to the lab which gives a trusted identifier to the patient.
7. The patient is authenticated and given the test.
8. The lab has consent and so passes the patient data to the doctor's practice.
9. The doctor asks for patient consent to schedule further diagnostics with a doctor in a different practice.
10. The patient can evaluate that other practice with respect to competence and compliance with appropriate privacy practices.
11. The patient gives consent, schedules a consultation and the lab results are passed to the other practice. The patient may or may not also get the results.
12. The patient receives a consent receipt from the primary doctor as to the transfer of health records to that other practice

Journey 2 - the user is directed to the site as they do want to start to collect contact data:

1. The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.
2. In this case the consent reciepts will be renderable to the user in understandable user experience.

Journey 3 -

Results

Accepted Risks:

1. Data transfers involved work within a framework of trust and mutual understand as to the patient's wishes with respect to care and privacy.

Post Condition:

1. There are now two additional consents steps, lab with sensitive data and secondary provider with sensitive.
2. No data is ever shared with any provider that has not been strongly identified to the patient.
3. The patient results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.

Examples:

1. tbd

Dependencies::

1. Web Sites must be trusted before any user information is provided to them.
2. Trust federations can be used to help users make informed decisions.
3. User consent and trust must begin with no user information transferred.
4. Standards exist to collect needed attributes where-ever they may be.

Workflow Diagram

TK