Hoot72 Capture The Care Process

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Beyond the paper piles, messages hold our health data.

    Many practitioners - more perfect union Not covering Security or Ownership (both contentious and often take over) Primary and Secondary uses Patient-accessible, Doctor-complete Trial Recruitment, Drug Safety, Outcomes research ... right now, more Iraq, than US

    HL7 holds our health data HL7 everywhere means v2. Don’t Blink or you’ll miss V3. We’ll get back to that ... [ISSUE: should I split this and move graph to v3’s problem ...]

    Of course, more structured than your average tweet Pick out message type, patient name, contact relationship, body weight observation

    Back in the real world Work in progress with codes. Restructuring. Mapping. Entering the Semantic Web. Patient data still off in bunkers

    In brief Key is automatic i.e. requirement

    In brief Key is automatic i.e. requirement

    Surprisingly unlinked. Codes explicit. Composition makes automatic URI hard Id and time not shown In flux: PersonName will probably become FOAF and other demographic stds Missing time

    Favorites, Groups & Events

    Hoot72 Capture The Care Process - Presentation Transcript

    1. Hoot72
      • Capture the Care Process
      www.hoot72.org
    2. A land of Silo’s
      • Health Data in “islands”, “silo’s”
        • Admissions/Pharmacy/Lab ... Systems
        • Billing data does leave the premises!
      • “Clinical Process” data is scattered
      • Research, portable records, management?
    3. Possible? A View for Everyone Linked Health Data Patient Doctor Manager Researcher Insurance IT
    4. Enabler: the Silo’s chat Source: Neotool, V3 vs V2 “ HL7 version 2 is a major breakthrough and market success. More than 93% hospitals in US are using this standard” - Health Level Horizon (HLH) Project
    5. One “tweet” ...
      • MSH|^~&|REGADT|MCM|IFENG||199112311501|| ADT ^A04^ADT_A01|000001|P|2.4|||
      • EVN|A04|199901101500|199901101400|01||199901101410
      • PID|||191919^^GENHOS^MR~371-66-9256^^^USSSA^SS|253763| MASSIE^JAMES^A ||19560129|M|||171 ZOBERLEIN^^ISHPEMING^MI^49849^""^||(900)485-5344|(900)485-5344||S^^HL70002|C^^HL70006|10199925^^^GENHOS^AN|371-66-9256||
      • NK1|1|MASSIE^ELLEN| SPOUSE^^HL70063 |171 ZOBERLEIN^^ISHPEMING^MI^49849^""^
      • |(900)485-5344|(900)545-1234~(900)545-1200|EC1^FIRST EMERGENCY CONTACT^HL70131
      • NK1|2|MASSIE^MARYLOU|MOTHER^^HL70063|300 ZOBERLEIN^^ISHPEMING^MI^49849^""^
      • |(900)485-5344|(900)545-1234~(900)545-1200|EC2^SECOND EMERGENCY CONTACT^HL70131
      • NK1|3
      • NK1|4|||123 INDUSTRY WAY^^ISHPEMING^MI^49849^""^||(900)545-1200|EM^EMPLOYER^HL70131|19940605||PROGRAMMER|||ACME SOFTWARE COMPANY
      • PV1||O|O/R||||0148^ADDISON,JAMES|0148^ADDISON,JAMES||AMB|||||||0148^ADDISON,JAMES|S|1400|A|||||||||||||||||||GENHOS|||||199501101410|
      • PV2||||||||199901101400|||||||||||||||||||||||||199901101400
      • ROL||AD|CP^^HL70443|0148^ADDISON,JAMES
      • OBX||NM| 3141-9^BODY WEIGHT^LN || 62 |kg|||||F
      James was admitted ... his wife is his emergency contact ... here’s his weight ...
    6. What if? From obscure Soup to query-ready Graph OR|20010331605||ORU^R01|20010422GA03|T|2.3.1|||AL|725^^^^MR||Doe^John^Fitzgerald^JR^^^L||20001007|M||2106-3^White^HL70005|123 Peachtree St^APT 3B^Atlanta^GA^30210^^M^^GA067||(678) 555-1212^^PRN||||||||||Peachtree Clinic|101 Main Street^^Atlanta^GA^38765^^O^^GA121|(404) 554-9097^^WPN|101 Main Street^^Atlanta^GA^38765^^O^^GA121|
    7. Graph?
      • Mechanism behind the Web of Data
        • “ common formats for integration and combination of data drawn from diverse sources” -- w3c
      • For the “semi-structured” like Health-data
        • many forms for the “same” thing
    8. Enter Hoot72
      • Hoot (w3c’s OWL), 72 (HL7 v2)
      • A Mapping: message to graph assertions
        • presumes little so generally applicable
      • A Reference Implementation
      • Open Source
    9. Two plus Two Hoot72 Mapper HL7 Messages HL7 Message Definitions Hoot72 Ontology Clinical Data Graph
    10. Observation (OBX) Identifiers and Time not shown PID||| 1234^^^^SR~1234-12^^^^LR~00725^^^^MR || Doe^John^Fitzgerald^JR^^^L | ... OBX|4|CE| 30949-2 ^Vaccination adverse event outcome^ LN |1| H ^required hospitalization^ NIP005 | LN 30949-2 CodingSystem Code H NIP005 CodingSystem Code observation observationValue Doe John Fitzgerald personName familyName givenName middleName context Patient type
    11. Just a query away ...
      • The care-process in one accessible place
      • Follow a patient’s path
      • Analyse a facility’s ways
      • Enable Interoperability
    12. Interested?
      • Hear more?
      • Your messages graphed?
      • Participate?
      Go to: http://www.hoot72.org and Contact!
    SlideShare Zeitgeist 2009

    + hoot72hoot72 Nominate

    custom

    225 views, 0 favs, 1 embeds more stats

    Hoot72 throws light on a health-care facility's car more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 225
      • 214 on SlideShare
      • 11 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 3
    Most viewed embeds
    • 11 views on http://www.hoot72.org

    more

    All embeds
    • 11 views on http://www.hoot72.org

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories