1 / 21

Template Exchange ITS Preliminary Report Project # 885

Template Exchange ITS Preliminary Report Project # 885 . Andy Stechishin , Mark Shafarman , Kai Heitmann. Dr Kai U. Heitmann Heitmann Consulting and Services, Germany Past Board Member, HL7 International Chair , HL7 Germany.

hisoki
Télécharger la présentation

Template Exchange ITS Preliminary Report Project # 885

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. Template Exchange ITSPreliminary Report Project #885 Andy Stechishin , Mark Shafarman, Kai Heitmann Dr Kai U. Heitmann Heitmann Consulting and Services, GermanyPast Board Member, HL7 InternationalChair, HL7 Germany HL7 Working Group Meeting Baltimore, US, September 2012

  2. Agenda • History and drivingforce • Objectives • Requirementanalysis • DECOR • Chapter I: C-CDA and Trifolia • Coming upnext

  3. History and drivingforce • Multiple (national/international) groupscreatingHL7 CDA templatesindependently • Creationof a (canonical) format for template specifications • Exchange of templates between groups / tools • Template Repository • Artefact Registry

  4. Objectives • Knowledge sharing • Creating new templates or new versions of templates • Version management support • Support implementations using templates • Persistent storage • Consistent documentation of templates

  5. Step 1: Requirements analysis • Existing template tools • Model-Driven Health Tools (MDHT) • Trifolia Workbench • DECOR • Templates Registry Business Process Requirements • Model Interchange Format (MIF) • Severalotherapproaches, e.g. UK, NZ • Howfits FHIR intothegame?

  6. Project #885 • HL7 Templates ITS Pilot • sub-project of #272 (Templates DSTU) • Creating an ITS that supports an interchange format in a canonical form for HL7 CDA templates • DECOR methodology as a candidate for that format

  7. DECOR:Skills +developmentcycle

  8. DECOR’s “separation of concerns” • Terminologists • Software-Vendors • DECOR • => Data-Elements,Codes, OID‘s and Rules • Goal: consistent artefactdocumentation, generation ofsupporting materials for • Implementation • Validation • Testing, Qualification, Certification • Change Management • Architects • Certificators • HL7 Experts

  9. DECOR projects “worldwide” • ELGA (AT), national infrastructure – CDA • RIVM (NL), national screening programme on bowel cancer – CDA • QiN/KfH(DE), dialysis treatment data exchange – Care Provision • Nictiz (NL), multiple projects, e.g. • Perinatology – CDA and Care Provision • Laboratory results for pharmacists – Orders • Care Transfer Data – CDA • GP Acute Care – Care Provision • Youth Health Care – Care Provision, Immunization

  10. Chapter I: C-CDA and Trifolia • Trifolia templates “data”  DECOR template • 2 step conversion (by xslt’s) • Keith Boone: extract from sql database • Kai: transform to DECOR

  11. Overviewtemplates(in ART, theinterfacetoDECOR)

  12. Value Sets • Integrated terminologyservices

  13. Chapter I: C-CDA and Trifolia • Material • ~ 140 templates of various types • ~ 40 value sets • Results • Conversion succeeded • DECOR Value set and templates documentation • Generation of schematron

  14. Tabularview One of many ways to present DECOR templates Distraction from “fixed” items Focus on instance construction Validation as a “side-effect” Youractualworkstartshere!!!

  15. Chapter I: C-CDA and Trifolia • Further findings • Need of an extendedversionmanagement(whichisrequiredby DECOR) • Id and Name • Version date • Status code • Template lifecyclesupport • Templates Meta Data (seeTemplates Registry Business Process Requirements) • Artefact Registry (HingX)

  16. Chapter I: C-CDA and Trifolia • Further findings • DECOR woulduselessembeddedschematronassertions • e.g. forchoices, data type assertionscount(cda:assignedPerson | cda:representedOrganization)=1SHALL containexactlyone [1..1] assignedPersonexactlyone [1..1]representedOrganization • C-CDA: mean # ofschematron per template: 1.1 • ELGA: 133 templates, 17 inline asserts (mean 0.13) • General problem: expressionofco-constraints

  17. Chapter I: C-CDA and Trifolia • Further findings • Reuse • „This reference/@value SHALL beginwith a '#' and SHALL pointtoitscorresponding narrative (usingtheapproachdefinedin...“ • Repeated 14 timeswith different conf-x • Consistency

  18. Chapter I: C-CDA and Trifolia • C-CDA (from Trifolia) can be expressed in DÉCOR • “Manual” enhancements possible • Conceptual enhancements

  19. Coming upnext • Model-Driven Health Tools (MDHT) • Completely different approach • Model Interchange Format (MIF) • FHIR • Profiles ~ Templates • Not really in the focus of the group yet • XML based profiles, small group of volunteers to proceed on expressing FHIR profiles in DECOR • Results will be available on the HL7 wiki

  20. Thankyou!More questions? Templates Exchange ITS Dr Kai U. Heitmann Later? mailto:hl7@kheitmann.de

More Related