• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Clinical Models - What Are They Good For?
 

Clinical Models - What Are They Good For?

on

  • 1,237 views

Dr Hugh Leslie

Dr Hugh Leslie
CMO, Ocean Informatics Ltd

Statistics

Views

Total Views
1,237
Views on SlideShare
1,237
Embed Views
0

Actions

Likes
3
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • I want to take you on a journey – moving from the left of the screen to the right.
  • I am a clinician – interested in the C in CDA
  • Increasing complexity & richness of clinical information exchange.Look to the future to make sure what we do now can support what we want to do in the futureIndividual CDA specs are developed for use cases – models end up being different even though they are modelling the same thing.
  • Estimated 7500 clinical systems in the USA alone developed with clinical input to cliniciansComplex technical artifacts are difficult for most clinicians to review and understand without additional training. Getting clinicians in a room is expensive, difficult (time poor)
  • More sophisticated systems need more sophisticated content - fractalVendors – rapidly increasing cost of businessNational Programs – coming to grips with need for models and terminology for national EHR programs
  • To build this clinical content, there is a need for an approach that allows a large number of clinicians and domain experts to collaborate in a cost and time effective way to create content. This content should be approachable for clinicians who have little technical expertise and should not be limited to health informaticians. The outputs from this process should be technical artifacts that can be directly used in information systems without any need for translation of paper specifications.
  • How do we get there? Step back from CDA.To get interoperability we need clinical information that is Consistent ie modelled in the same way everywhere, of high quality –validated by clinicians and using metrics to measure quality and strongly governed – versioned, released like software artefacts.
  • Doesn’t terminology solve the issues of clinical content? Can’t we just code something and get on with it?
  • Clinical models give context to terminology (and semantics generally)You can’t do it with terminology alone (and you can’t do it with clinical models alone…)
  • Doesn’t terminology solve the issues of clinical content? Can’t we just code something and get on with it?
  • There has been and still is, an enormous effort going on in terms of defining data elements as single reuseable entities. Example of VIC Health – minimum datasets.
  • National data collections are seriously importantDefining datasets is importantLets find a way to define them so that the context is clear.
  • So its about recording clinical information faithfullyIts about maximal data set and universal use caseIncludes needed terminology bindings and terminology valuesets
  • Ideal set of archetypes is a venn diagram with no overlap. Almost never a single data element.
  • Its about maximal data set - includes needed terminology bindings and terminology valuesetsMuch easier to get agreement than minimum datasets.
  • So its about recording clinical information faithfullyNot about creating an esoteric and academic model of something that represents that thing.
  • The universal use case.
  • Can be used directly in systems to create and persist data as well as other artefacts – top of an information tool chain.
  • Can be used to do real stuff.Can be used directly in systems to create and persist data as well as other artefacts – top of an information tool chain.
  • Can be used directly in systems to create and persist data as well as other artefacts – top of an information tool chain.
  • Can be used directly in systems to create and persist data as well as other artefacts – top of an information tool chain.
  • Can be used directly in systems to create and persist data as well as other artefacts – top of an information tool chain.
  • CKM demo to show:A couple of models and viewsGovernance aspectsCrowd sourced information
  • We have a set of clinical models that are vetted, governed and fit for purpose – how do we take these and use them everywhere? What is the link to CDA for instance?
  • Template designerQueryingFinish with MeHR

Clinical Models - What Are They Good For? Clinical Models - What Are They Good For? Presentation Transcript