FHIR Chat · US Core Jan 2022 Ballot · argonaut

Stream: argonaut

Topic: US Core Jan 2022 Ballot

view this post on Zulip Eric Haas (Oct 07 2021 at 18:32):

US Core is preparing for a 2022 January Ballot to address current trackers and incorporate new data classes and elements in USCD v2 . The Key US Core Dates table captures the rough outline for the CGP design calls Thursdays 1-2 PM ET.

The Cross-Group Project Work Group (CGP) is meeting next Thursday 10/14 from 2-3 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

  • @Linda
  • @Emma Jones
  • @Josh Mandel
  • @Jay Lyle
  • @Nick Radov
  • @Monique van Berkum
  • @Daniel Tam
  • @Stephen MacVicar

Key: Summary (Reporter) Resolution

  1. FHIR#34073: Medication.ingredient.item.code is a codeableConcept but is not bound to a value set (lmichaelsen) Not Persuasive
  2. FHIR#33243: US Core Procedure.performed[x] is 1..1 but not conducive with the various procedure.statuses (emmanurse) Persuasive
  3. FHIR#33160: docref missing actual content as mandatory element in narrative (ehaas) Persuasive
  4. FHIR#33159: Clarify distinct between repeated search params and composite params (jmandel) Persuasive
  5. FHIR#33156: Clarify requirement on date searches without prefix (smacvicar) Persuasive
  6. FHIR#33121: It's unclear why AllergyIntolerance.reaction.modifierExtension should be a Summary element (jlyle) Not Persuasive with Modification
  7. FHIR#33079: US Core to USCDI guidance page -- add patient email (dtam_onemedical) Persuasive with Modification
  8. FHIR#33069: remove requirement to use 401 only where authentication failed from capabiltystatement (ehaas) Persuasive with Modification
  9. FHIR#32857: For Condition, US Core is binding all repetitions of category instead of slicing (mvanber) Persuasive
  10. FHIR#32068: Add CMS Place of Service to Location profile (nradov) Not Persuasive

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

view this post on Zulip Daniel Tam (Oct 14 2021 at 17:49):

@Eric Haas : Thanks for the update on the Jan 2022 ballot, and for including #33079. I unfortunately have a meeting conflict -- please let me know if you need anything from me. Feel free to also ping me here if you need to chat.

view this post on Zulip Eric Haas (Oct 21 2021 at 15:44):

US Core is preparing for a 2022 January Ballot to address current trackers and incorporate new data classes and elements in USCD v2 . The Key US Core Dates table captures the rough outline for the CGP design calls Thursdays 1-2 PM ET.

The Cross-Group Project Work Group (CGP) is meeting next Thursday 10/28 from 2-3 PM Eastern (meeting link). We plan to vote on Block Vote 2 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

  • @Linda
  • @Cooper Thompson
  • @Daniel Tam
  • @Ellen Nies
  • @Robert McClure
  • @Mark Kramer
  • @Keith Salzman
  • @Floyd Eisenberg
  • @Michelle (Moseman) Miller
  • Glen Dickenson

Key: Summary (Reporter) Resolution

  1. FHIR#34133: US Core Birth Sex Extension (lmichaelsen) Not Persuasive
  2. FHIR#34127: Race and Ethnicity is Not Must Support (lmichaelsen) Not Persuasive
  3. FHIR#34036: Patient Ethnicity does not have the same Null options as Race (lmichaelsen) Not Persuasive
  4. FHIR#33609: Reconsider must-support guidance for unsupported data (cooper.thompson) Not Persuasive
  5. FHIR#33080: Utilize ""use"" field for patient previous name and previous address (dtam_onemedical) Persuasive with Modification
  6. FHIR#33048: Clarify Guidance for missing data for Coding data type element (ellennies_cerner) Persuasive with Modification
  7. FHIR#32953: Change drug class value set for allergens to align with C-CDA (Rob_McClure) Persuasive
  8. FHIR#32848: Differentials include things unchanged from base resource and/or parent profile (Mark_Kramer) Persuasive with Modification
  9. FHIR#32720: Provide a caution to the user that a query of MedicationRequest does not provide complete information. (klsalzman) Persuasive with Modification
  10. FHIR#17305: Goal.description incorrect details (feisenberg) Not Persuasive
  11. FHIR#8523: DocumentReference.content (michelle.m.miller) Not Persuasive
  12. FHIR#6281: Use AuditEvent/Provenance for Authenticity/Accountability Metadata (gdickinson) Not Persuasive

view this post on Zulip Mark Kramer (Oct 21 2021 at 20:05):

@Eric Haas I would like to discuss separately -- FHIR#32848: Differentials include things unchanged from base resource and/or parent profile (Mark_Kramer) Persuasive with Modification --- I don't understand the proposed resolution.

view this post on Zulip Eric Haas (Oct 21 2021 at 20:22):

1) see this chat for some background discussion and context.
Bottom line if the ig publisher doesn't gray out the duplicate elements, we will update the diffs where appropriate at our discretion to remove them.

view this post on Zulip Eric Haas (Oct 30 2021 at 01:25):

US Core is preparing for a 2022 January Ballot to address current trackers and incorporate new data classes and elements in USCD v2 . The Key US Core Dates table captures the rough outline for the CGP design calls Thursdays 1-2 PM ET. The next block vote is being prepared and will be posted Thursday.

view this post on Zulip Eric Haas (Nov 03 2021 at 22:46):

US Core is preparing for a 2022 January Ballot to address current trackers and incorporate new data classes and elements in USCD v2 . The Key US Core Dates table captures the rough outline for the CGP design calls every Thursdays 1-2 PM ET.

The Cross-Group Project Work Group (CGP) is meeting next Thursday 10/11 from 1-2 PM Eastern (meeting link). We plan to vote on Block Vote 3 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.

Please note that no trackers submitted after the 11th will be considered for addition to the Jan 22 Ballot (excluding technical corrections and variance requests).

Commenters

  • @Cooper Thompson
  • @Yunwei Wang
  • @Sarah Gaunt
  • @Keith Salzman
  • @Howard Strasberg
  1. Key: Summary (Reporter) Resolution
  2. FHIR#34231: USCDI v2 update: Support SDOH Problems/Health Concerns (ehaas) Persuasive
  3. FHIR#34230: USCDI v2 update: Support SDOH Interventions (ehaas) Persuasive
  4. FHIR#34229: USCDI v2 update: Support SDOH Goals (ehaas) Persuasive
  5. FHIR#34228: USCDI v2 update: Support SDOH Assessment (ehaas) Persuasive
  6. FHIR#34227: USCDI v2 update: Clinical Testing and Imaging (ehaas) Persuasive
  7. FHIR#34226: USCDI v2 update: Support Encounter Data Elements (ehaas) Persuasive
  8. FHIR#34225: USCDI v2 update: Support Problems Data Elements (ehaas) Persuasive
  9. FHIR#34224: USCDI v2 update: Support Care Team Data Elements (ehaas) Persuasive
  10. FHIR#34217: MedicationRequest should not require composite OR search on intent (cooper.thompson) Not Persuasive
  11. FHIR#34202: USCDI v2 update: Add Sexual Orientation and Gender Identity (ehaas) Persuasive
  12. FHIR#34061: Clarify MustSupport for Observaiton.component.value[x] vs dataAbsentReason (yunwwang) Persuasive with Modification
  13. FHIR#32949: Remove requirement for CarePlan.text (cooper.thompson) Not Persuasive
  14. FHIR#32845: Encounter.diagnosis not set to Must Support (minigrrl) Not Persuasive
  15. FHIR#32844: Condition.encounter not Must Support yet implementation guidance references the data element as an ""and"" condition for querying (minigrrl) Persuasive
  16. FHIR#32721: Discrepancy in use of terms and between base spec and this spec (klsalzman) Considered - No action required
  17. FHIR#30390: Do not overload SNOMED code for No Known Allergies (hstrasbe) Persuasive with Modification

view this post on Zulip Yunwei Wang (Nov 04 2021 at 13:31):

The resolution for FHIR#34061 is still not clear. @Eric Haas
"A server that always values Pulse-Ox + FlowRate + Concentration does not need to support DAR." this is fine but the scope is limited on Pulse-Ox. Does this apply to BP profile too? (or any other VitalSign profiles using component)
Could this resolution be generalized to something like Systems that never provide an observation without a component.value are not required to support Observation.component.dataAbsentReason

view this post on Zulip Eric Haas (Nov 04 2021 at 15:48):

@Yunwei Note that BP components have are mandatory

image.png

view this post on Zulip Eric Haas (Nov 04 2021 at 15:49):

vs the pulse ox components. Does that help explain the difference?

view this post on Zulip Yunwei Wang (Nov 04 2021 at 16:00):

The component is mandatory but the component.value[x] is not. So it is valid to have a systolic component without value.

view this post on Zulip Eric Haas (Nov 04 2021 at 16:07):

  1. "Systems that never provide an observation without a component.value are not required to support Observation.component.dataAbsentReason"

  2. vs-3 Observation.component If there is no a value a data absent reason must be present
    Expression : value.exists() or dataAbsentReason.exists()

would assume for pulse ox - no value --> no component

for bp I doubt that a system will always have both component value and since they are mandatory and based on the invariant a DAR will be needed here.

view this post on Zulip Eric Haas (Nov 04 2021 at 16:24):

NOTE one time changes on 11/4/2021 made to Block Vote-3 and Block Vote-4 based on reviewer feedback noted with :bangbang: there will be no more changes after this.

Addition of Block Vote-4

The Cross-Group Project Work Group (CGP) is meeting next Thursday 10/11 from 1-2 PM Eastern (meeting link). We plan to vote on Block Vote 3 (see above) AND Block Vote 4 of Jira Trackers. We have prepared proposed dispositions and listed the trackers for 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.

Please note that no trackers submitted after the 11th will be considered for addition to the Jan 22 Ballot (excluding technical corrections and variance requests).

Block -3 (same as above)

Commenters

  • @Cooper Thompson
  • @Yunwei Wang
  • @Sarah Gaunt
  • @Keith Salzman
  • @Howard Strasberg

. Key: Summary (Reporter) Resolution

  1. FHIR#34231: USCDI v2 update (ehaas) Persuasive :bangbang:
    1. FHIR#34230: USCDI v2 update: Support SDOH Interventions (ehaas) Persuasive :bangbang:
    1. FHIR#34229: USCDI v2 update: Support SDOH Goals (ehaas) Persuasive :bangbang:
    1. FHIR#34228: USCDI v2 update: Support SDOH Assessment (ehaas) Persuasive :bangbang:
    1. FHIR#34227: USCDI v2 update: Clinical Testing and Imaging (ehaas) Persuasive :bangbang:
    1. FHIR#34226: USCDI v2 update: Support Encounter Data Elements (ehaas) Persuasive :bangbang:
    1. FHIR#34225: USCDI v2 update: Support Problems Data Elements (ehaas) Persuasive :bangbang:
    1. FHIR#34224: USCDI v2 update: Support Care Team Data Elements (ehaas) Persuasive :bangbang:

  2. FHIR#34217: MedicationRequest should not require composite OR search on intent (cooper.thompson) Not Persuasive

  3. FHIR#34202: USCDI v2 update: Add Sexual Orientation and Gender Identity (ehaas) Persuasive
  4. FHIR#34061: Clarify MustSupport for Observaiton.component.value[x] vs dataAbsentReason (yunwwang) Persuasive with Modification :bangbang:
  5. FHIR#32949: Remove requirement for CarePlan.text (cooper.thompson) Not Persuasive
  6. FHIR#32845: Encounter.diagnosis not set to Must Support (minigrrl) Not Persuasive
  7. FHIR#32844: Condition.encounter not Must Support yet implementation guidance references the data element as an ""and"" condition for querying (minigrrl) Persuasive with Modification :bangbang:
  8. FHIR#32721: Discrepancy in use of terms and between base spec and this spec (klsalzman) Considered - No action required
  9. FHIR#30390: Do not overload SNOMED code for No Known Allergies (hstrasbe) Persuasive with Modification

Block -4

Commenters

  • @Saul Kravitz
  • @Gay Dolin
  • @Kensaku Kawamoto

Trackers are previously deferred and reopened after publishing US-Core 4.0.0 are marked with a :checkbox:

Row. Key: Summary (Reporter) Resolution

  1. FHIR#31997: Update Valuesets in PractitionerRole (saul_kravitz) Considered for Future Use
  2. :checkbox: FHIR#30478: Should US Core Procedure Value set include LOINC? (GDolin) Persuasive with Modification :bangbang:
  3. :checkbox: FHIR#20119: Add date search parameters to reduce latency - USCore #142 (kensaku_kawamoto) Persuasive with Modification :bangbang:
  4. :checkbox: FHIR#20102: Add Patient Birthtime extension and make must support - USCore #125 (kensaku_kawamoto) Not Persuasive
  5. :checkbox: FHIR#20093: Make Encounter Diagnosis Role extensible rather than preferred - USCore #116 (kensaku_kawamoto) Not Persuasive

view this post on Zulip Eric Haas (Nov 04 2021 at 19:42):

NOTE one time changes on 11/4/2021 made to Block Vote-3 and Block Vote-4 based on reviewer feedback noted with :bangbang: there will be no more changes after this.

view this post on Zulip Eric Haas (Dec 07 2021 at 19:33):

The US Core Jan 2022 Ballot version is ready to go here: http://hl7.org/fhir/us/core/2022Jan/
Thanks to all who contributed to this version. We have highlighted all the new stuff to make it easier to review and added few goodies such as consolidated Must Support element tables and slick interface mapping USCDI Data elements to US Core artifacts . As usually is the case, we expect a fair number of comments when the ballot opens next week.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -