Why only synchronize disparate healthcare applications' user interfaces?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: 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

      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

            Assignee:
            Unassigned
            Reporter:
            Ricardo Quintano
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: