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

review use of ext-coverage-information now that Coverage is handled in prefetch

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Financial Mgmt
    • CRD Service Request
    • Hide

      Will remove the 'Coverage' extensions and mustSupport from the standard 'insurance' elements where those exist.

      Show
      Will remove the 'Coverage' extensions and mustSupport from the standard 'insurance' elements where those exist.
    • Bob Dieterle / Chris Cioffi : 8-0-0
    • Correction
    • Non-compatible

    Description

      Follow up from call discussing the meaning of "Must Support"-

      The CRD profile for ServiceRequest currently marks ext-coverage-information as Must Support, however we've discussed how this information is often not available associated with the service and it will be more reliable to just get the patient level Coverages in the prefetch.

      The various CRD profiles should be reviewed and have the "Must Support" removed from ext-coverage-information (and possibly other fields?). It may also make sense to remove ext-coverage-information entirely, though there may be scenarios later in the life cycle where we do know the coverage associated with the service.

      Attachments

        Activity

          People

            Unassigned Unassigned
            kjohnsen Kyle Johnsen
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: