Good news for Epic sites and ETL prep for physical data!  Although only the 
last set of vitals go into the encounter record, it appears from my review of 
chart data compared to Clarity for Epic 2012 that all instances of vitals and 
flowsheet data are extracted into IP_FLWSHT_MEAS.

select m.fsd_id, m.flo_meas_id, m.RECORDED_TIME, m.MEAS_VALUE, m.EDITED_LINE
from ip_flwsht_meas m
join ip_flwsht_rec r
on m.fsd_id = r.fsd_id
where r.pat_id = 'ZNNNNN'
order by  m.recorded_time, m.flo_meas_id

Mapping on the basis of FLO_MEAS_ID to LOINC codes will give standardized 
coding for those variables.  These are my exemplar maps for core vitals signs 
for Nebraska system:

24824   R GISURG WEIGHT
14      WEIGHT/SCALE
111     WEIGHT  oz
11      HEIGHT  inch
24822   R HEIGHT
19      VITALS - BODY MASS INDEX
301070  BMI CALCULATED
24823   R GISURG BMI
304200886       R IP FN BMI PERCENTILE RANK
9       Respiratory rate        cyc/min
20      VITALS - BODY SURFACE AREA
5       BLOOD PRESSURE (COMPLEX FORMAT NNN/NN)  mmHg
6       TEMPERATURE     Fahrenheit
8       PULSE
10      PULSE OXIMETRY
18      PAIN SCORE

I had a call with Epic yesterday that indicated they were going to support 
mapping in EXM for LOINC codes soon.  Please check your system flowsheet row 
assignments  for some of the variables above.  I suspect that the lower row 
numbers are model system and may be consistent across sites in which case we 
will be able to generate 'starter set' LOINC mapping when supported by Epic
Jim


James R. Campbell MD
[email protected]<mailto:[email protected]>
Office 402-559-7505
Secretary 402-559-7299
Fax 402-559-8396
Pager 402-888-1230



The information in this e-mail may be privileged and confidential, intended 
only for the use of the addressee(s) above. Any unauthorized use or disclosure 
of this information is prohibited. If you have received this e-mail by mistake, 
please delete it and immediately contact the sender.
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to