Disagree that knowledge of X12 specs should be isolated - PAS #139

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Technical Background
    • Hide

      Will change "The intention of this implementation guide is that knowledge of X12 should be isolated from client/EHR implementers. However, intermediary systems will require an intimate understanding of the X12 specification, particulary the 278, 275 and 278i transactions." to

      "The intention of this implementation guide is that detailed knowledge of X12N is not required by client/EHR implementers, though knowledge of some value sets and business processes will be needed. Intermediary systems will require an intimate understanding of the X12N specification, particularly the 278 and 275 transactions.

      Show
      Will change "The intention of this implementation guide is that knowledge of X12 should be isolated from client/EHR implementers. However, intermediary systems will require an intimate understanding of the X12 specification, particulary the 278, 275 and 278i transactions." to "The intention of this implementation guide is that detailed knowledge of X12N is not required by client/EHR implementers, though knowledge of some value sets and business processes will be needed. Intermediary systems will require an intimate understanding of the X12N specification, particularly the 278 and 275 transactions.
    • Laurie Burckhardt/Mark Scrimshire: 31-0-0
    • Clarification
    • Non-substantive

      Existing Wording: The intention of this implementation guide is that knowledge of X12 should be isolated from client/EHR implementers. However, intermediary systems will require an intimate understanding of the X12 specification, particulary the 278, 275 and 278i transactions.

      Proposed Wording: Some basic knowledge of X12 transactions, especially data content, should be made available to client/EHR implementters.

      Comment:

      Disagree that knowledge of X12 specs should be isolated as there should be some familiarity with data elements and overlaps. Isolation is not good, we should be striving for cooperation and interoperability. Especially since section 5.2.1 references X12 transactions

      Summary:

      Disagree that knowledge of X12 specs should be isolated

            Assignee:
            Unassigned
            Reporter:
            mrocca
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: