Skip to content

Fix message parser fields Pt. 2 #1356

@angelathe

Description

@angelathe

What needs to be done

Several parsed data FHIR paths in message-parser are incorrect, resulting in missing data in the db.

  1. Reason for Visit - Our current FHIR path assumes that there is an extension with the reason for visit string (this may have been based off of old data).
  2. Disabilities - This FHIR path only pulls the question, should we also be displaying the answers? @austin-hall-skylight
  3. Specimen type and Specimen collectio date - Current FHIR paths are outdated

Why it needs to be done

Data is missing in the parsed data when it should be appearing.

Acceptance Criteria

  • Update FHIR paths for the fields above, and confirm that the data appears where it exists
  • Add / update tests as necessary

Technical Notes

Although the main files to edit are core.json and extended.json in message-parser/app/default_schemas, please check whether the fields exist in any of the other JSON schema files.

Additional context

Metadata

Metadata

Assignees

Labels

jurisdiction needTickets that directly impact users' ability to use our appmediumMedium-priority bug or issuestreamline eCRIssues for the Streamline eCR team🐛 bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions