2015May core #1108 - Need to create and document processes for achieving interoperability using FHIR

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • Summary
    • Hide

      This doesn't belong in the spec, but does need to be done, and the most appropriate thing to do is to take the content of the two implementation tutorials and move them to the wiki.

      Establish a wiki page for the home for this and then refer to it from the implementers page, the home page, and the documentation page. wiki page will be populated later from the tutorials

      Show
      This doesn't belong in the spec, but does need to be done, and the most appropriate thing to do is to take the content of the two implementation tutorials and move them to the wiki. Establish a wiki page for the home for this and then refer to it from the implementers page, the home page, and the documentation page. wiki page will be populated later from the tutorials
    • James Agnew / Grahame Grieve: 4-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Comment:

      FHIR has great documentation of its core resources and its APIs, but there little or nothing how to use FHIR to achieve interoperability. What is the process that organizations should follow when they employ FHIR to solve an interoperability problem? What we need is a very clear, structured process, analogous to the NIEM process. Whether you believe in NIEM or not, it is an excellent example of how to explicitly lay out an entire interoperability solution process. We can't assume people will pick up FHIR and know how to use it to solve real problems. There might be a temptation to leave this out of scope, but we do so at our own risk.

            Assignee:
            Unassigned
            Reporter:
            Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: