Important: This is a draft IG for trial use. Click here to give feedback.

HdBe-HealthcareOrganization

ProfileDescriptionStatusURL
HdBe-HealthcareOrganization

The physical location of a healthcare organization. A healthcare organization is an organization that offers and provides medical, paramedic and/or nursing care to patients/clients. Examples include: hospitals, nursing homes, doctor’s offices.

drafthttps://fhir.healthdata.be/StructureDefinition/HdBe-HealthcareOrganization
HdBe-HealthcareOrganization-Organization

The organizational information of a healthcare organization. A healthcare organization is an organization that offers and provides medical, paramedic and/or nursing care to patients/clients. Examples include: hospitals, nursing homes, doctor’s offices.

drafthttps://fhir.healthdata.be/StructureDefinition/HdBe-HealthcareOrganization-Organization

HdBe-HealthcareOrganization

Instructions

HealthcareOrganization is mapped to this Location profile and a profile on Organization (HdBe-HealthcareOrganization-Organization). This Location profile acts as the focal resource of HealthcareOrganization because most references to this CBB are concerned about the recording of the physical location where the care to patient takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the Location.managingOrganization element.

Healthcare organizations usually consist of multiple organizational levels and physical locations. The hierarchical structure may be captured by using multiple instances of this HealthcareOrganization profile using the Location.partOf element to refer to their parent Location. Each instance refers the HdBe-HealthcareOrganization-Organization at the appropriate level in the hierarchy.


idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
locationIdentificationNumberΣ I0..1IdentifierPattern
departmentIdentificationNumberΣ I0..1IdentifierPattern
statusΣ ?!0..1codeBinding
operationalStatusΣ0..1CodingBinding
nameΣ0..1string
alias0..*string
descriptionΣ0..1string
modeΣ0..1codeBinding
typeΣ0..*CodeableConceptBinding
telecomI0..*HdBe-ContactInformation
address0..1HdBe-AddressInformation
physicalTypeΣ0..1CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
longitude1..1decimal
latitude1..1decimal
altitude0..1decimal
managingOrganizationΣ I0..1Reference(Organization | HdBe-HealthcareOrganization Organization)
partOfI0..1Reference(Location)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
daysOfWeek0..*codeBinding
allDay0..1boolean
openingTime0..1time
closingTime0..1time
availabilityExceptions0..1string
endpointI0..*Reference(Endpoint)

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
locationIdentificationNumberΣ I0..1IdentifierPattern
departmentIdentificationNumberΣ I0..1IdentifierPattern
statusΣ ?!0..1codeBinding
operationalStatusΣ0..1CodingBinding
nameΣ0..1string
alias0..*string
descriptionΣ0..1string
modeΣ0..1codeBinding
typeΣ0..*CodeableConceptBinding
telecomI0..*HdBe-ContactInformation
address0..1HdBe-AddressInformation
physicalTypeΣ0..1CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
longitude1..1decimal
latitude1..1decimal
altitude0..1decimal
managingOrganizationΣ I0..1Reference(Organization | HdBe-HealthcareOrganization Organization)
partOfI0..1Reference(Location)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
daysOfWeek0..*codeBinding
allDay0..1boolean
openingTime0..1time
closingTime0..1time
availabilityExceptions0..1string
endpointI0..*Reference(Endpoint)

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
locationIdentificationNumberΣ I0..1IdentifierPattern
departmentIdentificationNumberΣ I0..1IdentifierPattern
statusΣ ?!0..1codeBinding
operationalStatusΣ0..1CodingBinding
nameΣ0..1string
alias0..*string
descriptionΣ0..1string
modeΣ0..1codeBinding
typeΣ0..*CodeableConceptBinding
telecomI0..*HdBe-ContactInformation
address0..1HdBe-AddressInformation
physicalTypeΣ0..1CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
longitude1..1decimal
latitude1..1decimal
altitude0..1decimal
managingOrganizationΣ I0..1Reference(Organization | HdBe-HealthcareOrganization Organization)
partOfI0..1Reference(Location)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
daysOfWeek0..*codeBinding
allDay0..1boolean
openingTime0..1time
closingTime0..1time
availabilityExceptions0..1string
endpointI0..*Reference(Endpoint)

Mapping FHIR profile to CBB

PathmapCBB
LocationHealthcareOrganizationHdBe-HealthcareOrganization
LocationHealthcareOrganization.OrganizationLocationHdBe-HealthcareOrganization
Location.identifier:locationIdentificationNumberHealthcareOrganization.OrganizationLocation.LocationIdentificationNumberHdBe-HealthcareOrganization
Location.identifier:departmentIdentificationNumberHealthcareOrganization.OrganizationLocation.DepartmentIdentificationNumberHdBe-HealthcareOrganization
Location.nameHealthcareOrganization.OrganizationLocation.LocationNameHdBe-HealthcareOrganization
Location.telecomHealthcareOrganization.ContactInformationHdBe-HealthcareOrganization
Location.addressHealthcareOrganization.AddressInformationHdBe-HealthcareOrganization

zib HealthcareOrganization-Location difference

Concept Category Description
description textual Added explanation, in StructureDefinition.description, about how and why the CBB is mapped to two profiles.
identifier element Added a slice of identifier to map LocationNumber which isn't mapped in the Nictiz profiles.
identifier element Added DepartmentNumber concept.
telecom reference Added reference to HdBe-ContactInformation profile, which replaces the two separate HdBe-ContactInformation profiles.
telecom slicing Removed slicing as the two HdBe-ContactInformation profiles are replaced with one general HdBe-ContactInformation profile, which makes slicing unnecessary.
telecom textual Removed the comment regarding the cardinality mismatch as this the cardinality is adapted in the CBB as well.



HdBe-HealthcareOrganization-Organization

Instructions

HealthcareOrganization is mapped to this Organization profile and a profile on Location (HdBe-HealthcareOrganization). The Location profile acts as the focal resource of HealthcareOrganization because most references to this CBB are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. Often there's no clear distinction between an organizational structure and a physical location. As a rule of thumb, locations are always used for recording where a service occurs, and hence where encounters and observations take place.

Healthcare organizations usually consist of multiple organizational levels and physical locations. The hierarchical structure may be captured by using multiple instances of this profile, using the Organization.partOf element to refer to their parent organization. The physical location is captured using the HdBe-HealthcareOrganization profile, which refers this profile at the appropriate level in the hierarchy.


idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
nidhiΣ I0..*IdentifierPattern
cbeΣ I0..*IdentifierPattern
activeΣ ?!0..1boolean
departmentSpecialtyΣ0..1CodeableConceptBinding
organizationTypeΣ0..1CodeableConceptBinding
nameΣ I0..1string
alias0..*string
telecomI0..*ContactPoint
addressI0..*Address
partOfΣ I0..1Reference(Organization)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
purpose0..1CodeableConceptBinding
name0..1HumanName
telecomI0..*ContactPoint
address0..1Address
endpointI0..*Reference(Endpoint)

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
nidhiΣ I0..*IdentifierPattern
cbeΣ I0..*IdentifierPattern
activeΣ ?!0..1boolean
departmentSpecialtyΣ0..1CodeableConceptBinding
organizationTypeΣ0..1CodeableConceptBinding
nameΣ I0..1string
alias0..*string
telecomI0..*ContactPoint
addressI0..*Address
partOfΣ I0..1Reference(Organization)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
purpose0..1CodeableConceptBinding
name0..1HumanName
telecomI0..*ContactPoint
address0..1Address
endpointI0..*Reference(Endpoint)

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
nidhiΣ I0..*IdentifierPattern
cbeΣ I0..*IdentifierPattern
activeΣ ?!0..1boolean
departmentSpecialtyΣ0..1CodeableConceptBinding
organizationTypeΣ0..1CodeableConceptBinding
nameΣ I0..1string
alias0..*string
telecomI0..*ContactPoint
addressI0..*Address
partOfΣ I0..1Reference(Organization)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
purpose0..1CodeableConceptBinding
name0..1HumanName
telecomI0..*ContactPoint
address0..1Address
endpointI0..*Reference(Endpoint)

Mapping FHIR profile to CBB

PathmapCBB
OrganizationHealthcareOrganizationHdBe-HealthcareOrganization
Organization.identifierHealthcareOrganizationIdentificationNumberHdBe-HealthcareOrganization
Organization.type:departmentSpecialtyDepartmentSpecialtyHdBe-HealthcareOrganization
Organization.type:organizationTypeOrganizationTypeHdBe-HealthcareOrganization
Organization.nameOrganizationNameHdBe-HealthcareOrganization

A UML overview at the bottom of this page provides an example of how a hierarchical structure is initialized in FHIR using Organization and Location resources.

zib HealthcareOrganization-Organization difference

Concept Category Description
description textual Added explanation, in StructureDefinition.description, about how and why the CBB is mapped to two profiles.
identifier slicing Replaced (URA, AGB) slices with NIDHI and CBE.
identifier textual Removed Dutch context of the URA and AGB identifiers on the root identifer.
DepartmentSpecialty textual Removed the Dutch context.
OrganizationType textual Removed the Dutch context.
OrganizationType terminology Replaced ValueSet OrganizationType codes with terminology based on a one-time export of HCO_TYPE as found in the Common Base Registry for HealthCare Actor (CoBRHA). These codes are placed in the healthdata.be namespace. HL7 BE GitHub issue #32 requests to standardize terminology on a federal level for Belgium.



Terminology Bindings

PathNameStrengthURLConceptMap
Organization.typeDepartmentSpecialtyrequiredhttps://fhir.healthdata.be/ValueSet/DepartmentSpecialtyNo bound ConceptMap
Organization.typeOrganizationTyperequiredhttps://fhir.healthdata.be/ValueSet/OrganizationTypeNo bound ConceptMap

NamingSystems

NameKindDescriptionUniqueId
DepartmentIdentificationNumberidentifier

This NamingSytem defines an identifier system to identify internal organization departments. The identifier value is equal to the department identification number as found in the fair.healthdata.be dataset named: Internal organization of departments within Belgian healthcare organizations. Please note that this dataset is a temporary solution. A more structured and standardized version will follow in the future, which will then be documented here.

https://fhir.healthdata.be/NamingSystem/DepartmentIdentificationNumber
LocationIdentificationNumberidentifier

This NamingSytem defines an identifier system to identify healthcare organizations' physical locations. The identifier value is equal to the HCOrganization.Site.SiteID (or site number) value as found in the Common Base Registry for HealthCare Actor (CoBRHA).

https://fhir.healthdata.be/NamingSystem/LocationIdentificationNumber



A UML example of a hierarchical structure initialized in FHIR resources

Please note: that he UML is splitst into two for readability purposes. The first UML demonstrates profoundly the Location hierarchical structure. The second UML shows how each instance of the Location hierachy can also refer to the Organization hierachy.

The locationId, departmentId and nihdi are all mapped to their approriate slice on .identifier.

Location hierarchy



Location and Organization hierarchy of one site and one ward