1. Modelling Configuration Management Investigation HL7UK Technical Committee Charlie McCay Joseph Waller Mike Odling-Smee 9 th December 2008

2. Approach Use cases / examples Requirements / governance / contractual Technical / publishing / wire formats 13/01/2016Modelling Configuration Management Investigation2

3. 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 strategy 13/01/2016Modelling Configuration Management Investigation3

4. Technical Units of change… Modular MIMs… Matrix for specifying configurability… Extended version manifest… Impacts… 13/01/2016Modelling Configuration Management Investigation4

5. 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 13/01/2016Modelling Configuration Management Investigation5

6. 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 13/01/2016Modelling Configuration Management Investigation6

7. Matrix for specifying configurability Class of change against system (type) Setting expectations of change Document current flexibility Basis for improved commercials 13/01/2016Modelling Configuration Management Investigation7

8. 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 13/01/2016Modelling Configuration Management Investigation8

9. Extended version manifest Reduce dependency on just InteractionId instances –Identifier(s) or inline manifest end points, applications –More detailed version support assertions 13/01/2016Modelling Configuration Management Investigation9

10. Impacts Design Process –improved change management process –Convergence with LRA Implementations –Support introduction of minor change –Fallback processing rules –Improved commercials for change 13/01/2016Modelling Configuration Management Investigation10

11. Wednesday, 13 January 2016Modelling Configuration Management Investigation11 Thank you Charlie McCay Ramsey Systems Ltd. www.ramseysystems.co.uk charlie@RamseySystems.co.uk Joseph Waller & Mike Odling-Smee www.xml-solutions.com joseph@xml-solutions.comjoseph@xml-solutions.com; mike@xml-solutions.commike@xml-solutions.com