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

Need to define expectations around data trust services, backend app and action codes

    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):
      MedMorph Backend Service App
      MedMorph Trust Service Provider
      US Public Health PlanDefinition Action Codes
      USPublicHealthPlanDefinition
    • Resolution Description:
      Hide

      We will add text to state that authorities for the service provider meets the needs before a service can be used (add to eCR IG as well). We will also:

      1. Create an Endpoint profile and add an extension(s) (expected capabilities and/or endpoint) on the action element to identify FHIR URLs that can be used for operations for specific use cases and action combinations.
      2. For each action, because we can have external services, allow PlanDefinition to specify URL (input to action type would be an endpoint (operation definition URL) that would conform to trust services capability statement). The URL is the instantiation of the service.
      3. Relax the cardinality on the Trust Services Capability Statement - actions are parameters.
      Show
      We will add text to state that authorities for the service provider meets the needs before a service can be used (add to eCR IG as well). We will also: Create an Endpoint profile and add an extension(s) (expected capabilities and/or endpoint) on the action element to identify FHIR URLs that can be used for operations for specific use cases and action combinations. For each action, because we can have external services, allow PlanDefinition to specify URL (input to action type would be an endpoint (operation definition URL) that would conform to trust services capability statement). The URL is the instantiation of the service. Relax the cardinality on the Trust Services Capability Statement - actions are parameters.
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      The IG states the use of Trust Service providers to perform tasks such as anonymization , pseudoanonymization, de-identification, re-identification.  There are also action codes defined for use in the plan definitions for such activities.   It is unclear however if the use of those actions in a plan definition are expected to correlate to calls to data trust services, as well as if specific instances of the trust services need to be called out for use in such circumstances.  For instance, if a data trust service is called to de-identify a bundle that is stands to reason that only that service can be used to re-identify the bundle.  As such one needs to know how to convey which set of data trust services to use to perform these activities.  

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: