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

Requirement for deidentified CRD (ballot version)

    XMLWordPrintableJSON

Details

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

      We will remove the de-identified profiles and all reference to support for de-identified invocation from CRD. The primary proponent of de-identified CRD was CMS and they have confirmed that this is no longer functionality they require.

      Show
      We will remove the de-identified profiles and all reference to support for de-identified invocation from CRD. The primary proponent of de-identified CRD was CMS and they have confirmed that this is no longer functionality they require.
    • Bob Dieterle / Rachael Foerster : 8-0-0
    • Correction
    • Non-compatible
    • Yes

    Description

      FHIR-35789 was closed, I think inappropriately.  We requested it get pulled from the block vote, but it looks like it was voted on in the block anyway.  We were asked to resubmit this as a ballot comment.

       

      Existing wording:

      Therefore, CRD Clients SHALL provide support for Coverage Requirements Discovery without PHI using a redacted view where the resources exposed through the CDS Hooks and SMART on FHIR interfaces are filtered as follows:

      AND

      CRD Clients SHALL determine whether a CRD Service will use the PHI or non-PHI version of the CRD interface at the time the CRD Service is configured to have access to their system. In situations where PHI will never be required to perform Coverage Requirements Discovery, the redacted view SHALL be used. 

       

      Issue:

      Not all FHIR implementations have the capabilities to de-identify and strip out potential PHI as described. Therefore use of SHALL here is very prescriptive and unreasonable. Request to change it to MAY or SHOULD.

       

      Proposed wording:

      Therefore, CRD Clients MAY provide support for Coverage Requirements Discovery without PHI using a redacted view where the resources exposed through the CDS Hooks and SMART on FHIR interfaces are filtered as follows:

       AND

      CRD Clients SHOULD determine whether a CRD Service will use the PHI or non-PHI version of the CRD interface at the time the CRD Service is configured to have access to their system. In situations where PHI will never be required to perform Coverage Requirements Discovery, the redacted view MAY be used.

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Cooper Thompson, Kyle Johnsen, Varghese Mathew
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: