FHIR/clinical data SME-BA-W2-Remote

Job Description-
We need a FHIR/clinical data SME to help the Health Records team inves4gate and remediate recurring data-quality and harmoniza4on issues across mul4ple sources. The resource(s) should be able to review raw/source FHIR and transformed records, validate mappings and resource seman4cs, iden4fy whether issues originate at the source or in our normaliza4on/display logic, and recommend scalable fixes rather than one-off filters.

Key areas of focus:
1. Encounters/Visits: Determine how to distinguish true visits from calls/messages and other non-visit encounters, particularly for QHIN, where there isn’t a reliable filtering signal.
2. Diagnostic Reports: Investigate incorrect/unknown dates and duplicate or incorrectly assembled diagnostic reports.
3. Medications: Identify causes of duplicate medication records and define appropriate deduplication/reconciliation logic.
4. Conditions: Review FHIR statdate semantics and correct the logic that classifies conditions as current vs. historical.
5. Dates: Establish consistent date-selection/mapping rules across FHIR resources and sources, including cases where displayed dates differ from the underlying clinical event.
6. Migrated encounters: Review the migrated-encounter issue Sonny reported and determine the appropriate reconciliation/mapping approach.
7. Procedures: Address misclassification of labs/immunizations as procedures and define source-aware rules that preserve clinically correct pa4ent-facing presenta4on.
Resource profile:
* Strong hands-on knowledge of FHIR R4
* Experience with clinical data quality, terminology/mapping, normalization, reconciliation,and de-duplication across EHR/HIE/QHIN sources.
* Ability to analyze source payloads and trace records through ingestion/harmonization to the consumer experience.
* Comfortable partnering with product and engineering teams to translate findings into reusable rules, validation checks, and longer-term data-quality improvements.

1. 
   1. Encounters/Visits: Determine how to distinguish true visits from calls/messages and other non-visit encounters, particularly for QHIN, where there isn’t a reliable filtering signal.
   2. Diagnostic Reports: Investigate incorrect/unknown dates and duplicate or incorrectly assembled diagnostic reports.
   3. Medications: Identify causes of duplicate medication records and define appropriate deduplication/reconciliation logic.
   4. Conditions: Review FHIR statdate semantics and correct the logic that classifies conditions as current vs. historical.
   5. Dates: Establish consistent date-selection/mapping rules across FHIR resources and sources, including cases where displayed dates differ from the underlying clinical event.
   6. Migrated encounters: Review the migrated-encounter issue Sonny reported and determine the appropriate reconciliation/mapping approach.
   7. Procedures: Address misclassification of labs/immunizations as procedures and define source-aware rules that preserve clinically correct pa4ent-facing presenta4on.                                           Years of Experience:    5.00 Years of Experience