Stream: committers
Topic: Post-freeze substantive changes
Lloyd McKenzie (Jul 19 2016 at 01:26):
On today's FHIR-I call, we approved a few changes that are substantive but which we believe won't impact any IG development. We ask that IG developers please review these items and let us know if there are any concerns. If no concerns are raised by EOD Wed, we'll proceed to apply the changes:
- 10355 - Remove content from Binary summary
- 10312 - Task.fulfillment.recipients should be singular
- 10362 - @value or children isn't tight enough
Lloyd McKenzie (Jul 19 2016 at 01:26):
If other work groups have similar issues, they should raise them in this stream as well
Brian Postlethwaite (Jul 19 2016 at 05:23):
As part of the QA occurring, if a standard extension is discovered that has been moved into the core resource can we remove it, or just document it as deprecated and to use the native element now.
Brian Postlethwaite (Jul 19 2016 at 05:23):
(Example is the Organization Alias Standard extension)
Grahame Grieve (Jul 19 2016 at 05:37):
propose removing it here, wait 24 hours
Grahame Grieve (Jul 19 2016 at 05:37):
if no obe objects, remove it
Eric Haas (Jul 20 2016 at 01:02):
Need this for DAF: http://hl7-fhir.github.io/extension-us-core-race.html
needs a cardinality upgrade from 1 to * Can I preapply this- DAF has a tracker on this - I know I do - lost in USRealm stuff.
Grahame Grieve (Jul 20 2016 at 01:05):
approved - that's not frozen so far as I know
Eric Haas (Jul 20 2016 at 05:45):
Discoverd problem with DeviceUseRequest updates after the freeze. only had a coded element for what device is being requested. Needs to be a choice of code or reference to device. Making a request here to update resource to change element name from 'code' to 'device' and make a choice of CodeableConcept or reference(Device)
Bob Milius (Jul 20 2016 at 13:48):
GF10117. Add Sequence as a Observation.related. The status page says it was pursuasive and resolved, but change required.
Eric Haas (Jul 20 2016 at 21:30):
So Bob wouldl like us to add it post freeze. Any objections ?
Eric Haas (Jul 21 2016 at 02:27):
I have not heard any objection to my proposed "fix" on DeviceUseRequest . post freeze. I'd like to make the commit this evening if possible.
Grahame Grieve (Jul 21 2016 at 02:30):
approved
Rob Hausam (Jul 21 2016 at 13:52):
Does adding a "standard" modifier extension, in general, constitute a substantive change? I'm thinking that it wouldn't, since it's use is optional, and if it's not understood then the resource instance simply wouldn't (shouldn't) be processed. But I'm not sure if that's the rule.
Lloyd McKenzie (Jul 21 2016 at 15:30):
It wouldn't be a substantive change.
Eric Haas (Jul 21 2016 at 15:32):
I haven't heard objections to adding Sequence to Observation.related so going to make that post freeze commit
Rob Hausam (Jul 21 2016 at 18:54):
thanks, @Lloyd McKenzie - just thought I should verify
Grahame Grieve (Jul 21 2016 at 19:50):
@Eric Browne ok
Grahame Grieve (Jul 21 2016 at 22:31):
GF#6389 - did we intend this to be made durign the freeze? or after it? I cannot remember. @Lloyd McKenzie
Lloyd McKenzie (Jul 21 2016 at 23:47):
@Grahame Grieve It shouldn't impact any profiles, so I don't see a problem . . .
Grahame Grieve (Jul 21 2016 at 23:47):
I'll take that as a yes
Grahame Grieve (Jul 21 2016 at 23:48):
but I don't know that it won't affect acy profiles
Grahame Grieve (Jul 21 2016 at 23:48):
at least a few IGs have conformance resources in them
Brian Postlethwaite (Jul 21 2016 at 23:48):
PA would like to update the binding of the Account.status propeerty to be a required binding (currently is preferred)
Lloyd McKenzie (Jul 21 2016 at 23:49):
Having conformance resources is different from profiling conformance resources. Adding a new optional element won't affect any existing Conformance instances
Grahame Grieve (Jul 21 2016 at 23:51):
Brian, that is approved now
Brian Postlethwaite (Jul 21 2016 at 23:55):
PA would also like to make a substantive change to remove 2 standard extensions that are now core properties.
Organization.alias and Location.alias (which were formerly aliases).
Brian Postlethwaite (Jul 21 2016 at 23:56):
(or should there be a process for deprecating standard extensions)
Grahame Grieve (Jul 21 2016 at 23:59):
search the guides directory to see if anyone is using it (text search is fine)
Grahame Grieve (Jul 21 2016 at 23:59):
if not, approved
Brian Postlethwaite (Jul 22 2016 at 00:03):
If they are using it, would like their profile updated to use the property rather than the extension.
So a good thing anyway right?
Brian Postlethwaite (Jul 22 2016 at 00:03):
Would that create a build error for them?
Grahame Grieve (Jul 22 2016 at 00:04):
don't know. agree they need to change
Last updated: Apr 12 2022 at 19:14 UTC
