A hands-on tour of the fleet engine. Discover a deployment's CapabilityStatement, read a Patient shaped like that vendor, diff the same resource across Epic, Oracle Health (Cerner), and MEDITECH, and read the manifest to see exactly what changed.
Every cluster route serves its own metadata. Fetch it first — the CapabilityStatement is what your client library reads to decide which searches it is allowed to issue, and it is the first place two deployments of the same vendor diverge.
Request one patient id through each vendor route and diff the responses. The identifiers, the codings, the extensions, and the narrative all move. This is the exercise that turns "we support FHIR" into a list of concrete things your parser has to tolerate.
Each deployment carries a manifest describing precisely which mutations were applied and why, with a source citation per claim. Nothing is asserted without provenance, so when a mutation surprises you, you can check whether the real vendor does it too.
Issue the search Oracle Health rejects at the secure tier. Write to a MEDITECH route with a scope the real consent screen drops. The failures come back in the vendor's own error format, which is the part no generic sandbox reproduces. Vendor detail: Epic · Cerner · MEDITECH. Concepts in the map overview.