So following on from the meeting, I would like to discuss what we have done, what others have done, and what should we be doing in the mobile arena with regards to interact with terminology servers.
Mobile devices/apps are starting to capture health information, so how should these devices interact with terminology servers.
What standards should we be encouraging the use of?
With HL7 FHIR currently in DSTU2, what is the appropriate way forward in serving up terminology? Using Medication Resources, Value Set Resources?
What does the vendor community need in terms of tools (open source) to help them support and integrate this?
Quick demo - if people are interested:
We have developed a Manage Meds app to showcase how we have used CSIRO’s Onto Server (Terminology) along with FHIR resources and other interfaces to complete the functionality of the app.
Some things I've been thinking of along the lines of open source software project mainenance and OTF and all that are:
Harmonizing architecture of IHTSDO (OTF) tooling
Handling configuration information independently of code (to support variety of differently configured deployments of the same tool)
Managing community contributions - e.g. policy about merge requests, unit/integration tests, etc.
Continuous Integration (along with things like static code analysis, etc).
Making developer "data sets" available (or at least tooling for generating them) - e.g. be able to have a stock "dev" build of each tool with sample configuration and data that makes it easy to get started.
Formats/templates for tooling documentation (e.g. on Confluence)
It seems we have some busy days ahead of us! I wish to nominate the following agenda items:
What is the role of National Release Centers in the open source software development & maintenance?
Release cycles: presumably the PMC has the final say but will there be some kind of (regular) schedule that looks further ahead than the upcoming release?
How to involve more organisations & people (Get started tutorials? Starter projects?)
Identifying gaps in the toolkit, or providing a confluence space where contributors can identify those gaps. Not so much extra features as entire tools that would be a logical and valuable part of the Open Tooling Framework. Philip's question about tools for HL7 FIHR would be a case in point. Such projects could also make it easier for other organisations to become involved.
Supporting new users, contributors, committers etc. It's mentioned in the Charter but how many people are currently able to offer such support?
4 Comments
Philip Wilford
So following on from the meeting, I would like to discuss what we have done, what others have done, and what should we be doing in the mobile arena with regards to interact with terminology servers.
Mobile devices/apps are starting to capture health information, so how should these devices interact with terminology servers.
What standards should we be encouraging the use of?
Quick demo - if people are interested:
We have developed a Manage Meds app to showcase how we have used CSIRO’s Onto Server (Terminology) along with FHIR resources and other interfaces to complete the functionality of the app.
Rory Davidson
Philip Wilford a demo would be great if possible.
Brian Carlsen
Some things I've been thinking of along the lines of open source software project mainenance and OTF and all that are:
Feikje Hielkema-Raadsveld
It seems we have some busy days ahead of us! I wish to nominate the following agenda items: