Modal MEDITECH (Greenfield Workspace + production fleet) cluster: 133 of 549 production endpoints (24%) deploy this exact CapabilityStatement shape, concentrated in MO (6), NE (6), WI (6). This cluster advertises 36 US Core 6.1 profiles in its CapabilityStatement.
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.
4741eedbf08f2d3e…AllergyIntolerance · CarePlan · CareTeam · Condition · Device · DiagnosticReport · DocumentReference · Encounter · Goal · Immunization · Location · MedicationRequest · Observation · Organization · Patient · Practitioner · PractitionerRole · Procedure · Provenance
Group · ValueSet
MO (6) · NE (6) · WI (6) · IL (6) · KS (6) · CA (5) · OK (5) · GA (5) · AR (5) · TX (5)
Greenfield's SMART configuration advertises `system/*` scopes for roughly 30 resources, yet Greenfield does not support the client_credentials grant — the machine-readable spec advertises capabilities the docs explicitly disable An integrator reading the machine-readable SMART configuration would reasonably conclude they can request Backend-Services-style access to Greenfield. They cannot — and they will only discover this by attempting the grant and observing the error, or by reading the human-readable PDF. This is a SMART App Launch STU 2.2 conformance gap: per §5.1, advertised capabilities must be issuable. Where the SMART config and the human-readable docs disagree, the SMART config is wrong.
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-G/ 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.