Patient Encounter Tracking Query (PEQ)

1. Patient Encounter Tracking Query(PEQ) Profile Proposal for IHE International IT Infrastructure Technical Committee <IHE Japan ITI Committee PEQ WG> Last update: 23/Apr/2012

2. What is PEQ profile for ? • The Patient Encounter Tracking Query (PEQ) Integration Profile is the integration profile in order to find the location of patient in a hospital.

3. Backgrounds (in Japan) • Single EMR/CPOE covers whole department in a hospital. • Patients are moving between multiple departments in a hospital. • Reservation time slot is flexible, and technicians manage patients in the slot. (5-15 min per CT exam, 5-15 min per 1 consultation),Therefore, sometimes the patient does not appear on time and medical workers need to find the location of the patient.

4. PEQ : Actors & Transactions Patient Encounter Manager Actors • Patient Encounter Manager • Patient Encounter Supplier • Patient Encounter Consumer Transactions • TBD Patient Encounter Management [ITI-031] or new transaction [TBD] Patient Demographics and Visit Query [ITI-22] or new transaction [TBD] Patient Encounter Supplier Patient Encounter Consumer

5. Difference between PEQ and PAM/PDQ PAM(PatientAdministrationManagement) Patient Identity Management [ITI-30] Patient Demographics Supplier Patient Demographics Consumer Patient Encounter Management [ITI-31] Patient Encounter Supplier Patient Encounter Consumer • ~ Difference between PAM and PEQ ~ • PAM has a capability to notify the patient location, but it does not archive locations of patient. • PEQ Manager archives the locations of patient and can be queried by Consumer.

6. Systems to be implemented • PEQ actors will be implemented with actors listed below. *1) ESI (Enterprise Schedule Integration) Integration Profile is published by Radiation Oncology Domain.

7. UseCase-1 (Typical) Patient Encounter Manager 3.Encounter Query/Response Reception staff 1.Encounter Feed 2. Where is Patient-Tanaka? Reception staff Medical staff 4. Patient-Tanaka’s temporary location is the internal medicine dept. 5. Medical staff starts CT examination of next patient (Patient-Suzuki). Patient-Tanaka <Internal Medicine dept.> <Radiology dept.>

8. UseCase-2 (RFID) Patient Encounter Manager 1. Encounter Feed 3. Encounter Query /Response RFID-System 2. Where is Patient-Sato? Reception staff 4. Patient-Sato’s temporary location is the Department internal medicine. Patient-Sato wearingRFID-Tag <Departmentinternal medicine - consultationroom> < Departmentophthalmology - consultation room >

9. Open Issues • Application to foreign hospital worldwideNeed to see the situation in foreign countries. • HL7 versionCurrently based on v2.5. (v3 can be considerable if needed). • Difference between PAM

10. Closed Issues • Assumption of location information:Assumptions of location information can be implemented on actors in PEQ when a location of patient A is undefined (e.g When patient A left location-A one hour ago and not detected at any place, Patient Encounter Manager or Consumer may be able to assume patient A is waiting at department-X).In this version, we do not consider such assumptions.

11. Timeline for Japan 2012/10 2013/1 2013/3 2013/5 2013/10 ▼ ▼ ▼ ▼ ▼ (Informal)Connectathonfor PEQ Finalization of PEQ TFfor Public Comment Vendor Workshopfor Connectathon Closing Public Comment Finalization of PEQ TFfor Trial Implementation

12. Trial Implementation Vendors (TBD) • Patient Encounter Supplier • Toppan Forms (RFID) • Adosol Nisshin (RFID) • Toshiba (RIS) • Carestream Health (RIS) • Konica (RIS) • Patient Encounter Manager • Fujitsu • Array • Patient Encounter Consumer • IBM • NEC # some vendors are already starting software design/implementation.