-
Notifications
You must be signed in to change notification settings - Fork 4
Fix message parser fields Pt. 2 #1356
Copy link
Copy link
Open
Labels
jurisdiction needTickets that directly impact users' ability to use our appTickets that directly impact users' ability to use our appmediumMedium-priority bug or issueMedium-priority bug or issuestreamline eCRIssues for the Streamline eCR teamIssues for the Streamline eCR team🐛 bugSomething isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
jurisdiction needTickets that directly impact users' ability to use our appTickets that directly impact users' ability to use our appmediumMedium-priority bug or issueMedium-priority bug or issuestreamline eCRIssues for the Streamline eCR teamIssues for the Streamline eCR team🐛 bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
What needs to be done
Several parsed data FHIR paths in message-parser are incorrect, resulting in missing data in the db.
Why it needs to be done
Data is missing in the parsed data when it should be appearing.
Acceptance Criteria
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