Use Case Diagram

1.1.1 New Family Physician Visit - Events
Use Case Diagram Health Service Event #4 - Scan the patient’s health service encounter’s events Event Diagram

Actors

Clinic staff
Scanned Patient Record system (POS)
EHRi systems

Assumptions

For his archives, the clinic uses a Scanned Patient Record system; this system is interfaced with the clinic’s ADT system, and can also send requests to EHR to keep scanned health service events for a specific health service encounter.
The clinic’s ADT system is interfaced with the Scanned Patient Record system. So, when a patient is created/updated in the clinic’s ADT system, the patient index is automatically updated in the Scanned Patient Record system.
The clinic staff is already logged on the Scanned Patient record 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 clinic staff 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).
A scanned health service event must contain one and only one type of event (ex.: allergies, diagnosis, prescription) to allow afterward being selective in the consultation of the EHR (this assumption also has impacts on the conception of paper forms and their utilisation by the clinical practices).
The grouping of events realized during a same “encounter” depends and varies according to the functional capacities of the POS. The definition of an “encounter” also depends on clinical practices of every organization and jurisdiction. In this case, the POS has the capacity to group the events with the “encounter” initially created at the admission.

Workflow Event Step	POS Action	EHRi System Action	EHR IP reference
Resolution of patient’s identification (in the current jurisdiction)
The clinic staff enters the patient’s identification information into Scanned Patient Record system.	The POS Scanned Patient Record system searches locally and finds the patient (because he is a patient of this clinic). The Scanned Patient Record system sends, to the EHRi system, a request with the key information (ex. name, birth date, provincial health care number) to search for the patient (and to obtain a EHRi Transaction Client ID).	The EHRi system searches, with the provided information (ex. name, birth date, provincial health care number), and finds the client in the current jurisdiction.	EHRIP10 Search Patient
		The EHRi System Client Registry returns, to POS system, the corresponding patient record (with a EHRi Transaction Client ID).
	The POS Scanned Patient Record system displays the corresponding record of current patient.
Record scanned patient’s encounter’s events (in the current jurisdiction)
The clinic staff scan and index (including quality controls) the health service events of this health service encounter in the Scanned Patient Record system.	The POS Scanned Patient Record system is updated. It sends, to the EHRi system, an update request to record the scanned health service events and to link these events with a specific health service encounter for the current patient (for the EHRi Transaction Client ID).	The EHRi system (of the current jurisdiction) adds the new scanned health service events and links them with the specific health service encounter for the current patient (for the EHRi Transaction Client ID).	EHRIP15 Put Event
		The EHRi system returns, to POS system, an acknowledgment that the update request is completed.
	The POS Scanned Patient Record system displays an acknowledgment about the completed update request.

Get SVG Format

General Info
Name	Health Service Event #4 - Scan the patient’s health service encounter’s events Event Diagram
Type	Use Case Diagram