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

Why only synchronize disparate healthcare applications' user interfaces?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Overview
    • Hide

      FHIRcast synchronizes the context of healthcare application user interfaces doesn't otherwise synchronize clinical content. Synchronizing content is the role of FHIR, v2, CDA, etc. All way bigger specs than FHIRcast.

      Show
      FHIRcast synchronizes the context of healthcare application user interfaces doesn't otherwise synchronize clinical content. Synchronizing content is the role of FHIR, v2, CDA, etc. All way bigger specs than FHIRcast.
    • Eric Martin / Bill Wallace: 8-0-0

    Description

      Why only synchronize disparate healthcare applications' user interfaces? I suggest use “disparate healthcare applications”.

      Existing Wording:

      APIs used to synchronize disparate healthcare applications' user interfaces in real time

      Proposed Wording:

      APIs used to synchronize disparate healthcare applications in real time

      Attachments

        Activity

          People

            Unassigned Unassigned
            rquintano Ricardo Quintano
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: