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 24, 2023

Time: 3PM ET

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


JD Nolen, Rob Hausam, Elliot Silver, Barbee Whitaker, Hans Buitendijk, Nancy Spector, John Hatem, Karen Moniz, Marti Velezis

Co-chair: Hans Buitendijk

Scribe: Hans/Marti

  • Quorum (Co-Chair + 4) Met 


  • Administrative
  • BDP Transformation - Next Week
  • Module Discussions
    • BDP Module - Next week with transformation
    • Nutrition Module
    • Device Module
  • Status on JIRA Tickets
  • AOB
  • Next Meeting


HCP_Backlog - FOR REVIEW (includes Nutrition resources)

HCP_Ballot Related - JIRA that need to be completed by R5 (many of these are related to Normative content)

HCP_Work In Progress - Items that need to be updated in the build and/or QA for completion

Module Pages

The following are draft pages to organize and author content for each of our health care product resources: 


Upcoming Topics/Due Dates



May 1, 2023Nutrition Module, Device Module
May 6-May 12

HL7 Connectathon,  WGM, WGM+ in New Orleans

Unscheduled Discussions

Action Items

Instructions: Type your task here, using "@" to assign to a user and "//" to select a due date

Action Item


  • Administrative
  • JIRA Tickets
  • value set
  • Nutrition Module - not discussed
  • BDP - not discussed - next week
    • BDP Transformations
      • Irradiated Transformation
      • Pediatrics
    • BDP Module
  • Device
    • Devices Module - not discussed
    • Review Miro Board for to address questions in the comments
      • Introduced the topic and will continue with others on the call.
      • Need to pick up next time
    • FHIR-40503
      • DRAFT: Motion to recognize that we reviewed the search parameters and agree to 


        • add version-type including .type and .value
        • update udi-carrier to udi-carrier-hrf as it is HRF format only


        • add device-identifier including .udiDeviceIdentifier.deviceIdentifier
        • add model-number
        • add version including .value only 
        • add version-type including .type and .value

        Additional search parameters may be identified in the future that may be used widely enough to consider for inclusion.

      • We will continue to add to the list next week (and review any comment submitted in the meantime.)

      • Will update ticket to include DeviceDefinition.

Next meeting:  May 1, 2023

------------Adjourned at 4:02PM EDT---------------

--------end of call--------


Note these are issues that we did not have time to discuss, or already have been discussed, but may not be ready for disposition (i.e., waiting for input or additional work needs to be completed).


  • TBD

  • FHIR-32756 - request-insurance extension needs more context given in the description
  • Waiting for Jose Costa-Teixeira  to respond to comments; this should be included in a future call (August 8 or 15)
  • FHIR-19516 - Substantive workflow changes for OO resources
  • Needs to be assigned (Status = Resolved Change Required)
  • TBD

  • TBD


  • Pending additional review

Appointment, AppointmentResponse, ArtifactAssessment, 

AuditEvent, Basic, BodyStructure, CarePlan, ChargeItem, ChargeItemDefinition, Claim, ClinicalUseDefinition, Communication, 

CommunicationRequest, Composition, Condition, Consent, Contract, DetectedIssue, itself, DeviceAssociation, DeviceDispense,DeviceMetric, DeviceRequest, DeviceUsage, 

DiagnosticReport, DocumentReference, Encounter, EvidenceReport, 

EvidenceVariable, ExplanationOfBenefit, FamilyMemberHistory, Flag

GenomicStudy, Group, GuidanceResponse, ImagingSelection, ImagingStudy,

InventoryItem, InventoryReport, Invoice, List, MeasureReport, MedicationAdministration, 

MedicationDispense, MedicationRequest, MessageHeader, 

MolecularSequence, NutritionIntake, Observation, 

ObservationDefinition, Permission, PlanDefinition, Procedure,Provenance, 

QuestionnaireResponse, RequestOrchestration, Requirements, ResearchSubject, 

RiskAssessment, Schedule, ServiceRequest, Signature, Specimen, 

SupplyDelivery, SupplyRequest, Task and Transport

  • FHIR-31750 - Complement Valueset-identifier-type for Device identifiers 

  • Approved; Updating UP-232
  • Examples
  • Search Parameters
  • Mappings (TBD)
  • Need to complete work on Device Definition to make it consistent with or address variations from Device resource
  • TBD


  • FHIR-26429  - Consider adding extension to allow fuzzy timing for DeviceRequest.occurrence

  • Note - Robert Hausam there is an outstanding question in comments for you - also see under Service Request.

  • Need update from OO on FHIR

  • FHIR-26948 - Create examples for prosthetics (e.g. glasses, lenses) in DeviceRequest; Comment added for Jose - Pending
  • See topic below (Device Request and VisionPrescription)
  • Device Request and VisionPrescription

  • Will be kept open until UDI IG has addressed these and can confirm it covers it.
  • FHIR-34491 - Add statusReason in ServiceRequest

  • FHIR-40631
    • Some OO requests need basedOn to RequestOrchestration
    • NutritionOrder (was NutritionRequest), ServiceRequest (Diagnostic/Procedure/ReferralRequest), VisionPrescription

  • FHIR-38818 - Clarify SupplyDelivery for shipment vs reception

Product Pattern
  • Need Jose Costa-Teixeira and Carl Leitner on the call.
  • Is there a benefit to have definition for BDP, in blood bank with ordering is one (and maybe only example).