OK, good to see progress. Now that discussion has moved from "what does it mean to lead a domain?" to lab hierarchy details, it'll be easier to find with a more relevant subject.
-- Dan ________________________________ From: Campbell, Walter S [wcamp...@unmc.edu] Sent: Tuesday, October 07, 2014 2:21 PM To: Dan Connolly; Campbell, James R; Hickman, Hubert B Cc: gpc-dev@listserv.kumc.edu Subject: RE: 10 Sites x N Domains and the GPC Interoperable Standardization Measurement Framework Hi Jim and Dan, I am proposing the following lab data hierarchy and am working with Hubert to create sample data for comment by other sites. Proposed hierarchy: 1. Labs by department (e.g., chemistry, hematology, micro, etc) 2. Lab panel groupings by department 3. Similar lab test groupings (eg., A1C’s by different methods) W. Scott Campbell, MBA, PhD Assistant Professor Director of Public Health Laboratory Informatics and Pathology Laboratory Informatics Department of Pathology/Microbiology University of Nebraska Medical Center 985900 Nebraska Medical Center Omaha NE 68198-5900 402-559-9593 (office) 402-350-7851 (mobile) ====Privacy Statement==== ATTENTION: This electronic document may contain confidential information and is intended for use by the addressee and/or their intended representative only. Review by unintended individuals is prohibited. If you are not the intended recipient, please do not read, transmit, copy, disclose, store or utilize this communication in any manner. If you received this message in error, please notify the sender immediately and permanently delete this message from your computer. Thank you. From: Dan Connolly [mailto:dconno...@kumc.edu] Sent: Tuesday, October 07, 2014 2:03 PM To: Campbell, James R; Campbell, Walter S; Hickman, Hubert B Cc: gpc-dev@listserv.kumc.edu Subject: RE: 10 Sites x N Domains and the GPC Interoperable Standardization Measurement Framework I had UMN and CMH as the other lead sites on labs, not Marshfield. But the more the merrier. Please do include CMH in early stages of discussion of labs. -- Dan ________________________________ From: Campbell, James R [campb...@unmc.edu] Sent: Tuesday, October 07, 2014 1:52 PM To: Dan Connolly; Campbell, Walter S; Hickman, Hubert B Cc: gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu> Subject: Re: 10 Sites x N Domains and the GPC Interoperable Standardization Measurement Framework Dan I agree that we need a more usable hierarchy for aggregating common lab data and Scott is working on a prototype for UNMC employing all LOINC coded lab. We plan to share with UMN and Marshfield for their thoughts on the organization and then distribute a common path to GPC-DEV. I agree that we should be having our ETL managers researching the depth of LOINC coding at each of our sites now and Hubert and Scott can share the Clarity procedures to check this out with each of our Epic sites. James R. Campbell MD campb...@unmc.edu<mailto:campb...@unmc.edu> Office: 402-559-7505 Secretary: 402-559-7299 Pager: 402-888-1230 On Oct 7, 2014, at 3:42 PM, "Dan Connolly" <dconno...@kumc.edu<mailto:dconno...@kumc.edu>> wrote: Nathan (of CMH, not KUMC) asked me what it means to lead on labs. My current expectation is two things: 1. Set the standard for lab metadata in babel, especially the concept paths. Deliver both a metadata CSV file and details on how it's built (from LOINC materials) and where to get the data for these terms (which workflows and perhaps i2b2 modifiers, which Epic clarity tables, etc.) Ideally work with cohort leads to develop queries that exercise labs. Work out any essential details around units etc. For bonus points, supply test data that we can put on babel. 2. Help other sites match this standard so that, for example, babel can show aggregate counts at each level of the hierarchy across all sites. We had agreed on a standard for lab metadata (#68<https://informatics.gpcnetwork.org/trac/Project/ticket/68>) but now we're trying to find something with better usability (#158). Currently diagnoses, vitals, and cancer cases are resolved and the others have details pending: * GPC Demographics (#67<https://informatics.gpcnetwork.org/trac/Project/ticket/67>) * Pediatric Weight and Health CC needs contact info? * GPC Diagnoses (#63<https://informatics.gpcnetwork.org/trac/Project/ticket/63>) * GPC Encounters (#155<https://informatics.gpcnetwork.org/trac/Project/ticket/155>) * GPC Enrollment * GPC Procedures * GPC Vitals (#23<https://informatics.gpcnetwork.org/trac/Project/ticket/23>) * GPC Labs (#68<https://informatics.gpcnetwork.org/trac/Project/ticket/68>) * GPC Medications (#78<https://informatics.gpcnetwork.org/trac/Project/ticket/78>) * GPC Cancer Tumor Registry For aggregate counts on babel, I'm thinking of a separate i2b2 project so that the paths don't collide. I have been talking about it with Nathan (@KUMC) a bit but we haven't made any tangible progress. Anybody who wants to help, please let me know. Meanwhile, you could, for example, get familiar with the status of LOINC coding at each site. And you could narrow the target from all labs to some prioritized list of labs by collaborating with the cohort groups. I'm tracking this effort (for all domains) as trac milestone data-domains2<https://informatics.gpcnetwork.org/trac/Project/milestone/data-domains2>, currently scheduled for mid November to match PMO milestone 2.4. -- Dan ________________________________ From: Dan Connolly Sent: Monday, September 08, 2014 6:55 PM To: gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu> Subject: 10 Sites x N Domains and the GPC Interoperable Standardization Measurement Framework Since Russ returned from vacation, he and Nathan and I have had a couple catch-up/planning discussions. The whiteboard evolved into a spreadsheet that looks at where we are on standardization of our data domains (Demographics, Diagnoses) as well as deployment of the standard at each site: * sites_gpc_ontology<https://docs.google.com/spreadsheets/d/1-uW2hod63gdlNlLAkhleuMvnQG6zNaw2jd-CAhSLqkk/edit#gid=208670379> (open for view and comment; current copy attached) I don't expect it's self-explanatory, but please do have it handy on the call tomorrow, and if you get a chance to look at it in advance, please do. -- Dan _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu<mailto:Gpc-dev@listserv.kumc.edu> http://listserv.kumc.edu/mailman/listinfo/gpc-dev 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
