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

Trusted Third Party Capability Statement seems un-needed

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • 0.1.0
    • Public Health
    • Trusted Third Party (TTP)
    • Hide

      The reason that this is required is because TTP implementers can refer to their specific portion of the specification and figure out what needs to be supported. Without the capability statement they would have to refer to both the Backend Service App and the PHA Capability Statements to determine what needs to be implemented.

      Show
      The reason that this is required is because TTP implementers can refer to their specific portion of the specification and figure out what needs to be supported. Without the capability statement they would have to refer to both the Backend Service App and the PHA Capability Statements to determine what needs to be implemented.
    • Kishore Bashyam / Craig Newman : 28 - 0 - 1

    Description

      The FHIR Messaging specification makes note of the fact that intermediary services may be used within different workflows to forward messages through.  The Trusted Third Party here seems like it is just one of these type of intermediaries and the inclusion of the CapabilityStatement seems unneeded. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            rdingwell Rob Dingwell
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: