FHIR Chat · Change Proposals for $validate-code post Connectathon · terminology

Stream: terminology

Topic: Change Proposals for $validate-code post Connectathon


view this post on Zulip Grahame Grieve (Sep 16 2021 at 19:36):

I have a series of change proposals for the $validate-code parameters subsequent to a discussion at the connectathon.

All of these changes are already in production on tx.fhir.org because we needed them in production. These are required in order to drive other terminology servers to usefully serve the FHIR validator and IG publisher, which the community desires to be possible.

view this post on Zulip Grahame Grieve (Sep 16 2021 at 19:37):

@Michael Lawley @Alexander Henket @Peter Jordan (and anyone else who maintains a terminology server)

view this post on Zulip Grahame Grieve (Sep 16 2021 at 19:37):

https://jira.hl7.org/browse/FHIR-33941: $validate-code should return system | version | code when display is returned

view this post on Zulip Grahame Grieve (Sep 16 2021 at 19:47):

https://jira.hl7.org/browse/FHIR-33943: $validate-code should return an operation outcome with the full details of issues found, including paths

view this post on Zulip Grahame Grieve (Sep 16 2021 at 19:59):

https://jira.hl7.org/browse/FHIR-33944: $validate-code and $expand should have a parameter for related value sets and code systems

view this post on Zulip Grahame Grieve (Sep 16 2021 at 20:19):

https://jira.hl7.org/browse/FHIR-33946: $validate-code and $expand need a session parameter

view this post on Zulip Grahame Grieve (Sep 16 2021 at 20:27):

https://jira.hl7.org/browse/FHIR-33947: Clarify the use of fragment

(this is a discovered issue from the same session, relating to the first of the tasks above)


Last updated: Apr 12 2022 at 19:14 UTC