This IG uses the published ISiK location profiles directly. It does not define a
local shadow Location profile.
| ISiK profile | Ambulatory use |
|---|---|
ISiKStandort |
facility, practice site, ward, or functional area |
ISiKStandortRaum |
consultation, treatment, or resident room |
ISiKStandortBettenstellplatz |
bed placement when bed-level detail is known |
The canonical pattern is
https://gematik.de/fhir/isik/StructureDefinition/{profile}.
PraxisNursingHomeResidencyDE carries the resident's place through
NursingHomeLocationExt.
Location.partOf for the enclosing room, ward, and facility hierarchy.EncounterPraxis.location.location accepts the same ISiK profiles. A home visit
references the actual nursing-home Location; an in-practice encounter references
the practice site or room. PractitionerRole.location and
PraxisHealthcareServiceDE.location use the same location identities.
FHIR Location.type has an extensible binding to HL7 v3
ServiceDeliveryLocationRoleType. The standard codes cover broad delivery
settings but not the room-level functions needed in ambulatory practices.
This IG therefore publishes a hybrid ValueSet:
| Artifact | Canonical |
|---|---|
| Local CodeSystem | https://fhir.cognovis.de/praxis/CodeSystem/praxis-workplace-function |
| Hybrid ValueSet | https://fhir.cognovis.de/praxis/ValueSet/praxis-workplace-function |
Room and area locations should use the local function codes. Site-level
locations may use suitable v3 codes such as PROFF or RADDX.
Keep these axes separate:
| Axis | FHIR carrier |
|---|---|
| Physical shape | Location.physicalType |
| Operational function | Location.type |
| Offered service | HealthcareService.type and HealthcareService.specialty |
| Practitioner qualification | Practitioner.qualification and PractitionerRole |
| Live occupancy or queue state | Encounter, Appointment, and Task |
HealthcareService.location links an offering to a place. It does not replace
the workplace function. Queue position and occupancy are runtime state and are
not encoded as normative Location codes.
When several organizations share a physical site, publish one Location per
physical place. Each organization references that identity through its
PractitionerRole.location; organization-specific routing remains on
PractitionerRole.organization. Installation display names belong in
Location.name or Location.alias, not in the normative function coding.
The workplace location examples cover a practice site, shared reception, waiting area, consultation room, blood-draw room, ECG room, radiology room, dental room, and virtual workspace. The artifact index links each generated instance.