Description
A Health Care Provider, in any care setting , views and, optionally uses, a Patient Summary at the point of care.
Scenario
A patient schedules a visit with a health care provider, outside of their Medical Home, with symptoms including dizziness and an earache. The patient mentions that they have a regular health care provider, within their Medical Home, and experience high blood pressure (hypertension) which is being monitored at home for now. The health care provider collects information from the patient and searches their Patient Summary-CA Solution for an existing Patient Summary (e.g., searches the network to determine if a Patient Summary was created and shared by another Health Care Provider). Upon finding a Patient Summary for their patient, the health care provider views and uses the information in the Patient Summary in support of providing care for this patient.
Triggers, Pre-conditions & Post-conditions
This section describes example triggers, pre-conditions & post-conditions related to the creation of the Patient Summary. It is not inclusive of all potential workflow scenarios which may be implemented within Canadian jurisdictions.
Triggers
- Health Care Provider gathers all available information about their patient to provide care.
- Where applicable, HCP received a notification that new Patient Summary information is available for a Patient to which they have subscribed to receive notifications.
Pre-conditions
- In jurisdictions where a patient may have applied consent directives to their Patient Summary, HCP complies with local/jurisdictional privacy policies.
Post-conditions
- Health Care Provider views and uses the Patient Summary in support of Patient care.
Use Case Participants & Diagram
The participants involved in this use case are:
- PS-CA Consumer (Health Care Provider requesting access to a PS-CA)
- PS-CA Solution (Health Records System enabling access to the PS-CA)
This use case diagram represents the participants and their role in the use case with a high-level view of the flow of information.
Use Case - Primary Flow
The following provides a textual description corresponding to the use case diagram.
- Health Care Provider, providing care for their Patient gathers information from the Patient and other information that may be available in the PS-CA Solution (e.g. Health Records System such as an EHR).
- Health Care Provider requests access to view an existing Patient Summary for their Patient from the PS-CA Solution.
PS-CA Solution applies applicable business/privacy/policy rules (e.g., privacy rules related to consent).
- PS-CA Solution determines if there are patient consent directives applied to the Patient Summary. If yes, proceed to step 5. If there are no consent directives applied, proceed to step 8.
- Health Care Provider is presented with the patient's consent directives in their Health Records System (e.g., EMR).
- HCP chooses to proceed with the request to view the Patient Summary? If yes, proceed to step 6. If no, proceed to step 5 b.
- HCP chooses to abandon the request to view the Patient Summary. Process complete. (Refer to Alternate Flow for step 5 b.)
- Health Care Provider abides by the applicable local/jurisdictional privacy policies (e.g., provides reason code for viewing the Patient Summary).
PS-CA Solution applies the applicable local/jurisdictional privacy policy information provided by the HCP (e.g., records the reason code for viewing the Patient Summary).
- PS-CA Solution applies data transformation and access to view/consume the Patient Summary (e.g., Provide request to view the PS information in PDF format).
- Health Care Provider obtains access to the Patient Summary and, optionally, consumes the information into their Health Records System.
- Health Care Provider views/uses the most current Patient Summary information available in support of caring for the Patient.
Use Case - Alternate Flow
The following list provides possible alternate flows that may occur within this use case.
- Step 5.b. Provider is not authorized to view the Patient Summary. Process abandoned and HCP does not obtain access to Patient Summary. HCP, alternatively, collects additional input from the Patient.