I think it's cost-effective to support find people with high A1C, whatever
each site decides that means using i2b2's ability to represent out-of-range
lab results categorically (observation_fact.valueflag_cd).
But I'm not aware of any requirement that GPC define network-wide numeric lab
In our pragmatic model we will be providing metadataxml for common tests,
defaulting our lab ranges since the i2b2 query tool only shows that as a
guideline. In the case of HbA1C, virtually all results will be 'abnormal'
('high') since we are chiefly ordering the test in followup of diabetes.
In order to determine whether we have critical mass for a Nov 25 meeting,
please indicate whether you're available using this doodle poll:
* gpc-dev 25 Nov vs Thanksgivinghttp://doodle.com/ubkycws2p6gfx5r9
--
Dan
___
Gpc-dev mailing list
#90: Diagnoses Modifiers for data attribution
--+
Reporter: campbell | Owner: nateapathy
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains2
Component: data-stds |
#90: Diagnoses Modifiers for data attribution
--+
Reporter: campbell | Owner: nateapathy
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains2
Component: data-stds |
Hi all, hoping some of you are in a good state of mind to share your
experience, brilliance, shattering good looks... enough flattery?
Anyway, my first attempt at building a NAACCR ontology was disappointing in
that the NAACCR tables were not as helpful as I expected. Fundamental problem:
A
#90: Diagnoses Modifiers for data attribution
--+
Reporter: campbell | Owner: nateapathy
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains2
Component: data-stds |
#90: Diagnoses Modifiers for data attribution
--+
Reporter: campbell | Owner: nateapathy
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains2
Component: data-stds |
