FHIR Chat · Life cycle governance principles · fgb (archived)

Stream: fgb (archived)

Topic: Life cycle governance principles


view this post on Zulip Grahame Grieve (May 22 2017 at 20:46):

hi All - on this weeks call, a few of us discussed what issues are at play for FGB. Most of the noise - that is unhappy - that I am hearing is around life cycles, versions, rate of change...

view this post on Zulip Grahame Grieve (May 22 2017 at 20:47):

we agreed to work on this at a governance level over the next little while - to lay down our goals and precepts for this subject

view this post on Zulip Grahame Grieve (May 22 2017 at 20:48):

this is a prompt for anyone who wants to share some initial thoughts on this matter (and also a prompt for me not to forget about it)

view this post on Zulip Grahame Grieve (Jun 19 2017 at 03:30):

so since we are meeting this week. here's a strawman for discussion:

view this post on Zulip Grahame Grieve (Jun 19 2017 at 03:30):

Life Cycle Governance
The life cycle strategy is a combination of
• the rules that describe what changes may be made between versions of FHIR, for what level of maturity of artefact
• the technical facilities provided for implementers to communicate about the version they are using
• The facilities provided in the specification itself for converting content between versions
Together these enable and/or constrain the ways implementers can deal with ongoing changes in the FHIR standard.
Governing Principles:
• There will be a clearly documented versioning strategy
• Changes to it will be discussed transparently and with multiple opportunities for comment from FHIR implementers
• Known risks around the versioning strategy will be documented
• The versioning strategy will provide confidence to FHIR implementers about what steps to take to protect their investment going forward
• The specification will clearly document for the community what processes are in place to test the versioning strategy, and to gather feedback about in in a transparent manner
• The specification should recommend one or more best-practices for handling inter-version change
• The FMG is responsible for ensuring that these principles are executed in the specification


Last updated: Apr 12 2022 at 19:14 UTC