Use Case Diagram

2.1.1 Infection Diagnosis - Events
Use Case Diagram Health Service Event #1 - Clinic Visit Admission Event Diagram

Actors

Patient
Receptionist
Clinic’s ADT system (POS)
EHRi systems

Assumptions

There is one jurisdiction involved (e.g. the jurisdiction where the visit takes place is the same as that where the patient lives); also, there is one (minimum) EHR.
The receptionist is already logged on the clinic’s ADT 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 receptionist 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).
The clinic’s ADT system searches the local POS and doesn’t find the patient (because it’s her first visit to this clinic), and sends a request to EHRi system to obtain the client’s identification information.
The EHRi system finds the client in the EHR Client registry of the current jurisdiction (e.g. where the patient lives and where the visit takes place), because the patient already exists in the jurisdictional EHR. The EHRi system returns the client’s identification information with a EHRi Transaction Client ID; this “temporary” unique patient identifier is always sent with a request to the EHRi system.
The patient is then created in the clinic’s ADT system with the data coming from EHR of the current jurisdiction.
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.
Because consent management depends on the legislation of each jurisdiction it is not described in detail in this document.
In this case, the consent is required to obtain and update the demographic and clinical information. The consent directive is recorded in the clinic’s ADT system and sends to EHR Consent registry (of the current jurisdiction) at the same time as the request to create the client, but only the consent directive is added in the EHR because the client already exists.
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 clinic’s ADT system has the capacity to create an initial “encounter” at the same time as the creation of the admission event.

Workflow Event Step	POS Action	EHRi System Action	EHR IP reference
The patient is concerned she might also have an infection so attends a walk-in clinic for the first time, rather than go to her family’s usual physician.
The patient checks in with the clinic receptionist.
The receptionist confirms that the patient has never been there before.
Resolution of patient’s identification (in the current jurisdiction)
The patient gives her full name, birth date and provincial health care number.
The receptionist checks in the patient through the clinic’s ADT system (with key information).	The POS ADT system searches locally the patient and does not find (because it’s her first visit at this clinic). The POS ADT 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.	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 client record (with a EHRi Transaction Client ID).
	The POS ADT system displays the corresponding record of current patient.
Creation of patient record (and adding of consent directive in the current jurisdiction)
The receptionist confirms the presence of a record for an individual matching patient identifiers and verifies the information with the patient. The receptionist asks also her consent regarding the storage and use of health information by the clinic.
The patient confirms the informationand gives her consent.
The receptionist records the identification information and patient’s consent in the clinic’s ADT system.	The POS ADT system adds the new patient with the consent directive. The POS ADT system sends, to the EHRi system, an update request to add the consent directive for the current patient (for the EHRi Transaction Client ID), for this provider in the current jurisdiction.	The EHRi system adds the patient’s consent directive for this provider in the current jurisdiction (for the EHRi Transaction Client ID).	EHRIP08 Put Patient Consent
		The EHRi system returns, to POS system, an acknowledgment that the update request is completed.
	The POS ADT system displays an acknowledgment about the completed update request.
Update of patient’s demographic information (in the current jurisdiction)
The receptionist searches the demographic information through the clinic’s ADT system.	The POS ADT system searches locally the demographic information and does not find (because it’s her first visit at this clinic) . The POS ADT system sends, to EHRi system, a search request (for the EHRi Transaction Client ID) to find the demographic information for the current patient.	The EHRi system searches and finds the demographic information for the current patient (for the EHRi Transaction Client ID).	EHRIP03 Get Patient Demographic Data
		The EHRi system returns, to POS system, the demographic information for the current patient (for the EHRi Transaction Client ID).
	The POS ADT system receives and displays the demographic information.
The receptionist confirms the demographic information with the patient.
The patient confirms her information and gives also the contact information.
The receptionist enters the contact information in the clinic’s ADT system.	The POS ADT system adds the demographic information (including the new contact information). The POS ASDT system sends, to EHRi system, and update request to add the contact information for the current patient (for the EHRi Transaction Client ID).	The EHRi system adds the contact information (in demographic information) for the current patient (for the EHRi Transaction Client ID).	EHRIP04 Put Patient Demographic Data
		The EHRi system returns, to POS system, an acknowledgment that the update request is completed.
	The POS ADT system displays an acknowledgment about the completed update request.
Record the clinic admission (in the current jurisdiction)
The receptionist records patient’s admission in the clinic’s ADT system.	The POS ADT system records the admission for the current patient. The POS ADT system sends, to the EHRi system, an update request to record the admission event and create a health service encounter for the current patient (for the EHRi Transaction Client ID).	The EHRi system adds the new admission event for this provider, and links this event with a new health service encounter for the current patient (for the EHRi Transaction Client ID). The EHRi system adds a role event to identify the patient role for the current client (for the EHRi Transaction Client ID), for this provider.	EHRIP15 Put Event
		The EHRi system returns, to POS system, an acknowledgment that the update request is completed.
	The POS ADT system displays an acknowledgment about the completed update request.

Get SVG Format

General Info
Name	Health Service Event #1 - Clinic Visit Admission Event Diagram
Type	Use Case Diagram