You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an RS engineer
I want to ensure all fields included in the NIST profile are mapped,
so that any sender or receiver using the NIST format can confident the data will be processed fully.
Description/Use Case
As part of the two NIST mapping PRs (here and here) there were fields added to the 251-elr mapping suite that need to be replicated in the catchall mapping suite. Here is the list of fields to be added:
MSH.10 to MSHExtension
OBR.25 to OBRExtension
XAD/Address add $country to country element
CNN.8 in CNNExtension
create NDLExtension and add in NDL.9
XAD.6 to XADExtension
XTN.11 to XTNExtension
Acceptance Criteria
All fields listed in the description are added to the catchall mapping suite
All fields listed in the description are tested in the mapping integration tests
The text was updated successfully, but these errors were encountered:
User Story
As an RS engineer
I want to ensure all fields included in the NIST profile are mapped,
so that any sender or receiver using the NIST format can confident the data will be processed fully.
Description/Use Case
As part of the two NIST mapping PRs (here and here) there were fields added to the 251-elr mapping suite that need to be replicated in the catchall mapping suite. Here is the list of fields to be added:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: