Russ I haven't discussed this personally with Dan Vreeman but I suspect that this is paralleling some of the work that Regenstrief-IHTSDO are doing to harmonize (and ontologize) Observable entities. (Both LOINC and SNOMED CT have concepts pertinent to Observeable entities)
The groups codes that Dan is releasing are a step in that direction of creating a master hierarchy for the LOINC community but my review of the current draft is that it has modest coverage of our common labs. The metadata we are preparing at UNMC for i2b2 will cover the 1600 or so lab LOINC concepts deployed at our institutions and will be built from an ontological defining of the LOINC concepts using the RI/IHTSDO concept model that has been under development the past several years. In plain terms, UNMC will be publishing a free for use ontology of common lab LOINC codes (OWL format) along with an i2b2 metadata for SCILHS that will cover the lab codes in common use at our institutions. The work issued by RI/IHTSDO missed a number of lab codes GPC sites use and we are adding those and finalizing our ontology build. We will be posting that to NCBO and updating every six months if Harvard agrees to the approach and approves the content. I hope to have this out in a couple weeks as we have a call to discuss with Jeff Klann and Shawn Murphy week after next. UNMC has also offered its services in this regard to TranSmart and I would ask any i2b2 community members who are interested in ONC standard metadata support to drop me an email as I have been encouraged to gather stakeholders interested in collaborating on i2b2 metadata standardization. Jim ________________________________ From: Gpc-dev <[email protected]> on behalf of Russ Waitman <[email protected]> Sent: Thursday, July 27, 2017 5:55 PM To: [email protected]; [email protected]; members; '[email protected]'; PCORnet DRN OC ([email protected]) Subject: LOINC alpha release of LOINC groups. Hi Everyone, This is just an informational item but wanted to share that LOINC led by Dan Vreeman has released a project to create groups for LOINC terms. This may be very useful for our communities (CTSA, PCORnet, i2b2, etc). https://loinc.org/groups/ They are now in the latest June release of LOINC. https://loinc.org/news/loinc-version-2-61-and-relma-version-6-20-available/ Jim Campbell: given your interest as well in clinical observables I didn’t know if this crossed your radar. Most of the groups are for lab results as well as clinical observables and seem less bloated as an organizational construct than panel. But, it’s not complete yet. I think Dan and LOINC have already reached out to the OHDSI community but wanted to cross pollinate with PCORnet, i2b2, and CTSA iDTF. He and Katie may follow up with more detail. Or, just get a LOINC account and help out by commenting on their forum as you consider how LOINC groups might help your informatics needs. Sincerely, Russ Waitman, PhD Director of Medical Informatics Associate Vice Chancellor for Enterprise Analytics Professor, Department of Internal Medicine University of Kansas Medical Center, Kansas City, Kansas 913-945-7087 (office) [email protected]<mailto:[email protected]> http://www.kumc.edu/ea-mi/ http://informatics.kumc.edu<http://informatics.kumc.edu/> http://www.gpcnetwork.org<http://www.gpcnetwork.org/> – a PCORnet collaborative www.pcornet.org<http://www.pcornet.org> >From the release notes: LOINC GroupFile release notes ----------------------- Version 2.61, Alpha 1 Released June 2017 ----------------------- This is the first release of the LOINC Group artifact. This release contains 6597 rows of data representing 12 Parent Groups and 2178 Groups. These Groups contain 6438 unique LOINC terms. Please see the associated Readme for details about the contents of the file, including definitions of the ParentGroups and Groups. IMPORTANT NOTES: 1. The LOINC Groups project is a work in progress. Expect the contents of this file, including the Parent Group and Group names and the types of Groups that are included, to change from release to release as we receive feedback from users and refine our processes. 2. The contents of the file and the groupings MUST be validated by the user prior to implementation in any aspect of clinical care. We have created Groups that may be useful in specific contexts, but these Groups have not been vetted for use in either patient care or research and should be used with caution. 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
