Secondary Use FHIR Server Implementation Guide
0.1.0 - ci-build
Secondary Use FHIR Server Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
The runtime serializes FHIR R4 (4.0.1) resources with HAPI FHIR. It applies focused request checks but does not run general FHIR or declared-profile validation.
PatientConditionAllergyIntoleranceMedicationRequestMedicationStatementObservationProcedureProvenanceThese types are also the default _type set when _type is omitted.
All listed resource types support _id, _elements=id, and _summary=count, in addition to the parameters below.
| Resource | Parameters |
|---|---|
| Patient | gender, birthdate, supported _has |
| Condition | code, subject, date |
| Observation | code, subject, patient, date |
| MedicationRequest | code, subject, patient, date |
| MedicationStatement | code, subject, patient, date |
| Procedure | code, subject, patient, date |
| AllergyIntolerance | code, patient, date |
| Provenance | date, target |
The parser also accepts Encounter searches with subject, patient, and date. The synthetic datasets contain no Encounters, and Encounter is not an export type.
Unsupported search parameters return HTTP 400 rather than being ignored.
Token code matching supports bare code, system|code, system|, and |code. Patient reference matching recognizes bare ids, relative and versioned Patient/{id} references, and absolute references below the configured source FHIR base as one source identity. Foreign absolute Patient URLs are not equated to local ids.
Patient reference parameters also support chaining. For example, subject:Patient.gender selects by gender, and subject:Patient._has:Condition:subject:code selects by a Patient's conditions. Where the table lists patient, that alias also supports Patient chains. Provenance uses target:Patient.*.
Keep result controls at the top level. Verkennen uses _summary=count, so its responses have no resource entries. _elements=id is also available for ordinary searches. Neither result control can be used as a reverse-chain target or a Patient-chained criterion.
Outside the count-only UI flow, ordinary adapter searches return the matched source resources without privacy transformation. Their Patient ids and identifiers are source values from the synthetic fixture. Pseudonymization and minimization apply only during adapter Bulk export.
| Resource | Candidate field or fields |
|---|---|
| Patient | birthDate |
| Condition | onsetDateTime or recordedDate |
| Observation | effectiveDateTime or issued |
| MedicationStatement | effectiveDateTime or dateAsserted |
| MedicationRequest | authoredOn |
| Procedure | performedDateTime |
| AllergyIntolerance | onsetDateTime |
| Provenance | recorded |
The implementation compares the leading ISO YYYY-MM-DD of the listed date/dateTime fields. It does not implement every FHIR choice type or interval rule. For Condition, Observation, and MedicationStatement, each comparison may match either candidate field. The generic date name is a prototype convenience and is not uniformly the standard FHIR R4 parameter name for these resource types.