This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Patient Administration Work Group | Maturity Level: 3 | Trial Use | Security Category: Business | Compartments: Not linked to any defined compartments |
Detailed Descriptions for the elements in the Organization resource.
Organization | |||||||||||||
Element Id | Organization | ||||||||||||
Definition | A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | DomainResource | ||||||||||||
Invariants |
| ||||||||||||
Organization.identifier | |||||||||||||
Element Id | Organization.identifier | ||||||||||||
Definition | Identifier for the organization that is used to identify the organization across multiple disparate systems. | ||||||||||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Identifier | ||||||||||||
Requirements | Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization. | ||||||||||||
Summary | true | ||||||||||||
Invariants |
| ||||||||||||
Organization.active | |||||||||||||
Element Id | Organization.active | ||||||||||||
Definition | Whether the organization's record is still in active use. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | boolean | ||||||||||||
Is Modifier | true (Reason: This element is labelled as a modifier because it is a status element that can indicate that a record should not be treated as valid) | ||||||||||||
Meaning if Missing | This resource is generally assumed to be active if no value is provided for the active element | ||||||||||||
Requirements | Need a flag to indicate a record is no longer to be used and should generally be hidden for the user in the UI. | ||||||||||||
Summary | true | ||||||||||||
Comments | This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used. This element is labeled as a modifier because it may be used to mark that the resource was created in error. | ||||||||||||
Organization.type | |||||||||||||
Element Id | Organization.type | ||||||||||||
Definition | The kind(s) of organization that this is. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Terminology Binding | Organization type (Example) | ||||||||||||
Type | CodeableConcept | ||||||||||||
Requirements | Need to be able to track the kind of organization that this is - different organization types have different uses. | ||||||||||||
Summary | true | ||||||||||||
Comments | Organizations can be corporations, wards, sections, clinical teams, government departments, etc. Note that code is generally a classifier of the type of organization; in many applications, codes are used to identity a particular organization (say, ward) as opposed to another of the same type - these are identifiers, not codes When considering if multiple types are appropriate, you should evaluate if child organizations would be a more appropriate use of the concept, as different types likely are in different sub-areas of the organization. This is most likely to be used where type values have orthogonal values, such as a religious, academic and medical center. We expect that some jurisdictions will profile this optionality to be a single cardinality. | ||||||||||||
Organization.name | |||||||||||||
Element Id | Organization.name | ||||||||||||
Definition | A name associated with the organization. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | string | ||||||||||||
Requirements | Need to use the name as the label of the organization. | ||||||||||||
Summary | true | ||||||||||||
Comments | If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches. | ||||||||||||
Invariants |
| ||||||||||||
Organization.alias | |||||||||||||
Element Id | Organization.alias | ||||||||||||
Definition | A list of alternate names that the organization is known as, or was known as in the past. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | string | ||||||||||||
Requirements | Over time locations and organizations go through many changes and can be known by different names. For searching knowing previous names that the organization was known by can be very useful. | ||||||||||||
Comments | There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the organization. | ||||||||||||
Organization.telecom | |||||||||||||
Element Id | Organization.telecom | ||||||||||||
Definition | A contact detail for the organization. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | ContactPoint | ||||||||||||
Requirements | Human contact for the organization. | ||||||||||||
Comments | The use code 'home' is not to be used. Note that these contacts are not the contact details of people who are employed by or represent the organization, but official contacts for the organization itself. | ||||||||||||
Invariants |
| ||||||||||||
Organization.address | |||||||||||||
Element Id | Organization.address | ||||||||||||
Definition | An address for the organization. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Address | ||||||||||||
Requirements | May need to keep track of the organization's addresses for contacting, billing or reporting requirements. | ||||||||||||
Comments | Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used. | ||||||||||||
Invariants |
| ||||||||||||
Organization.partOf | |||||||||||||
Element Id | Organization.partOf | ||||||||||||
Definition | The organization of which this organization forms a part. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Reference(Organization) | ||||||||||||
Hierarchy | This reference is part of a strict Hierarchy | ||||||||||||
Requirements | Need to be able to track the hierarchy of organizations within an organization. | ||||||||||||
Summary | true | ||||||||||||
Organization.contact | |||||||||||||
Element Id | Organization.contact | ||||||||||||
Definition | Contact for the organization for a certain purpose. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Requirements | Need to keep track of assigned contact points within bigger organization. | ||||||||||||
Comments | Where multiple contacts for the same purpose are provided there is a standard extension that can be used to determine which one is the preferred contact to use. | ||||||||||||
Organization.contact.purpose | |||||||||||||
Element Id | Organization.contact.purpose | ||||||||||||
Definition | Indicates a purpose for which the contact can be reached. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Terminology Binding | Contact entity type (Extensible) | ||||||||||||
Type | CodeableConcept | ||||||||||||
Requirements | Need to distinguish between multiple contact persons. | ||||||||||||
Organization.contact.name | |||||||||||||
Element Id | Organization.contact.name | ||||||||||||
Definition | A name associated with the contact. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | HumanName | ||||||||||||
Requirements | Need to be able to track the person by name. | ||||||||||||
Organization.contact.telecom | |||||||||||||
Element Id | Organization.contact.telecom | ||||||||||||
Definition | A contact detail (e.g. a telephone number or an email address) by which the party may be contacted. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | ContactPoint | ||||||||||||
Requirements | People have (primary) ways to contact them in some way such as phone, email. | ||||||||||||
Organization.contact.address | |||||||||||||
Element Id | Organization.contact.address | ||||||||||||
Definition | Visiting or postal addresses for the contact. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Address | ||||||||||||
Requirements | May need to keep track of a contact party's address for contacting, billing or reporting requirements. | ||||||||||||
Organization.endpoint | |||||||||||||
Element Id | Organization.endpoint | ||||||||||||
Definition | Technical endpoints providing access to services operated for the organization. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Reference(Endpoint) | ||||||||||||
Requirements | Organizations have multiple systems that provide various services and need to be able to define the technical connection details for how to connect to them, and for what purpose. |