Implement code to condition comparison API

[victor-chaparro]

Problem statement

When onboarding a sender, they are currently required to provide a CSV file containing their supported LOINC and SNOMED codes. An onboarding engineer processes this file using a CLI command to identify codes not mapped in the code-to-condition table. To simplify and automate this workflow, a new UI is being developed that will allow senders to upload their CSV files directly and view which codes are mapped or unmapped.

To support this UI, a REST API is needed. This API will accept the contents of the sender's CSV file, process it to identify unmapped codes and any errors, and return the results.

What you need to know

• Example UI response: Figma Design
• Sender Example Sheet: ReportStream Mapping Template.xlsx
• CLI Instructions: How to check error codes manually: CLI Documentation
• Logic Source:
  • Code comparison logic: LookupTableCommands.kt (line 560)
  • Example API with authentication: ReportFunction.kt (processFhirDataRequest, line 141)

API Requirements

• Input: The API must accept the contents of the sender's CSV file in the request body.
• Authorization: Only accounts with "sender" or "admin" roles should have access to the API.
• Processing: The API will:
  • Compare CSV file data against the code-to-condition table.
  • Return a list of mapped and unmapped codes.
  • Return details of any errors encountered during processing.

Acceptance criteria

• The API correctly identifies and returns mapped and unmapped codes.
• The API provides clear error details for any issues during processing.
• The API accepts the CSV file contents in the request body.
• Access to the API is restricted to authorized "sender" and "admin" roles.
• Comprehensive documentation is created for the API.