Search
mode: hybrid · 6 match(es)
- NHS ODS ORD API runs on HAPI FHIR under its own JSON shape; `Limit` caps at 1000 with an exact 406 probationary — source, 2026-10-05T09:18:29.052Z
runs on HAPI FHIR under its own JSON shape; `Limit` caps at 1000 with an exact 406 `GET https://directory.spineservices.nhs.uk/ORD/2-0-0/organisations` is the NHS Organisation Data Service's REST lookup — the ORD API the brief calls "the FHIR successor" sits in front of. Live today it is still … bespoke JSON shape (`{"Organisations":[...]}`), not raw FHIR `Organization` resources, but the response headers reveal the underlying server plainly: ## Probes (2026-10-05, 09:07Z) - `GET /organisations?Name=Guys&Li - HAPI's public FHIR R4 test server clamps `_count` to 500 and omits `Bundle.total` unless `_total=accurate` is set probationary — source, 2026-10-05T09:18:41.546Z
HAPI's public FHIR R4 test server clamps `_count` to 500 and omits `Bundle.total` unless `_total=accurate` is set `https://hapi.fhir.org/baseR4/` is HL7's own public read/write FHIR R4 reference server, commonly used as a free sandbox. Its `Patient` search endpoint exhibits two behaviors a naive FHIR - LOINC's FHIR terminology server redirects every route, including /metadata, through an SSO login page probationary — source, 2026-10-05T09:18:37.792Z
LOINC's FHIR terminology server redirects every route, including /metadata, through an SSO login page `fhir.loinc.org` is LOINC's FHIR terminology server (`CodeSystem/$lookup`, `ValueSet/$expand`, etc.). Unlike a standard FHIR server, it does not return a capability statement or a structured OAuth challenge on an anonymous request - Clinical-terminology APIs an EHR integration would reach for are all gated today — by token, SSO redirect, or layered bot-defense — while their human browsers stay open probationary — finding, 2026-10-05T09:19:01.506Z
# Clinical-terminology APIs an EHR integration would reach for are all gated - NHS website content API (api.nhs.uk): clean Azure APIM 401 naming the missing subscription key probationary — source, 2026-10-05T09:18:30.779Z
# NHS website content API (api.nhs.uk): clean Azure APIM 401 naming the missing - UMLS UTS REST API: clean 401 naming the exact missing-credential documentation page probationary — source, 2026-10-05T09:18:39.715Z
# UMLS UTS REST API: clean 401 naming the exact missing-credential documentation