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

IG needs to define how keys will be exchanged for encryption

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Public Health
    • Related Artifact(s):
      US Public Health PlanDefinition Action Codes
      USPublicHealthPlanDefinition
    • Related Page(s):
      Provisioning Workflow Specification
      Report Submission
    • Grouping:
    • Resolution Description:
      Hide

      Add an extension to the PlanDefinition to indicate the following 

      • URL for the Public Key of the Recipient
      • Encryption Algorithm to be used along with the public key for encrypting.

      When the publisher of the Knowledge Artifact decides to use the Encryption Action, they have to populate the above extension for the encryption action to be performed by the Backend Service App. If the action is selected but the above extension is not populated, then the Backend Service App will not perform the encryption action and may fail to perform a submission depending on the use case error handling requirements.

      Show
      Add an extension to the PlanDefinition to indicate the following  URL for the Public Key of the Recipient Encryption Algorithm to be used along with the public key for encrypting. When the publisher of the Knowledge Artifact decides to use the Encryption Action, they have to populate the above extension for the encryption action to be performed by the Backend Service App. If the action is selected but the above extension is not populated, then the Backend Service App will not perform the encryption action and may fail to perform a submission depending on the use case error handling requirements.
    • Change Category:
      Correction
    • Change Impact:
      Compatible, substantive

      Description

      The IG states that reports may be encrypted before they are sent from the Backend Service app to where they are going. This statement is made in various locations such as the pages referenced in the ticket as well as through the definition of an action to use in the PlanDefinition. However, there is no mention as to how keys will be exchanged between disparate parties to perform the encryption and ensure that the data can be encrypted once it arrives at it's destination. If this specification expects to allow for automation of these types of actions then it needs to define how the keys will be shared between the systems. This could be as simple as piggy backing on the smart bulk data configuration and stating that there needs to be encryption keys defined in the keyset as well as signing keys , but it needs to be defined somehow.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              rdingwell Rob Dingwell
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: