HL7 Version 2 Vocabulary Requests

HL7 Version 2 Vocabulary Requests

HL7 Version 2 Vocabulary Requests

/ RECOMMENDATION ID[1]:
For Harmonization During: / MAR2016 / OO CR 187-844
Sponsored by[2]: / HL7 Orders & Observations Work Group / PSS ID[3]: / 792 (LRI)
922 (LOI)
973 (eDOS)
Date Approved by Sponsor: / 2016Jan WGM and minor revision 2016-01-21 / Sponsor’s Status[4] / Approved
Editor/ Author: / Freida Hall/Mark Jones
PROPOSALNAME: / Additions to V2 Table 103 Processing ID
V2.9 Ballot Technical/Errata for 2.8.2
Immediate Release Other: <Earlier Release or IG>

SUMMARY RECOMMENDATION

Add new codes to HL7 Table 0103 – Processing ID; additional add clarifying comments.

VOCABULARY OBJECTS CHANGE SUMMARY

REQUIRED – fill in the numbers in the rightmost three columns that total the number of vocabulary changes in the proposal. This is used to cross-check the accuracy of capturing and applying the requested changes>

Description / # to add / # to remove / # to change
V2 Tables
V2 Table Codes / 2 / 5 (add comments)
POSITION OF CONCERNED ORGANIZATIONS:
ORG / RECOMMENDATION APPROVAL STATUS / AFFECTED ELEMENTS OF INTEREST TO ORG
Orders and Observations / Approved January 2016 WGM and reviewed 2016-01-20 OO Call / Additions to V2 Table 103; original request from US Realm Standards & Interoperability Lab Work Groups to add code V for Validation; additional revisions by HL7 OO Work Group
InM /

Pending endorsement of proposed revisions to MSH-11 field definition; Table 103 is used in MSH segment defined in V2 Chapter 2; InM is steward of Chapter 2

ISSUE:

Add values to Table 103 Processing ID to support current industry use, e.g. the ability to indicate non-production message for validation testing. In the US Realm, 3rd party validation is a requirement for the federal Meaningful Use program.

CURRENT STATE - EXISTING TABLE VALUES:

0103 – Processing ID (from v2.8.2)

Table Metadata

Table / Steward / V3 Harmonization / V3 Equivalent / Where used / Status
0103 / InM / TBD / TBD / PT.1 / Active
Code Value / Print Name / Description / Usage Note / Comment
D / Debugging
P / Production
T / Training

OPTIONS CONSIDERED:

N/A

RATIONALE:

Original proposal to add V-Validation requested during review of Table 103 values for the S&I Framework Lab Implementation Guides developed by OO. In the US, conformance to these guides is validated under the Meaningful Use program and the existing values were felt to be too limited. During discussion of the proposal at the January 2016 WGM, OO adding another code (N for Non-production) and added clarifying comments to reflect current industry usage.

RECOMMENDATION DETAILS: (inline or associated spreadsheet)

New Code Value for an Existing Table

Table Name: Processing ID

Table number: 0103 – Add N and V. Also add Clarifying ‘Comment’ for all values. Additions are yellow highlighted in Table below.

Code Value / Print Name / Description / Usage Note / Comment
N / Non-Production / Any non-production testing of an interface for structure, content, and conformance between trading partners.
V / Validation / Used for messages that are being used for validation, e.g., by third parties.

Change to existing Code

Table number: 0103

Old Code: see table below

Change Code To:

Old print/display name:

New print/display name:

Old Description and Comment:

New Description:

New Comment/Usage Note: see table below

Change code status from:

Active

Deprecated

Backwards compatibility only

Retired

To:

Active

Deprecated

Backwards compatibility only

Retired

Code Value / Print Name / Description / Usage Note / Comment
D / Debugging / Used for messages where software is subject to debugging and related fixing.
P / Production / Used for messages which contain real, live production data.
T / Training / Used for training messages where new/updated configurations are used to prepare users before that user shifts to the production setting.

Change to Table: (table number)

Change Name

Old Name:

New Name:

Change/Add Table Description: (table number)

New Description:

Add a new Table

Table Name:

Table Description:

Chapter(s) Where Used:

Field(s) Where Used:

Table Type: (HL7, User)

Steward WG:

Codes for new table

Code Value / Print Name / Description / Usage Note / Comment

DISCUSSION:

n/a

ACTION ITEMS:

Pending InM approval.

RESOLUTION:

< REQUIRED before recommendation can be closed. Indicates how recommendation was brought to closure. Can include notes on further study or networking required, and by whom.>

Pending InM Approval-proposed revisions to MSH-11 (and associated data type) definitions:

  • Update MSH-11 definition to be: This field is used to decide in what message setting whether to process the message as defined in HL7 Application (level 7) Processing rules.
  • Update PT.1 definition to be: “A value that defines whether the message is used inpart of a production, training, or debugging, validation or other non-production setting system. Refer to HL7 Table 0103 - Processing ID for valid values.”

From HL7 V2.8.2

Form version 1.6

[1] identifier by which proposal is known to sponsor

[2] must be sponsored by an HL7 WorkGroup, the HL7 International Committee or an ANSI or ISO accredited SDO

[3] project ID from Project Insight for reference, if proposal is from a PSS approved project

[4] for sponsor tracking only, Sponsor’s status must be “Approved” for final submission to Harmonization