110 likes | 229 Vues
This document outlines the findings of the HL7UK Technical Committee on configuration management, led by Charlie McCay, Joseph Waller, and Mike Odling-Smee. It delves into the requirements, governance, and standardization of technical publishing and wire formats. Key components include use cases, modular MIM configurations, and strategies for managing change while ensuring compliance with HL7 versioning. The team's insights aim to foster a structured approach to configuration management in healthcare IT systems, emphasizing traceability and phased deployment.
E N D
Modelling Configuration Management Investigation HL7UK Technical Committee Charlie McCay Joseph Waller Mike Odling-Smee 9th December 2008
Approach • Use cases / examples • Requirements / governance / contractual • Technical / publishing / wire formats Modelling Configuration Management Investigation
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 Modelling Configuration Management Investigation
Technical • Units of change… • Modular MIMs… • Matrix for specifying configurability… • Extended version manifest… • Impacts… Modelling Configuration Management Investigation
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 Modelling Configuration Management Investigation
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 Modelling Configuration Management Investigation
Matrix for specifying configurability • Class of change against system (type) • Setting expectations of change • Document current flexibility • Basis for improved commercials Modelling Configuration Management Investigation
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 Modelling Configuration Management Investigation
Extended version manifest • Reduce dependency on just InteractionId • instances • Identifier(s) or inline manifest • end points, applications • More detailed version support assertions Modelling Configuration Management Investigation
Impacts • Design Process • improved change management process • Convergence with LRA • Implementations • Support introduction of minor change • Fallback processing rules • Improved commercials for change Modelling Configuration Management Investigation
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.com; mike@xml-solutions.com Modelling Configuration Management Investigation