This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR: Enhancing Implementation (ONC Grant Project)"

From HL7Wiki
Jump to navigation Jump to search
Line 27: Line 27:
 
*****gForge: https://gforge.hl7.org/gf/project/fhir
 
*****gForge: https://gforge.hl7.org/gf/project/fhir
 
*****terminology server: http://tx.fhir.org
 
*****terminology server: http://tx.fhir.org
 
 
**Deliverable Documentation: IG Publisher
 
**Deliverable Documentation: IG Publisher
 
***During the period from May 2017 to September 2017, we undertook substantial rework of the FHIR IG Publisher so that it would be possible to run it as a web server rather than as a batch file. The principle purpose of this work is to allow the IG publisher to be used to serve website tools that publish implemetnation guides, the most important of which is the FHIR registry eco-system. The idea is that a web site will provide authoring services, and then use the web services provided to by the IG publisher to actually produce the publication content.  
 
***During the period from May 2017 to September 2017, we undertook substantial rework of the FHIR IG Publisher so that it would be possible to run it as a web server rather than as a batch file. The principle purpose of this work is to allow the IG publisher to be used to serve website tools that publish implemetnation guides, the most important of which is the FHIR registry eco-system. The idea is that a web site will provide authoring services, and then use the web services provided to by the IG publisher to actually produce the publication content.  

Revision as of 14:33, 26 September 2017

Return to the HL7 wiki Main Page.

Overview

This page supports the FHIR projects occurring within the ONC Grant funded opportunity: Enhancing C-CDA and FHIR Implementation.

The collaboration encompasses the following projects to support a $500,000 grant awarded to HL7 by the Office of the National Coordinator for Health Information Technology (ONC). Respective deliverables are linked below each project:

  • FHIR Repository Processes
  • FHIR Registry Prototype
  • FHIR Tools Profile Roadmap
    • Registry Requirements Analysis / Registry Gap Assessment - Gevity Consulting Deliverable
    • The tooling roadmap is here: http://wiki.hl7.org/index.php?title=FHIR_Tooling_Eco-system.
    • Deliverable Documentation: FHIR Core
      • During the period from May 2017 to September 2017, the FHIR core infrastructure was subject to ongoing maintenance throughout the period. The FHIR code infrastructure includes the following:
        • the main FHIR build process for the specification itself
        • the IG publisher
        • the java validator
        • tx.fhir.org terminology service
      • Though these tools are primarily provided for the generation of the published specifications, where ever it is possible for the tools to provide services that are relevant to implementers, they are moved into their own module so these services are available. This means that the tools - and their viability - are tied to implementation success.
    • Deliverable Documentation: IG Publisher
      • During the period from May 2017 to September 2017, we undertook substantial rework of the FHIR IG Publisher so that it would be possible to run it as a web server rather than as a batch file. The principle purpose of this work is to allow the IG publisher to be used to serve website tools that publish implemetnation guides, the most important of which is the FHIR registry eco-system. The idea is that a web site will provide authoring services, and then use the web services provided to by the IG publisher to actually produce the publication content.
      • The fundamental problem the work faced was that the IG publisher was structured so that the project was loaded, the configuration analysed, and then all the dependency content was loaded - a process that could take up to a minute. In order to rework the build process so that it was suitable for use as a web service, the code had to be re-organised to be both thread safe and for the large resource dependencies (internal and external terminology servers, conformance service) to be loaded in advance. Most of the work was under the cover improvements around the code structure.
      • The outcome is a web process that re-uses the same code base as the IG publisher command line version, but can be invoked across the web.