Product Brief - V3 Domain: Patient Administration
- 1 Product Brief - V3 Domain: Patient Administration
- 1.1 Product Name
- 1.2 Topics
- 1.3 Standard Category
- 1.4 Integration Paradigm
- 1.5 Type
- 1.6 Releases
- 1.7 Summary
- 1.8 Description
- 1.9 Business Case (Intended Use, Customers)
- 1.10 Benefits
- 1.11 Implementations/ Case Studies (Actual Users)
- 1.12 Resources
- 1.13 Relationship to/ Dependencies on, other standards
- 1.14 Links to current projects in development
Patient Administration (UVPA/ PRPA)
also known as ADT (Admit, Discharge, and Transfer)
also known as Encounter Management
also known as Administrative Registries
- Ambulatory Encounter
- Inpatient Encounter
- Emergency Encounter
- Home Health Encounter
- Attending Practitioner
- Encounter Location
- Encounter Organization
- Encounter Queries
- Short Stay Encounter
- Person, (Person Registries) - May2010 DSTU Ballot to update the Person topic within the current Patient Administration DSTU to include the changes to support social services use cases as well as other several other requests approved by the work group since the topic was last updated.
Future plans include publishing with Provider and Organization Registries in Personnel Management
- Identity Document
- Patient, (Patient Registries)
- Service Delivery Location (Registries)
- Health Information Exchange Standards
- DSTU: HL7 PA, R2-2007 - HL7 Version 3 Standard: Patient Administration, Release 2- R2 2007
- HL7 V3 PA, R2 - HL7 Version 3 Standard: Patient Administration, Release 2; Domain Level DSTU Ballot 2 - September 2009
- DSTU Ballot May 2010: HL7 Version 3 Standard: Patient Administration, DSTU Release 2; Person Registry Enhancement, Release 1
Patient Administration, also known as ADT (Admit, Discharge and Transfer), supports many of the core administrative functions in healthcare such as person and patient registration and encounter management. Generally, information is entered into a Patient or Person Registry or into a Patient Administration system and passed to other systems (e.g., other registries, clinical, ancillary and financial systems).
Person Registry Enhancement - May 2010:
- This ballot will document requirements, identify modeling and vocabulary changes to the existing Person Registry topic and publish an enhanced Person Registry as DSTU to include enhancements by the Youth Healthcare program of the Netherlands to the universal standard. *This ballot proposes changes to support the following use cases:
- Record a child's current living situation. A child may be a member of zero, one or more households. For each household, record when the child is in residence (e.g., alternate weeks, only weekdays or weekends), the members of the household and an observation for recording any relevant reasons for the household arrangements. For each household member record his/her relation to the child as well as information about the person such as birth date and occupation (including volunteer work).
- Record a person’s citizenship status. A child or child’s parent may be in the process of applying for refugee status or permanent citizenship.
- Record arrangements for before or after school care of a child including type of care, responsible person and schedule. (This construct might generalize to any kind of part time custodial care such elder day care).
- Record additional information about guardianship arrangements.
Major Changes approved by PA Work Group since the topic was last updated :
- The DSTU ballot includes one change that is not backwards compatible:
- ContactParty changes code attribute from the AdministrativeContactRoleType domain to the PersonalRelationshipRoleType domain. This change aligns Person messages with the CCD Implementation Guide.
- Other changes:
- Change Member.effectiveTime from IVL to QSET;
- Add second Member class with traversal from Group to Member; add ObservationEvent with subjectOf participation to Member;
- Add code attribute to Employee, Guardian and Citizen classes, add structure to convey CareProvisionEvent act.
- Add two parameters to the Query Person Registry by Demographics model:
- GroupId parameter
- PersonDeceased parameter
Business Case (Intended Use, Customers)
- Provider: Health Care Institutions
Implementations/ Case Studies (Actual Users)
- Helse Vest, Norway;
- CSC Scandihealth, Denmark (encounter management)
- Tutorial included with V3 Overview
- See more at http://hl7new.amg-hq.net/implement/training.cfm
Relationship to/ Dependencies on, other standards
Links to current projects in development
- Project Insight ID # 489, Patient Encounters