Creation and Curation of FHIR Profiles - process and governance
Publication date: Dec 14, 2017
FHIR needs profiling. During the recent FHIR DevDays in Amsterdam I held a talk covering the best practices around the process of creating a profile, as
well as the process of the curation of profiles created by others.
Creation and Curation
The focus wasn't on the technical process of creating profiles (using tools like Forge), but on the governance of the creation process. How does one
ensure that the created artefact (a profile in this case) has a sufficiently high maturity for it to be used in production? How does one ensure
participation and input from all stakeholder groups ?
Creation and Curation of FHIR Profiles - process and governance (Rene Spronk)
To skip directly to the summary of the best practices around the Creation of artefacts (covered below in a separate section), go to 07:03 in the video.
To skip directly to the summary of the best practices around the Curation of artefacts (also covered below in a separate section), go to 22:05 in the video.
Creation of FHIR Profiles
When looking at the process of creating new FHIR profiles one can look at the process of the creation of FHIR artefacts in general.
HL7 itself has quite an elaborate process for the creation of production-ready (normative) artefacts. In general, FHIR distinguishes
3 phases in the lifecycle of an artefact: draft, active and retired. Multiple 'Maturity Levels' have been introduced, with a set of well-defined
criteria as to when a new maturity level has been reached. Other projects use different maturity models.
Quite a few use some form of test event to drive the maturity of the artefacts forward, through hackathons or sprints.
Some FHIR projects focus on the 'draft' stage of the artefact, to ensure that the underlying requirements have been well described. care should
be taken not to develop a profile which (partially) already exists.
In general, the best practices around the creation of profiles can be summized as follows:
- Create a maturity model - QA criteria, test events, input from specific stakeholder groups
- Use test events to advance the maturity level - Sprints, connectathons, etc.
- Use a 24/7 issue tracker - Resolve issues as they arise, short cycles
- Occasionally Freeze a coherent set of artifacts - Versioning, formal approval process
- Monitor/adjust process - Ensure proper representation of all stakeholder groups
Curation of FHIR Profiles
When one doesn't define ones own profiles, but one has a responsability to curate the profiles as created by others, the situation looks a bit different.
In general (see image below) Organisation1 usies its own process to define an artefact, and at some point in time sends the arefact to Organisation2 for
approval/wider use. Organisation2 will have to determine at what maturity level it's going to accept the proposed artefact, given that e.g.
there may be issues around the scope or the overall quality of the proposed material.
In order to ensure participation by representatives of Organisation1 in the curation process one could make it mandatory for those that propose
a profile for curation also commit themselves to participate in the curation process. If one proposes a profile for curation, one will have to
accept that the scope of the profile may change (mostly: the scope will be widened), so the resulting profile (as accepted by Organisation2) may have
to be profiled by Organsisation2 for it to be useful in its own (more narrow) context.
In general, the best practices around the curation of profiles can be summarized as follows:
- Ensure participation of those proposing acceptance of an artifact (“third-party”) in the curation process itself (both governance TAG_BODY actual curation)
- Decide: co-development (get involved early), or curate ‘final version’ created by third-party
- Curated/accepted artifact may differ from the one used by third-party - third-party to use constrained version of accepted artifact
Most large projects (be they coordinated by a vendor-consortium, an HL7 affiliate or a national health IT organisation) will end up having
to deal with a mixture of curation and creation.
PermaLink to this page: http://www.ringholm.com/column/FHIR_Profile_creation_curation_best_practices.htm
Index of columns:
- Creation and Curation of FHIR Profiles - process and governance (Dec 14, 2017)
- De Algemene Verordening Gegevensbescherming (AVG) in de zorg (Dutch, Sep 19, 2017)
- Impact of the GDPR on the use of interoperability standards (Jun 27, 2017)
- News from the FHIR DevDays in Amsterdam (Dec 15, 2016)
- Next XDS Release (Oct 27, 2016)
- Five years of FHIR (Aug 11, 2016)
- Interoperability projects in Ireland - FHIReland (Mar 14, 2016)
- 2016 FHIR Jedi Calendar (Jan 06, 2016)
- Top 10 HL7 videos watched in 2015 (Dec 24, 2015)
- Update from the trenches on CDA R2.1/R3 and HL7v2. (Oct 15, 2015)
- FHIR DevDays - UK GP System APIs (Sep 16, 2015)
- IHE XDS - testing and implementation tools (Aug 25, 2015)
- Most often implemented IHE Profiles (Jun 08, 2015)
- Why we sponsor the HL7 WGM (May 10, 2015)
- FHIR in Paris (Apr 21, 2015)
- Mapping HL7v2 messages to FHIR. (Apr 13, 2015)
- Analysis of CDA R2 testing tools - most requirements are neither tested nor respected. (Feb 13, 2015)
- HL7 and IHE in Sweden (Feb 08, 2015)
- 2015 FHIR Chiefs Calendar (Jan 07, 2015)
- The Merry FHIR Choir caroling the 12 Days of Christmas (Dec 09, 2014)
- Chicago FHIR Update (Oct 13, 2014)
- Internationalization of HL7 (Sep 25, 2014)
- New XDS Advanced training course on offer by IHE Services and IHE Academy (Jul 14, 2014)
- Recent and Future developments of the DICOM standard (Mar 06, 2014)
- Top 10 HL7 videos watched in 2013 (Jan 02, 2014)
- Report from the HL7 WGM in Cambridge (Oct 16, 2013)
- Documenting the history of HL7 (Sep 03, 2013)
- Histology Lab Device Automation using HL7 version 2 (Jul 23, 2013)
- HL7 FHIR Elevator Pitch (Jul 15, 2013)
- Interoperability Standards - the no-sales pitch (Jul 09, 2013)
- HL7 UK - new landscape, new opportunities (Jun 26, 2013)
- Validation and error correction at the IHE Connectathon (Apr 25, 2013)
- CDA Implementation Guides - (not) invented here (Apr 17, 2013)
- Usage of IHE Profiles (Feb 25, 2013)
- 10 year anniversary - Dutch Ringholm HL7 v2 training courses. (Feb 19, 2013)
- About IHE Academy and new IHE training courses (Jan 12, 2013)
- CDA implementation experiences in the UK (Dec 04, 2012)
- Musings on free HL7 IP (Oct 01, 2012)
- HL7 Connectathons (Sep 09, 2012)
- Renovate HL7 version 3 (Aug 03, 2012)
- Frequency of use of HL7 message types (Jul 24, 2012)
- Lighting the FHIR, HL7s new major interoperability standard (Jun 15, 2012)
- Reflections on the HL7 membership model - the affiliate life cycle (Dec 28, 2011)
- Thinking like an OWL reasoner (Sep 17, 2011)
- RFH (Resources for Health): HL7 version 3 taken to the next step (Aug 18, 2011)
- What's so great about the HL7 organization? (Aug 04, 2011)
- Kerndossier: een Nederlandse versie van CCD (Dutch, May 03, 2011)
- A HL7 RIMBAA update (Apr 21, 2011)
- Timezone Hotel (Mar 29, 2011)
- HL7 and openEHR are cooperating (finally) (Jan 21, 2011)
- Increasing demand for IHE training courses (Dec 18, 2010)
- Context issues with the IHE QED profile (Dec 15, 2010)
- The changing role of HL7 country organizations (Jul 16, 2010)
- Implementing HL7 version 3 - the book (May 06, 2010)
- Adding openness to a closed world (Feb 09, 2010)
- How to lower the hurdle for HL7 v3 implementers (Jan 21, 2010)
- HL7 v3 deployment statistics (Dec 17, 2009)
- There's Trouble in Paradigm (Sep 25, 2009)
- Internationalization of HL7 (Sep 24, 2009)
- HL7 UK signs deal with Ringholm to deliver HL7 v2/v3 training courses in London (Sep 17, 2009)
- The use of HL7 in South Africa (Aug 20, 2009)
- The Next Web Conference in Amsterdam (Apr 17, 2009)
- The HL7 UK AGM and RIMBAA (Apr 16, 2009)
- The HL7 Wiki reaches 2000 pages (Mar 02, 2009)
- The HL7 roadmap for CDA R3 and the CCD (Jan 17, 2009)
- HL7 Affiliates Meeting in Orlando (Jan 11, 2009)
- Swiss and Dutch HL7 News (Dec 31, 2008)
- Devices and Prizes (Nov 22, 2008)
- HL7 in Norway: a situation report (Sep 02, 2008)
- Russian whitepaper (Jul 09, 2008)
- The HL7 Interoperability Conference - IHIC 2008 (May 30, 2008)
- HL7 creates a RIM Based Application Architecture (RIMBAA) group (May 18, 2008)
- Notes from the HL7 WGM in Phoenix (May 08, 2008)
- Germany embraces CDA eReferral document specification (May 02, 2008)
- HL7 v3 RIM based applications: an unintended side effect (Jan 19, 2008)
- Collaborative Tools (Jun 21, 2007)
- HL7 ist Pflicht in der deutschen Telematikinfrastruktur (German, Mar 16, 2007)
- HL7 based Tree inventory system (Jan 30, 2007)
- The link between HL7 and Open Source Software (Jan 06, 2007)
- Workflow Bribery (Sep 15, 2006)
- Timezones in HL7 (Jan 23, 2004)
- Controlled vocabularies: "@*%!!!" ? (Sep 01, 2003)
- Trusting the other Party (Nov 01, 2002)
About Ringholm bv
Ringholm bv is a group of European experts in the field of messaging standards and systems integration in healthcare IT.
We provide the industry's most advanced training courses and consulting on healthcare information exchange standards.
See http://www.ringholm.com or call +31 33 7 630 636 for additional information.
Rene is the Tutor-in-chief of Ringholm.