Clinical Terminologist (OMOP & Health Data Standards)

HK TechSandy, UtahOn-siteFull-timeMid level, 2–5 yearsListed 2 days ago

Apply now

About this role

Responsibilities

- Work the orphan-concept queue: review local codes the harmonization stage could not map, ordered by occurrence count, and map each to a standard concept or reject it as intentionally unmapped.
- Evaluate machine-proposed targets (lexical search, hierarchy evidence, OHDSI Usagi exports) and accept, correct or replace them; no AI/LLM assistance is used in Year 1.
- Approve concept-map releases as the credentialed terminologist of record, with a documented rationale per decision, and keep the SOW's 30-day median orphan time-to-disposition.
- Onboard each new partner's code sets: run a first-week mapping sprint on their lab, problem, medication and procedure dictionaries, reusing mappings across partners on the same EHR vendor.
- Verify OMOP alignment: that each mapped concept is a Standard concept in the right domain (Measurement, Condition, Drug, Procedure), with correct source_concept_id handling and units in UCUM.
- Maintain the vocabulary snapshot: coordinate Athena and UMLS releases with the vocab-loader, assess impact of deprecated or re-mapped concepts, and re-validate existing maps.
- Author mapping conventions and partner-facing guidance; review US Core profile bindings and ValueSets with the FHIR developers.
- Serve as the terminology point of contact for partner clinics, DHHS and UHIN (CHIE) on code questions, data-quality findings and measure definitions.

Required qualifications

- Credentialed in health information or clinical terminology: RHIA or RHIT (AHIMA), CCS, or a clinical license (RN, pharmacist, lab scientist) with terminology experience. The SOW requires a credentialed approver, so this is not negotiable.
- 3+ years mapping local or legacy codes to LOINC, SNOMED CT, RxNorm and ICD-10-CM in a production setting (HIE, EHR vendor, lab, health system or research network).
- Working knowledge of the OMOP CDM v5.4 vocabulary tables (concept, concept_relationship, concept_ancestor, source_to_concept_map), Standard vs non-standard concepts, and domain assignment.
- Hands-on with OHDSI Usagi or an equivalent mapping tool, and with Athena vocabulary downloads.
- Reading fluency in FHIR R4: CodeableConcept, Coding, CodeSystem, ValueSet, ConceptMap, and US Core terminology bindings.
- SQL sufficient to query vocabulary and mapping tables and to produce mapping quality reports.
- Can document a mapping decision so that an auditor or a second terminologist can reproduce it.
- Comfortable with the program's PHI rule: works with synthetic or de-identified data outside the platform; no PHI in email, chat, tickets, spreadsheets or AI tools.

Preferred qualifications

- Utah candidates are preferred
- Experience with rural or critical-access providers, small-vendor EHRs (athenahealth, eClinicalWorks, MEDITECH, CPSI/TruBridge) and the local dictionaries they produce.
- HIE or CHIE background; familiarity with UHIN or another state exchange's converter output.
- Quality-measure terminology: VSAC value sets, eCQM and HEDIS code sets, USCDI data classes.
- OHDSI community involvement, ATLAS cohort definitions, or Data Quality Dashboard experience.
- Exposure to Tuva Project claims and measure marts.
- UMLS Metathesaurus license holder; experience with CPT licensing constraints.