This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Patient Administration"

From HL7Wiki
Jump to navigation Jump to search
Line 61: Line 61:
 
* '''Registries''' R1 passed Normative ballot in January 2010
 
* '''Registries''' R1 passed Normative ballot in January 2010
 
* '''Scheduling''' R1 passed Normative ballot in December 2003; plan to begin DSTU ballot for R2 in January 2012 and Normative ballot in January 2013
 
* '''Scheduling''' R1 passed Normative ballot in December 2003; plan to begin DSTU ballot for R2 in January 2012 and Normative ballot in January 2013
 +
 +
==Active Projects==
 +
*[[PA_Interdependent_Registries|Interdependent Registries Project Wiki]]
  
 
==Documents authored by the Committee==
 
==Documents authored by the Committee==
  
 
*[[Adminstrative Management Domain Analysis Model]]
 
*[[Adminstrative Management Domain Analysis Model]]
*[[PA_Interdependent_Registries|Interdependent Registries Wiki]]
 
  
 
==Documents authored by others==
 
==Documents authored by others==

Revision as of 18:22, 23 December 2010

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:
    1. 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.
    2. 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:
    1. Additions and modifications to registries such as patients, persons, service delivery locations, healthcare providers, places, and organizations
    2. 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.
    3. 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

Status and Plans

  • Patient Administration R2 passed DSTU ballot in September 2009; plan to begin Normative ballot in May 2011
  • Personnel Management R1 passed Normative ballot in October 2005; plan to begin DSTU ballot for R2 in January 2011
  • Registries R1 passed Normative ballot in January 2010
  • Scheduling R1 passed Normative ballot in December 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

Conference Calls

Working Group Meetings

Submission / Proposals