FHIR Chat · January 2022 Ballot Reconciliation · argonaut

Stream: argonaut

Topic: January 2022 Ballot Reconciliation

view this post on Zulip Eric Haas (Jan 20 2022 at 19:00):

US Core is reconciling the 2022 January Ballot comments with the goal of publishing US Core Version 5.0.0 by June 2022. We had over 100 comments and thank the commenters for their feedback. To address many of these comments in the upcoming weeks, we will be posting block votes here and on the Cross Group Project list serve. We will vote on the Block Votes and and discuss and vote on individual trackers on the Weekly Cross Group Project Work Group scheduled calls. See below for details.

The Cross-Group Project Work Group (CGP) is Thursdays from 1-2 PM Eastern. The next weekly call is 1/27/2022 where we plan to vote on Block Vote 1 and discuss individual ballot comments (which comments tbd)

CGP zoom information: https://zoom.us/j/91506058769
CGP listserve email address: cgp@lists.hl7.org

view this post on Zulip Eric Haas (Jan 20 2022 at 19:12):

Block Vote 1

The Cross-Group Project Work Group (CGP) is meeting next Thursday 1/27/2022 from 1-2 PM Eastern (meeting link). We plan to vote on Block Vote 1 of Jira Trackers. We have prepared proposed dispositions and listed the trackers below. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

Commenters

  • @Eric Haas
  • @Virginia Lorenzi
  • @Riki Merrick
  • @Sean Muir
  • @Keith Salzman
  • @Michelle (Moseman) Miller
  • @Emma Jones
  • @Bas van den Heuvel
  • @Mitra Rocca
  • @Marti Velezis
  • @Floyd Eisenberg
  • @Yunwei Wang
  • @Cooper Thompson

1. Key: Summary (Reporter) Resolution

  1. FHIR#35854: Change fixed category slice to max=1 (ehaas) Persuasive
  2. FHIR#35755: Change Home Page to an explanation to exec summary of the problem and solution (vlorenzi) Persuasive with Modification
  3. FHIR#35716: ObservationStatus codes will need updating per V2 to FHIR mapping (RikiM) Not Persuasive
  4. FHIR#35707: Status of active requires a period start to allow proper evaluation of status; Additional rules no active status if period has ended (seanmuir) Not Persuasive
  5. FHIR#35706: Pleased with this update, in particular SDOH Clarifications and Gender Identity (klsalzman) Considered - No action required
  6. FHIR#35576: New profiles missing from table (michelle.m.miller) Persuasive with Modification
  7. FHIR#35452: Duplicate sections in US Core RelatedPerson profile (michelle.m.miller) Persuasive with Modification
  8. FHIR#35449: Thank you for adding guidance on using US Core Profiles where not formally defined. (emmanurse) Considered - No action required
  9. FHIR#35318: US Core Condition - add optional verificationStatus search parameter (michelle.m.miller) Persuasive with Modification
  10. FHIR#35317: Need to review the DiagnosticReport status codes for lab (RikiM) Not Persuasive
  11. FHIR#35283: Conflicting documentation for MS within US Core Social History Assessment Observation Profile (michelle.m.miller) Persuasive with Modification
  12. FHIR#35282: Conflicting guidance for Observation category for SDOH assessments (michelle.m.miller) Persuasive with Modification
  13. FHIR#35280: US Core Condition profile ""status"" is ambiguous; clarify to be clinicalStatus (michelle.m.miller) Persuasive with Modification
  14. FHIR#35152: CareTeam example has misleading CareTeam.participant.role value (michelle.m.miller) Persuasive with Modification
  15. FHIR#35125: Bad description in mandatory element for DiagnsticReport.effective (RikiM) Persuasive with Modification
  16. FHIR#35122: Need to provide some guidance when specific code systems are to be used in ServiceRequest (RikiM) Not Persuasive with Modification
  17. FHIR#35065: Is the Guidance chapter informative? (bvdh) Persuasive with Modification
  18. FHIR#35064: Make npm package more prominent (bvdh) Persuasive with Modification
  19. FHIR#35047: Change the query parameter value to be consistent with previous statement (mrocca) Persuasive
  20. FHIR#34973: Clarify ""time"" elements used in these report profiles (marti_velezis) Persuasive with Modification
  21. FHIR#34971: Observation.component without a value - should it exist in the diff table? (marti_velezis) Not Persuasive with Modification
  22. FHIR#34755: RelatedPerson relationshiptype should have binding to FHIR value set RelatedPerson-relationshiptype (feisenberg) Persuasive with Modification
  23. FHIR#34646: Multiple us-core-1 invariants in IG (yunwwang) Persuasive with Modification
  24. FHIR#34645: ServiceRequest.category:us-core should be required? (yunwwang) Not Persuasive
  25. FHIR#34554: Narrative and structure mis-match on abatement date (cooper.thompson) Persuasive with Modification
  26. FHIR#34552: Should Condition date of diagnosis be an invariant instead of special MS meaning? (cooper.thompson) Not Persuasive
  27. FHIR#34468: Condition.clinicalStatus clarification (of invariant con-3) (michelle.m.miller) Persuasive with Modification

view this post on Zulip Eric Haas (Jan 20 2022 at 19:27):

On the docket for the 1/27/2022 CGP call:

  1. Block Vote 1

  2. Discuss Assessments modeling related trackers:

    • FHIR#35364 Streamline representation of SDOH screening instruments
    • FHIR#35363 Confused about “Results” vs “Screening Response”
    • FHIR#35282 Conflicting guidance for Observation category for SDOH assessments
    • FHIR#34752 Assessment codes for individual components of existing assessments too limited and superfluous
    • FHIR#34751 CLONE - Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation
    • FHIR#34748 Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation
    • FHIR#34384 Why is SDOH Assessment's Observation.component.code MS? Why is Observation.component?

view this post on Zulip Eric Haas (Jan 24 2022 at 22:25):

In Person Comments Pulled from Block Vote 1:

My apologies to those of you who requested in person ballot resolution that I included in Block 1 above. I am pulling these 6 issues to to give you chance to review in person on our weekly call. Let us know when you will make the CGP call to discuss ASAP. If you agree with the proposed resolution, let me know and I will add them to the next block.

Commenters:

  • @Bas van den Heuvel
  • @Riki Merrick
  • @Marti Velezis

Key: Summary (Reporter) Resolution
FHIR#35716: ObservationStatus codes will need updating per V2 to FHIR mapping (RikiM) Not Persuasive
FHIR#35317: Need to review the DiagnosticReport status codes for lab (RikiM) Not Persuasive
FHIR#35125: Bad description in mandatory element for DiagnsticReport.effective (RikiM) Persuasive with Modification
FHIR#35065: Is the Guidance chapter informative? (bvdh) Persuasive with Modification
FHIR#34973: Clarify ""time"" elements used in these report profiles (marti_velezis) Persuasive with Modification
FHIR#34971: Observation.component without a value - should it exist in the diff table? (marti_velezis) Not Persuasive with Modification

view this post on Zulip Yunwei Wang (Jan 25 2022 at 19:06):

@Eric Haas Should the resolution for https://jira.hl7.org/browse/FHIR-34645 be "Not Persuasive with Mod" b/c there is proposed wording change.

view this post on Zulip Marti Velezis (Jan 29 2022 at 02:29):

@Eric Haas I will attend the CGP meeting on 2/10 for the items you pulled for me. Thanks for pulling these for in person resolution.

view this post on Zulip Eric Haas (Feb 02 2022 at 01:18):

Block Vote 2

The Cross-Group Project Work Group (CGP) meets every Thursday from 1-2 PM Eastern (meeting info). We plan to vote on Block Vote 2 of Jira Trackers on Thursday 2/10/2022 (Conference Call Details) which we have prepared with proposed dispositions and listed below. All "in-person" ballots in this block have been approved by the commenter. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

Commenters

  • @Riki Merrick
  • @Emma Jones
  • @Yunwei Wang
  • @Cooper Thompson
  • @Hayden Bader
  • @Joan Harper
  • @Lee Surprenant
  • @janice karen

Key: Summary (Reporter) Resolution

  1. FHIR-35870: Organization does not technically have a ""status"" element. It has an ""active"" element. (hbader) Persuasive with Modification
  2. FHIR-35716: ObservationStatus codes will need updating per V2 to FHIR mapping (RikiM) Not Persuasive
  3. FHIR-35622: Do not use inactive as a resource status to represent entered-in-error or deleted information (emmanurse) Persuasive with Modification
  4. FHIR-35454: Defining URLshould be anchored in THO not hl7.org/fhir. Only those with required binding to a 'code' data type should be anchored in hl7.fhir.org.1 (j_harper) Not Persuasive
  5. FHIR-35380: provide clearer guidance for $docref operation when no date range is specified (emmanurse) Not Persuasive with Modification
  6. FHIR-35317: Need to review the DiagnosticReport status codes for lab (RikiM) Not Persuasive
  7. FHIR-35125: Bad description in mandatory element for DiagnsticReport.effective (RikiM) Persuasive with Modification
  8. FHIR-34643: Inconsistent on conditional required element (yunwwang) Persuasive with Modification
  9. FHIR-34642: Missing search query parameter value (yunwwang) Persuasive
  10. FHIR-34637: Is Reference(Organization) MustSupport? (yunwwang) Persuasive
  11. FHIR-34630: Get Medication's narrative examples don't match the JSON examples (yunwwang) Persuasive with Modification
  12. FHIR-34629: contextDirection in Example 1 is wrong (yunwwang) Persuasive
  13. FHIR-34628: reportedReference to other resources are not must supported (yunwwang) Not Persuasive
  14. FHIR-34626: Add further clarification between slicing a binding (4.1.0) vs using extensible binding (4.0.0) (yunwwang) Persuasive
  15. FHIR-34624: Example in Missing Data for coded element has wrong code system (yunwwang) Persuasive
  16. FHIR-34623: Referencing US Core Profiles (yunwwang) Persuasive
  17. FHIR-34604: BirthSex: inconsistent usage note in UNK description (janicemhdc) Considered - Question answered
  18. FHIR-34488: Ethnicity ValueSet code display needlessly differs from CodeSystem display (lmsurprenant) Persuasive

view this post on Zulip Eric Haas (Feb 02 2022 at 21:19):

On the next CGP call tomorrow 2/3/2022 ( Call Details) we plan to discuss and vote on the following trackers time permitting.
(CGP Agenda: https://confluence.hl7.org/display/CGP/2022+Cross-Group+Project+Calls)

  1. ODH trackers (2) (15 minutes) in person request:

    • FHIR-34703: Clarify in ""New Content"" that this does not include work information observations (ODH) (genny_luensman) Duplicate
    • FHIR-34702: Reconsider the LOINC code used for Employment status to align with ODH (genny_luensman) Not Persuasive
    • FHIR-34701: Clarify that SDOH data elements does not include work information (see ODH) (genny_luensman) Not Persuasive

  2. Assessments (pick up from January 27 call - (45) come to resolution

    • FHIR#35364 Streamline representation of SDOH screening instruments
    • FHIR#35363 Confused about “Results” vs “Screening Response”
    • FHIR#35282 Conflicting guidance for Observation category for SDOH assessments
    • FHIR#34752 Assessment codes for individual components of existing assessments too limited and superfluous
    • FHIR#34751 CLONE - Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation
    • FHIR-34748 Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation
    • FHIR#34384 Why is SDOH Assessment's Observation.component.code MS? Why is Observation.component?

  3. RelatedPerson tracker (Cooper) (if time)

    • FHIR-34556 Remove MS from CareTeam.member / RelatedPerson reference

Ballot content: http://build.fhir.org/ig/HL7/US-Core/branches/master/profiles-and-extensions.html

Ballot Dashboard:https://jira.hl7.org/secure/Dashboard.jspa

CGP zoom information: https://zoom.us/j/91506058769

CGP listserve email address: cgp@lists.hl7.org

view this post on Zulip Yunwei Wang (Feb 03 2022 at 00:48):

@Eric Haas Can you pull FHIR-34628 out of block vote 2? I would like to have an in-person discussion.

view this post on Zulip Eric Haas (Feb 03 2022 at 05:37):

of course

view this post on Zulip Eric Haas (Feb 16 2022 at 18:24):

This Week's Agenda

The Cross-Group Project Work Group (CGP) is meeting this Thursday from 1-2 PM Eastern (meeting info). We have posted the complete agenda and trackers on Confluence.

  • Assessments - final discussion :fingers_crossed:
  • In person comments with:
    • @Andrea Pitkus, PhD, MLS(ASCP)CM , @Riki Merrick Topic: laboratory reporting and CLIA compliant examples
    • @Bas van den Heuvel Topics: requirements for server upgrading to USCore R4 from DSTU2 and what guidance is required.
  • Don't add "OTH" to OMB Race categories. :stop:
  • Condition Profiling :thinking:

view this post on Zulip Eric Haas (Feb 18 2022 at 04:15):

After the January 2022 US Core ballot reconciliation is completed, we will publish the next version of USCore (ver 5.0.0) in June. Any regular non-ballot US Core trackers submitted before March 18 will also be considered prior to publication. Any tracker submitted after that date will be considered for the January 2023 ballot cycle. Technical corrections will be exempt from this deadline.

view this post on Zulip Eric Haas (Feb 18 2022 at 04:25):

The next Cross-Group Project Work Group (CGP) where we will be discussing and voting on US Core trackers is Thursday March 3 from 1-2 PM Eastern (meeting info). The agenda and trackers are posted on Confluence.

  • Assessments - review of detailed proposal supporting option of both QuestionnaireResponse and Structured Observation to represent Assessment/Survey results and disposition of Assessment trackers.
  • In person comments with:
    • @Riki Merrick Topic: laboratory reporting
    • @Bas van den Heuvel Topics: requirements for server upgrading to USCore R4 from DSTU2 and what guidance is required.
  • Don't add "OTH" to OMB Race categories. :stop:
  • Condition Profiling :thinking:

view this post on Zulip Eric Haas (Feb 18 2022 at 04:26):

The following trackers are still extant and will be addressed on future calls:

view this post on Zulip Eric Haas (Feb 18 2022 at 04:28):

Clinical Tests

FHIR-35640: Need to clarify the meaning/purpose of this profile/observation category (joelbales) Persuasive with Modification
FHIR-34973: Clarify ""time"" elements used in these report profiles (marti_velezis) Persuasive with Modification
FHIR-34949: Observation.category - Imaging vs Procedure (steven_nichols) Not Persuasive
FHIR-34753: Clinical Test Result Observation Profile Must Have needs to address the 3 slices for procedure, exam, and activity in the explanatory text (feisenberg) ****
FHIR-34555: Do we need slices on category for Clinical Test Results? (cooper.thompson) ****

Diagnostic Imaging
FHIR-35759: Remove MS from DiagnosticReport.imagingStudy (corey_spears) ****
FHIR-34975: Imaging Study or Media is still unclear (marti_velezis) ****
FHIR-34966: Clarify profile specific implementation guidance for US Core DiagnosticReport Profile for Report and Note exchange (steven_nichols) ****
FHIR-34958: Imaging DiagnosticReport ontology (steven_nichols) Persuasive with Modification
FHIR-34949: Observation.category - Imaging vs Procedure (steven_nichols) Not Persuasive

Other Topics

FHIR-35762: Enable the use of US Core for non-provider specified data (corey_spears) ****
FHIR-34890: There are now about 19 profiles based on Observation, consider consolidating to all purpose Observation with code specific rule pages (dventon) ****
FHIR-34546: Remove text search requirement for Goal.description (cooper.thompson) ****

Trackers Submitted since ballot: ( Trackers submitted after HIMMS (March 18) will be considered for Jan 2023 Ballot of USCore)

FHIR-35998: race is needed in FamilyMemberHistory (john_moehrke) ****
FHIR-35997: allow ethnicity extension in FamilyMemberHistory (john_moehrke) ****
FHIR-35937: Consider Encounter.reason and reasonCode must support flags (cooper.thompson) ****
FHIR-34478: Several Vital Signs missing from CapabilityStatement US Core Server page (beckyangeles) ****

Review deferrals from prior cycles:

TBD

view this post on Zulip Eric Haas (Feb 18 2022 at 07:31):

Block Vote 3

The Cross-Group Project Work Group (CGP) plans to vote on Block Vote 3 of Jira Trackers on Thursday 3/3/2022 (Conference Call Details) which we have prepared with proposed dispositions and listed below.. If there are any of these anodyne items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

Commenters
@Eric Haas
@John Moehrke

Key: Summary (Reporter) Resolution

  1. FHIR-36058: Update US Core Yearly Updates (ehaas) Persuasive
  2. FHIR-36056: Update Condition Implementation Guidance to reflect recent changes (ehaas) Persuasive
  3. FHIR-35998: race is needed in FamilyMemberHistory (john_moehrke) Persuasive
  4. FHIR-35997: allow ethnicity extension in FamilyMemberHistory (john_moehrke) Persuasive

view this post on Zulip John Moehrke (Feb 18 2022 at 13:07):

thanks

view this post on Zulip Eric Haas (Mar 02 2022 at 01:17):

Based on the Feb 17th Call proposal to include both QuestionnaireResponse and Observations to Record and Store Assessments Responses in FHIR, I am drafting a mock up how this would look here. This is still incomplete. I will complete the draft the narrative introduction and Quick starts and overall guidance later today. Based on this, I will update all the assessment related trackers so we can review and vote on them on this Thursday's call.

view this post on Zulip Eric Haas (Mar 02 2022 at 20:20):

On tomorrow's Cross-Group Project Work Group (CGP) call we will be discussing and voting on the following US Core trackers. (Meeting info).

  1. Block vote 3

  2. Assessments

    • review of detailed proposal supporting option of both QuestionnaireResponse and Structured Observation to represent Assessment/Survey results
    • Vote on a raft of SDOH Assessment trackers.

  3. Don't add "OTH" to OMB Race categories.

  4. (time permitting ) In person comments with:

    • @Riki Merrick Topic: laboratory reporting
    • @Bas van den Heuvel Topics: requirements for server upgrading to USCore R4 from DSTU2 and what guidance is required.

The agenda and trackers are posted on Confluence. Please review the proposed dispositions and supporting material prior to the call.

view this post on Zulip Eric Haas (Mar 03 2022 at 20:19):

Block Vote 5

The Cross-Group Project Work Group (CGP) plans to vote on Block Vote 5 on Thursday 3/10/2022 (Conference Call Details) which we have prepared with proposed dispositions and listed below. Many of these items have been discussed here in Zulip and on the CGP calls for the past several weeks and the resolutions are based on the Feb 17th Call proposal to include both QuestionnaireResponse and Observations to Record and Store Assessments Responses in FHIR, and mock up draft proposal here. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

Commenters
@Josh Mandel
@Floyd Eisenberg
@Cooper Thompson
@Bas van den Heuvel
@Michelle (Moseman) Miller
@Ruby Nash

Issue key: Summary (Reporter) Resolution

  1. FHIR-35364: Streamline representation of SDOH screening instruments (jmandel) Persuasive with Modification
  2. FHIR-35283: Conflicting documentation for MS within US Core Social History Assessment Observation Profile (michelle.m.miller) Persuasive
  3. FHIR-35068: DSTU2 and R4 support status (bvdh) Persuasive with Modification
  4. FHIR-35067: DSTU2 support not specified (bvdh) Persuasive with Modification
  5. FHIR-35066: DSTU2 and R4 requirements hard to support (bvdh) Persuasive with Modification
  6. FHIR-34986: Response to the question posted in 10.96.1.1 (ruby_j_nash) Considered - No action required
  7. FHIR-34752: Assessment codes for individual components of existing assessments too limited and superfluous (feisenberg) Persuasive with Modification
  8. FHIR-34751: CLONE - Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation (feisenberg) Persuasive with Modification
  9. FHIR-34748: Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation (feisenberg) Persuasive with Modification
  10. FHIR-34551: MustSupport feedback for SDOH Assessment Obs profile (cooper.thompson) Not Persuasive

view this post on Zulip Eric Haas (Mar 22 2022 at 03:48):

On Thursday's Cross-Group Project Work Group (CGP) call we will be discussing and voting on the following US Core trackers. (Meeting info).

These items have been discussed here in Zulip and on the CGP calls for the past several weeks and the resolutions are based on the Feb 17th Call proposal to include both QuestionnaireResponse and Observations to Record and Store Assessments Responses in FHIR, and mock up draft proposal here. (TLDR)

  1. FHIR-35364: Streamline representation of SDOH screening instruments (jmandel) Persuasive with Modification
  2. FHIR-34752: Assessment codes for individual components of existing assessments too limited and superfluous (feisenberg) Persuasive with Modification
  3. FHIR-34751: CLONE - Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation (feisenberg) Marked as Duplicate of FHIR-34752 (Persuasive with Modification)
  4. FHIR-34748: Feedback on the inclusion of Observation.component as a Must Support element for systems to record multiple answers for a screening question in a single Observation (feisenberg) Persuasive with Modification
  5. FHIR-34384: Why is SDOH Assessment's Observation.component.code MS? Why is Observation.component? (Isaac.Vetter) Persuasive with Modification
  6. FHIR-34550: SDOH Category Codes section could call out that categorization is fuzzy for SDOH (cooper.thompson) Persuasive with Modification

The agenda and trackers are posted on Confluence. Please review the proposed dispositions and supporting material prior to the call.

view this post on Zulip Eric Haas (Mar 22 2022 at 03:51):

... we will also be discussing these in person comments:

@Riki Merrick : Lab results/ Diagnostic Report

FHIR-35316: Should be able to refer to media or images for pathology, hematology etc (RikiM) Not Persuasive
FHIR-35122: Need to provide some guidance when specific code systems are to be used in ServiceRequest (RikiM) Not Persuasive with

@Floyd Eisenberg , @Robert McClure
FHIR-36247 Modify OMB Race value set (in person)

view this post on Zulip Eric Haas (Apr 05 2022 at 19:39):

On Thursday's Cross-Group Project Work Group (CGP) call we will be discussing and voting on several US Core Trackers. The agenda and trackers are posted on Confluence. Please review the proposed dispositions and supporting material prior to the call. listed in the [Agenda]

(Meeting info).

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -