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: April 18, 2023

Time: 2PM

Coordinates:  Join Zoom meeting: | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)


JD Nolen, Elliot Silver, Rob Hausam, David Barwin, Kathy Walsh, Ksenia Adamov

Co-chair: JD Nolen

Scribe: Marti Velezis

  • Quorum (Co-Chair + 4) Met 


  • JIRA Tickets - Backlog
  • Next Meeting


Meeting Notes

JIRA Trackers for Today

  • FHIR-26674 - ServiceRequest.asNeeded[x] and ServiceRequest.reason
    • Follow-up on Zulip discussion

    • Move this ticket to become a Change Request
      • Rob Hausam / Elliot Silver : 6-0-0
    • Updated the Proposed disposition
    • Add to the Thursday April 20, 2023 OO Main teleconference
  • FHIR-40765
    • Triaged the ticket; and need to link or classify as duplicate of FHIR-26674
    • Marti Velezis will send email to Pharmacy and OO Co-chairs with the following 2 options:
      • Follow MedicationRequest and DeviceRequest pattern with an invariant
        • RuleAsNeededFor can only be set if AsNeeded is empty or trueasNeededFor.empty() or asNeeded.empty() or asNeeded (dos-1)


      • Follow ServiceRequest with choice; and update the definition to be clear as to the difference from the reason element.
.... asNeededBoolean

.... asNeededCodeableConcept

  • 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??  
    • 4/18 - No further discussion this week - the submitter did not respond to the comments yet.
    • Rob will send Finnie Flores an email to get a response
  • 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
    • No further discussion this week - need to determine need with Hans Buitendijk 
    • Marti Velezis sent email to Hans with request to review this ticket.
  • FHIR-39448  
    • This ticket was reopened after R5 publication
    • We reviewed the previous proposed changes and confirmed that the changes still need to be made
    • Robert Hausam will add to the list of proposed changes if any additional changes are required; and we will discuss next time.
  • FHIR-38985
    • Added to the FHIR-I session at WGM on Thursday Q2
  • FHIR-38833
    • This ticket was reopened after R5 publication
    • Added to the FHIR-I session at WGM on Thursday Q2
    • See if we can get FHIR-I to add another time slot for Rob to participate

-------Adjourned meeting at 3:01PM EDT -----------

Next Meeting: April 25, 2023