When fetching the CapabilityStatement from an Aidbox instance (e.g., https://<instance>.aidbox.app/fhir/metadata), the software object is empty/absent. The server name is only available via implementation.description:
{
"resourceType": "CapabilityStatement",
"fhirVersion": "4.0.1",
"implementation": {
"description": "Aidbox FHIR Server"
}
// software.name is missing
}Per the FHIR R4 CapabilityStatement spec:
software.name — Name the software is known by.
Most FHIR clients use software.name to identify the server. Because Aidbox omits it, the server shows up as "Unknown FHIR Server" in management UIs that follow the standard pattern.
Expected: software.name should be populated (e.g., "Aidbox FHIR Server" or "Aidbox").
Tested on: obqermtecb.aidbox.app (free tier), March 2026.
When fetching the CapabilityStatement from an Aidbox instance (e.g.,
https://<instance>.aidbox.app/fhir/metadata), thesoftwareobject is empty/absent. The server name is only available viaimplementation.description:{ "resourceType": "CapabilityStatement", "fhirVersion": "4.0.1", "implementation": { "description": "Aidbox FHIR Server" } // software.name is missing }Per the FHIR R4 CapabilityStatement spec:
Most FHIR clients use
software.nameto identify the server. Because Aidbox omits it, the server shows up as "Unknown FHIR Server" in management UIs that follow the standard pattern.Expected:
software.nameshould be populated (e.g.,"Aidbox FHIR Server"or"Aidbox").Tested on:
obqermtecb.aidbox.app(free tier), March 2026.