1. An Introduction to the Reportable Condition Mapping Tables Jeremiah Sable Consultant, The St. John Group Contractor to APHL

2. What problem do the RCMTs solve? Which test results are of public health interest in which jurisdiction? Clinical Lab Test results Consumer of lab data

3. Filtering the output of clinical labs RCMT tables can identify tests and results of public health interest. RCMT filter Clinical Lab Test results Reportable Non reportable Consumer of lab data

4. Within a public health agency Test results Public health agency TB STD Foodborne Hepatitis etc. RCMT Routing test results within an agency

5. The problem of non-comparable lab data It isn’t possible to map the test catalog of each lab to reportable conditions. Each lab has its own codes and names for lab tests. There is no consistency across labs. ARUP labs LabCorp Mayo labs etc.... Quest labs

6. LOINC enables data aggregation across labs It is possible to map LOINC tests to reportable conditions. ARUP labs LabCorp Mayo labs etc.... Quest labs This problem disappears when labs send LOINC codes along with their own codes. LOINC

7. RCMTs map LOINC tests to reportable conditions Simplified example of RCMT content LOINC codeLOINC test nameCondition 5672-1Lead : MCnc : Pt : Bld : Ord :Lead poisoning 38462-8Legionella sp Ag : ACnc : Pt : Sputum : Ord : IFLegionellosis 17324-5Neisseria meningitidis Ag : ACnc : Pt : CSF : Qn : LAMeningococcal disease 31955-8Rubella virus Ag : ACnc : Pt : CSF : Ord :Rubella 33688-3Yersinia pestis Ag : ACnc : Pt : Isolate : Ord : IFPlague

8. Does this LOINC map to a reportable condition? Many LOINCs are non-specific and cannot be mapped to conditions. LOINC code LOINC test name Condition 5883-4 Virus identified : Prid : Pt : Bld : Nom : Culture ???

9. Does this LOINC map to a reportable condition? Many LOINCs are non-specific and cannot be mapped to conditions. LOINC code LOINC test name Condition 5883-4 Virus identified : Prid : Pt : Bld : Nom : Culture ??? For these non-specific LOINCs the RCMTs contain lists of organisms that cause reportable conditions. These lists contain SNOMED organism codes and names.

10. Current work 1.Documentation 2.SDO updates 3.Collaboration Document existing RCMT processes LOINC and SNOMED processes, including downloading, browsing, searching, etc. Getting LOINC and SNOMED data into locally maintained spreadsheets and databases Finding information online: taxonomy web sites, clinical information, commercial lab sites, microbiology text books, etc. Administrative activities

11. Current work 1.Documentation 2.SDO updates 3.Collaboration New SNOMED releases occur every six months Update RCMTs with July 31 release of SNOMED Develop and document processes for reviewing changes in SNOMED and updating RCMT content Iterative improvement of SNOMED processes LOINC is released three to four times per year Update RCMTs with LOINC version 2.35 Develop and document processes for reviewing changes in LOINC and updating RCMT content Iterative improvement of LOINC processes

12. Current work 1.Documentation 2.SDO updates 3.Collaboration The RCMT project overlaps the work of some current and planned projects. Mechanisms for communication and collaboration between RCMT and these other projects will be necessary to avoid duplicated efforts and inconsistent recommendations.

13. RCMT contact information RCMT Planning Team E-mail: PHINVS@CDC.GOVPHINVS@CDC.GOV RCMT Website (phConnect) : http://www.phconnect.org/group/rcmthttp://www.phconnect.org/group/rcmt