Generated Narrative: StructureDefinition hcpd-organization Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> Organization <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( inv-01-identifier-hpi-or-hsp-required, inv-02-identifier-not-both-hpio-hspo )">C 0..* AUCoreOrganization(2.0.0) Australian Organisation Directory Entry #xD; identifier 1..* Identifier(4.0.1), AUHPIO(6.0.0), AUPAIOIdentifier(6.0.0), AUCSPRegistrationNumber(6.0.0), AUAustralianBusinessNumber(6.0.0), AUAustralianCompanyNumber(6.0.0), AUAustralianRegisteredBodyNumber(6.0.0), AUNATAAccreditationNumber(6.0.0), AUPharmacyApprovalNumber(6.0.0) Identifies this organization across multiple systems #xD; Slices for identifier Content/Rules for all slices #xD; identifier:hpio O 0..1 HCPD_HPIO_Identifier(26.0.0) HPI-O identifier Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; identifier:abn O 1..1 AUAustralianBusinessNumber(6.0.0) Identifies this organization across multiple systems Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; identifier:hspo SO 0..1 HCPD_HSPO_Identifier(26.0.0) HSP-O identifier Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; identifier:acn SO 0..1 AUAustralianCompanyNumber(6.0.0) Identifies this organization across multiple systems Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; name O 1..1 string Name of Directory Entry Organisation Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; telecom O 0..* ContactPoint A contact detail for the organization Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; system O 0..1 code phone | fax | email | pager | url | sms | other Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; value O 0..1 string The actual contact point details Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; Slices for address O 1..1 Address(4.0.1), AustralianAddress(6.0.0) Addresses of Directory Entry Organisation Slice: Unordered, Open by value:type Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; address:physical 1..1 Address(4.0.1), AustralianAddress(6.0.0) Registered Business Address of the organisation, as recorded against the HPI-O record. #xD; type 1..1 code postal | physical | both Required Pattern: physical #xD; partOf SO 0..1 Reference(HCPD Organization(26.0.0)) The organization of which this organization forms a part Obligations Actor SHALL:populate-if-known Health Connect Provider Directory Responder Actor SHOULD:handle Health Connect Provider Directory Requester Actor #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
This profile defines a Health Connect Provider Directory entry for an organisation.
This profile addresses the business need for standardised organisation representation in the Health Connect Provider Directory, ensuring consistent capture of healthcare organisation details including identifiers, classifications, and contact information for directory services.
Copyright © 2026 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.
Directory entry Australian realm Organization profile often healthcare or related service provision.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The organization SHALL at least have a name or an identifier, and possibly more than one
Either an HPI-O (hpio) or an HSP-O (hspo) identifier must be present on the Organization.
identifier.where(system='http://ns.electronichealth.net.au/id/hi/hpio/1.0').exists() or identifier.where(system='http://ns.electronichealth.net.au/id/hi/hspo/1.0').exists()
Warn if both HPI-O and HSP-O identifiers are present on the same Organization; HI Service is expected to assign only one.
identifier.where(system='http://ns.electronichealth.net.au/id/hi/hpio/1.0').exists() implies identifier.where(system='http://ns.electronichealth.net.au/id/hi/hspo/1.0').exists().not() and identifier.where(system='http://ns.electronichealth.net.au/id/hi/hspo/1.0').exists() implies identifier.where(system='http://ns.electronichealth.net.au/id/hi/hpio/1.0').exists().not()
Organization(classCode=ORG, determinerCode=INST)
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identifies this organization across multiple systems
Identifier for the organization that is used to identify the organization across multiple disparate systems.
Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.
A National Organisation Identifier (type=NOI) shall be an HPI-O or PAI-O
type.coding.where(code='NOI').exists() implies ((system='http://ns.electronichealth.net.au/id/hi/hpio/1.0') or (system='http://ns.electronichealth.net.au/id/pcehr/paio/1.0'))
Whether the organization's record is still in active use
Whether the organization's record is still in active use.
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.
Need a flag to indicate a record is no longer to be used and should generally be hidden for the user in the UI.
This resource is generally assumed to be active if no value is provided for the active element
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
./Status (however this concept in ServD more covers why the organization is active or not, could be delisted, deregistered, not operational yet) this could alternatively be derived from ./StartDate and ./EndDate and given a context date.
The kind(s) of organization that this is.
When selecting a code for Organization type, if a system is unable to provide a code from the preferred value set [Healthcare Organisation Role Type](https://healthterminologies.gov.au/fhir/ValueSet/healthcare-organisation-role-type-1) because the implementation context is not restricted to healthcare practitioner providers then it is recommended to select from the wider set available in SNOMED CT. If a suitable code from SNOMED CT is not available, a code from the code system [Australian and New Zealand Standard Industrial Classification (ANZSIC), 2006 (Revision 2.0)](https://www.healthterminologies.gov.au/integration/R4/fhir/CodeSystem/anzsic-2006-20130626) may be used.
Need to be able to track the kind of organization that this is - different organization types have different uses.
A name associated with the organization.
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.
Need to use the name as the label of the organization.
A list of alternate names that the organization is known as, or was known as in the past
A list of alternate names that the organization is known as, or was known as in the past.
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.
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.
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.
The telecom of an organization can never be of use 'home'
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
phone | fax | email | pager | url | sms | other
Telecommunications form for contact point - what communications system is required to make use of the contact.
Telecommunications form for contact point.
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Need to support legacy numbers that are not in a tightly controlled format.
home | work | temp | old | mobile - purpose of this contact point
Identifies the purpose for the contact point.
Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one
Specify preferred order of use (1 = highest)
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
Time period when the contact point was/is in use
Time period when the contact point was/is in use.
Slice based on address type: physical, postal, both. Must have at least one physical or both.
Addresses of Directory Entry Organisation
The address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
May need to keep track of the organization's addresses for contacting, billing or reporting requirements.
An address of an organization can never be of use 'home'
Registered Business Address of the organisation, as recorded against the HPI-O record.
The registered business address of the organisation as required for directory entry. Must be type 'physical'.
home | work | temp | old | billing - purpose of this address
Applications can assume that an address is current unless it explicitly says that it is temporary or old.
Allows an appropriate address to be chosen from a list of many.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the [Location](http://hl7.org/fhir/R4/location.html#) resource).
The type of an address (physical / postal).
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
Street name, number, direction & P.O. Box etc.
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.
The order in which lines should appear in an address label
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
The name of the city, town, suburb, village or other community or delivery center.
The name of the administrative area (county).
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).
A postal code designating a region defined by the postal service.
Country (e.g. can be ISO 3166 2 or 3 letter code)
Country - a nation as commonly understood or generally accepted.
ISO 3166 3 letter codes can be used in place of a human readable country name.
Allows addresses to be placed in historical context.
The organization of which this organization forms a part
The organization of which this organization forms a part.
Need to be able to track the hierarchy of organizations within an organization.
Contact for the organization for a certain purpose
Contact for the organization for a certain purpose.
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.
Need to keep track of assigned contact points within bigger organization.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Indicates a purpose for which the contact can be reached.
Need to distinguish between multiple contact persons.
Need to be able to track the person by name.
Contact details (telephone, email, etc.) for a contact
A contact detail (e.g. a telephone number or an email address) by which the party may be contacted.
People have (primary) ways to contact them in some way such as phone, email.
Visiting or postal addresses for the contact
Visiting or postal addresses for the contact.
May need to keep track of a contact party's address for contacting, billing or reporting requirements.
Technical endpoints providing access to services operated for the organization
Technical endpoints providing access to services operated for the organization.
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.