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

Does this raise concerns about an increased potential for interoperability issues?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • FHIR Data Segmentation for Privacy (FHIR)
    • 0.1 [deprecated]
    • Security
    • Background
    • 2.3.3
    • Hide

      The text is making a point from a software engineering perspective --that it is possible to implement SLS as a utility that interacts with the EHR as an alternative to implementing the SLS inside the EHR.

      Show
      The text is making a point from a software engineering perspective --that it is possible to implement SLS as a utility that interacts with the EHR as an alternative to implementing the SLS inside the EHR.

    Description

      Beyond the EHR and FHIR server that a physician is already paying for, what else would need to be considered?

      Existing Wording:

      #implementation - While existing EHRs can certainly implement the security labeling service inside their products, this is not the only approach and the labeling service can be implemented as a separate product  that interacts with a standard EHR and applies labels to the outgoing information on-the-fly or on the existing information in a batch mode.

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: