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

processing missing data requirements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US CARIN Digital Insurance Card (DIC) (FHIR)
    • 0.1.0
    • Payer/Provider Information Exchange
    • STU
    • General Guidance
    • 4.0.3
    • Hide

      -We will update language to clarify this section. Proposed updated language is as follows:
      "In situations where information on a particular data element is not present and the reason for absence is unknown, Health Plan API actors SHALL NOT include the data elements in the resource instance returned as part of the query results."
      "In situations where information on a particular data element is missing and the Health Plan API actor knows the precise reason for the absence of data, Health Plan API actors SHALL send the reason for the missing information using either the nullFlavors or dataAbsentReason extensions."
      "When querying Health Plan APIs, Consumer App actors SHALL interpret missing data elements within resource instances as data not present in the Health Plan API actor's system. Consumer App actors SHALL be able to process resource instances with missing data without generating an error or causing the application to fail for the user. Consumer App actors SHOULD configure their applications to translate nullFlavors and dataAbsentReason extensions into a user-friendly message indicating the data has not been provided by the Health Plan API actor."

      Show
      -We will update language to clarify this section. Proposed updated language is as follows: "In situations where information on a particular data element is not present and the reason for absence is unknown, Health Plan API actors SHALL NOT include the data elements in the resource instance returned as part of the query results." "In situations where information on a particular data element is missing and the Health Plan API actor knows the precise reason for the absence of data, Health Plan API actors SHALL send the reason for the missing information using either the nullFlavors or dataAbsentReason extensions." "When querying Health Plan APIs, Consumer App actors SHALL interpret missing data elements within resource instances as data not present in the Health Plan API actor's system. Consumer App actors SHALL be able to process resource instances with missing data without generating an error or causing the application to fail for the user. Consumer App actors SHOULD configure their applications to translate nullFlavors and dataAbsentReason extensions into a user-friendly message indicating the data has not been provided by the Health Plan API actor."
    • Mark Roberts/Mary Kay McDaniels: 14-0-2
    • Clarification
    • Non-substantive

    Description

      • Consumer App actors SHALL be able to process resource instances containing data elements asserting missing information.

      Are we to interpret this to mean that the consumer app simply needs to accept the resource instances "without generating an error or causing the application to fail"?

      Or, SHOULD the consumer app be capable of storing the nullFlavor/dataAbsentReason information? What about displaying said information?

      Attachments

        Activity

          People

            Unassigned Unassigned
            eddyhnieves Eddy Hernandez-Nieves (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: