1 / 6

Diversity and Standardization in the Development of Clinical Guideline Models: Room for both

Diversity and Standardization in the Development of Clinical Guideline Models: Room for both. Mor Peleg, Ph.D. Dept. Management Information Systems University of Haifa. Goal: Share Guideline Models. Creating a Computer-interpretable guideline model takes much effort

macey-eaton
Download Presentation

Diversity and Standardization in the Development of Clinical Guideline Models: Room for both

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. Diversity and Standardization in the Development of Clinical Guideline Models:Room for both Mor Peleg, Ph.D. Dept. Management Information Systems University of Haifa

  2. Goal: Share Guideline Models • Creating a Computer-interpretable guideline model takes much effort • Interpretation of content is made during that process • We would like to share the encoded guideline to save effort and enforce consistency

  3. Approaches for Sharing • A repository of guideline models encoded in a guideline formalism • DeGeL (Digital Electronic Guideline Library) (Shahar) • Publets support enactment, encourage review (Fox) • An interchange format for translating between guideline formalisms • An execution engine that supports several guideline formalisms (Wang) • Astandard guideline formalism (HL7 Guidelines SIG) • With authoring, validation, and execution tools

  4. Benefits of a Standard formalism • Ease sharing of encoded guidelines • Concentrate efforts on developing • better tools for authoring, validating, disseminating, executing & revising GLs in the standard format (vendors) • methods to facilitate local adaptation and integration with EMRs and HISs • Compliance with standards: HL7 standards • Should developers encode guidelines in the standard or in specialized formalisms? • If they will encode in specialized formalisms, then parts of the encoding could be mapped to the common format

  5. System Development Life Cycle Determining objectives, alternatives, constraints Evaluating alternatives Identifying risks Prototyping R R C Modeling, simulation Development Verification R Planning next phase R Review C Commitment

  6. Standard Development Life Cycle Determining objectives, alternatives, constraints Why do we want a standard? What components? What functional requirements? Evaluating alternatives Identifying risks Prototyping Examine ideas from GL formalisms Propose new ideas, consensus Open development process R R C Planning next phase Evaluation What should be the next component? Need ideas from continuing research Experiment with mixing component using Publets Modeling, simulation Development Verification Defining the standard components Working out examples Testing implementing R R Review C Commitment

More Related