Vendor Connections
- riki.merrick
- Anonymous
Vendor Name | System Type | Responsible for outreach | Notes |
|---|---|---|---|
Epic | Beaker APLIS |
|
|
Epic | Beaker LIS |
|
|
Cerner | Novius (Siemens) LIS (list each LIS) |
|
|
Cerner | Millennium LIS |
|
|
Cerner | Millennium PathNet APLIS |
|
|
Cerner | CoPath APLIS |
|
|
Orchard | Harvest LIS (list each product) |
|
|
OpenELIS | LIS | Riki Merrick |
|
StarLIMS | LIS |
|
|
CliniSys | LIS CoPath AP LIS | Riki Merrick (MIPS got bought by CliniSys, so I moved my name here) | sent email to Amir in March and again in July |
Epic | EHR-s |
|
|
Cerner | EHR-s |
|
|
Clinical Architecture | Terminology Services | Riki Merrick | Have agreement that they will incorporate into their subscription service - creating the content model by Sept, publish by end of the year |
IMO | Terminology Services |
|
|
3M | Terminology Services | Pam Banning |
|
Wolter Kluwers / Health Language | Terminology Services | Riki Merrick | Cheryl Mason reached out and asked about when we will publish |
Optum | Terminology Services |
|
|
Meditech | Client Server LIS (list each LIS) |
|
|
Meditech | Magic LIS |
|
|
Meditech | Expanse LIS |
|
|
SCC SoftLab | LIS |
|
|
Allscripts / McKesson | Horizon Lab LIS |
|
|
Psyche | APLIS |
|
|
LigoLab | LIS |
|
|
Jamel Guma from JTG Consulting Group | middleware services | Nancy | met with him and he would like to see, if he could work with it |
Pfizer | IVD vendor | Riki | met with Joshua Swan -his team reviewed the draft SCT shared in 2022Q4 and found it useful; they spoke with several data standardization vendors, and they were mostly aware of and planning to incorporate SCT into their data semantic relationships. New contacts are: Beverly Buckta (data standardization efforts across our portfolio)and Kristi Kuper (data standardization efforts related to anti-infective research) Have asked for feedback on requirements for data sharing |
<PLEASE ADD OTHERS> |
|
|
|
Draft email text:
APHL has been working for a long time to sort out the specimen attributes, commonly comingled as “source” in many lab systems into Type (and modifier), source site (and modifier), collection method, additives and collection access site called the specimen Cross-Mapping Table (CMT).
In addition to the mapping to SCT concepts in the appropriate hierarchies, we are also providing a definition for each term as well as collection instructions, preference for usage in the different lab domains as well as an indicator that the term is fully defined, or only partial, in which case we highlight which additional attribute(s) need to be populated. We currently have it in a postGRES database and are finalizing the content and looking for some systems that might want to pilot its use in the near future and so I thought of you.
This one-pager (https://aphlinformatics.atlassian.net/wiki/download/attachments/1853947928/20200601_CBR_SCM_OnePager_v04_final_cleared.pdf?api=v2) explains what it is and why we think it would be a useful resource (we will bring it to SHIELD as well for feedback) – let me know, if that is something you would consider.