ANSI Anti-Trust Policy:

Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).

Meeting Details

Date: March 21, 2023

Time: 2PM

Coordinates:  Join Zoom meeting: https://zoom.us/j/5100467805 | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)

Attendees

Elliot Silver, David Barwin, Yanick Gaudet, Rob Hausam, Marti Velezis

Co-chair: Marti Velezis

Scribe: Marti Velezis

  • Quorum (Co-Chair + 4) Met 

Agenda

  • JIRA Tickets - Backlog
  • Next Meeting

LINKS TO JIRA - OO on FHIR DASHBOARDS

Meeting Notes

  • FHIR-40286 - Getting issue details... STATUS

    • Can be solved using ServiceRequest.orderDetail.parameterFocus introduced with Jira 31584. Note that you are required to specify a parameter code/value with it which could be a target dose or instruction to infuse the entire product.

    • Retracted by Submitter
  • FHIR-40664 - Getting issue details... STATUS
    • Found a typo - Technical Correction
      • Assigned to Rob Hausam to update in R5 publication with other changes
  • FHIR-40397 - Align product code search parameters
    • Discussed the lack of semantic consistency between code* search parameters - (*code is equivalent to the kind or type)
      • BDP.productCode is represented by code search parameter
      • NutritionProduct.code is represented by code search parameter
      • Device.definition.concept is represented by code search parameter
        • This should be changed to or add Device.type as it is equivalent to the other code search parameters; the codable definition may yield differences across resources
        • This will be added to Monday's HCP call
  • FHIR-34491 - Add statusReason in ServiceRequest

    • We initially discussed that we did not see value in adding statusReason as we didn't know what additional value it would bring (esp. with the example of Procedure.statusReason value set)

    • We left a comment to reporter to provide use cases for us to consider
    • Also – could this be used for the next JIRA re: verbal orders??  
  • FHIR-34207 - Add attribute to document confirmation
    • We started to discuss this ticket - re: As various orders may be place verbally, a ServiceRequest needs to be able to document that this ServiceRequest confirms a verbal order that may already have been fulfilled, thus not re-initiated.
    • Proposal to add extension
      • The backbone includes .time and .note (Annotation) – and annotation also includes  time.  Need to evaluate how to represent this information. 
    • We also discussed whether or not there was some connection to the status and statusReason

Next Meeting: March 28, 2023

------end of meeting-----