Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship.
Business identifiers that are specific to this role
Business identifiers that are specific to this role.
Whether this organization affiliation record is in active use
Whether this organization affiliation record is in active use.
If this value is false, you may refer to the period to see when the role was in active use. If there is no period specified, no inference can be made about when it was active.
The period during which the participatingOrganization is affiliated with the primary organization
The period during which the participatingOrganization is affiliated with the primary organization.
Organization where the role is available
Organization where the role is available (primary organization/has members).
Organization that provides/performs the role (e.g. providing services or is a member of)
The Participating Organization provides/performs the role(s) defined by the code to the Primary Organization (e.g. providing services or is a member of).
Health insurance provider network in which the participatingOrganization provides the role's services (if defined) at the indicated locations (if defined)
Health insurance provider network in which the participatingOrganization provides the role's services (if defined) at the indicated locations (if defined).
Definition of the role the participatingOrganization plays
Definition of the role the participatingOrganization plays in the association.
Specific specialty of the participatingOrganization in the context of the role
Specific specialty of the participatingOrganization in the context of the role.
The location(s) at which the role occurs
The location(s) at which the role occurs.
Healthcare services provided through the role
Healthcare services provided through the role.
Contact details at the participatingOrganization relevant to this Affiliation
Contact details at the participatingOrganization relevant to this Affiliation.
Technical endpoints providing access to services operated for this role
Technical endpoints providing access to services operated for this role.
|active||token||Whether this organization affiliation record is in active use||OrganizationAffiliation.active|
|date||date||The period during which the participatingOrganization is affiliated with the primary organization||OrganizationAffiliation.period|
|token||A value in an email contact||OrganizationAffiliation.telecom|
|endpoint||reference||Technical endpoints providing access to services operated for this role||OrganizationAffiliation.endpoint|
|identifier||token||An organization affiliation's Identifier||OrganizationAffiliation.identifier|
|location||reference||The location(s) at which the role occurs||OrganizationAffiliation.location|
|network||reference||Health insurance provider network in which the participatingOrganization provides the role's services (if defined) at the indicated locations (if defined)||OrganizationAffiliation.network|
|participating-organization||reference||The organization that provides services to the primary organization||OrganizationAffiliation.participatingOrganization|
|phone||token||A value in a phone contact||OrganizationAffiliation.telecom|
|primary-organization||reference||The organization that receives the services from the participating organization||OrganizationAffiliation.organization|
|role||token||Definition of the role the participatingOrganization plays||OrganizationAffiliation.code|
|service||reference||Healthcare services provided through the role||OrganizationAffiliation.healthcareService|
|specialty||token||Specific specialty of the participatingOrganization in the context of the role||OrganizationAffiliation.specialty|
|telecom||token||The value in any kind of contact||OrganizationAffiliation.telecom|
Logical id of this artifact
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.
Metadata about the resource
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.
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.
Language of the resource content
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.
Contained, inline Resources
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.
Extensions that cannot be ignored
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).