If we are going to reference the 278i, it needs to be defined somewhere in this guide. - PAS #203

XMLWordPrintableJSON

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

      In the background section, we will provide a brief overview of all of the X12 referenced transactions (ids, formal names and short descriptions as well as pointers to the appropriate portion of the X12 specification where further detail can be found).

      Show
      In the background section, we will provide a brief overview of all of the X12 referenced transactions (ids, formal names and short descriptions as well as pointers to the appropriate portion of the X12 specification where further detail can be found).
    • Laurie Burckhardt/Mark Scrimshire: 31-0-0
    • Clarification
    • Compatible, substantive

      Existing Wording: The intermediary SHOULD execute a 278i response t o return the status. However, if the payer does not support that function, the intermediary SHALL return the most recent copy of the prior authorization response as received from the payer. (Note that in this latter case, the intermediary would need to persist prior authorization information and would therefore be a 'covered entity' for HIPAA purposes.)

      Comment:

      If we are going to reference the 278i, it needs to be defined somewhere in this guide. Included in such defintiion should be an indication that this is NOT a HIPAA-mandated transaction. Also, should the IG mention earlier that the provider system is sending the 278i inquiry first? This appears out of nowhere.

      Summary:

      If we are going to reference the 278i, it needs to be defined somewhere in this guide.

            Assignee:
            Unassigned
            Reporter:
            Terrence Cunningham
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: