1 / 11

Modelling Configuration Management Investigation

Modelling Configuration Management Investigation. HL7UK Technical Committee Charlie McCay Joseph Waller Mike Odling-Smee 9 th December 2008. Approach. Use cases / examples Requirements / governance / contractual Technical / publishing / wire formats. Requirements. Keep it simple

thomas-beck
Download Presentation

Modelling Configuration Management Investigation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Approach • Use cases / examples • Requirements / governance / contractual • Technical / publishing / wire formats Modelling Configuration Management Investigation

  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 Modelling Configuration Management Investigation

  4. Technical • Units of change… • Modular MIMs… • Matrix for specifying configurability… • Extended version manifest… • Impacts… Modelling Configuration Management Investigation

  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 Modelling Configuration Management Investigation

  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 Modelling Configuration Management Investigation

  7. 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

  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 Modelling Configuration Management Investigation

  9. 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

  10. 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

  11. 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

More Related