Share Your Thoughts on our Terminology Server! Let us know your insights and help enhance our services. The survey is open from Nov 19 to Dec 3, 2024. Your feedback matters!
Learn More >
Demonstration of hosted repository and implementation guide generation (Lloyd)
Key folders for each domain/project:
*framework - defines implementation guide templates, headers, footers, etc. Most people will not need to modify anything in this folder
*src - this is where resource, profile and implementation guide content will reside
Key files in src s structure
*Notes
*Intro
Build process only generates implementation guide content. Output is found in "website" folder.
Also creates QA file showing validation results
Profiles used in today's demo are based on the May 2016 version of FHIR
The website output will link to the live FHIR specification (e.g. data type definitions, non-CA terminology, etc.)
Each domain will have its build process
A continuous build environment can be configured
The vision would be to tie access to the FHIR environment to one's InfoCentral account
Requirements for running a build locally:
*JVM 1.8 or above
*Ruby with Jeckyll
* Apache Ant (though Ant could be integrated in the framework)
InfoScribe could be used as a wiki, but there are a limited number of edit licenses (i.e. for community authors). This could be scaled up over time.
Next steps:
*Recording to be posted to the FHIR work group
*Infoway follow up on internal discussions occurring later this week
*Development of guidelines: How do the tools work, caveats, etc., Conventions (e.g. naming conventions), and Design principles (e.g. when to constrain cardinality, usage of "must support", etc.
Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.
Notes from 2016-10-26 FHIR Tooling call
Print
Email
Twitter