The Healthcare Enterprise Repository for Ontological Narration (HERON) is a method to integrate clinical and biomedical data for translational research.
- HERON cohort discovery queries can span the EMR from KUH and an increasing list of other sources for retrospective studies.
- HERON queries can give you hard data on how many patients come through KUH that meet the criteria of your next clinical trial.
- Combined with the Frontiers participant registry, HERON can even give you contact information to support recruitment directly.
To get started, see HERON Training Materials.
Or if you're a returning HERON user, proceed directly to:
Please cite us as:
- Waitman LR, Warren JJ, Manos EL, Connolly DW. Expressing Observations from Electronic Medical Record Flowsheets in an i2b2 based Clinical Data Repository to Support Research and Quality Improvement. AMIA Annu Symp Proc. 2011;2011:1454-63. Epub 2011 Oct 22.
Progress, History, and Plans
- HERON Team offers support for complex searching, data access
- HERON Saline Release integrates 1.6 billion observations from 8 data sources
- HERON Hackberry release includes emergency, inpatient and outpatient encounter data
- HERON Marmaton introduces Cardiology labs and BMI percentile data
- KUMC receives PCORI award to lead Greater Plains Collaborative
- HERON Lovewell improves navigation and fixes Frontiers patient count issue
- HERON Toronto update powered by newer, faster hardware and load process
- HERON Milford simplifies the Cancer Cases folder
- How to prepare your REDCap project to be loaded into HERON?
- HERON Solomon marks the 32nd consecutive release
... see HERONAnnouncements for the full list.
Training and Support
- Ask the Clinical Informatics Coordinator for help via the feedback form or at 5-7470.
- The FrontiersInformaticsClinic meets every other week. Register in advance if possible but drop-ins are welcome.
- Send a question to the HERON-USERS@LISTSERV.KUMC.EDU or review the mailing list archive.
Data Sources and Monthly Update Process
Our initial approach is to get dumps from the source systems, wipe out our store in nightHERON for i2b2 and reload it all, reassigning i2b2 internal patient, provider, visit ids.
- Data Sources
- ClinicIdxSource (including HICTR)
- UHCSource (billing diagnoses and DRGs)
- KUH TumorRegistry for NCI designation
- BiospecimenRepository (#517)
- ... things like CRIS, CoPath?, GME, and biospecimens will follow; April DROCMeetingMinutes? has a list:
- SMS (lower priority; UHC data meets most of the relevant needs)
- CRIS/REDCap (clinical trial enrollment and registries)
- Read only Chronicles Access for Content not included in Clarity #20
- HeronLoad monthly update process
Bring-up and some configuration notes on the machines are in:
- #80 - bring up identified server hardware, os
- #82 - bring up de-identified database server
- #43 - bring up virtual server for production web services
Open Source ETL Code
Our presentation materials may help with the bigger picture; in particular:
- Using Python and Paver to Control a Large Medical Informatics ETL Process presented at PyData? Silicon Valley May 3, 2014
- LabDiscussion January 31, 2011
- LabDiscussion2 February 11, 2011
- MedDiscussion March 7, 2011
- LoincMapping? largely obsolete as of #311 milestone:heron-apr-update
Leveraging NIH funded i2b2 framework
Per section C.2.2. Implement cost effective, researcher-centric solutions while preserving patient privacy and respecting community trust among disparate participating organizations by leveraging open source and existing NIH funded initiatives of the CTSA grant application:
User access, activity logs, and project management for the de-identified repository is managed via the i2b2 framework ...
Governance (DROC), Privacy (De-identification), and Security
Governance is provided by an executive committee and the Data Request Oversight Committee (DROC). All three contributing organizations: the University of Kansas Medical Center, the University of Kansas Hospital and the University of Kansas Physicans Incorporated are represented and contribute to making this initiative possible.
- DROCMeetingMinutes? and oversight issues
See section C2.1. Develop repeatable business agreements, policies, data use agreements and oversight for organization inclusion in KUMC HICTR CTSA outline for more scenarios. For reference:
- Final legal agreement for HERON with System Access Agreement
- Signed master agreement for medical data sharing
- HERON IRB protocol original 2010-2011
- HERON IRB protocol revised for 2011-2012
Another design consideration is de-identification of data and then what's kept on blue HERON. See DeIdentificationStrategy.
This work was supported by a CTSA grant from NCRR and NCATS awarded to the University of Kansas Medical Center for Frontiers: The Heartland Institute for Clinical and Translational Research # UL1TR000001 (formerly #UL1RR033179). The contents are solely the responsibility of the authors and do not necessarily represent the official views of the NIH, NCRR, or NCATS.
(51.1 KB) -
added by dconnolly 5 years ago.
HERON arch from Russ's msg of 07/12/2010 09:48:12 AM
(318.0 KB) -
added by rwaitman 4 years ago.
HERON IRB protocol
(62.5 KB) -
added by rwaitman 4 years ago.
Final legal agreement for HERON with System Access Agreement
(793.7 KB) -
added by rwaitman 3 years ago.
HERON IRB renewal version 2
(316.0 KB) -
added by ngraham 6 months ago.
New architecture diagram as per meeting 2014.09.10, #2894
Download all attachments as: .zip