Patient Encounter Tracking Query (PEQ)

1. Patient Encounter Tracking Query(PEQ) Profile Proposal for IT Infrastructure Technical Committee <Yutaka ANDOando_y@nirs.go.jp> <05/Nov/2011> Last update: 12/Nov/2011

2. Summary • The Patient Encounter Tracking Query (PEQ) Integration Profile is the integration profile in order to find the location of patient only in a hospital, not for cross-referencing between multiple hospitals. • It is difficult to monitor the location of patient and there is no standard way to find the location of patient immediately when needed.

3. UseCase-1

4. UseCase-2

5. System • The Patient Encounter Tracking Query (PEQ) Integration Profile has three actors ; a) Patient Encounter Source/Supplier？？ b) Patient Encounter Manager c) Patient Encounter Consumer

6. Actors & Transactions Patient Demographics Supplier Patient Identity Management [ITI-030] Actors • Patient Encounter Manager • Patient Encounter Source • Patient Encounter Consumer Transactions • Patient Encounter Feed • Patient Encounter Query Patient Encounter Manager Patient Encounter Query [PEQ-x02] Patient Encounter Feed [PEQ-x01] Patient Encounter Source Patient Encounter Consumer

7. OpenIssue • Incomplete location information: We believe that some assumptions are necessary for PEQ actors. There must be some methods to compensate and/or supplement the location between two encounters. When PEQ consumer actor inquires PEQ manager, PEQ manager replies the last encounter information. If this information indicates departing from location-A, the PEQ consumer could not find the patient location. Some assumption is inevitable for PEQ consumer actor at receiving incomplete information. • Target systems to be implemented: When existing system supports PEQ actors, we must consider which system needs to be corresponded to PEQ actors.

8. To solve these open issues, we are thinking that the trial implementation is very important.

9. Effort Estimation • Number of pages = 25-30 pages • Complexity of issues = low • Overall estimate = low