Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-22660

ClaimResponse.outcome has a required binding but is quite limiting

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Financial Mgmt
    • ClaimResponse
    • Hide

      1) Add further text on .outcome to clarify that this is the processing outcome (queued, complete, etc.) not the adjudication decision (denied, approved, etc.).

      2) Add a new data element in .adjudication to convey the decision as 0..1 CodeableConcept

      to and example valueset.

      Show
      1) Add further text on .outcome to clarify that this is the processing outcome (queued, complete, etc.) not the adjudication decision (denied, approved, etc.). 2) Add a new data element in .adjudication to convey the decision as 0..1 CodeableConcept to and example valueset.
    • Jean Duteau/Jeff Brown: 8-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      The outcome value set on ClaimResponse is a required binding to a value set of four codes. X12 has a set of codes that encompass the four codes but also has some that have more detail or that aren't in the set. Since the binding is required, that means we are stuck.

      Example: If the review of the claim requires additional medical information and is thus pending waiting for the information, that could map to the code 'partial' but I'd really rather have a code that gave more information.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jduteau Jean Duteau
            Jean Duteau
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: