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
In examples for measures, SNOMED codes are specified with a version "2021-09", which the HL7 Validator doesn't like. This results in a large number of errors on the IG's QA report, which is not ideal.
Some experimentation shows that the validator is happy with the version string http://snomed.info/sct/554471000005108/version/20210930, which is the only valid release in that timeframe. Does that mean that the examples are wrong and this is the version that should be used, or is the validator being overly strict? Ideally, which ever it is, the corresponding tool (example generator or validator) should be fixed. However, both are outside of the MADFSH process itself.
Determine if this is critical, and if so, a fix could be adjusting the examples in MADFSH to resolve the issue ourselves.
The text was updated successfully, but these errors were encountered:
In examples for measures, SNOMED codes are specified with a version "2021-09", which the HL7 Validator doesn't like. This results in a large number of errors on the IG's QA report, which is not ideal.
Some experimentation shows that the validator is happy with the version string http://snomed.info/sct/554471000005108/version/20210930, which is the only valid release in that timeframe. Does that mean that the examples are wrong and this is the version that should be used, or is the validator being overly strict? Ideally, which ever it is, the corresponding tool (example generator or validator) should be fixed. However, both are outside of the MADFSH process itself.
Determine if this is critical, and if so, a fix could be adjusting the examples in MADFSH to resolve the issue ourselves.
The text was updated successfully, but these errors were encountered: