HL7's Orchestration, Services, and Architecture Work Group (renamed from "Services Oriented Architecture") historically owns service functional models — identification / MPI-style services, de-identification service concepts, and orchestration patterns over healthcare endpoints.

Two threads matter for a FHIR lab. First, service functional models are the right mental frame for an adapter/console architecture: an orchestration layer over FHIR endpoints is exactly this WG's domain. Second, historical de-identification service work feeds how we think about DARTS-style "payload in, policy applied, cleansed payload out" operations — even when a specific ballot (like DARTS) is sponsored elsewhere.

What ImOnFHIR does with it: light-touch Builder-track reference. We are not a SOA WG dependency; we borrow the service-shape vocabulary when designing lab adapters and the Washer's future rule-config surface, and we keep linking to open HL7 pages rather than republishing committee prose.