400 likes | 528 Views
Health eDecisions (HeD) All Hands Meeting. January 16th, 2014. Meeting Etiquette. Remember: If you are not speaking, please keep your phone on mute Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call
E N D
Health eDecisions (HeD)All Hands Meeting January 16th, 2014
Meeting Etiquette • Remember: If you are not speaking, please keep your phone on mute • Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call • Hold = Elevator Music = frustrated speakers and participants • This meeting is being recorded • Another reason to keep your phone on mute when not speaking • Use the “Chat” feature for questions, comments and items you would like the moderator or other participants to know. • Send comments to All Panelists so they can be addressed publically in the chat, or discussed in the meeting (as appropriate). From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute All Panelists
Announcements • Our Ballots close January 20th • Ballots are still open so please vote if you are a voting member of HL7 if you are not please submit your comments to a member of the HeD support team and we will compile a “submitted by the HeD Community” list of comments • Our All Hands meeting (January 23rd) is CANCELED next week due to HL7 – we will resume meeting January 30th • Updates on HL7 meeting and activities including follow-up tasks and plans
SDS & Harmonization HeD • Timeline Overview • Ballot Votes
HeD Use Case 2 Timeline Publish Artifacts Dec 30 (1/24) (2/7) (1/10) Feb 21 (Today) Ballot Reconciliation vMR Templates Publishing Artifacts Legend: Not Started; In progress; Ready 7
HeD Use Case 2 Timeline Overview • All six HeD artifacts, including both UC1 & UC2, have been published • vMR Templates, vMR Logical Model, and vMR XML IG have been submitted for re-ballot on 12/19, with the ballot closing on 1/20 • Continue to communicate between QI and HeD initiatives to ensure proper harmonization & development of the QI model • Determine next steps for alignment with the Tacoma Project
SDS & Harmonization HeD • Timeline Overview • Ballot Votes
A Model-drivenEditorforHealthe-DecisionsKnowledgeArtifacts Robert Greenes, MD, PhD Davide Sottara, PhD Peter Haug, MD, PhD Matthew EbertEdinardoPotrich
Outline • Requirements • Architecture • Features • Roadmap
Requirements • Build a scalable CDS Artifactauthoringtool • user (SME)-friendly • compatible with the HeD standard • Rules / OrderSets / DocumentationTemplates • (future) Measures / Guidelines • Assistingwith the management oflargeknowledgebases • facilitating customization / localization • facilitating storage / indexing / retrieval • facilitating integration / deployment
Goals • Short Term • Allowto create / modifyHeDdocuments • Long Term • Automate the authoringprocess • Managelargeknowledgebases • Integrate editing and runtimeplatforms
Architecture - --- Core Presentation AddedValue AuthoringKnowledge Model ArtifactInstance Runtime XML DB Future
Architecture (technical) UIHTML+JS REST - WS GraphML Graph manipulation HeD SHARP Reasoner(s)HermiiTDrools XML OWL (A-Box) Java CTS2 Abstraction Layer Stanbol (Semantic) Content Management Systems Persistency
ModelDrivenApproach • OntologyBased • Modular • Decouples: • ArtifactModel : HeDontologies • Information Model : vMR / SKOS • Terminologies : CTS2 integration • CompatiblewithStandards • HL7, OMG • Advantages : • Schemas and Code generation • Robustw.r.t.changes • Serializationagnostic • Transparent • Addsemanticsto the syntax Model
Persistence • Supportedstorageformats: • XML (filesystem) • CMS (Stanbol) • Compatible(tobeimplemented) • ObjectStore • Relational Database • Triple Store ArtifactInstance XML DB
Deployment • Model-driventranslationintoactionableformats • HeD • Compatible(mappingexists, tobeimplemented) • Arden (ML) • Drools ArtifactInstance Runtime
User Interface • Browser-Based • Html + javascript • “Core” functionalitiesexposedas REST-WS • Deployable on the cloud
Templates Abstract“Patient on Med” Primitive Template Semantic(graph-based) “Med” HeDDatatypes Parameters ExpressionTemplates Classification elements constraints “Aspirin ?” Querybyexample
Roadmap • January – March 2014 • Consolidate the coreeditor • UI Improvement, Bug fixes, Usability, … • Complete and release the templatelibrary • Prepare a redistributable package • Source code (Maven) • VirtualMachineImage
Roadmap • Community Engagement • Code available on GitHub • https://github.com/SHARPC2B/HeD-editor • Licensed under ASLv2.0 • Documentation, Website, Demos • ScientificPaper(s) • Collaborators
Roadmap • Future Works • Build a KnowledgeRepository • Semantic CMS • Versioning • Managerelationshipsbetweenartifacts • Integrate RuntimeEnvironments • “Customize and Deploy”
Contact Information • For questions, please contact your support leads • Coordinator: • Ken Kawamoto: kensaku.kawamoto@utah.edu • Co-Coordinators: • Aziz Boxwala: aziz.boxwala@meliorix.com • Bryn Rhodes: bryn@veracitysolutions.com • ONC Leadership: • Alicia Morton: alicia.morton@hhs.gov • Project Management: • Jamie Parker: jamie.parker@esacinc.com • Use Case 2: • AtanuSen: atanu.sen@accenture.com • Harmonization: • DivyaRaghavachari: divya.raghavachari@accenturefederal.com
Useful Links • Wiki • http://wiki.siframework.org/Health+eDecisions+Homepage • Use Case 1& 2 • http://wiki.siframework.org/Health+eDecisions+Use+Case • UC 2: Use Case 2: http://wiki.siframework.org/UC+2+-+CDS+Guidance+Service • Pilots • http://wiki.siframework.org/Health+eDecisions+Pilots • HL7 Ballot Submission: • http://wiki.siframework.org/Health+eDecisions+Reference+Materials#Ballot • UC 1 Harmonization and IG: • http://wiki.siframework.org/Health+eDecisions+Harmonization+and+Standards+%28Implementation%29 • HeD Glossary • http://wiki.siframework.org/HeD+Glossary