This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Patient Administration"
Jump to navigation
Jump to search
Line 57: | Line 57: | ||
==Status and Plans== | ==Status and Plans== | ||
− | + | '''Patient Administration''' HL7 V3 PA, R2 passed ballot in September 2009<br/> | |
− | + | : Plan to begin Normative ballot for '''Patient Encounters''' content in May 2011<br/> | |
− | + | : Plan to begin DSTU ballot In September 2011 for Person, Identity Document, Patient and Service Delivery Location as part of '''Administrative Registries'''<br/> | |
− | + | '''Personnel Management''' ANSI/HL7 V3 PM, R1-2005 approved 10/28/2005<br/> | |
− | + | : Plan to begin DSTU ballot in September 2011 for Provider and Organization as part of '''Administrative Registries'''<br/> | |
− | + | '''Registries''' R1 passed Normative ballot in January 2010<br/> | |
− | + | : No enhancements planned<br/> | |
− | + | '''Scheduling''' ANSI/HL7 V3 SC, R1-2003 approved 12/17/2003<br/> | |
− | + | : Plan to begin DSTU ballot for R2 in January 2012 and Normative ballot in January 2013<br/> | |
==Active Projects== | ==Active Projects== |
Revision as of 17:10, 30 December 2010
Contents
Mission & Charter
The Patient Administration Work Group supports the HL7 mission by defining the requirements and specifications to support the interoperability among clinical and non-clinical systems regarding patient encounters and administrative registries.
This group produces normative standards by:
- Identifying requirements and providing specifications for exchanging:
- Demographic and administrative data used to describe patients, persons, service delivery locations and patient encounters [scheduled and/or actual], including healthcare providers, places, organizations, and their relationships in the context of healthcare encounters.
- Administrative data to describe resources, their availability, [for example, represented by schedules or by status], and regulatory topics such as licensing and credentialing information about individuals, animals, organizations and devices directly or indirectly involved in the delivery of healthcare services.
- Identifying requirements and providing specifications regarding the dynamic behaviors involved in requests and their fulfillment with respect to:
- Additions and modifications to registries such as patients, persons, service delivery locations, healthcare providers, places, and organizations
- Scheduling of appointments for services, encounters and associated resources. These processes include the functions of requesting, booking, notification, and modification pertaining to appointments and resources.
- Queries for information
- Defining the domain and process of scheduling. As a domain, Scheduling offers a generic set of messages and behavior to implement any number of Scheduling scenarios. As a process, Scheduling offers an abstract data model and a set of operations to any domain within HL7 that utilizes scheduling concepts.
Scope
The Patient Administration work group develops and maintains the following standards:
- HL7 v2
- Chapter 3 - Patient Administration
- Chapter 10 - Scheduling
- Chapter 15 - Personnel Management
- HL7 v3
- Patient Administration Domain
- Person topic
- Identity Document topic
- Patient topic
- Service Delivery Location topic
- Ambulatory Encounter topic
- Short Stay Encounter topic
- Inpatient Encounter topic
- Emergency Encounter topic
- Home Health Encounter topic
- Attending Practitioner topic
- Encounter Location topic
- Encounter Organization topic
- Encounter Queries
- Patient Administration CMETs
- Personnel Management Domain
- Provider Registry topic
- Organization Registry topic
- Human Resource topic
- Regulatory topic
- Personnel Management CMETs
- Registries Domain
- Real Time Location System topic
- Scheduling Domain
- Appointment topic
- Slot topic
- Appointment CMETs
- Patient Administration Domain
Status and Plans
Patient Administration HL7 V3 PA, R2 passed ballot in September 2009
- Plan to begin Normative ballot for Patient Encounters content in May 2011
- Plan to begin DSTU ballot In September 2011 for Person, Identity Document, Patient and Service Delivery Location as part of Administrative Registries
Personnel Management ANSI/HL7 V3 PM, R1-2005 approved 10/28/2005
- Plan to begin DSTU ballot in September 2011 for Provider and Organization as part of Administrative Registries
Registries R1 passed Normative ballot in January 2010
- No enhancements planned
Scheduling ANSI/HL7 V3 SC, R1-2003 approved 12/17/2003
- Plan to begin DSTU ballot for R2 in January 2012 and Normative ballot in January 2013
Active Projects
Documents authored by the Committee
Documents authored by others
- Registry - What is a Registry ?
- Master File/Registry Control Act Wrapper - Linking/merging of registrations
- Query Parameters - implementation and modelling aspects
- CSCR-053 Include A Encounter Universal CMET in CSP - Patient Care discussion related to the potential use of A_Encounter.
- Nictiz Care Provider Registry - three registries deliver combined functionality
Conference Calls
Working Group Meetings
Submission / Proposals
- Proposals under review
- Harmonization Proposal: AdministrativeContactRoleType - added 20090723
- Helse Vest Patient Encounter issues - added 200812
- New application registry topic: PRPM_-_AORTA_use_cases, workitem since the 2008-09 WGM.
- Proposals which have been reviewed (accepted or rejected)
- Proposal: Patient Registry, add Find Candidates query parameters - added 20090204, accepted by PA 2010-01 WGM
- Scheduling topic: Proposal: add Find Appointments Query - added 20090215, accepted by 2010-01 WGM
- Proposal: update Find Encounters Query - added 20090717, accepted by PA 2009-09 WGM
- Person Topic: Proposal: Person Registry, add AdministrativeObservation parameter - added 20090204, revised and accepted by PA 2010-01 WGM
- Harmonization_Proposal:_Add_new_EXISTENCEPL_roleClass - added 20090710, rejected 2009Aug harmonization
- PA Harmonization Proposal Encounter Types - added 20090715, accepted w/mod 2009Aug harmonization
- Add Ward/Bed/Room to ServiceDeliveryLocationRoleType - added 20090711, postponed, value set needs an overhaul
- Harmonization Proposal: New PersonalRelationshipRoleType codes - added 20090317, accepted 2009Apr harmonization
- Harmonization Proposal: add EducationLevel codes - added 20090313, withdrawn 2009Apr harmonization
- Harmonization Proposal: add InformRequestActType Concept Domain - accepted by PA 20090225, accepted 2009Apr harmonization
- Patient Topic: Add Patient Request, accepted by PA 2008-09 WGM
- Provider topic: Proposal: Add new Parameter to Provider Detail Query, accepted by PA 2008-09 WGM
- Completed Proposals
- Real_Time_Location_Systems - passed DSTU July 2008; passed Normative January 2010
- Appointment_CMETs - added 20090204, passed DSTU in 2010JAN ballot