Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody.
A district hospital needs to transfer a patient to a tertiary campus while a laboratory specimen travels separately under a strict stability window. The coordinator must resolve the correct clinical entrance, choose eligible transport, retain custody at every hand-off, detect route and temperature delay, reveal only the minimum operational location, and close each journey only after the receiving team accepts it.
Compose multiple capabilities while the application owns user intent, policy, and continuity.
Authoritative systems own patient or specimen identity, clinical priority, consent, custody policy, stability window and receiving acceptance; the location workflow stores only opaque operational references.
Transfer ↔ opaque clinical reference, priority, consent and accepted entrance
GETGeocode API/api/places/geocodeThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Present approved campus entrances as explicit candidates, require coordinator confirmation, and retain the original query and selection revision.
Search and governed campus data resolve a stable Mappls Pin or enterprise entrance identity while preserving candidate, confirmer and revision evidence.
Transport assignment ↔ eligibility snapshot, vehicle, route revision and expiry
GETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}This normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Show last verified time and source, alert the responsible coordinator, and stop projecting an invented ETA or safe-condition claim.
Application policy filters vehicle, equipment, staff, service area and availability before network ETA ranks eligible options.
Custody event ↔ item reference, from/to role, event/receipt time and acknowledgement
GETRouting API with driving profile/{REST_KEY}/{resources}/driving/{geopositions}This is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Keep the journey at arrived-but-unaccepted, preserve both observations and escalate through a human reconciliation queue without exposing clinical data.
Event-time vehicle and custody observations derive progress and exceptions; role projections withhold clinical content and unnecessary precise history.
Condition exception ↔ sensor/source identity, threshold policy and reviewer outcome
GETThis API will get all the alarm configurations for a user./alarmThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Present approved campus entrances as explicit candidates, require coordinator confirmation, and retain the original query and selection revision.
The recipe starts from the normalized GET /api/places/geocode contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://atlas.mapmyindia.com/api/places/geocode?region=ind&address=237+Okhla+industrial+estate+phase+3+new+delhi%2C+delhi+110020&itemCount=1&bias=0&podFilter=example&bound=TAVI5Scurl --request GET \
--url 'https://atlas.mapmyindia.com/api/places/geocode?region=ind&address=237+Okhla+industrial+estate+phase+3+new+delhi%2C+delhi+110020&itemCount=1&bias=0&podFilter=example&bound=TAVI5S' \
--header "Accept: application/json" \
--header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
Every capability has one owner, bounded input, explicit timeout, and useful unavailable state.
Application intent survives refresh, back navigation, duplicate callbacks, and partial capability failure.
Provider identities, source fingerprints, request identities, and application decisions remain attributable.
Accessibility, privacy, quota, observability, support, and rollback evidence cover the complete user flow.
/api/places/geocodeGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETGets The List Of Alarm Config(s)/alarm/alarmLog/GETNearby API/api/places/nearby/jsonGETDistance Matrix Predictive ETA API/{REST_KEY}/distance_matrix_predictive/driving/{coordinates}GETThis API will get all the alarm configurations for a user./alarmGETAutoSuggest API/api/places/search/jsonGETRouting API with driving profile/{REST_KEY}/{resources}/driving/{geopositions}Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.
This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.