-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DoD for OBX Segment for outbound OML #521
Conversation
- added initially supported fields - added provenance update
- removed fields that were not required - added fields that are being converted - updated provenance entry
- added fields that are being converted to HL7 - removed unnecessary field flag - updated provenance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few comments/questions. I thought we were supposed to add the names for each field exactly as they are in the documentation, but seeing your PR it seems I had the wrong assumption. Do we we need to describe the fields in plain language or do we need to document the names matching the HL7 guideline?
Kudos, SonarCloud Quality Gate passed! |
Updated required OBX Segment fields for Implementation Guide
Issue #495
Checklist