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
Hoot72 Capture The Care Process - Presentation Transcript
Hoot72
Capture the Care Process
www.hoot72.org
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?
Possible? A View for Everyone Linked Health Data Patient Doctor Manager Researcher Insurance IT
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
James was admitted ... his wife is his emergency contact ... here’s his weight ...
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|
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
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
Two plus Two Hoot72 Mapper HL7 Messages HL7 Message Definitions Hoot72 Ontology Clinical Data Graph
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
Hoot72 throws light on a health-care facility's car more
Hoot72 throws light on a health-care facility's care-process. It transfers clinical data into the Semantic Web from HL7 messages being exchanged by Health-care applications. less
0 comments
Post a comment