Conditions Endpoint

[JNygaard-Skylight]

PULL REQUEST

Summary

Adds /api/conditions endpoint to get a list of the conditions in ecr-viewer. This returns a list of condition names found in the ecr_rr_conditions table.

Related Issue

Fixes #2749

Acceptance Criteria

• Backend query available to gather all unique conditions across our eCR storage
  • Query works for core schema
  • Query works for extended schema
• Endpoint so that frontend can use this query should also be included

Additional Information

To test with Postgres and the core metadata schema you'll need the following variables in your .env.local:

# METADATA_DATABASE_TYPE=postgres
# METADATA_DATABASE_SCHEMA=core

And for SQL Server and the extended metadata schema:

METADATA_DATABASE_TYPE=sqlserver
METADATA_DATABASE_SCHEMA=extended
SQL_SERVER_USER=sa
SQL_SERVER_PASSWORD=Password1!
SQL_SERVER_HOST=sqlserver

In addition, to populate SQL Server you will need to modify the orchestration configs (save-bundle-to-ecr-viewer.json, and save-eicr-to-ecr-viewer-config.json) the seed data script uses to use the philly_ecr.json message-parser config. E.g.:

⋮
    {
      "name": "metadata_values",
      "service": "message_parser",
      "endpoint": "/parse_message",
      "params": {
        "message_format": "fhir",
        "parsing_schema_name": "philly_ecr.json",
        "credential_manager": "azure"
      }
⋮

Checklist

• If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.)

[mcmcgrath13]

not super familiar with the part of the code base, so just commenting

[BobanL]

Looks good, but just a couple of small nits.

[BobanL]

Instead of copying this file here, can we update the docker-compose to copy the real one? I believe you'll need to update test_type_system and test_result_qualitative in that one too.

- ./sql/extended.sql:/var/opt/mssql/scripts/extended.sql

[BobanL]

since we have another variable called "source", could we update this error to specifically say Invalid metadata database type?

[BobanL]

Since we initialize this connection in this file and in save-fhir-data-service.ts can we just pull this out into a single file like we do for postgres?