IHE FHIR Profile Publication/Status summary
Revision as of 03:29, 30 September 2018 by Costateixeira (talk | contribs) (Created page with "Discussion points: We have been experimenting and the IG Publisher does meet our goals. The PoC that we have so far consists of: # A base IG template (currently experimentin...")
Discussion points:
We have been experimenting and the IG Publisher does meet our goals. The PoC that we have so far consists of:
- A base IG template (currently experimenting with a fork of one of the DaVinci IGs)
- A base profile - an IG with just a few pages (currently one, will work on making more)
- Instructions on how an editor can use these to get a local build
- An IHE location for uploading profiles (WIP)
Short-term roadmap (to reach an MVP):
- Editing:
- Allow users to import page content from another formats (e.g. MS Word .docx) (1)
- Ability to use "Content templates" so that every IHE ig automatically uses the basic set of pages and user does not need to define those
- Publishing tools
- Check if it is OK to "fork" one of the existing templates - e.g. DaVinci
- Continue improving the IHE IG template
- Can we use Jekyll themes?
- enhance rendering (contributing to HL7)
- Use plantUML (MIT license) to render workflow definitions and examples
- Possibly use plantUML (MIT license) to render actor diagrams?
- Further improve user tools to validate content and run the build process (1)
- Technical artefacts
- Define naming convention
- Shared Repositories
- Ability to base a profile on an existing profile, and import / display the base profile. Example: if Pharmacy further profiles an ITI profile, users should be able to track this
(1) Will contribute these improvements to the HL7 FHIR Toolkit