Stream: Announcements
Topic: Technical corrections for FHIR R3
Grahame Grieve (Jan 30 2019 at 22:37):
FMG has agreed to issue a new technical correction for FHIR Release 3. At this point, we are aware of grounds for issuing a technical correction to the supporting collatoral - FHIRPath statements for a few invariants, and the generated snapshots, and our focus is on fixing these.
if you are aware of implementation issues that need addressing in an R3 technical correction, please create a gForge task that has a target specification of "FHIRSpecificaition:DSTU3Release" and a Category of "Correction" for FHIR-Infrstructure to look at (issues that should be addressed to other committees probably won't be considered for a technical correction). (+ you have to edit the target specification after first creating the task)
Note: there are no such tasks at this time.
Alexander Henket (Jan 30 2019 at 22:46):
Nice. I'm thinking of GF#13782 for one which has been voted on and is approved, just hasn't made it's way into the schematrons yet, for example. Should I update that issue with the suggested markers, or create a new one? If new: should a I file a new one for all together or each separate?
Grahame Grieve (Jan 30 2019 at 22:54):
create a new one - it's signed off and done for a more recent version
Alexander Henket (Jan 30 2019 at 22:55):
One new for each similar, or one bulk with references to issues like this?
Grahame Grieve (Jan 30 2019 at 22:58):
one for each, I think, unless you want all to fail to get approval if any one fails to be approved
Eric Haas (Jan 31 2019 at 01:02):
I do I need to OO vote for GF#20319 assuming this is candidate ( for both R4 and R3 )
Grahame Grieve (Jan 31 2019 at 01:03):
yes it's a candidate for both
Grahame Grieve (Jan 31 2019 at 01:04):
FHIR-I can vote on it since it's not changing the meaning, only getting the meaning right - but OO can do it too
Eric Haas (Jan 31 2019 at 01:07):
L either way is fine. probably easier in FHIR-I as a technical block vote
Lloyd McKenzie (Jan 31 2019 at 01:26):
Discussion should be on #implementers
Michel Rutten (Jan 31 2019 at 12:21):
please create a gForge task that has a target specification of "FHIRSpecificaition:DSTU3Release
The Specification drop-down in the GForge tracker item submission form does not seem to contain a "DSTU3Release" option?
Grahame Grieve (Jan 31 2019 at 12:27):
no, the target release
Michel Rutten (Jan 31 2019 at 12:33):
I can't see an input field for "target release"?
pasted image
Grahame Grieve (Jan 31 2019 at 13:24):
No you have to create it first
Michel Rutten (Jan 31 2019 at 14:00):
Ah, thanx!
Lloyd McKenzie (Jan 31 2019 at 15:06):
Please discuss on #implementers , not here...
Last updated: Apr 12 2022 at 19:14 UTC
