Closed arnejduranovic closed 1 week ago
@GilmoreA6 I have some documentation and rough mapping from CSTE around condition mapping if you want to discuss this some more.
@LaFreda1 @brandonnava We have moved this epic over to Engagement. Please note, there are three tickets in this epic.
Link to completed research document:
User Story:
As ReportStream, I need to be able to determine what condition a DiagnosticReport FHIR resource or Condition FHIR resource relates to so receivers can easily filter on a condition or conditions.
Description/Use Case
Presently, at least in the case of the California Flu pilot, receivers have to enter a long list of LOINC codes that are associated with the condition they are interested in and we filter on that via the condition filter. The main drawback of this method is that we have to manually manage the list of LOINC codes in the settings file, per receiver. So when a new test for a condition gets released we need to modify the setting file, which is unmanageable at scale. Even if we said "Okay, let's just start moving all LOINC codes to our LIVD table and map to conditions there", we still need to answer the following questions:
We need to have an efficient and reliable way to map test LOINC codes to the conditions they represent. Patricia has written up a document detailing the intricacies of mapping codes in general (not just LOINC) to conditions.
Risks/Impacts/Considerations
Dev Notes:
Acceptance Criteria