Section title: X12 Pilots

PIL01 – Publishing X12 Data Maps

Background

X12 does not currently have a product which describes the relationship between the data elements described in an EDI Standard transaction set and an external entity's data elements.

The X12 Board received a request from an external entity to publish such a crosswalk, reviewed the request, and approved the creation of a new crosswalk product, to be known as a Data Map. The resulting Data Maps will not be joint works but will be published exclusively as X12 products.

Speed to market is a critical component of the crosswalk product's viability.

The ASC procedures do not currently cover approval of a crosswalk product. The ASC Operating Manual (ASC01) supports the concept of pilot processes to prove out procedures for new products. This document proposes a pilot for approval of Data Maps between specific Da Vinci- developed products and X12 transaction sets maintained by X12N.

Pilot Proposal – High Level

The following shall govern the pilot.

        
  • The pilot process will be patterned off the ASC Standards Development Manual (ASC02) where possible.
  •     
  • Progress will be monitored by the PRB chair, with staff assistance as requested.
  •     
  • ASC subcommittees shall not define additional procedural steps under this pilot. All procedural steps are defined herein, or in a subsequent approved version of this document.
  •     
  • Since the subject matter is related to business use of X12 data elements and there is no technical component involved in the resulting product, a TAS review shall not be required.
  •     
  • Since the subject matter is specific to the health care industry, all reviews and voting shall occur within the X12N subcommittee.
  •     
  • X12 staff will be responsible for messaging and education related to the pilot and the new X12 product.
  •     
  • Consensus will be demonstrated via a X12N constituent ballot. The results will be determined based on majority.
  •     
  • The pilot shall be deemed a success if the defined process steps can be executed within 90 days, without uncovering any unexpected show-stopper issues.

Pilot Proposal – Process

The process laid out below assumes best-case results. If there are setbacks in the best-case plan, the ASC chair, PRB chair, and X12N chair shall determine the appropriate procedural fallback based on the procedure defined herein. If the chairs cannot agree on an appropriate procedural fallback, Steering will review the situation, amend this pilot plan to cover the situation, and approve a new version of this pilot plan.

Process Steps:

        
  1. X12 staff (staff) receive draft crosswalks from the Da Vinci Project.
  2.     
  3. Staff formats the draft into a publication-ready data map.
  4.     
  5. Staff submits a maintenance request for the work in alignment with ASC02 Section 2.2.
  6.     
  7. Staff posts a voting thread in the PRB iMeet workspace notifying PRB of the maintenance request and its assignment to X12N, specifically to X12N|TGB|WG10. The thread shall be posted as a 15-day electronic ballot in alignment with ASC02 2.2. The post shall state that absent any comments disputing the maintenance request or assignment, PRB approval of the request and assignment will be recorded 15 days from the posting date.
  8.     
  9. On the 16th day after the thread is posted, if there are no disputing comments the request and assignment are considered approved.     
              
    1. Staff will include the approval as an interim decision when drafting the next PRB minutes.
    2.     
        
  10.     
  11. Staff notifies the chairs of TGB|WG10 of the assignment, copying the ASC chair, PRB chair, X12N chair, X12N vice-chair, and TGB co-chairs.
  12.     
  13. TGB|WG10 reviews the data mapping as a priority task, completing the work within 30 days of the assignment.     
              
    1. If TGB|WG10 concurs with the mapping, go to step #8
    2.         
    3. If TGB|WG10 identifies mapping concerns, the concerns are reported to support@x12.org for escalation, copying the recipients of the notification email identified in step #6.
    4.         
    5. The X12 operational liaison works with the X12N chair and the Da Vinci project leads to resolve any mapping concerns, return to step #7.
    6.     
        
  14.     
  15. TGB|WG10 approves the document for X12N vote.
  16.     
  17. The TGB|WG10 co-chairs notify support@x12.org of their concurrence, copying the recipients of the notification email identified in step #6.
  18.     
  19. The X12N chair authorizes a 30-day electronic X12N constituent ballot.
  20.     
  21. Staff prepares an electronic constituent ballot and notifies eligible X12N constituents.     
              
    1. A ballot notice is issued to each primary and alternate representative who is eligible to receive an X12N voting card at the next X12 Standing Meeting.
    2.     
        
  22.     
  23. At the close of the balloting period, staff notifies the ASC chair of the results, copying the TGB|WG10 co-chairs and recipients of the notification email identified in step #6.
  24.     
  25. At the close of the balloting period, staff notifies the ASC chair of the results, copying the TGB|WG10 co-chairs and recipients of the notification email identified in step #6.     
              
    1. TGB|WG10 drafts responses to any ballot comments directly related to the data mapping itself.
    2.         
    3. Staff drafts responses to any ballot comments which are not directly related to the data mapping itself.
    4.         
    5. Staff formats all the draft responses for Steering review.
    6.         
    7. Steering reviews and approves the draft responses within 15 days.
    8.         
    9. Staff sends the responses to the commenters within 5 days.
    10.     
        
  26.     
  27. Following Steering approval, staff posts a voting thread in the PRB iMeet workspace notifying PRB of the ballot results. The thread shall be posted as a 15-day electronic ballot. The post shall state that absent any comments disputing due process, PRB approval to publish will be recorded 15 days from the posting date.     
              
    1. Staff will include this approval as an interim decision when drafting the next PRB minutes.
    2.     
        
  28.     
  29. Staff processes the approval, finalizes the Data Map, and makes it available to licensees.
  30.     
  31. The X12 operational liaison notifies the Da Vinci project leads that the Data Map is approved and coordinates with them on a joint announcement.
  32.     
  33. Feedback may be solicited in a post-publication feedback period at the discretion of the ASC and X12N chairs. Any feedback received will be considered for inclusion in a later version of the Data Map.

Document History

                                                       
ApprovedDescription
06/02/2019V1: Pilot Approved by Steering