Modelling Configuration Management Investigation

HL7UK Technical CommitteeCharlie McCayJoseph Waller

Mike Odling-Smee

9th December 2008

Approach

• Use cases / examples• Requirements / governance / contractual• Technical / publishing / wire formats

19/04/23 Modelling Configuration Management Investigation 2

Requirements

• Keep it simple• Some change is unavoidable• Traceable, testable change• Users work with “compliance modules”

not domains• Live build baseline specifications• Support for phased deployment

– One version in the wild is not practical

• Consistent with HL7 versioning strategy19/04/23 Modelling Configuration Management Investigation 3

Technical

• Units of change…• Modular MIMs…• Matrix for specifying configurability…• Extended version manifest…• Impacts…

19/04/23 Modelling Configuration Management Investigation 4

Units of change

• Technical configuration Items– ValueSets, Schemas, Templates– Tightly defined with identity criteria and

versioning rules

• Domain Specific Configuration Items– Prescription Exemption Codes– Dosage expression

• Configuration Item relationships – Uses, extends, constrains, etc

19/04/23 Modelling Configuration Management Investigation 5

Modular MIM

• Baseline specifications includes– Compliance documents, MIM, EIS parts, etc– All specification documentation in one place

• Compliance Module and Domain view– Built using dependency relationships

19/04/23 Modelling Configuration Management Investigation 6

Matrix for specifying configurability

• Class of change against system (type)• Setting expectations of change• Document current flexibility• Basis for improved commercials

19/04/23 Modelling Configuration Management Investigation 7

Publication

• Annotated change reports What would be useful?

• What about transforms?– Mappings are useful– Needs business rules and vocabulary– Transforms ARE being done under the hood

in all implementations

19/04/23 Modelling Configuration Management Investigation 8

Extended version manifest

• Reduce dependency on just InteractionId• instances

– Identifier(s) or inline manifest

• end points, applications– More detailed version support assertions

19/04/23 Modelling Configuration Management Investigation 9

Impacts

• Design Process– improved change management process– Convergence with LRA

• Implementations– Support introduction of minor change– Fallback processing rules– Improved commercials for change

19/04/23 Modelling Configuration Management Investigation 10

Wednesday 19 April 2023 Modelling Configuration Management Investigation 11

Thank you

Charlie McCay

Ramsey Systems Ltd.www.ramseysystems.co.ukcharlie@RamseySystems.co.uk

Joseph Waller & Mike Odling-Smeewww.xml-solutions.comjoseph@xml-solutions.com; mike@xml-solutions.com