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

Clarify use of hex:policy slice

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci HRex (FHIR)
    • 1.0.0
    • Clinical Interoperability Council
    • HRex Consent Profile
    • Hide

      Will tighten the cardinality to 1..1.  Will leave the base cardinality at 1..*, though it may be that PDex should tighten that too, as other policies are not necessary and problematic.

      Will also add guidance that "If the server either does not recognize or is unable to comply with ALL listed policies, it SHALL return a 422 indicating an inability to comply with the provided consent."

      Show
      Will tighten the cardinality to 1..1.  Will leave the base cardinality at 1..*, though it may be that PDex should tighten that too, as other policies are not necessary and problematic. Will also add guidance that "If the server either does not recognize or is unable to comply with ALL listed policies, it SHALL return a 422 indicating an inability to comply with the provided consent."
    • Lloyd McKenzie/Jimmy Tcheng: 9-0-0
    • Correction
    • Compatible, substantive

    Description

      The policy element uses the HRex Consent Policy ValueSet (required). This has two values of regular or sensitive.

      The cardinality of the slice should be constrained to 1..1 

      This will avoid confusion for implementers since the policy element has a 1.* cardinality which could lead to both codes being inserted.

      Additional narrative to explain the use of the codes could also be useful. For example:

      "One of the codes should be used to express the member's preference for the data being transferred. The sensitive code includes regular data. The regular code excludes sensitive data."

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            ekivemark Mark Scrimshire
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: