Difference between revisions of "Patient Administration Management"

Latest revision as of 10:07, 12 January 2022

enables applications to share accurate patient demographic data within and between acute care settings as well as between those and ambulatory healthcare providers.

Formal Specification

PAM (html) specification

Final Text

Patient Demographics Query [PDQ] is an alternative to PAM in many situations: It provides the same category of data in pull (query/response) mode whereas PAM operates in push (notification/acknowledgement) mode.
Laboratory Testing Workflow [LTW], Laboratory Point Of Care Testing [LPOCT] and a number of other profiles require their actors to be grouped with PAM or PDQ actors to get needed demographic information.

Current: IT Infrastructure Technical Framework.

This page is based on the Profile Template

@@ Line 1: / Line 1: @@
-'''Patient Administration Management (PAM)''' enables applications to share accurate patient demographic data within and between acute care settings as well as between those and ambulatory healthcare providers.
+enables applications to share accurate patient demographic data within and between acute care settings as well as between those and ambulatory healthcare providers.
 __TOC__
+==Formal Specification==
-==Summary==
+===[https://profiles.ihe.net/ITI/TF/Volume1/ch-14.html PAM (html) specification]===
+* [https://profiles.ihe.net/ITI/TF/Volume1/ch-14.html Final Text]
-The PAM profile specifies two transactions to fulfill two great missions among applications cooperating in healthcare:
-* '''Patient Identity Feed''': Maintain consistency of patient demographics (i.e. patient identitification, full identity and persons related to the patient such as primary caregiver, family doctor, guarantor, next of kin) across applications operating in acute care settings as well as in the ambulatory environment.
-* '''Patient Encounter Management''': Coordinate the exchange of patient account, encounter and location information within and between acute care settings.
-These two transactions provide sets of event-triggered messages, notifying the creation and update of patient administrative data. Each transaction involves a pair of (Supplier, Consumer) Actors. Transaction Patient Identity Feed operates in a centralized manner (one Supplier application providing a number of Consumers). <br/>
-Transaction Patient Encounter Management can work in centralized mode as well as in peer to peer mode (Several applications cooperating as peers, each one playing alternatively Supplier and Consumer roles).
-Transaction Patient Encounter Management can be self contained in a sense that the Patient Encounter Supplier sends both patient encounter information and patient identity and demographics information (in the context of the encounter data) to the Patient Encounter Consumer. In addition, this transaction also allows the Patient Encounter Supplier to send messages to the Patient Encounter Consumer for patient identity maintenance in the encounter context, including patient update and identity merge.<br/>
-<center>[[Image:iti_pam_ip.jpg]]</center>
-==Benefits==
-'''Reduce Errors and Enhance Patient Care'''
-* Prevents manual data entry errors by ensuring that each piece of patient or encounter data is entered only once
-'''Improve Throughput'''
-==Details==
-The '''''Patient Administration Management (PAM) Integration Profile''''':
-==Systems Affected==
-Systems involved in this profile are:
-* Enterprise-wide information systems that manage patient registration (i.e., admit-discharge-transfer /registration system and hospital information system (HIS ))
-*
-'''Actors & Transactions:'''
-[[Image:pam-actor-transaction.JPG]]
-==Specification==
-'''Profile Status:''' [[Comments| Final Text]]
-'''Documents:'''
-[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework:]
-:* [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_4_0_Vol1_FT_2007_08_22.pdf Vol. 1] - Section 4 (PAM profile overview, use cases, actors, transactions, options, groupings)
-:* [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_4_0_Vol2_FT_2007-08-22.pdf Vol. 2:]
-::* Section 3.30: Transaction Patient Identity Feed
-::* Section 3.31: Transaction Patient Encounter Management
-::* Appendix C: HL7 Profiling Conventions
-::* Appendix E: Usage of CX Data Type in PID-3 - Patient Identifier List
-::* Appendix N: Common HL7 Data Types
-::* Appendix P: Examples of messages
-'''Underlying Standards:'''
-:* [http://www.hl7.org HL7]
 ==See Also==
 '''Related Profiles'''
+* [[Patient Demographics Query]] [PDQ] is an alternative to PAM in many situations: It provides the same category of data in pull (query/response) mode whereas PAM operates in push (notification/acknowledgement) mode.
+* [[Laboratory Testing Workflow]] [LTW], [[Laboratory Point Of Care Testing]] [LPOCT] and a number of other profiles require their actors to be grouped with PAM or PDQ actors to get needed demographic information.
-* [[Patient Demographics Query]] [PDQ] ...
+Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
-'''Consumer Information'''
-'''Implementer Information'''
 This page is based on the [[Profile Template]]
 [[Category:Profiles]]
+[[Category:ITI Profile]]
+[[Category:HL7v2]]
+[[Category:PatientId]]

Difference between revisions of "Patient Administration Management"

Latest revision as of 10:07, 12 January 2022

Contents

Formal Specification

PAM (html) specification

See Also

Navigation menu

Search