FHIR Management Group
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

  • Choose Affirmative, Negative, Abstain, Refer to Telcon for each item.

  • Use the  in the comments section to add comments to the vote.


title of item up for approval w/link

Project Approval Request for PSS-2138 - Getting issue details... STATUS

Click for anchor link Project Approval Request

Choices Your Vote Current Result: (5 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Why is this not international realm?
affirmative
5 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%
Items needing FMG approval to go to ballot in 2023Jan:

HL7 FHIR Implementation Guide: ICHOM Breast Cancer PCOM Set, Release 1 https://build.fhir.org/ig/HL7/fhir-ichom-breast-cancer-ig/

Click for anchor link ICHOM

Choices Your Vote Current Result: (6 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Contingent on fixing JiraSpecArtifacts
affirmative
6 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%

HL7 FHIR® Implementation Guide: Clinical Study Schedule of Activities https://build.fhir.org/ig/HL7/Vulcan-schedule-ig/

Click for anchor link Study Schedule

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: "taken from an actual example in the wild" is not a rationale to suppress a URL message. This can go to ballot so long as there's a warning in the ballot that the URL might change. It also needs to get into the HTA approval process so there's an approved URL before you want to publish the official release.
Not voted: The CodeSystem URL is referenced in the guide but just in an example where a PUBMED code is being used. There is no place to put a warning since it is in the example. Since it is an example, I have just used the text in the focus originalText so this warning has disappeared.
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%

HL7 FHIR® Implementation Guide: Electronic Medicinal Product Information https://build.fhir.org/ig/HL7/emedicinal-product-info/

Click for anchor link EMPI

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Operation canonical URLs have the wrong case. id search parameter should be Resource-id. Other search parameters don't show up in registry in R5 - should they?
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%

HL7 FHIR® Implementation Guide: Retrieval of Real World Data for Clinical Research https://build.fhir.org/ig/HL7/vulcan-rwd/

Click for anchor link RWD Retrieval

Choices Your Vote Current Result: (6 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: There should be a Security Considerations section that covers security and privacy considerations.
affirmative
6 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%

HL7 FHIR® Implementation Guide: Potential Drug-Drug Interaction (PDDI) Clinical Decision Support (CDS) https://build.fhir.org/ig/HL7/PDDI-CDS/

Click for anchor link PDDI

Choices Your Vote Current Result: (6 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Contingent on JiraSpec error/warning being gone.
Not voted: contingent on NOT linking to build.fhir.org, these should be to published FHIR core. e.g. https://build.fhir.org/security-labels.html#break-the-glass
affirmative
6 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%

HL7 FHIR® Implementation Guide: Data Exchange for Quality Measures https://build.fhir.org/ig/HL7/davinci-deqm/

Click for anchor link DEQM

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Sequence of "CI-build" is wrong. QA is not yet ready. See if cured by Wed.
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%

HL7 FHIR® Implementation Guide: Quality Measures https://build.fhir.org/ig/HL7/cqf-measures/

Click for anchor link CQF Measures

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Suppression message for text/cql-identifier messages doesn't make sense
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%
HL7 FHIR® Implementation Guide: US-Core http://build.fhir.org/ig/HL7/US-Core/

Click for anchor link US Core

Choices Your Vote Current Result: (6 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: HTA issues are not issues. Errors are fine. Contingent on JiraSpec being fixed.
Not voted: Note there are some ignore warnings that are no longer happening so should be removed from ignore warnings.
affirmative
6 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%

HL7 FHIR® Implementation Guide: Record Lifecycle Event (RLE) https://build.fhir.org/ig/HL7/ehrs-rle-ig/

Click for anchor link RLE

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Why is this going forward as an informative ballot? Jira spec needs fixing. Examples are mandatory.
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%
HL7 FHIR® IG: SMART Application Launch Framework https://build.fhir.org/ig/HL7/smart-app-launch/

Click for anchor link SMART App

Choices Your Vote Current Result: (6 Total Votes) Comments
abstain
0 Votes , 0%
affirmative
6 Votes , 100%
negative
0 Votes , 0%
refer to telecon
0 Votes , 0%

HL7 FHIR® Implementation Guide: Member Attribution List https://build.fhir.org/ig/HL7/davinci-atr/

Click for anchor link Member Attribution List

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Why is the URL 2023feb? "STU2 Release 1" sequence should just be "STU2"
Not voted: I don't see 2023, but the header does say 2.0.0-ballot which it should not.
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%

HL7 FHIR® Implementation Guide: Human Services Directory https://build.fhir.org/ig/HL7/FHIR-IG-Human-Services-Directory

Click for anchor link HSD

Choices Your Vote Current Result: (3 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: Not ready for QA
Not voted: much better, but still some info and warnings that need to be cleaned up.
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
3 Votes , 100%

HL7 FHIR® Implementation Guide: Multiple Chronic Conditions (MCC) Dynamic Electronic Care Plan https://build.fhir.org/ig/HL7/fhir-us-mcc/

Click for anchor link MCC

Choices Your Vote Current Result: (2 Total Votes) Comments
abstain
0 Votes , 0%
Not voted: " CareTeam.participant:caregiver: minimum required = 1" is a legitimate error. Other errors are fine. Has non-validating LOINC code been reported?
affirmative
0 Votes , 0%
negative
0 Votes , 0%
refer to telecon
2 Votes , 100%

*  Refer to Can I add comments without editing the page? for directions.

  • No labels