Patient Encounter Tracking Query (PEQ). Profile Proposal for IT Infrastructure Technical Committee < Yutaka ANDO firstname.lastname@example.org > < 05/Nov/2011 > Last update: 12/Nov/2011. Summary.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Profile Proposal for
IT Infrastructure Technical Committee
Last update: 12/Nov/2011
a) Patient Encounter Source/Supplier？？
b) Patient Encounter Manager
c) Patient Encounter Consumer
Patient Demographics Supplier
Patient Identity Management [ITI-030]
Patient Encounter Manager
Patient Encounter Query [PEQ-x02]
Patient Encounter Feed [PEQ-x01]
Patient Encounter Source
Patient Encounter Consumer
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.
When existing system supports PEQ actors, we must consider which system needs to be corresponded to PEQ actors.
To solve these open issues, we are thinking that the trial implementation is very important.