Use Case Diagram

10.1.2 Cough Recheck - Events
Use Case Diagram Health Service Event #1 – Exam and DI order Event Diagram

Actors

Patient
Physician
Clinic’s EMR system (POS)
EHRi systems

Assumptions

There are two involved jurisdictions (e.g. the jurisdiction where the patient lives and the jurisdiction where the patient going to university and the visit takes place); also, there is two (minimum) EHR.
The patient is already registered in the clinic’s ADT system.
The clinic’s ADT system is interfaced with the clinic’s EMR system. So, when a patient is created/updated in the clinic’s ADT system, the patient index is automatically updated in the clinic’s EMR system.
The physician is already logged on the clinic’s EMR system.
To resolve the patient’s identification, the provincial health care number is also used, because it is key information to find the patient. In this case, the physician uses the following key information to find the patient: name, birth date, and provincial health care number.
The resolution of the patient’s identification information is also necessary to obtain a “temporary” unique patient identifier from the EHR, to allow the user to view and update the patient’s record. The “temporary” unique patient identifier (EHRi Transaction Client ID) is provided by the EHRi only for one user session (without a break in the time), for the same patient and the same provider (person) who are engaged in the health service event. If there is an interruption during a health service, this becomes another health service event, and another resolution of the patient’s identification is required to obtain another “temporary” unique patient identifier (EHRi Transaction Client ID).

Workflow Event Step	POS Action	EHRi System Action	EHR IP reference
The physician re-assesses patient and this time hears what he thinks is a mild rub.
Resolution of patient’s identification (in the current jurisdiction)
The physician enters the patient’s identification information in the clinic’s EMR system.	The POS EMR system searches and finds locally the identification of patient. The POS EMR system sends, to the EHRi system, a request with the key information (ex. name, birth date, provincial health care number) (and to obtain a EHRi Transaction Client ID).	The EHRi system searches the client, in the current jurisdiction, with the provided key information (ex. name, birth date, provincial health care number) and finds the client.	EHRIP10 Search Patient
		The EHRi System Client Registry returns, to POS system, the corresponding patient record (with a EHRi Transaction Client ID).
	The POS EMR system displays the corresponding record of current patient.
DI order and referral (in the current jurisdiction)
The physician orders a chest x-ray.	The POS EMR system is updated with the DI order. The POS EMR system sends, to the EHRi system, an update request to record the DI order for the current patient (for the EHRi Transaction Client ID).	The EHRi system adds the DI order event for the current patient (for the EHRi Transaction Client ID).	EHRIP15 Put Event (Event Type = DI Order)
		The EHRi system returns, to POS system, an acknowledgment that the update request is completed.
	The POS EMR system displays an acknowledgment about the completed update request.
The physician arranges to see patient again in follow up shortly.

Get SVG Format

General Info
Name	Health Service Event #1 – Exam and DI order Event Diagram
Type	Use Case Diagram