Per-deployment FHIR routes that proxy a canonical response, then mutate the payload to match the shape of a real EHR endpoint — Epic, Oracle Health (Cerner), or MEDITECH.
Epic publishes one CapabilityStatement. Production hospitals deploy nine distinct shapes of it. Reproducing every endpoint individually would be noise; reproducing the shape clusters is the useful abstraction, because the cluster is what your integration actually has to survive. Roughly 3,800 production FHIR endpoints were harvested from the published Brands Bundles and grouped by CapabilityStatement shape.
CapabilityStatements, search-parameter subsets, OperationOutcome formats, and SMART on FHIR variants all match the source EHR. Same patients underneath, three vendor personalities at the wire — so you build once and integrate three times without a partner contract. Vendor quirks reproduced include Epic's dual-coded category OIDs and narrow Patient.Create demographics subset, Oracle Health's rejection of a bare Patient search at the secure tier with a verbatim diagnostic, and MEDITECH's silent drop of patient/*.write at consent.
Element-level deviation tables against US Core 6.1, every row source-cited with a verbatim quote and a date checked: Epic, Oracle Health (Cerner), and MEDITECH. For a hands-on tour, read using the map. Browse the public deployment map at /map.