Stream: implementers
Topic: STU Status
Peter Bernhardt (May 10 2016 at 16:07):
When will STU3 be ballotted? Also, any updates on when HL7 expects a normative release?
Grahame Grieve (May 10 2016 at 16:16):
well, we are planning to ballot in the september ballot
Grahame Grieve (May 10 2016 at 16:16):
we're not currently planning 'a normative release'
Grahame Grieve (May 10 2016 at 16:17):
instead, content will be migrating through the maturity levels towards normative status.
Grahame Grieve (May 10 2016 at 16:17):
we have no plans to move any content into normative status this ballot, but I expect a few things to get there next time
Peter Bernhardt (May 10 2016 at 16:18):
thanks ... so, normative status is defined at the resource level based on maturity?
Grahame Grieve (May 10 2016 at 16:18):
yes. next step after level 5 is normative
Peter Bernhardt (May 10 2016 at 16:20):
makes sense given the pace of development of some resources that some would be 'de facto' final while others are still undergoing change
Grahame Grieve (May 10 2016 at 16:20):
yep
Peter Bernhardt (May 10 2016 at 16:24):
So in trying to help set expectations within my organization, I can say that we should focus more on the maturity level of particular resources rather than a golden date on which the FHIR standard is "final".
Grahame Grieve (May 10 2016 at 16:35):
yes
Lloyd McKenzie (May 10 2016 at 20:50):
We won't go through the effort of a normative ballot until we have a minimum set of content that's ready to go normative. I.e. The HTTP page, XML & JSON formats, search and key resources such as Patient, Practitioner, etc. And getting to the top of the FMM list will be driven by a mix of work group and implementer activity
Last updated: Apr 12 2022 at 19:14 UTC
