Stream: Announcements
Topic: Community Consultation
Grahame Grieve (Oct 05 2017 at 03:56):
https://onfhir.hl7.org/2017/10/05/proposed-breaking-changes-for-fhir-r4/
Grahame Grieve (Oct 05 2017 at 03:56):
FYI
Grahame Grieve (Oct 16 2017 at 07:09):
Results so far: several comments about renaming ValueSet.compose (all quite strongly negative). One guardedly reluctant comment about changes to Observation.related, and nothing about markdown
Ewout Kramer (Oct 16 2017 at 08:06):
I have discussed using markdown with my colleagues who were not present at the San Diego WGM - we have no problems going for GFM minus html....
Grahame Grieve (Feb 19 2018 at 22:43):
Reminder that there are community consultations open, closing this week or the start of next week (including one that I just posted right now). As yet, I have received no comments on this cycle. Relevant posts:
- https://onfhir.hl7.org/2018/02/09/report-january-2018-meeting-community-consultation/
- https://onfhir.hl7.org/2018/02/19/community-consultation-urls-vs-references/
Eric Haas (Feb 26 2018 at 19:01):
Critical and breaking change to Observation.dataAbsentReason
There are 3 trackers related to the required binding to Observation.dataAbsentReason which would be a breaking change to the Observation Resource. The Orders and Observations workgroup is recommending to use the standard FHIR DataAbsentReason valueset instead of Observation Value Absent Reason value set both of which are based upon the DataAbsentReason code system. This code system has the following proposed breaking changes as well:
* the codes NAN, asked, temp, and astext have been changed to not-a-number, asked-unknown, temp-unknown, and as-text for clarity
* A heirarchy of unknown has been created and the codes asked-unknown (asked) and temp-unknown (temp) , and not-asked are now members of it.
* The definition of not-a-number("NAN') asked-unknown (asked) has changed.
These changes and more nonbreaking changes to this valueset and codesystem have been preapplied to the CI build and can be viewed here
These changes are related to the following trackers:
* GF#10556
* GF#15567- data absent reason code, definition, hierarchy and value set updates
* GF#13521
Richard Townley-O'Neill (Feb 27 2018 at 02:12):
#13066 is about location mode
Eric Haas (Feb 27 2018 at 04:25):
Thanks for the heads up... updated
Ewout Kramer (Feb 27 2018 at 09:31):
In the pre-applied changes I can see not a number is actually not-a-number, which I prefer (codes with a space would not make me jump for joy)!
Grahame Grieve (Feb 27 2018 at 10:35):
must be a typo - we can't define codes with spaces
Eric Haas (Feb 27 2018 at 16:08):
yes a typo in my summary of changes - corrected above. but the preapplied changes are all valid codes.. Thanks Eric
Rob Hausam (Mar 07 2018 at 19:16):
We are looking for implementer community input on tightening the cardinality of ConceptMap source and target in this topic: https://chat.fhir.org/#narrow/stream/terminology/subject/Proposal.20to.20tighten.20ConceptMap.20source.20and.20target.20cardinality
Last updated: Apr 12 2022 at 19:14 UTC
