Document Outline - HL7 Version 2.5.1
- Publication History of Previous Versions
- Table of Contents
- Table of Figures
- 1. Introduction
- Intended Audience
- Scope
- Organization and Flow
- 2. Actors, Goals, and Messaging Transact
- Actors and Goals
- High-Level View of Use Cases
- Use Case Descriptions
- Use Case 1—Send Immunization History
- Use Case 2—Receive Immunization History
- Use Case 3—Request Immunization History
- Use Case 4—Return Immunization History
- Use Case 4A—Find Candidate Clients
- Request Identity Resolution Prior to Req
- Use Case 5--Accept requested history:
- Use Case 6—Send Demographic Data
- Use Case 7—Accept Demographic Data
- Use Case 8--Acknowledge Receipt
- Use Case 9—Report Error
- Messaging in the Context of the Business
- Core Data Elements of an Immunization Hi
- Key Technical Decisions
- Pre-Adoption Of Some Features Of HL7 Ver
- Use Of Vocabulary Standards
- Snapshot Mode
- Field Length And Truncation
- Conventions
- 3. HL7 Messaging Infrastructure
- Keywords
- HL7 definitions
- Basic Message Construction Rules
- Encoding Rules for Sending
- Encoding Rules for Receiving
- Implications of the Encoding Rules
- Determining Usage of Segments, Fields an
- USAGE CONFORMANCE TESTING RECOMMENDATION
- Usage
- Definition Of Conditional Usage
- Sending And Receiving Application Confor
- Message Element Attributes
- 4. HL7 Data Types
- Data Types for IIS Use
- CE -- Coded Element (most uses)
- CE_TX -- Coded Element (text only in RXA
- CQ -- Composite Quantity with Units
- CWE -- Coded With Exceptions
- CX -- Extended Composite ID With Check D
- DT -- Date
- DTM -- Date/Time
- EI -- Entity Identifier
- ERL -- Error Location
- FN -- Family Name
- FT – Formatted Text
- HD -- Hierarchic Designator
- ID -- Coded Values for HL7 Tables
- IS -- Coded Values for User Defined Tabl
- LA2 -- Location with Address Variation 2
- MSG -- Message Type
- NM -- Numeric
- PT -- Processing Type
- SAD -- Street Address
- SI -- Sequence Id
- ST – String
- TS -- Time Stamp
- VID -- Version Id
- XAD -- Extended Address
- XCN - Extended Composite ID Number and N
- XON - Extended Composite Name and ID Num
- Extended Person Name (XPN)
- XTN - Extended Telecommunication Number
- 5. Segments and Message Details
- BHS—Batch Header Segment
- BTS—Batch Trailer Segment
- ERR—Error Segment
- EVN - Event Type Segment
- FHS—File Header Segment
- FTS—File Trailer Segment
- IN1—Insurance Segment (IN2, IN3)
- MSA—Message Acknowledgement Segment
- MSH—Message Header Segment
- NK1—Next of Kin Segment
- NTE—Note Segment
- OBX—Observation Result Segment
- ORC—Order Request Segment
- Conformance Statement:
- ORC field definitions
- PD1—Patient Demographic Segment
- PID—Patient Identifier Segment
- PV1—Patient Visit Segment
- QAK—Query Acknowledgement Segment
- QPD – Query Parameter Definition
- RCP – Response Control Parameter Segment
- Conformance Statement:
- RCP field definitions
- RXA-- Pharmacy/Treatment Administration
- RXR-- Pharmacy/Treatment Route Segment
- 6. Messages for Transmitting Immunizatio
- Introduction
- Send Immunization History--VXU
- Requesting Information (Immunization His
- Respond to Request for Information– RSP
- Requesting An Immunization History from
- Acknowledging a Message--ACK
- Sending Demographic Information – VXU or
- Sending Messages in a Batch
- 7. Query and Response Profile (QBP/RSP)
- Request Immunization History Query Profi
- Return a List of Candidates Profile -- Z
- Introduction:
- Use Case:
- Static Definition
- Segment Level Profile
- Field Level Profile
- Dynamic Definition
- Acknowledgement Responsibilities
- Return an Immunization History – Z32^CDC
- Introduction:
- Use Case:
- Static Definition
- Segment Level Profile
- Field Level Profile
- Dynamic Definition
- Change History Details
- APPENDIX A:
- User-defined Table 0001 - Sex
- HL7-defined Table 0003 - Event type
- User-defined Table 0004 - Patient class
- User-defined Table 0005 – Race
- HL7-defined Table 0008 - Acknowledgment
- User-defined Table 0010 - Physician ID
- HL7-defined Table 0061 - Check digit sch
- User-defined Table 0063 – Relationship
- User-defined Table 0064 - Financial clas
- HL7-defined Table 0076 - Message type
- HL7-defined Table 0078 - Abnormal flags
- HL7-defined Table 0085 - Observation res
- HL7-defined Table 0091 - Query priority
- HL7-defined Table 0102 - Delayed acknowl
- HL7-defined Table 0103 - Processing ID
- HL7-defined Table 0104 - Version ID
- HL7-defined Table 0105 - Source of comme
- HL7-defined Table 0119 – Order Control C
- HL7-defined Table 0126 - Quantity limite
- HL7-defined Table 0136 - Yes/No indicato
- HL7-defined Table 0155 - Accept/Applicat
- HL7-defined Table 0162 - Route of admini
- User-defined Table 0189 - Ethnic Group
- HL7-defined Table 0190 - Address type
- HL7-defined Table 0202 - Telecommunicati
- User-defined Table 0203 - Identifier typ
- User-defined Table 0204 - Organizational
- HL7-defined Table 0207 - Processing mode
- User-defined Table 0208 - Query response
- HL7-defined Table 0211 - Alternate chara
- User-defined Table 0215 - Publicity code
- User-defined Table 0220 - Living arrange
- HL7-defined Table 0227 - Manufacturers o
- alphabetized by manufacturer name
- User-defined Table 0288 - Census tract
- User-defined Table 0289 - County/parish
- HL7-defined Table 0292 - Codes for Vacci
- CVX – Vaccines Administered
- User-defined Table 0296 - Language
- User-defined Table 0297 - CN ID source
- User-defined Table 0300 - Namespace ID
- HL7-defined Table 0301 - Universal ID ty
- HL7-defined Table 0322 - Completion stat
- HL7-defined Table 0323 - Action code
- HL7-defined Table 0354 - Message structu
- HL7-defined Table 0356 - Alternate chara
- HL7-defined Table 0357 - Message error s
- User-defined Table 0360 – Degree
- User-defined Table 0361 – Application
- User-defined Table 0362 – Facility
- User-defined Table 0363 – Assigning Auth
- User-defined Table 0396 – Coding system
- User-defined Table 0441 - Immunization r
- User-defined Table 0471 – Query Name
- HL7 Table 0516 - Error Severity (use in
- User-defined Table 0533 – Application Er
- CDC-defined NIP001 - Immunization inform
- CDC-defined NIP002 - Substance refusal r
- CDC-defined NIP003 - Observation identif
- CDC-defined NIP004 - Contraindications,
- Value Set Name – Immunization Funding So
- Value Set Name – Vaccination Contraindic
- Value Set Name – Vaccination Reaction -
- Value Set Name – Vaccination Special Ind
- Value Set Name – Immunization Profile Id
- Value Set Name – Immunization Schedule I
- Value Set Name – Evidence of Immunity -
- Value Set Code: PHVS_VISBarcodes_IIS
- Value Set Name – Funding Eligibility Obs
- Value Set Name – VIS Vaccines (IIS)
- Appendix B
- Core Data Elements for an Immunization H
- Send Immunization History (VXU)
- Supported Message Segments
- Example VXU # 1-Basic message:
- Example VXU #2 - Indicate client eligibi
- Patient Eligibility Status:
- Example VXU #3 - Include immunization hi
- Indicating the Schedule that was used:
- Indicating Vaccine Group associated:
- Reporting The Ordinal Position In A Seri
- Reporting the Number of Doses in a Serie
- Reporting Next Dose Recommendation Dates
- Reporting Recommendation Reasons:
- Complete Example Of Evaluation And Forec
- Using The NTE Segment Associated With An
- Example VXU #4 - Send client specific co
- Evidence of immunity:
- Contraindications to immunization:
- Factors which indicate the need for an i
- Example VXU #5 – Send immunizations asso
- Example VXU #6 –Delete an Immunization R
- VXU Example #7--Send Information About V
- VXU Example #8—Send Information About Im
- VXU Example #9—Send Two Lot Numbers in R
- VXU Example #10—Recording Birth Informat
- VXU Example #11—Recording an incompletel
- Send Acknowledgement ACK In Response To
- Send acknowledgement of success in ACK
- Send Request for Vaccine History (QBP/RS
- Process for requesting Immunization Hist
- Description of the VXQ/VXX/VXR Process F
- Using QBP query to replicate VXQ/VXX/VXR
- Returning a list of candidate clients in
- Returning an immunization history in res
- Acknowledging a Query that finds no cand
- Acknowledging a query that finds more ca
- Using a Two-step process to request an i
- Returning a list of candidate clients in
- Receiving system determines that message
- Malformed message
- No Match Is Found
Do'stlaringiz bilan baham: |
