Since observation_fact seems to have no good way to represent a date fact 
natively, we could use an integer to represent the date as a Julian date, which 
we could convert back to a 'regular' date when needed.  I don't know if I like 
this though - but it is one way to express a date fact in the observation_fact 
table.  Oracle has conversion functions for Julian dates.

H2

From: gpc-dev-boun...@listserv.kumc.edu 
[mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of Phillip Reeder
Sent: Thursday, July 24, 2014 1:35 PM
To: gpc-dev@listserv.kumc.edu
Subject: PCORI Mapping

I'm working with the i2b2 PCORI terms that Dan created and attempting to map 
the demographics to our local UTSW terms.  I've mapped the PCORI Sex, Gender, 
and Hispanic which are pretty straight forward.  I simply put our local 
corresponding c_fullname into the dimcode field of the PCORI terminology and it 
now allows me to query the pcori terms through our existing i2b2 dataset.

For birth date & birth time, we currently have the birth date stored in the 
patient dimension.  Is there a proposed way to handle querying for this through 
i2b2?

I can map \PCORI\DEMOGRAPHIC\BIRTHDATE and have it return all patients that 
have a birthdate in the patient dimension which will work for getting the 
counts.  That seems like it may be a good way to show compliance, but it 
doesn't allow you to query the date/time by value.

Does anyone have a good method for handling this through i2b2, or should we 
plan to write a SQL query outside of i2b2 to get the numbers for the GPC Site 
Population Data Summary?   Thoughts?

Phillip Reeder
UT Southwestern




________________________________

UT Southwestern Medical Center
The future of medicine, today.

________________________________

The Nebraska Medical Center E-mail Confidentiality Disclaimer

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
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to