Outlier MEDITECH (Greenfield Workspace + production fleet) cluster: just 4 of 549 production endpoints share this CapabilityStatement shape, including Armstrong County Memorial Hospital. This cluster advertises 36 US Core 6.1 profiles in its CapabilityStatement. A long-tail deployment variant that integrators rarely see in vendor sandbox documentation.
A CapabilityStatement shape cluster groups production FHIR endpoints by the exact CapabilityStatement they serve at runtime. MEDITECH (Greenfield Workspace + production fleet) publishes one reference CapabilityStatement, but production hospitals deploy several distinct shapes of it — each cluster is one of those shapes.
ddfad6b7f537e411…AllergyIntolerance · CarePlan · CareTeam · Condition · Device · DiagnosticReport · DocumentReference · Encounter · Goal · Immunization · Location · MedicationRequest · Observation · Organization · Patient · Practitioner · PractitionerRole · Procedure · Provenance
Group · ValueSet
PA (1) · TN (1) · GA (1) · NY (1)
Greenfield sandbox runs US Core STU6 (CapStmt dated 2023-05-25, software v2.0.0), but Phase F's harvest of 542 production customer endpoints shows almost no customer on STU6: 322 advertise software version `1.0.0` and 12 advertise `1.0`, both dated 2021-04-01 — the frozen R4 baseline An integrator who builds against the Greenfield sandbox is testing US Core STU6, but their actual MEDITECH customers are running the R4 v1.0.0 baseline frozen in 2021. Profile changes between the 2021 baseline and STU6 are nontrivial — including us-core-vital-signs supportedProfile shape, us-core-pulse-oximetry inclusion criteria, and date-period semantics on us-core-encounter — so sandbox-passing integrations may fail against real customer endpoints purely from version drift. This compounds the well-known gotcha that vendor sandboxes track ahead of customer reality. In MEDITECH's case the gap is unusually wide because Greenfield is also out of sync with MEDITECH's own newest published implementation (STU7 v2.0.0, observed at one customer endpoint outside the brands-bundle harvest).
From the public MEDITECH (Greenfield Workspace + production fleet) overlay finding sweep (2026-04-27). Full vendor overlay has 4 findings with verbatim quotes and source URLs.
This outlier cluster has too few production endpoints for us to host a dedicated mock under /v/cluster/meditech-cluster-D/ today. The modal MEDITECH (Greenfield Workspace + production fleet) cluster is the wire shape that most production deployments use — that's the right starting point for integration testing.
MEDITECH Greenfield Workspace publishes a US Core STU6 v2.0.0 implementation (dated 2023-05-25) that is anonymous-readable for CapabilityStatement and SMART configuration. Authenticated probing is gated by an authorization_code flow with PKCE S256 and `client_secret_post`; identity is bound to a single operator-provisioned Google ID per client_id with no self-service management. As of 2026-04-27 the consent step rejects developer Google identities at Greenfield's user-to-client allowlist with a bare `error=access_denied` and no diagnostic body; the only documented recovery path is an email round-trip with greenfieldinfo@meditech.com. The Greenfield sandbox runs a US Core version (STU6) in use by almost no MEDITECH production customer per Phase F's harvest of 542 customer endpoints — most customers remain on the frozen R4 v1.0.0 baseline from 2021. Synthetic sandbox modeled after observed MEDITECH (Greenfield Workspace + production fleet) deployment shapes. Not affiliated with the vendor or any listed hospital. Trademarks used for identification only.