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

CDex Purpose of use value set is not consistent with requirements for 45 CFR 164.506

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Resolved - change required (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • CDex Purpose of Use Value Set
    • Hide
      1. Will Roll up the VS into one or more TPO concepts using the ACT CodeSystem and migrate the CDex codes into the CodeSystem as well.
      2. change "NOS" codes to "NOE" codes : define NOE as "Not otherwise enumerated" and provide description.
      3. add "Treatment NOE" to valueset
      4. and explicitly document that an extended code SHALL be provided as an additional coding
      5. provide example
      6. Publish the purpose of use value set as draft (keeping NOE for now) and then publish a final value set as part of STU update.  Add a comment in spec to raise awareness of this forthcoming change to the value set.
      Show
      Will Roll up the VS into one or more TPO concepts using the ACT CodeSystem and migrate the CDex codes into the CodeSystem as well. change "NOS" codes to "NOE" codes : define NOE as "Not otherwise enumerated" and provide description. add "Treatment NOE" to valueset and explicitly document that an extended code SHALL be provided as an additional coding provide example Publish the purpose of use value set as draft (keeping NOE for now) and then publish a final value set as part of STU update.  Add a comment in spec to raise awareness of this forthcoming change to the value set.
    • Bob Dieterle / Jay Lyle : 6-0-2
    • Enhancement
    • Non-compatible

    Description

      within the use of CDex in US Realm, there should tight alignment with, at a minimum, the uses allowed for health care data noted in [45 CFR 164.506|https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/disclosures-treatment-payment-health-care-operations/index.html].

      1. The current set of ActCode values in the value set are not well aligned with existing ActCodes under PurposeOfUse, for example HOPERAT Healthcare Operations is not included. 
      2. The set of codes should be expansive to include all descendants of appropriate codes. This is true even with an extensible binding
      3. Any missing concepts should be fully named and defined, then added to this part of ActClass
        1. One particularly problematic proposed "temporary code" is operations-nos because this assumes it is proper to have an allowed POU that is not an explicitly defined healthcare operation. Only specified healthcare operations are allowed as noted in 45 CFR 164.506: "Health care operations are certain administrative, financial, legal, and quality improvement activities of a covered entity that are necessary to run its business and to support the core functions of treatment and payment. These activities, which are limited to the activities listed in the definition of “health care operations” at 45 CFR 164.501". For this reason this code should not be allowed.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Rob_McClure Rob McClure
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: