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

Clarify action when required data is not available

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US CARIN Blue Button (FHIR)
    • Financial Mgmt
    • (profiles) [deprecated]
    • General Guidance
    • Hide

      Revised verbiage will read:

      If the source system does not have data for a Must Support data element with minimum cardinality = 0, the data element is omitted from the resource. If the source system does not have data for a required data element (in other words, where the minimum cardinality is > 0), follow guidance defined in the US Core IG missing data.

      Show
      Revised verbiage will read: If the source system does not have data for a Must Support data element with minimum cardinality = 0, the data element is omitted from the resource. If the source system does not have data for a required data element (in other words, where the minimum cardinality is > 0), follow guidance defined in the US Core IG missing data.
    • Mark Roberts/Pat Taylor: 18-0-5
    • Clarification
    • Non-substantive

    Description

      Currently reads:

      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.

       

      What should happen if the missing data element is required (minimum cardinality of 1)? Should the whole resource not be returned? Should there be some indication that such information exists but cannot be returned? Some clarification may be helpful even it's just pointing back to general FHIR recommendations for handling this situation in general.

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: