-
Notifications
You must be signed in to change notification settings - Fork 149
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
When validating ConceptMap ensure codes listed are actually in value sets #522
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
(from https://jira.hl7.org/browse/FHIR-17566)
The v3 concept map for AdministrativeGender (http:https://hl7.org/fhir/cm-administrative-gender-v3.html) includes a mapping from
unknown
toUNK
, butUNK
does not appear to be part of the destination value set (http:https://hl7.org/fhir/v3/AdministrativeGender/vs.html). According to Lloyd McKenzie, "Ideally our build process should be checking that the codes listed in the ConceptMaps actually exist in the expansions of the source and target value sets, which would have caught this issue."Still a problem in the CI build 2021-05-27
The text was updated successfully, but these errors were encountered: