Patient Encounter Tracking QueryPatient Encounter Tracking Query (PEQ)(PEQ)

Profile Proposal forProfile Proposal forIHE International IT Infrastructure Technical CommitteeIHE International IT Infrastructure Technical Committee

<<IHE Japan ITI Committee PEQ WGIHE Japan ITI Committee PEQ WG>>Last update: 23/Apr/2012Last update: 23/Apr/2012

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

What is PEQ profile for ?What is PEQ profile for ?

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

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Backgrounds (in Japan)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.

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Patient Encounter Manager

Patient Encounter Supplier

Patient Encounter Consumer

Patient Encounter Management [ITI-031] or new transaction [TBD]

Patient Demographics and Visit Query [ITI-22] or new transaction [TBD]

PEQ : Actors & TransactionsPEQ : Actors & Transactions

ActorsActors• Patient Encounter ManagerPatient Encounter Manager• Patient Encounter SupplierPatient Encounter Supplier• Patient Encounter ConsumerPatient Encounter Consumer

TransactionsTransactions• TBDTBD

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Difference between PEQ and PAM/PDQ

PAM(Patient Administration Management)

Patient Demographics Supplier

Patient Demographics Consumer

Patient 　 Encounter Supplier

Patient 　 Encounter Consumer

Patient Identity Management [ITI-30]

Patient Encounter Management [ITI-31]

~ 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.

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

*1) ESI (Enterprise Schedule Integration) Integration Profile is published by Radiation Oncology Domain.

Systems to be implementedSystems to be implemented

• PEQ actors will be implemented with actors listed below.PEQ actors will be implemented with actors listed below.

PEQ Actor Required Grouping Actor TF Reference Note

Patient Encounter Manager

ITI Patient Administration Management (PAM)Patient Demographics Consumer

ITI TF1: 14.2.2 Note 1

Patient Encounter Supplier

RAD Scheduled Workflow (SWF) Performed Procedure Step Manager

RAD TF1: 3.1 Note 2

RAD Scheduled Workflow (SWF)Order Placer

RAD TF1: 3.1 Note 2

LAB Laboratory Testing Workflow (LTW)Order Filler

LAB TF1: 4.3 Note 2

RO Enterprise Schedule Integration (ESI)Treatment Management System

RO ESI Supplement Vol1: 3.5

Note 2

Patient Encounter Consumer

None - -

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

UseUse Case-1 (Typical)Case-1 (Typical)

<Internal Medicine dept.> <Radiology dept.>

Patient-Tanaka5. Medical staff starts CT examination of

next patient (Patient-Suzuki).

4.Patient-Tanaka’s

temporary location

is the internal medicine dept.

Patient　Encounter　Manager

1.Encounter　Feed

3.Encounter　Query/Response

Reception staff

Reception staff

2.Where is Patient-Tanaka?

Medical staff

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

UseUse Case-2 (RFID)Case-2 (RFID)

<Department internal medicine - consultation room>

Patient -Sato wearing RFID-Tag

Patient　Encounter　Manager

1.　Encounter　Feed

< Department ophthalmology - consultation

room >

4.　Patient-Sato’s　temporary　location　is　the　Department　　internal　

medicine.

Reception staff

2. Where is Patient -Sato?

RFID-System

3.　Encounter　Query　　　　/Response

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Open IssuesOpen Issues

1) Application to foreign hospital worldwideNeed to see the situation in foreign countries.

2) HL7 versionCurrently based on v2.5. (v3 can be considerable if needed).

3) Difference between PAM

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Closed IssuesClosed Issues

1) 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.

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Timeline for JapanTimeline for Japan

▼2012/10

Finalization of PEQ TFfor Public Comment

▼2013/1

▼2013/5

Closing Public Comment

Vendor Workshopfor Connectathon

(Informal)Connectathon

for PEQ

▼2013/10

▼2013/3

Finalization of PEQ TFfor Trial Implementation

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Trial Implementation Vendors Trial Implementation Vendors (TBD)(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.