Stream: fhircast-github
Topic: fhircast-docs / Issue #111 May 2019 Ballot Comment: Can a...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #111
## May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #111
## May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #111
## May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot edited Issue #111
## May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 22:29):
isaacvetter commented on Issue #111
During conversation at the Montreal, May 2019 working group meeting, @RicardoQuintano, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to:
Proposed resolution: Persuasive. During the publication of the materials that are currently, albeit confusingly labeled Draft 1.0; we will re-label these modified material to 1.0.
Github Notifications (FHIRcast) (May 07 2019 at 17:25):
bvdh commented on Issue #111
So far as I understand, HL7 has guidelines for this. I looked them up.
According to chapter 13 GOM the proper name for the first, non normative version of the specification is STU1.
I see no reason to deviate from these guideline.
Please note that it also indicates some guidelines regarding text to appear on the front-page.This means that the current version would then be the draft version of STU1.
Github Notifications (FHIRcast) (May 07 2019 at 22:14):
isaacvetter commented on Issue #111
Hey @bvdh , mind pointing to a section of the GOM for the guidelines for text to appear on the front-page?
I couldn't find it with a quick Ctrl+F.
Isaac
Github Notifications (FHIRcast) (May 08 2019 at 09:12):
bvdh commented on Issue #111
13.02.07.01 Standard for Trial Use (STU) Front Matter
The front cover of a STU shall include the following statement.
“Publication of this standard for trial use (STU) has been approved by Health Level
Seven International (HL7). This STU is not an accredited American National
Standard. The comment period for use of this STU shall end [indicate the number of
months allocated for evaluation and review] months from the date of publication.
Suggestions for revision should be submitted at
http://www.hl7.org/stucomments/index.cfm .
Following this [the number of months shown above] month evaluation period, this
STU, revised as necessary, will be submitted to a normative ballot in preparation for
approval by ANSI as an American National Standard. Implementations of this STU
shall be viable throughout the normative ballot process and for up to six months after
publication of the relevant normative standard.”
The use of the ANSI logo or trademark on a STU is strictly prohibited and at no time shall the STU be
referred to as an American National Standard for Trial Use.
Github Notifications (FHIRcast) (May 09 2019 at 02:53):
isaacvetter commented on Issue #111
Github Notifications (FHIRcast) (May 09 2019 at 02:55):
isaacvetter edited a comment on Issue #111
Github Notifications (FHIRcast) (May 09 2019 at 02:56):
isaacvetter edited a comment on Issue #111
Hmmmmmm, I can't find any other FHIR implementation guides that follow this. Is it possible there are different rules for FHIR IGs?
Github Notifications (FHIRcast) (May 09 2019 at 13:43):
wmaethner commented on Issue #111
Duplicate of #174
Github Notifications (FHIRcast) (May 09 2019 at 13:43):
wmaethner labeled Issue #111
## May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:50):
wmaethner closed Issue #111:
May 2019 Ballot Comment: Can a 1.0 version be applied in a draft version?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: NA
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Can a 1.0 version be applied in a draft version?
Comment: Can a 1.0 version be applied in a draft version? Wouldn’t 0.1 be more appropriate? Otherwise label it as STU1.
Existing wording: "1.0 Draft" This is the draft of the 1.0 release of the FHIRcast specification. We are currently working towards a 1.0 release and would love your feedback and proposed changes.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
