🔗 An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. Note: 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](http://hl7.org/fhir/R4/location.html#) resource).ch-core-address(xsd)(doc)=
<#base:Address>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this address. Applications can assume that an address is current unless it explicitly says that it is temporary or old.; (xsd)use:code>?
< 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).; (xsd)type:code>?
< 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.; (xsd)text:string>?
[]< This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.; (xsd)line:ch-core-address.line>*
< The name of the city, town, suburb, village or other community or delivery center.; (xsd)city:ch-core-address.city>?
< 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.; (xsd)district:string>?
< 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).; (xsd)state:string>?
< A postal code designating a region defined by the postal service.; (xsd)postalCode:string>?
< 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.; (xsd)country:ch-core-address.country>?
< Time period when address was/is in use.; (xsd)period:Period>?🔗 The name of the city, town, suburb, village or other community or delivery center.ch-core-address.city(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Extension for eCH-0011 - bfs number (ministry of statistics number); (xsd)bfs:ch-ext-ech-7-municipalityid>?🔗 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.ch-core-address.country(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< The content of the country code element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, if the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.; (xsd)countrycode:iso21090-SC-coding>?🔗 This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.ch-core-address.line(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine1:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine2:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)street:ch-ext-ech-10-linetype>?
< streetName.; (xsd)streetName:iso21090-ADXP-streetName>?
< The number of a building, house or lot alongside the street. Also known as "primary street number". This does not number the street but rather the building.; (xsd)houseNumber:iso21090-ADXP-houseNumber>?
< The number or name of a specific unit contained within a building or complex, as assigned by that building or complex.; (xsd)unitID:iso21090-ADXP-unitID>?
< eCH-0010: Extension to define line types for an address; (xsd)postOfficeBoxText:ch-ext-ech-10-linetype>?
< A numbered box located in a post station.; (xsd)postOfficeBoxNumber:iso21090-ADXP-postBox>?🔗 An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. Note: 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](http://hl7.org/fhir/R4/location.html#) resource).ch-core-address-ech-10(xsd)(doc)=
<#base:ch-core-address>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this address. Applications can assume that an address is current unless it explicitly says that it is temporary or old.; (xsd)use:code>?
< 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). postal; (xsd)type:code>?
< 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.; (xsd)text:string>?
[]< This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.; (xsd)line:ch-core-address-ech-10.line>*
< The name of the city, town, suburb, village or other community or delivery center.; (xsd)city:ch-core-address-ech-10.city>
< 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.; (xsd)district:string>?
< 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).; (xsd)state:string>?
< A postal code designating a region defined by the postal service.; (xsd)postalCode:string>
< 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.; (xsd)country:ch-core-address-ech-10.country>
< Time period when address was/is in use.; (xsd)period:Period>{0,0}🔗 The name of the city, town, suburb, village or other community or delivery center.ch-core-address-ech-10.city(xsd)(doc)=
<#base:ch-core-address.city>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Extension for eCH-0011 - bfs number (ministry of statistics number); (xsd)bfs:ch-ext-ech-7-municipalityid>?🔗 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.ch-core-address-ech-10.country(xsd)(doc)=
<#base:ch-core-address.country>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< The content of the country code element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, if the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.; (xsd)countrycode:iso21090-SC-coding>?🔗 This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.ch-core-address-ech-10.line(xsd)(doc)=
<#base:ch-core-address.line>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine1:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine2:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)street:ch-ext-ech-10-linetype>?
< streetName.; (xsd)streetName:iso21090-ADXP-streetName>?
< The number of a building, house or lot alongside the street. Also known as "primary street number". This does not number the street but rather the building.; (xsd)houseNumber:iso21090-ADXP-houseNumber>?
< The number or name of a specific unit contained within a building or complex, as assigned by that building or complex.; (xsd)unitID:iso21090-ADXP-unitID>?
< eCH-0010: Extension to define line types for an address; (xsd)postOfficeBoxText:ch-ext-ech-10-linetype>?
< A numbered box located in a post station.; (xsd)postOfficeBoxNumber:iso21090-ADXP-postBox>?🔗 An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. Note: 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](http://hl7.org/fhir/R4/location.html#) resource).ch-core-address-ech-11-placeofbirth(xsd)(doc)=
<#base:ch-core-address>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this address. Applications can assume that an address is current unless it explicitly says that it is temporary or old.; (xsd)use:code>{0,0}
< 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).; (xsd)type:code>{0,0}
< 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.; (xsd)text:string>{0,0}
< This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.; (xsd)line:ch-core-address-ech-11-placeofbirth.line>{0,0}
< optional if country is not Switzerland; (xsd)city:ch-core-address-ech-11-placeofbirth.city>?
< 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.; (xsd)district:string>{0,0}
< Canton 2 letter abbreviation; (xsd)state:string>?
< A postal code designating a region defined by the postal service.; (xsd)postalCode:string>{0,0}
< Country if place of Birth is not Switzerland ISO 3166 3 letter codes can be used in place of a human readable country name.; (xsd)country:ch-core-address-ech-11-placeofbirth.country>?
< Time period when address was/is in use.; (xsd)period:Period>{0,0}🔗 optional if country is not Switzerlandch-core-address-ech-11-placeofbirth.city(xsd)(doc)=
<#base:ch-core-address.city>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Extension for eCH-0011 - bfs number (ministry of statistics number); (xsd)bfs:ch-ext-ech-7-municipalityid>?🔗 Country if place of Birth is not Switzerland ISO 3166 3 letter codes can be used in place of a human readable country name.ch-core-address-ech-11-placeofbirth.country(xsd)(doc)=
<#base:ch-core-address.country>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< The content of the country code element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, if the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.; (xsd)countrycode:iso21090-SC-coding>?🔗 This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.ch-core-address-ech-11-placeofbirth.line(xsd)(doc)=
<#base:ch-core-address.line>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine1:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine2:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)street:ch-ext-ech-10-linetype>?
< streetName.; (xsd)streetName:iso21090-ADXP-streetName>?
< The number of a building, house or lot alongside the street. Also known as "primary street number". This does not number the street but rather the building.; (xsd)houseNumber:iso21090-ADXP-houseNumber>?
< The number or name of a specific unit contained within a building or complex, as assigned by that building or complex.; (xsd)unitID:iso21090-ADXP-unitID>?
< eCH-0010: Extension to define line types for an address; (xsd)postOfficeBoxText:ch-ext-ech-10-linetype>?
< A numbered box located in a post station.; (xsd)postOfficeBoxNumber:iso21090-ADXP-postBox>?🔗 An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. Note: 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](http://hl7.org/fhir/R4/location.html#) resource).ch-core-address-ech-11-placeoforigin(xsd)(doc)=
<#base:ch-core-address>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this address. Applications can assume that an address is current unless it explicitly says that it is temporary or old.; (xsd)use:code>{0,0}
< 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).; (xsd)type:code>{0,0}
< 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.; (xsd)text:string>{0,0}
< This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.; (xsd)line:ch-core-address-ech-11-placeoforigin.line>{0,0}
< optional if country is not Switzerland; (xsd)city:ch-core-address-ech-11-placeoforigin.city>?
< 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.; (xsd)district:string>{0,0}
< Canton 2 letter abbreviation; (xsd)state:string>
< A postal code designating a region defined by the postal service.; (xsd)postalCode:string>{0,0}
< Country if place of orgin is not Switzerland ISO 3166 3 letter codes can be used in place of a human readable country name.; (xsd)country:ch-core-address-ech-11-placeoforigin.country>{0,0}
< Time period when address was/is in use.; (xsd)period:Period>{0,0}🔗 optional if country is not Switzerlandch-core-address-ech-11-placeoforigin.city(xsd)(doc)=
<#base:ch-core-address.city>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Extension for eCH-0011 - bfs number (ministry of statistics number); (xsd)bfs:ch-ext-ech-7-municipalityid>?🔗 Country if place of orgin is not Switzerland ISO 3166 3 letter codes can be used in place of a human readable country name.ch-core-address-ech-11-placeoforigin.country(xsd)(doc)=
<#base:ch-core-address.country>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Provides a coded expression for the content represented in a string.; (xsd)countrycode:iso21090-SC-coding>?🔗 This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.ch-core-address-ech-11-placeoforigin.line(xsd)(doc)=
<#base:ch-core-address.line>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine1:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)addressLine2:ch-ext-ech-10-linetype>?
< eCH-0010: Extension to define line types for an address; (xsd)street:ch-ext-ech-10-linetype>?
< streetName.; (xsd)streetName:iso21090-ADXP-streetName>?
< The number of a building, house or lot alongside the street. Also known as "primary street number". This does not number the street but rather the building.; (xsd)houseNumber:iso21090-ADXP-houseNumber>?
< The number or name of a specific unit contained within a building or complex, as assigned by that building or complex.; (xsd)unitID:iso21090-ADXP-unitID>?
< eCH-0010: Extension to define line types for an address; (xsd)postOfficeBoxText:ch-ext-ech-10-linetype>?
< A numbered box located in a post station.; (xsd)postOfficeBoxNumber:iso21090-ADXP-postBox>?🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-ahvn13-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.32; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings.ch-core-allergyintolerance(xsd)(doc)=
<#base:AllergyIntolerance>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; (xsd)identifier:Identifier>*
< The clinical status of the allergy or intolerance. Refer to [discussion](http://hl7.org/fhir/R4/extensibility.html#Special-Case) if clincalStatus is missing data.
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.; (xsd)clinicalStatus:CodeableConcept>?
< Assertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.; (xsd)verificationStatus:CodeableConcept>?
< Identification of the underlying physiological mechanism for the reaction risk. Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians might not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts might not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource.; (xsd)type:code>?
[]< Category of the identified substance. This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the substance where coding systems are used, and is effectively redundant in that situation. When searching on category, consider the implications of AllergyIntolerance resources without a category. For example, when searching on category = medication, medication allergies that don't have a category valued will not be returned. Refer to [search](http://hl7.org/fhir/R4/search.html) for more information on how to search category with a :missing modifier to get allergies that don't have a category. Additionally, category should be used with caution because category can be subjective based on the sender.; (xsd)category:code>*
< Estimate of the potential clinical harm, or seriousness, of the reaction to the identified substance. The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere). Systems that capture a severity at the condition level are actually representing the concept of criticality whereas the severity documented at the reaction level is representing the true reaction severity. Existing systems that are capturing both condition criticality and reaction severity may use the term "severity" to represent both. Criticality is the worst it could be in the future (i.e. situation-agnostic) whereas severity is situation-dependent.; (xsd)criticality:code>?
< Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. It is strongly recommended that this element be populated using a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNII, and ATC. Plain text should only be used if there is no appropriate terminology available. Additional details can be specified in the text.
When a substance or product code is specified for the 'code' element, the "default" semantic context is that this is a positive statement of an allergy or intolerance (depending on the value of the 'type' element, if present) condition to the specified substance/product. In the corresponding SNOMED CT allergy model, the specified substance/product is the target (destination) of the "Causative agent" relationship.
The 'substanceExposureRisk' extension is available as a structured and more flexible alternative to the 'code' element for making positive or negative allergy or intolerance statements. This extension provides the capability to make "no known allergy" (or "no risk of adverse reaction") statements regarding any coded substance/product (including cases when a pre-coordinated "no allergy to x" concept for that substance/product does not exist). If the 'substanceExposureRisk' extension is present, the AllergyIntolerance.code element SHALL be omitted.; (xsd)code:CodeableConcept>?
< The patient who has the allergy or intolerance.; (xsd)patient:ch-core-patient*>
< The encounter when the allergy or intolerance was asserted.; (xsd)encounter:Encounter*>?
< Estimated or actual date, date-time, or age when allergy or intolerance was identified.; (xsd)onset:(<Age>
|<dateTime>
|<Period>
|<Range>
|<string>)>?
< The recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.; (xsd)recordedDate:dateTime>?
< Individual who recorded the record and takes responsibility for its content.; (xsd)recorder:(<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
< The source of the information about the allergy that is recorded. The recorder takes responsibility for the content, but can reference the source from where they got it.; (xsd)asserter:(<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
< Represents the date and/or time of the last known occurrence of a reaction event. This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used.; (xsd)lastOccurrence:dateTime>?
[]< Additional narrative about the propensity for the Adverse Reaction, not captured in other fields. For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.; (xsd)note:Annotation>*
[]< Details about each adverse reaction event linked to exposure to the identified substance.; (xsd)reaction:ch-core-allergyintolerance.reaction>*🔗 Details about each adverse reaction event linked to exposure to the identified substance.ch-core-allergyintolerance.reaction(xsd)(doc)=
<#base:AllergyIntolerance.reaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Identification of the specific substance (or pharmaceutical product) considered to be responsible for the Adverse Reaction event. Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. Coding of the specific substance (or pharmaceutical product) with a terminology capable of triggering decision support should be used wherever possible. The 'code' element allows for the use of a specific substance or pharmaceutical product, or a group or class of substances. In the case of an allergy or intolerance to a class of substances, (for example, "penicillins"), the 'reaction.substance' element could be used to code the specific substance that was identified as having caused the reaction (for example, "amoxycillin"). Duplication of the value in the 'code' and 'reaction.substance' elements is acceptable when a specific substance has been recorded in 'code'.; (xsd)substance:CodeableConcept>?
[]< Clinical symptoms and/or signs that are observed or associated with the adverse reaction event. Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10.; (xsd)manifestation:CodeableConcept>+
< Text description about the reaction as a whole, including details of the manifestation if required. Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives.; (xsd)description:string>?
< Record of the date and/or time of the onset of the Reaction.; (xsd)onset:dateTime>?
< Clinical assessment of the severity of the reaction event as a whole, potentially considering multiple different manifestations. It is acknowledged that this assessment is very subjective. There may be some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions.; (xsd)severity:code>?
< Identification of the route by which the subject was exposed to the substance. Coding of the route of exposure with a terminology should be used wherever possible.; (xsd)exposureRoute:CodeableConcept>?
[]< Additional text about the adverse reaction event not captured in other fields. Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.; (xsd)note:Annotation>*
< Statement about the degree of clinical certainty that the specific substance was the cause of the manifestation in this reaction event. When certainty is missing, it means no information exists (although it could be in narrative). By contrast, the unknown code is used when there is an explicit assertion that certainty is not known, such as when a patient eats a meal and it is unknown which food caused the reaction.; (xsd)certainty:allergyintolerance-certainty>?
< The amount of time that the Adverse Reaction persisted.; (xsd)duration:allergyintolerance-duration>?
< The anatomical location / body site(s) where the symptoms manifested.; (xsd)location:openEHR-location>?
< Record of the date and/or time of the first exposure to the Substance for this Reaction Event. Exposure can be more complicated by more than one exposure events leading to a reaction. Further details about the nature of the exposure can be provided in additional extensions, or as text in the Exposure Description extension.; (xsd)exposureDate:openEHR-exposureDate>?
< The amount of time the individual was exposed to the Substance.; (xsd)exposureDuration:openEHR-exposureDuration>?
< Text description about exposure to the Substance.; (xsd)exposureDescription:openEHR-exposureDescription>?
< Text description about the clinical management provided.; (xsd)management:openEHR-management>?🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-ber-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.45; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. The Claim resource fulfills three information request requirements: Claim - a request for adjudication for reimbursement for products and/or services provided; Preauthorization - a request to authorize the future provision of products and/or services including an anticipated adjudication; and, Predetermination - a request for a non-bind adjudication of possible future products and/or services.ch-core-claim(xsd)(doc)=
<#base:Claim>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A unique identifier assigned to this claim.; (xsd)identifier:Identifier>*
< The status of the resource instance. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
< The category of claim, e.g. oral, pharmacy, vision, institutional, professional. The majority of jurisdictions use: oral, pharmacy, vision, professional and institutional, or variants on those terms, as the general styles of claims. The valueset is extensible to accommodate other jurisdictional requirements.; (xsd)type:CodeableConcept>
< A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. This may contain the local bill type codes, for example the US UB-04 bill type code or the CMS bill type.; (xsd)subType:CodeableConcept>?
< A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future.; (xsd)use:code>
< The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought.; (xsd)patient:ch-core-patient*>
< The period for which charges are being submitted. Typically this would be today or in the past for a claim, and today or in the future for preauthorizations and predeterminations. Typically line item dates of service should fall within the billing period if one is specified.; (xsd)billablePeriod:Period>?
< The date this resource was created. This field is independent of the date of creation of the resource as it may reflect the creation date of a source document prior to digitization. Typically for claims all services must be completed as of this date.; (xsd)created:dateTime>
< Individual who created the claim, predetermination or preauthorization.; (xsd)enterer:(<Practitioner>
|<PractitionerRole>)>?
< The Insurer who is target of the request.; (xsd)insurer:Organization*>?
< The provider which is responsible for the claim, predetermination or preauthorization. Typically this field would be 1..1 where this party is responsible for the claim but not necessarily professionally responsible for the provision of the individual products and services listed below.; (xsd)provider:(<ch-core-organization>
|<ch-core-practitioner>
|<ch-core-practitionerrole>)>
< The provider-required urgency of processing the request. Typical values include: stat, routine deferred. If a claim processor is unable to complete the processing as per the priority then they should generate and error and not process the request.; (xsd)priority:CodeableConcept>
< A code to indicate whether and for whom funds are to be reserved for future claims. This field is only used for preauthorizations.; (xsd)fundsReserve:CodeableConcept>?
[]< Other claims which are related to this claim such as prior submissions or claims for related services or for the same event. For example, for the original treatment and follow-up exams.; (xsd)related:ch-core-claim.related>*
< Prescription to support the dispensing of pharmacy, device or vision products.; (xsd)prescription:(<DeviceRequest>
|<MedicationRequest>
|<VisionPrescription>)>?
< Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products. For example, a physician may prescribe a medication which the pharmacy determines is contraindicated, or for which the patient has an intolerance, and therefore issues a new prescription for an alternate medication which has the same therapeutic intent. The prescription from the pharmacy becomes the 'prescription' and that from the physician becomes the 'original prescription'.; (xsd)originalPrescription:(<DeviceRequest>
|<MedicationRequest>
|<VisionPrescription>)>?
< The party to be reimbursed for cost of the products and services according to the terms of the policy. Often providers agree to receive the benefits payable to reduce the near-term costs to the patient. The insurer may decline to pay the provider and choose to pay the subscriber instead.; (xsd)payee:ch-core-claim.payee>?
< A reference to a referral resource. The referral resource which lists the date, practitioner, reason and other supporting information.; (xsd)referral:ServiceRequest*>?
< Facility where the services were provided.; (xsd)facility:Location*>?
[]< The members of the team who provided the products and services.; (xsd)careTeam:ch-core-claim.careTeam>*
[]< Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.; (xsd)supportingInfo:ch-core-claim.supportingInfo>*
[]< Information about diagnoses relevant to the claim items.; (xsd)diagnosis:ch-core-claim.diagnosis>*
[]< Procedures performed on the patient relevant to the billing items with the claim.; (xsd)procedure:ch-core-claim.procedure>*
[]< Financial instruments for reimbursement for the health care products and services specified on the claim. All insurance coverages for the patient which may be applicable for reimbursement, of the products and services listed in the claim, are typically provided in the claim to allow insurers to confirm the ordering of the insurance coverages relative to local 'coordination of benefit' rules. One coverage (and only one) with 'focal=true' is to be used in the adjudication of this claim. Coverages appearing before the focal Coverage in the list, and where 'Coverage.subrogation=false', should provide a reference to the ClaimResponse containing the adjudication results of the prior claim.; (xsd)insurance:ch-core-claim.insurance>+
< Details of an accident which resulted in injuries which required the products and services listed in the claim.; (xsd)accident:ch-core-claim.accident>?
[]< A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details.; (xsd)item:ch-core-claim.item>*
< The total value of the all the items in the claim.; (xsd)total:Money>?
< Optional Extension Element - found in all resources.; (xsd)biller:ch-ext-biller>?
< Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.; (xsd)treatmentReason:ch-core-claim.treatmentReason>?
< Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.; (xsd)remark:ch-core-claim.remark>?🔗 Details of an accident which resulted in injuries which required the products and services listed in the claim.ch-core-claim.accident(xsd)(doc)=
<#base:Claim.accident>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Date of an accident event related to the products and services contained in the claim. The date of the accident has to precede the dates of the products and services but within a reasonable timeframe.; (xsd)date>
< The type or context of the accident event for the purposes of selection of potential insurance coverages and determination of coordination between insurers.; (xsd)type:CodeableConcept>?
< The physical location of the accident event.; (xsd)location:(<Address>
|<Location>)>?🔗 The members of the team who provided the products and services.ch-core-claim.careTeam(xsd)(doc)=
<#base:Claim.careTeam>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify care team entries.; (xsd)sequence:positiveInt>
< Member of the team who provided the product or service.; (xsd)provider:(<Organization>
|<Practitioner>
|<PractitionerRole>)>
< The party who is billing and/or responsible for the claimed products or services. Responsible might not be required when there is only a single provider listed.; (xsd)responsible:boolean>?
< The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team. Role might not be required when there is only a single provider listed.; (xsd)role:CodeableConcept>?
< The qualification of the practitioner which is applicable for this service.; (xsd)qualification:CodeableConcept>?🔗 Information about diagnoses relevant to the claim items.ch-core-claim.diagnosis(xsd)(doc)=
<#base:Claim.diagnosis>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify diagnosis entries. Diagnosis are presented in list order to their expected importance: primary, secondary, etc.; (xsd)sequence:positiveInt>
< The nature of illness or problem in a coded form or as a reference to an external defined Condition.; (xsd)diagnosis:(<CodeableConcept>
|<Condition>)>
[]< When the condition was observed or the relative ranking. For example: admitting, primary, secondary, discharge.; (xsd)type:CodeableConcept>*
< Indication of whether the diagnosis was present on admission to a facility.; (xsd)onAdmission:CodeableConcept>?
< A package billing code or bundle code used to group products and services to a particular health condition (such as heart attack) which is based on a predetermined grouping code system. For example DRG (Diagnosis Related Group) or a bundled billing code. A patient may have a diagnosis of a Myocardial Infarction and a DRG for HeartAttack would be assigned. The Claim item (and possible subsequent claims) would refer to the DRG for those line items that were for services related to the heart attack event.; (xsd)packageCode:CodeableConcept>?🔗 Financial instruments for reimbursement for the health care products and services specified on the claim. All insurance coverages for the patient which may be applicable for reimbursement, of the products and services listed in the claim, are typically provided in the claim to allow insurers to confirm the ordering of the insurance coverages relative to local 'coordination of benefit' rules. One coverage (and only one) with 'focal=true' is to be used in the adjudication of this claim. Coverages appearing before the focal Coverage in the list, and where 'Coverage.subrogation=false', should provide a reference to the ClaimResponse containing the adjudication results of the prior claim.ch-core-claim.insurance(xsd)(doc)=
<#base:Claim.insurance>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order.; (xsd)sequence:positiveInt>
< A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true. A patient may (will) have multiple insurance policies which provide reimbursement for healthcare services and products. For example a person may also be covered by their spouse's policy and both appear in the list (and may be from the same insurer). This flag will be set to true for only one of the listed policies and that policy will be used for adjudicating this claim. Other claims would be created to request adjudication against the other listed policies.; (xsd)focal:boolean>
< The business identifier to be used when the claim is sent for adjudication against this insurance policy. Only required in jurisdictions where insurers, rather than the provider, are required to send claims to insurers that appear after them in the list. This element is not required when 'subrogation=true'.; (xsd)identifier:Identifier>?
< Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system.; (xsd)coverage:ch-core-coverage*>
< A business agreement number established between the provider and the insurer for special business processing purposes.; (xsd)businessArrangement:string>?
[]< Reference numbers previously provided by the insurer to the provider to be quoted on subsequent claims containing services or products related to the prior authorization. This value is an alphanumeric string that may be provided over the phone, via text, via paper, or within a ClaimResponse resource and is not a FHIR Identifier.; (xsd)preAuthRef:string>*
< The result of the adjudication of the line items for the Coverage specified in this insurance. Must not be specified when 'focal=true' for this insurance.; (xsd)claimResponse:ClaimResponse*>?🔗 A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details.ch-core-claim.item(xsd)(doc)=
<#base:Claim.item>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify item entries.; (xsd)sequence:positiveInt>
[]< CareTeam members related to this service or product.; (xsd)careTeamSequence:positiveInt>*
[]< Diagnosis applicable for this service or product.; (xsd)diagnosisSequence:positiveInt>*
[]< Procedures applicable for this service or product.; (xsd)procedureSequence:positiveInt>*
[]< Exceptions, special conditions and supporting information applicable for this service or product.; (xsd)informationSequence:positiveInt>*
< The type of revenue or cost center providing the product and/or service.; (xsd)revenue:CodeableConcept>?
< Code to identify the general type of benefits under which products and services are provided. Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage.; (xsd)category:ch-core-claim.item.category>?
< When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'.; (xsd)productOrService:ch-core-claim.item.productOrService>
[]< Item typification or modifiers codes to convey additional context for the product or service. For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or outside of office hours.; (xsd)modifier:CodeableConcept>*
[]< Identifies the program under which this may be recovered. For example: Neonatal program, child dental program or drug users recovery program.; (xsd)programCode:CodeableConcept>*
< The date or dates when the service or product was supplied, performed or completed.; (xsd)serviced:(<date>
|<Period>)>?
< Where the product or service was provided.; (xsd)location:(<Address>
|<CodeableConcept>
|<Location>)>?
< The number of repetitions of a service or product.; (xsd)quantity:SimpleQuantity>?
< If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group.; (xsd)unitPrice:Money>?
< A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10).; (xsd)factor:decimal>?
< The quantity times the unit price for an additional service or product or charge. For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied.; (xsd)net:Money>?
[]< Unique Device Identifiers associated with this line item.; (xsd)udi:Device*>*
< Physical service site on the patient (limb, tooth, etc.). For example: Providing a tooth code, allows an insurer to identify a provider performing a filling on a tooth that was previously removed.; (xsd)bodySite:CodeableConcept>?
[]< A region or surface of the bodySite, e.g. limb region or tooth surface(s).; (xsd)subSite:CodeableConcept>*
[]< The Encounters during which this Claim was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.; (xsd)encounter:Encounter*>*
[]< A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items.; (xsd)detail:ch-core-claim.item.detail>*
< Optional Extension Element - found in all resources.; (xsd)responsible:ch-ext-responsible>?🔗 Code to identify the general type of benefits under which products and services are provided. Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage.ch-core-claim.item.category(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)tariff:ch-core-claim.item.category.tariff>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-claim.item.category.tariff(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items.ch-core-claim.item.detail(xsd)(doc)=
<#base:Claim.item.detail>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify item entries.; (xsd)sequence:positiveInt>
< The type of revenue or cost center providing the product and/or service.; (xsd)revenue:CodeableConcept>?
< Code to identify the general type of benefits under which products and services are provided. Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage.; (xsd)category:CodeableConcept>?
< When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'.; (xsd)productOrService:CodeableConcept>
[]< Item typification or modifiers codes to convey additional context for the product or service. For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or out of office hours.; (xsd)modifier:CodeableConcept>*
[]< Identifies the program under which this may be recovered. For example: Neonatal program, child dental program or drug users recovery program.; (xsd)programCode:CodeableConcept>*
< The number of repetitions of a service or product.; (xsd)quantity:SimpleQuantity>?
< If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group.; (xsd)unitPrice:Money>?
< A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10).; (xsd)factor:decimal>?
< The quantity times the unit price for an additional service or product or charge. For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied.; (xsd)net:Money>?
[]< Unique Device Identifiers associated with this line item.; (xsd)udi:Device*>*
[]< A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items.; (xsd)subDetail:ch-core-claim.item.detail.subDetail>*🔗 A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items.ch-core-claim.item.detail.subDetail(xsd)(doc)=
<#base:Claim.item.detail.subDetail>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify item entries.; (xsd)sequence:positiveInt>
< The type of revenue or cost center providing the product and/or service.; (xsd)revenue:CodeableConcept>?
< Code to identify the general type of benefits under which products and services are provided. Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage.; (xsd)category:CodeableConcept>?
< When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'.; (xsd)productOrService:CodeableConcept>
[]< Item typification or modifiers codes to convey additional context for the product or service. For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or out of office hours.; (xsd)modifier:CodeableConcept>*
[]< Identifies the program under which this may be recovered. For example: Neonatal program, child dental program or drug users recovery program.; (xsd)programCode:CodeableConcept>*
< The number of repetitions of a service or product.; (xsd)quantity:SimpleQuantity>?
< If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group.; (xsd)unitPrice:Money>?
< A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10).; (xsd)factor:decimal>?
< The quantity times the unit price for an additional service or product or charge. For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied.; (xsd)net:Money>?
[]< Unique Device Identifiers associated with this line item.; (xsd)udi:Device*>*🔗 When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'.ch-core-claim.item.productOrService(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:ch-core-claim.item.productOrService.coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)GTIN:ch-core-claim.item.productOrService.GTIN>?
< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)TARMED:ch-core-claim.item.productOrService.TARMED>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-claim.item.productOrService.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>?
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-claim.item.productOrService.GTIN(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-claim.item.productOrService.TARMED(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 The number of repetitions of a service or product.ch-core-claim.item.quantity(xsd)(doc)=
<#base:Quantity>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The value of the measured amount. The value includes an implicit precision in the presentation of the value. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).; (xsd)value:decimal>?
< Not allowed to be used in this context; (xsd)comparator:code>{0,0}
< A human-readable form of the unit.; (xsd)unit:string>?
< The identification of the system that provides the coded form of the unit.; (xsd)system:uri>?
< A computer processable form of the unit in some unit representation system. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.; (xsd)code>?🔗 The party to be reimbursed for cost of the products and services according to the terms of the policy. Often providers agree to receive the benefits payable to reduce the near-term costs to the patient. The insurer may decline to pay the provider and choose to pay the subscriber instead.ch-core-claim.payee(xsd)(doc)=
<#base:Claim.payee>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Type of Party to be reimbursed: subscriber, provider, other.; (xsd)type:CodeableConcept>
< Reference to the individual or organization to whom any payment will be made. Not required if the payee is 'subscriber' or 'provider'.; (xsd)party:(<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?🔗 Procedures performed on the patient relevant to the billing items with the claim.ch-core-claim.procedure(xsd)(doc)=
<#base:Claim.procedure>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify procedure entries.; (xsd)sequence:positiveInt>
[]< When the condition was observed or the relative ranking. For example: primary, secondary.; (xsd)type:CodeableConcept>*
< Date and optionally time the procedure was performed.; (xsd)date:dateTime>?
< The code or reference to a Procedure resource which identifies the clinical intervention performed.; (xsd)procedure:(<CodeableConcept>
|<Procedure>)>
[]< Unique Device Identifiers associated with this line item.; (xsd)udi:Device*>*🔗 Other claims which are related to this claim such as prior submissions or claims for related services or for the same event. For example, for the original treatment and follow-up exams.ch-core-claim.related(xsd)(doc)=
<#base:Claim.related>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Reference to a related claim.; (xsd)claim:Claim*>?
< A code to convey how the claims are related. For example, prior claim or umbrella.; (xsd)relationship:CodeableConcept>?
< An alternate organizational reference to the case or file to which this particular claim pertains. For example, Property/Casualty insurer claim # or Workers Compensation case # .; (xsd)reference:Identifier>?🔗 Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.ch-core-claim.remark(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify supporting information entries.; (xsd)sequence:positiveInt>
< The general class of the information supplied: information; exception; accident, employment; onset, etc. This may contain a category for the local bill type codes.; (xsd)category:CodeableConcept>
< System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.; (xsd)code:CodeableConcept>?
< The date when or period to which this information refers.; (xsd)timing:(<date>
|<Period>)>?
< Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. Could be used to provide references to other resources, document. For example could contain a PDF in an Attachment of the Police Report for an Accident.; (xsd)value:string>
< Provides the reason in the situation where a reason code is required in addition to the content. For example: the reason for the additional stay, or why a tooth is missing.; (xsd)reason:CodeableConcept>?
< Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. Could be used to provide references to other resources, document. For example could contain a PDF in an Attachment of the Police Report for an Accident.; (xsd)valueString:string>🔗 Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.ch-core-claim.supportingInfo(xsd)(doc)=
<#base:Claim.supportingInfo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify supporting information entries.; (xsd)sequence:positiveInt>
< The general class of the information supplied: information; exception; accident, employment; onset, etc. This may contain a category for the local bill type codes.; (xsd)category:CodeableConcept>
< System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.; (xsd)code:CodeableConcept>?
< The date when or period to which this information refers.; (xsd)timing:(<date>
|<Period>)>?
(<valueAttachment:Attachment>
|<valueBoolean:boolean>
|<valueQuantity:Quantity>
|<valueResource:Resource>
|<valueString:string>)?
< Provides the reason in the situation where a reason code is required in addition to the content. For example: the reason for the additional stay, or why a tooth is missing.; (xsd)reason:CodeableConcept>?🔗 Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are multiple jurisdiction specific valuesets which are required.ch-core-claim.treatmentReason(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A number to uniquely identify supporting information entries.; (xsd)sequence:positiveInt>
< The general class of the information supplied: information; exception; accident, employment; onset, etc. This may contain a category for the local bill type codes.; (xsd)category:CodeableConcept>
< System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.; (xsd)code:CodeableConcept>
< The date when or period to which this information refers.; (xsd)timing:(<date>
|<Period>)>?
(<valueAttachment:Attachment>
|<valueBoolean:boolean>
|<valueQuantity:Quantity>
|<valueResource:Resource>
|<valueString:string>)?
< Provides the reason in the situation where a reason code is required in addition to the content. For example: the reason for the additional stay, or why a tooth is missing.; (xsd)reason:CodeableConcept>?🔗 A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.ch-core-composition(xsd)(doc)=
<#base:Composition>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.; (xsd)identifier:Identifier>?
< The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required.; (xsd)status:code>
< Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.; (xsd)type:CodeableConcept>
[]< A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).; (xsd)category:CodeableConcept>*
< Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For clinical documents, this is usually the patient.; (xsd)subject:ch-core-patient*>?
< Describes the clinical encounter or type of care this documentation is associated with.; (xsd)encounter:ch-core-encounter*>?
< The composition editing time, when the composition was last logically changed by the author. The Last Modified Date on the composition may be after the date of the document was attested without being changed.; (xsd)date:dateTime>
[]< Identifies who is responsible for the information in the composition, not necessarily who typed it in.; (xsd)author:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>+
< Official human-readable label for the composition. For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.; (xsd)title:string>
< The code specifying the level of confidentiality of the Composition. The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.; (xsd)confidentiality:code>?
[]< A participant who has attested to the accuracy of the composition/document. Only list each attester once.; (xsd)attester:ch-core-composition.attester>*
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.; (xsd)custodian:ch-core-organization*>?
[]< Relationships that this composition has with other compositions or documents that already exist. A document is a version specific composition.; (xsd)relatesTo:ch-core-composition.relatesTo>*
[]< The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.; (xsd)event:ch-core-composition.event>*
[]< The root of the sections that make up the composition.; (xsd)section:ch-core-composition.section>*🔗 A participant who has attested to the accuracy of the composition/document. Only list each attester once.ch-core-composition.attester(xsd)(doc)=
<#base:Composition.attester>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of attestation the authenticator offers.; (xsd)mode:code>
< When the composition was attested by the party.; (xsd)time:dateTime>?
< Who attested the composition in the specified way.; (xsd)party:(<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?🔗 Who attested the composition in the specified way.ch-core-composition.attester.party(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Identifies who is responsible for the information in the composition, not necessarily who typed it in.ch-core-composition.author(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.ch-core-composition.custodian(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.ch-core-composition.event(xsd)(doc)=
<#base:Composition.event>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.; (xsd)code:CodeableConcept>*
< The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.; (xsd)period:Period>?
[]< The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy.; (xsd)detail:Resource*>*🔗 Relationships that this composition has with other compositions or documents that already exist. A document is a version specific composition.ch-core-composition.relatesTo(xsd)(doc)=
<#base:Composition.relatesTo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship that this composition has with anther composition or document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.; (xsd)code>
< The target composition/document of this relationship.; (xsd)target:(<ch-core-composition>
|<Identifier>)>🔗 The root of the sections that make up the composition.ch-core-composition.section(xsd)(doc)=
<#base:Composition.section>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.; (xsd)title:string>?
< A code identifying the kind of content contained within the section. This must be consistent with the section title. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.; (xsd)code:CodeableConcept>?
[]< Identifies who is responsible for the information in this section, not necessarily who typed it in.; (xsd)author:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>*
< The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.; (xsd)focus:Resource*>?
< A human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety.; (xsd)text:Narrative>?
< How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. This element is labeled as a modifier because a change list must not be misunderstood as a complete list.; (xsd)mode:code>?
< Specifies the order applied to the items in the section entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.; (xsd)orderedBy:CodeableConcept>?
[]< A reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided.; (xsd)entry:Resource*>*
< If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.; (xsd)emptyReason:CodeableConcept>?
[]< A nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.; (xsd)section:Composition.section>*🔗 Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For clinical documents, this is usually the patient.ch-core-composition.subject(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.ch-core-composition-epr(xsd)(doc)=
<#base:ch-core-composition>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.; (xsd)identifier:ch-core-composition-epr.identifier>
< The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required.; (xsd)status:code>
< Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.; (xsd)type:CodeableConcept>
[]< A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).; (xsd)category:CodeableConcept>*
< Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For clinical documents, this is usually the patient.; (xsd)subject:ch-core-patient-epr*>
< Describes the clinical encounter or type of care this documentation is associated with.; (xsd)encounter:ch-core-encounter*>?
< The composition editing time, when the composition was last logically changed by the author. The Last Modified Date on the composition may be after the date of the document was attested without being changed.; (xsd)date:dateTime>
[]< Identifies who is responsible for the information in the composition, not necessarily who typed it in.; (xsd)author:(<Device>
|<ch-core-organization-epr>
|<ch-core-patient-epr>
|<ch-core-practitioner-epr>
|<ch-core-practitionerrole-epr>
|<RelatedPerson>)>+
< Official human-readable label for the composition. For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.; (xsd)title:string>
< The code specifying the level of confidentiality of the Composition. The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.; (xsd)confidentiality:ch-core-composition-epr.confidentiality>
[]< A participant who has attested to the accuracy of the composition/document. Only list each attester once.; (xsd)attester:ch-core-composition-epr.attester>*
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.; (xsd)custodian:ch-core-organization-epr*>?
[]< Relationships that this composition has with other compositions or documents that already exist. A document is a version specific composition.; (xsd)relatesTo:ch-core-composition-epr.relatesTo>*
[]< The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.; (xsd)event:ch-core-composition-epr.event>*
[]< The root of the sections that make up the composition.; (xsd)section:ch-core-composition-epr.section>*
[]< Extension to define the information about the recipient; (xsd)informationRecipient:ch-ext-epr-informationrecipient>*
< Extension to define the information about the person and organization that entered data and the time of the data input; (xsd)dataEnterer:ch-ext-epr-dataenterer>?
< A participant who has attested to the accuracy of the composition/document. Only list each attester once.; (xsd)legalAuthenticator:ch-core-composition-epr.legalAuthenticator>?
< The root of the sections that make up the composition.; (xsd)originalRepresentation:ch-core-composition-epr.originalRepresentation>?🔗 A participant who has attested to the accuracy of the composition/document. Only list each attester once.ch-core-composition-epr.attester(xsd)(doc)=
<#base:Composition.attester>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of attestation the authenticator offers.; (xsd)mode:code>
< When the composition was attested by the party.; (xsd)time:dateTime>?
< Who attested the composition in the specified way.; (xsd)party:(<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?🔗 Who attested the composition in the specified way.ch-core-composition-epr.attester.party(xsd)(doc)=
<#base:ch-core-composition.attester.party>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Identifies who is responsible for the information in the composition, not necessarily who typed it in.ch-core-composition-epr.author(xsd)(doc)=
<#base:ch-core-composition.author>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?
< Extension to define the timestamp of the authorship/data input; (xsd)time:ch-ext-epr-time>?🔗 The code specifying the level of confidentiality of the Composition. The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.ch-core-composition-epr.confidentiality(xsd)(doc)=
<#base:code>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>+
< Primitive value for code; (xsd)value:string>?
< Extension to define the confidentiality code of the document; (xsd)confidentialityCode:ch-ext-epr-confidentialitycode>🔗 Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.ch-core-composition-epr.custodian(xsd)(doc)=
<#base:ch-core-composition.custodian>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.ch-core-composition-epr.event(xsd)(doc)=
<#base:Composition.event>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.; (xsd)code:CodeableConcept>*
< The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.; (xsd)period:Period>?
[]< The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy.; (xsd)detail:Resource*>*🔗 A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.ch-core-composition-epr.identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:ietf:rfc:3986; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A participant who has attested to the accuracy of the composition/document. Only list each attester once.ch-core-composition-epr.legalAuthenticator(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of attestation the authenticator offers. legal; (xsd)mode:code>
< When the composition was attested by the party.; (xsd)time:dateTime>?
< Who attested the composition in the specified way.; (xsd)party:(<ch-core-patient-epr>
|<ch-core-practitioner-epr>
|<ch-core-practitionerrole-epr>
|<RelatedPerson>)>🔗 Who attested the composition in the specified way.ch-core-composition-epr.legalAuthenticator.party(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 The root of the sections that make up the composition.ch-core-composition-epr.originalRepresentation(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.; (xsd)title:string>
< A code identifying the kind of content contained within the section. This must be consistent with the section title. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.; (xsd)code:CodeableConcept>
[]< Identifies who is responsible for the information in this section, not necessarily who typed it in.; (xsd)author:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>*
< The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.; (xsd)focus:Resource*>?
< A human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety.; (xsd)text:Narrative>
< How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. This element is labeled as a modifier because a change list must not be misunderstood as a complete list.; (xsd)mode:code>?
< Specifies the order applied to the items in the section entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.; (xsd)orderedBy:CodeableConcept>?
< A reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided.; (xsd)entry:Binary*>
< If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.; (xsd)emptyReason:CodeableConcept>?
< A nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.; (xsd)section:Composition.section>{0,0}🔗 Relationships that this composition has with other compositions or documents that already exist. A document is a version specific composition.ch-core-composition-epr.relatesTo(xsd)(doc)=
<#base:Composition.relatesTo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship that this composition has with anther composition or document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.; (xsd)code>
< The target composition/document of this relationship.; (xsd)target:(<ch-core-composition-epr>
|<Identifier>)>🔗 The root of the sections that make up the composition.ch-core-composition-epr.section(xsd)(doc)=
<#base:Composition.section>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.; (xsd)title:string>?
< A code identifying the kind of content contained within the section. This must be consistent with the section title. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.; (xsd)code:CodeableConcept>?
[]< Identifies who is responsible for the information in this section, not necessarily who typed it in.; (xsd)author:(<Device>
|<ch-core-organization-epr>
|<ch-core-patient-epr>
|<ch-core-practitioner-epr>
|<ch-core-practitionerrole-epr>
|<RelatedPerson>)>*
< The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.; (xsd)focus:Resource*>?
< A human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety.; (xsd)text:Narrative>?
< How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. This element is labeled as a modifier because a change list must not be misunderstood as a complete list.; (xsd)mode:code>?
< Specifies the order applied to the items in the section entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.; (xsd)orderedBy:CodeableConcept>?
[]< A reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided.; (xsd)entry:Resource*>*
< If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.; (xsd)emptyReason:CodeableConcept>?
[]< A nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.; (xsd)section:Composition.section>*🔗 Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For clinical documents, this is usually the patient.ch-core-composition-epr.subject(xsd)(doc)=
<#base:ch-core-composition.subject>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.ch-core-condition(xsd)(doc)=
<#base:Condition>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; (xsd)identifier:Identifier>*
< The clinical status of the condition. The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.; (xsd)clinicalStatus:CodeableConcept>?
< The verification status to support the clinical status of the condition. verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.
The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.; (xsd)verificationStatus:CodeableConcept>?
[]< A category assigned to the condition. The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.; (xsd)category:CodeableConcept>*
< A subjective assessment of the severity of the condition as evaluated by the clinician. Coding of the severity with a terminology is preferred, where possible.; (xsd)severity:CodeableConcept>?
< Identification of the condition, problem or diagnosis.; (xsd)code:CodeableConcept>?
[]< The anatomical location where this condition manifests itself. Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.; (xsd)bodySite:CodeableConcept>*
< Indicates the patient or group who the condition record is associated with.; (xsd)subject:(<Group>
|<ch-core-patient>)>
< The Encounter during which this Condition was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".; (xsd)encounter:Encounter*>?
< Estimated or actual date or date-time the condition began, in the opinion of the clinician. Age is generally used when the patient reports an age at which the Condition began to occur.; (xsd)onset:(<Age>
|<dateTime>
|<Period>
|<Range>
|<string>)>?
< The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.; (xsd)abatement:(<Age>
|<dateTime>
|<Period>
|<Range>
|<string>)>?
< The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.; (xsd)recordedDate:dateTime>?
< Individual who recorded the record and takes responsibility for its content.; (xsd)recorder:(<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
< Individual who is making the condition statement.; (xsd)asserter:(<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
[]< Clinical stage or grade of a condition. May include formal severity assessments.; (xsd)stage:ch-core-condition.stage>*
[]< Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.; (xsd)evidence:ch-core-condition.evidence>*
[]< Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.; (xsd)note:Annotation>*🔗 Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.ch-core-condition.evidence(xsd)(doc)=
<#base:Condition.evidence>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A manifestation or symptom that led to the recording of this condition.; (xsd)code:CodeableConcept>*
[]< Links to other relevant information, including pathology reports.; (xsd)detail:Resource*>*🔗 Clinical stage or grade of a condition. May include formal severity assessments.ch-core-condition.stage(xsd)(doc)=
<#base:Condition.stage>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.; (xsd)summary:CodeableConcept>?
[]< Reference to a formal record of the evidence on which the staging assessment is based.; (xsd)assessment:(<ClinicalImpression>
|<DiagnosticReport>
|<Observation>)>*
< The kind of staging, such as pathological or clinical staging.; (xsd)type:CodeableConcept>?🔗 Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.ch-core-contactpoint-ech-46-email(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact. email; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:ch-core-contactpoint-ech-46-email.use>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:ch-core-contactpoint-ech-46-email.period>?🔗 Time period when the contact point was/is in use.ch-core-contactpoint-ech-46-email.period(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 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.ch-core-contactpoint-ech-46-email.use(xsd)(doc)=
<#base:code>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Primitive value for code; (xsd)value:string>?
< Optional Extension Element - found in all resources.; (xsd)emailCategory:ch-ext-ech-46-emailcategory>?🔗 Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.ch-core-contactpoint-ech-46-internet(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact. url; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:ch-core-contactpoint-ech-46-internet.use>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:ch-core-contactpoint-ech-46-internet.period>?🔗 Time period when the contact point was/is in use.ch-core-contactpoint-ech-46-internet.period(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 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.ch-core-contactpoint-ech-46-internet.use(xsd)(doc)=
<#base:code>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Primitive value for code; (xsd)value:string>?
< Optional Extension Element - found in all resources.; (xsd)internetCategory:ch-ext-ech-46-internetcategory>?🔗 Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.ch-core-contactpoint-ech-46-phone(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact. phone; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:ch-core-contactpoint-ech-46-phone.use>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:ch-core-contactpoint-ech-46-phone.period>?🔗 Time period when the contact point was/is in use.ch-core-contactpoint-ech-46-phone.period(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 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.ch-core-contactpoint-ech-46-phone.use(xsd)(doc)=
<#base:code>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Primitive value for code; (xsd)value:string>?
< Optional Extension Element - found in all resources.; (xsd)phoneCategory:ch-ext-ech-46-phonecategory>?🔗 This is basic constraint on Coverage for use in CH Core resources. The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.ch-core-coverage(xsd)(doc)=
<#base:Coverage>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A unique identifier assigned to this coverage. The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.; (xsd)identifier:Identifier>*
< The status of the resource instance. This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.; (xsd)status:code>
< The type of coverage: social program, medical plan, accident coverage (workers compensation, auto), group health or payment by an individual or organization.; (xsd)type:CodeableConcept>?
< The party who 'owns' the insurance policy. For example: may be an individual, corporation or the subscriber's employer.; (xsd)policyHolder:(<ch-core-organization>
|<ch-core-patient>
|<RelatedPerson>)>?
< The party who has signed-up for or 'owns' the contractual relationship to the policy or to whom the benefit of the policy for services rendered to them or their family is due. May be self or a parent in the case of dependants.; (xsd)subscriber:(<ch-core-patient>
|<RelatedPerson>)>?
< The insurer assigned ID for the Subscriber.; (xsd)subscriberId:string>?
< The party who benefits from the insurance coverage; the patient when products and/or services are provided.; (xsd)beneficiary:ch-core-patient*>
< A unique identifier for a dependent under the coverage. Periodically the member number is constructed from the subscriberId and the dependant number.; (xsd)dependent:string>?
< The relationship of beneficiary (patient) to the subscriber. Typically, an individual uses policies which are theirs (relationship='self') before policies owned by others.; (xsd)relationship:CodeableConcept>?
< Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.; (xsd)period:Period>?
[]< The program or plan underwriter or payor including both insurance and non-insurance agreements, such as patient-pay agreements. May provide multiple identifiers such as insurance company identifier or business identifier (BIN number).
For selfpay it may provide multiple paying persons and/or organizations.; (xsd)payor:(<ch-core-organization>
|<ch-core-patient>
|<RelatedPerson>)>+
[]< A suite of underwriter specific classifiers. For example may be used to identify a class of coverage or employer group, Policy, Plan.; (xsd)class:ch-core-coverage.class>*
< The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.; (xsd)order:positiveInt>?
< The insurer-specific identifier for the insurer-defined network of providers to which the beneficiary may seek treatment which will be covered at the 'in-network' rate, otherwise 'out of network' terms and conditions apply.; (xsd)network:string>?
[]< A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card. For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.; (xsd)costToBeneficiary:ch-core-coverage.costToBeneficiary>*
< When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs. Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.; (xsd)subrogation:boolean>?
[]< The policy(s) which constitute this insurance coverage.; (xsd)contract:Contract*>*
[]< Cardnumber Swiss insurance card v1 The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.; (xsd)insuranceCardNumber:ch-core-veka-identifier>*🔗 A suite of underwriter specific classifiers. For example may be used to identify a class of coverage or employer group, Policy, Plan.ch-core-coverage.class(xsd)(doc)=
<#base:Coverage.class>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.; (xsd)type:CodeableConcept>
< The alphanumeric string value associated with the insurer issued label. For example, the Group or Plan number.; (xsd)value:string>
< A short description for the class.; (xsd)name:string>?🔗 A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card. For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.ch-core-coverage.costToBeneficiary(xsd)(doc)=
<#base:Coverage.costToBeneficiary>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The category of patient centric costs associated with treatment. For example visit, specialist visits, emergency, inpatient care, etc.; (xsd)type:CodeableConcept>?
(<valueMoney:Money>
|<valueSimpleQuantity:SimpleQuantity>)
[]< A suite of codes indicating exceptions or reductions to patient costs and their effective periods.; (xsd)exception:ch-core-coverage.costToBeneficiary.exception>*🔗 A suite of codes indicating exceptions or reductions to patient costs and their effective periods.ch-core-coverage.costToBeneficiary.exception(xsd)(doc)=
<#base:Coverage.costToBeneficiary.exception>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The code for the specific exception.; (xsd)type:CodeableConcept>
< The timeframe during when the exception is in force.; (xsd)period:Period>?🔗 A container for a collection of resources.ch-core-document(xsd)(doc)=
<#base:Bundle>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.; (xsd)identifier:ch-core-document.identifier>
< Indicates the purpose of this bundle - how it is intended to be used. It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types. document; (xsd)type:code>
< The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
Usage:
* document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
* message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
* searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.; (xsd)timestamp:instant>
< If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.; (xsd)total:unsignedInt>?
[]< A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R4/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R4/search.html#conformance) and [paging](http://hl7.org/fhir/R4/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.; (xsd)link:ch-core-document.link>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)entry:ch-core-document.entry>+
< Digital Signature - base64 encoded. XML-DSig or a JWT. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.; (xsd)signature:Signature>?
< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Composition:ch-core-document.Composition>
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Patient:ch-core-document.Patient>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Practitioner:ch-core-document.Practitioner>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)PractitionerRole:ch-core-document.PractitionerRole>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Organization:ch-core-document.Organization>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)RelatedPerson:ch-core-document.RelatedPerson>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Device:ch-core-document.Device>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Encounter:ch-core-document.Encounter>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Location:ch-core-document.Location>*🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Composition(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.; (xsd)resource:ch-core-composition>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Composition.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Composition.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Composition.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Composition.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Composition.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Composition.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Device(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.; (xsd)resource:Device>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Device.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Device.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Device.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Device.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Device.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Device.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Encounter(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< This is basic constraint on Encounter for use in CH Core resources.; (xsd)resource:ch-core-encounter>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Encounter.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Encounter.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Encounter.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Encounter.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Encounter.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Encounter.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.entry(xsd)(doc)=
<#base:Bundle.entry>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>
< The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.; (xsd)resource:Resource>?
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.entry.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.entry.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.entry.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.entry.request(xsd)(doc)=
<#base:Bundle.entry.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.entry.response(xsd)(doc)=
<#base:Bundle.entry.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.entry.search(xsd)(doc)=
<#base:Bundle.entry.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.ch-core-document.identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive.; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R4/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R4/search.html#conformance) and [paging](http://hl7.org/fhir/R4/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.ch-core-document.link(xsd)(doc)=
<#base:Bundle.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1).; (xsd)relation:string>
< The reference details for the link.; (xsd)url:uri>🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Location(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.; (xsd)resource:ch-core-location>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Location.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Location.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Location.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Location.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Location.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Location.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Organization(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< 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.; (xsd)resource:ch-core-organization>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Organization.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Organization.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Organization.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Organization.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Organization.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Organization.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Patient(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< The CH Core Patient is based upon the core FHIR Patient Resource and designed to meet the applicable patient demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further information; (xsd)resource:ch-core-patient>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Patient.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Patient.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Patient.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Patient.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Patient.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Patient.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.Practitioner(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< The CH Core Practitioner is based upon the core FHIR Practitioner Resource and designed to meet the applicable practitioner demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further information; (xsd)resource:ch-core-practitioner>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.Practitioner.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.Practitioner.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.Practitioner.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.Practitioner.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.Practitioner.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.Practitioner.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.PractitionerRole(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.; (xsd)resource:ch-core-practitionerrole>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.PractitionerRole.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.PractitionerRole.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.PractitionerRole.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.PractitionerRole.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.PractitionerRole.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.PractitionerRole.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document.RelatedPerson(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.; (xsd)resource:RelatedPerson>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document.RelatedPerson.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document.RelatedPerson.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document.RelatedPerson.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document.RelatedPerson.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document.RelatedPerson.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document.RelatedPerson.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A container for a collection of resources.ch-core-document-epr(xsd)(doc)=
<#base:ch-core-document>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.; (xsd)identifier:ch-core-document-epr.identifier>
< Indicates the purpose of this bundle - how it is intended to be used. It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types. document; (xsd)type:code>
< The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
Usage:
* document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
* message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
* searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.; (xsd)timestamp:instant>
< If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.; (xsd)total:unsignedInt>?
[]< A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R4/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R4/search.html#conformance) and [paging](http://hl7.org/fhir/R4/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.; (xsd)link:ch-core-document-epr.link>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)entry:ch-core-document-epr.entry>+
< Digital Signature - base64 encoded. XML-DSig or a JWT. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.; (xsd)signature:Signature>?
< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Composition:ch-core-document-epr.Composition>
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Patient:ch-core-document-epr.Patient>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Practitioner:ch-core-document-epr.Practitioner>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)PractitionerRole:ch-core-document-epr.PractitionerRole>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Organization:ch-core-document-epr.Organization>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)RelatedPerson:ch-core-document-epr.RelatedPerson>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Device:ch-core-document-epr.Device>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Encounter:ch-core-document-epr.Encounter>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Location:ch-core-document-epr.Location>*
[]< An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).; (xsd)Binary:ch-core-document-epr.Binary>*🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Binary(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>
< A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. Typically, Binary resources are used for handling content such as:
* CDA Documents (i.e. with XDS)
* PDF Documents
* Images (the Media resource is preferred for handling images, but not possible when the content is already binary - e.g. XDS).; (xsd)resource:Binary>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Binary.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Binary.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Binary.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Binary.request(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Binary.response(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Binary.search(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Composition(xsd)(doc)=
<#base:ch-core-document.Composition>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.; (xsd)resource:ch-core-composition-epr>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Composition.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Composition.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Composition.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Composition.request(xsd)(doc)=
<#base:ch-core-document.Composition.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Composition.response(xsd)(doc)=
<#base:ch-core-document.Composition.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Composition.search(xsd)(doc)=
<#base:ch-core-document.Composition.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Device(xsd)(doc)=
<#base:ch-core-document.Device>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.; (xsd)resource:Device>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Device.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Device.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Device.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Device.request(xsd)(doc)=
<#base:ch-core-document.Device.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Device.response(xsd)(doc)=
<#base:ch-core-document.Device.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Device.search(xsd)(doc)=
<#base:ch-core-document.Device.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Encounter(xsd)(doc)=
<#base:ch-core-document.Encounter>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< This is basic constraint on Encounter for use in CH Core resources.; (xsd)resource:ch-core-encounter>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Encounter.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Encounter.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Encounter.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Encounter.request(xsd)(doc)=
<#base:ch-core-document.Encounter.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Encounter.response(xsd)(doc)=
<#base:ch-core-document.Encounter.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Encounter.search(xsd)(doc)=
<#base:ch-core-document.Encounter.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.entry(xsd)(doc)=
<#base:Bundle.entry>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>
< The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.; (xsd)resource:Resource>?
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.entry.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.entry.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.entry.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.entry.request(xsd)(doc)=
<#base:Bundle.entry.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.entry.response(xsd)(doc)=
<#base:Bundle.entry.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.entry.search(xsd)(doc)=
<#base:Bundle.entry.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.ch-core-document-epr.identifier(xsd)(doc)=
<#base:ch-core-document.identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:ietf:rfc:3986; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R4/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R4/search.html#conformance) and [paging](http://hl7.org/fhir/R4/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.ch-core-document-epr.link(xsd)(doc)=
<#base:Bundle.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1).; (xsd)relation:string>
< The reference details for the link.; (xsd)url:uri>🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Location(xsd)(doc)=
<#base:ch-core-document.Location>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.; (xsd)resource:ch-core-location>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Location.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Location.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Location.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Location.request(xsd)(doc)=
<#base:ch-core-document.Location.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Location.response(xsd)(doc)=
<#base:ch-core-document.Location.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Location.search(xsd)(doc)=
<#base:ch-core-document.Location.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Organization(xsd)(doc)=
<#base:ch-core-document.Organization>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< 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.; (xsd)resource:ch-core-organization>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Organization.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Organization.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Organization.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Organization.request(xsd)(doc)=
<#base:ch-core-document.Organization.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Organization.response(xsd)(doc)=
<#base:ch-core-document.Organization.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Organization.search(xsd)(doc)=
<#base:ch-core-document.Organization.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Patient(xsd)(doc)=
<#base:ch-core-document.Patient>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< The CH Core Patient is based upon the core FHIR Patient Resource and designed to meet the applicable patient demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further information; (xsd)resource:ch-core-patient>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Patient.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Patient.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Patient.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Patient.request(xsd)(doc)=
<#base:ch-core-document.Patient.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Patient.response(xsd)(doc)=
<#base:ch-core-document.Patient.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Patient.search(xsd)(doc)=
<#base:ch-core-document.Patient.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.Practitioner(xsd)(doc)=
<#base:ch-core-document.Practitioner>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< The CH Core Practitioner is based upon the core FHIR Practitioner Resource and designed to meet the applicable practitioner demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further information; (xsd)resource:ch-core-practitioner>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.Practitioner.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.Practitioner.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.Practitioner.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.Practitioner.request(xsd)(doc)=
<#base:ch-core-document.Practitioner.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.Practitioner.response(xsd)(doc)=
<#base:ch-core-document.Practitioner.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.Practitioner.search(xsd)(doc)=
<#base:ch-core-document.Practitioner.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.PractitionerRole(xsd)(doc)=
<#base:ch-core-document.PractitionerRole>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.; (xsd)resource:ch-core-practitionerrole>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.PractitionerRole.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.PractitionerRole.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.PractitionerRole.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.PractitionerRole.request(xsd)(doc)=
<#base:ch-core-document.PractitionerRole.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.PractitionerRole.response(xsd)(doc)=
<#base:ch-core-document.PractitionerRole.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.PractitionerRole.search(xsd)(doc)=
<#base:ch-core-document.PractitionerRole.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).ch-core-document-epr.RelatedPerson(xsd)(doc)=
<#base:ch-core-document.RelatedPerson>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
* Results from operations might involve resources that are not identified. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>?
< Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.; (xsd)resource:RelatedPerson>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ch-core-document-epr.RelatedPerson.search>?
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ch-core-document-epr.RelatedPerson.request>?
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ch-core-document-epr.RelatedPerson.response>?🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ch-core-document-epr.RelatedPerson.request(xsd)(doc)=
<#base:ch-core-document.RelatedPerson.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.; (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ch-core-document-epr.RelatedPerson.response(xsd)(doc)=
<#base:ch-core-document.RelatedPerson.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ch-core-document-epr.RelatedPerson.search(xsd)(doc)=
<#base:ch-core-document.RelatedPerson.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.; (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR.ch-core-documentreference(xsd)(doc)=
<#base:DocumentReference>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Document identifier as assigned by the source of the document. This identifier is specific to this version of the document. This unique identifier may be used elsewhere to identify this version of the document. CDA Document Id extension and root.; (xsd)masterIdentifier:Identifier>?
[]< Other identifiers associated with the document, including version independent identifiers.; (xsd)identifier:Identifier>*
< The status of this document reference. This is the status of the DocumentReference object, which might be independent from the docStatus element.
This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid.; (xsd)status:code>
< The status of the underlying document. The document that is pointed to might be in various lifecycle states.; (xsd)docStatus:code>?
< Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents.; (xsd)type:CodeableConcept>?
[]< A categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching.; (xsd)category:CodeableConcept>*
< Who or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure).; (xsd)subject:(<Device>
|<Group>
|<ch-core-patient>
|<ch-core-practitioner>)>?
< When the document reference was created. Referencing/indexing time is used for tracking, organizing versions and searching.; (xsd)date:instant>?
[]< Identifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant).; (xsd)author:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>*
< Which person or organization authenticates that this document is valid. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator.; (xsd)authenticator:(<ch-core-organization>
|<ch-core-practitioner>
|<ch-core-practitionerrole>)>?
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.; (xsd)custodian:ch-core-organization*>?
[]< Relationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.; (xsd)relatesTo:ch-core-documentreference.relatesTo>*
< Human-readable description of the source document. What the document is about, a terse summary of the document.; (xsd)description:string>?
[]< A set of Security-Tag codes specifying the level of privacy/security of the Document. Note that DocumentReference.meta.security contains the security labels of the "reference" to the document, while DocumentReference.securityLabel contains a snapshot of the security labels on the document the reference refers to. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce.
In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects.; (xsd)securityLabel:CodeableConcept>*
[]< The document and format referenced. There may be multiple content element repetitions, each with a different format.; (xsd)content:ch-core-documentreference.content>+
< The clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.; (xsd)context:ch-core-documentreference.context>?🔗 The document and format referenced. There may be multiple content element repetitions, each with a different format.ch-core-documentreference.content(xsd)(doc)=
<#base:DocumentReference.content>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The document or URL of the document along with critical metadata to prove content has integrity.; (xsd)attachment:ch-core-documentreference.content.attachment>
< An identifier of the document encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI.; (xsd)format:Coding>?🔗 The document or URL of the document along with critical metadata to prove content has integrity.ch-core-documentreference.content.attachment(xsd)(doc)=
<#base:Attachment>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.; (xsd)contentType:code>?
< The human language of the content. The value can be any valid value according to BCP 47.; (xsd)language:code>?
< The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>?
< A location where the data can be accessed. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>?
< The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:unsignedInt>?
< The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
< A label or set of text to display in place of the data.; (xsd)title:string>?
< The date that the attachment was first created.; (xsd)creation:dateTime>?🔗 The clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.ch-core-documentreference.context(xsd)(doc)=
<#base:DocumentReference.context>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Describes the clinical encounter or type of care that the document content is associated with.; (xsd)encounter:(<EpisodeOfCare>
|<ch-core-encounter>)>*
[]< This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation.; (xsd)event:CodeableConcept>*
< The time period over which the service that is described by the document was provided.; (xsd)period:Period>?
< The kind of facility where the patient was seen.; (xsd)facilityType:CodeableConcept>?
< This property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC.; (xsd)practiceSetting:CodeableConcept>?
< The Patient Information as known when the document was published. May be a reference to a version specific, or contained.; (xsd)sourcePatientInfo:ch-core-patient*>?
[]< Related identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.; (xsd)related:Resource*>*🔗 Relationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.ch-core-documentreference.relatesTo(xsd)(doc)=
<#base:DocumentReference.relatesTo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship that this document has with anther document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.; (xsd)code>
< The target document of this relationship.; (xsd)target:ch-core-documentreference*>🔗 A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR.ch-core-documentreference-epr(xsd)(doc)=
<#base:ch-core-documentreference>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Document identifier as assigned by the source of the document. This identifier is specific to this version of the document. This unique identifier may be used elsewhere to identify this version of the document. CDA Document Id extension and root.; (xsd)masterIdentifier:Identifier>?
[]< Other identifiers associated with the document, including version independent identifiers.; (xsd)identifier:Identifier>*
< The status of this document reference. This is the status of the DocumentReference object, which might be independent from the docStatus element.
This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid.; (xsd)status:code>
< The status of the underlying document. The document that is pointed to might be in various lifecycle states.; (xsd)docStatus:code>?
< Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents.; (xsd)type:CodeableConcept>
[]< A categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching.; (xsd)category:CodeableConcept>+
< Who or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure).; (xsd)subject:ch-core-patient-epr*>
< When the document reference was created. Referencing/indexing time is used for tracking, organizing versions and searching.; (xsd)date:instant>
[]< Identifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant).; (xsd)author:(<Device>
|<ch-core-patient-epr>
|<ch-core-practitioner-epr>
|<ch-core-practitionerrole-epr>
|<RelatedPerson>)>+
< Which person or organization authenticates that this document is valid. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator.; (xsd)authenticator:(<ch-core-organization-epr>
|<ch-core-practitioner-epr>
|<ch-core-practitionerrole-epr>)>?
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.; (xsd)custodian:ch-core-organization-epr*>?
[]< Relationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.; (xsd)relatesTo:ch-core-documentreference-epr.relatesTo>*
< Human-readable description of the source document. What the document is about, a terse summary of the document.; (xsd)description:string>?
[]< A set of Security-Tag codes specifying the level of privacy/security of the Document. Note that DocumentReference.meta.security contains the security labels of the "reference" to the document, while DocumentReference.securityLabel contains a snapshot of the security labels on the document the reference refers to. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce.
In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects.; (xsd)securityLabel:CodeableConcept>+
[]< The document and format referenced. There may be multiple content element repetitions, each with a different format.; (xsd)content:ch-core-documentreference-epr.content>+
< The clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.; (xsd)context:ch-core-documentreference-epr.context>?🔗 Identifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant).ch-core-documentreference-epr.author(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 The document and format referenced. There may be multiple content element repetitions, each with a different format.ch-core-documentreference-epr.content(xsd)(doc)=
<#base:DocumentReference.content>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The document or URL of the document along with critical metadata to prove content has integrity.; (xsd)attachment:ch-core-documentreference-epr.content.attachment>
< An identifier of the document encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI.; (xsd)format:Coding>🔗 The document or URL of the document along with critical metadata to prove content has integrity.ch-core-documentreference-epr.content.attachment(xsd)(doc)=
<#base:ch-core-documentreference.content.attachment>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.; (xsd)contentType:code>
< The human language of the content. The value can be any valid value according to BCP 47.; (xsd)language:code>
< The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>?
< A location where the data can be accessed. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>
< The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:unsignedInt>?
< The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
< A label or set of text to display in place of the data.; (xsd)title:string>?
< The date that the attachment was first created.; (xsd)creation:dateTime>?🔗 The clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.ch-core-documentreference-epr.context(xsd)(doc)=
<#base:DocumentReference.context>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Describes the clinical encounter or type of care that the document content is associated with.; (xsd)encounter:(<EpisodeOfCare>
|<ch-core-encounter>)>*
[]< This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation.; (xsd)event:CodeableConcept>*
< The time period over which the service that is described by the document was provided.; (xsd)period:Period>?
< The kind of facility where the patient was seen.; (xsd)facilityType:CodeableConcept>?
< This property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC.; (xsd)practiceSetting:CodeableConcept>?
< The Patient Information as known when the document was published. May be a reference to a version specific, or contained.; (xsd)sourcePatientInfo:ch-core-patient-epr*>?
[]< Related identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.; (xsd)related:Resource*>*🔗 Relationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.ch-core-documentreference-epr.relatesTo(xsd)(doc)=
<#base:DocumentReference.relatesTo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship that this document has with anther document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.; (xsd)code>
< The target document of this relationship.; (xsd)target:ch-core-documentreference*>🔗 Who or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure).ch-core-documentreference-epr.subject(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>
< The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>?
< An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>?
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Indicates how the medication is/was taken or should be taken by the patient.ch-core-dosage(xsd)(doc)=
<#base:Dosage>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Indicates the order in which the dosage instructions should be applied or interpreted.; (xsd)sequence:integer>?
< Free text dosage instructions e.g. SIG.; (xsd)text:string>?
[]< Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps"). Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text.; (xsd)additionalInstruction:CodeableConcept>*
< Instructions in terms that are understood by the patient or consumer.; (xsd)patientInstruction:string>?
< When medication should be administered. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.; (xsd)timing:Timing>?
< Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept). Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed".; (xsd)asNeeded:(<boolean>
|<CodeableConcept>)>?
< Body site to administer to. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.; (xsd)site:CodeableConcept>?
< How drug should enter body.; (xsd)route:CodeableConcept>?
< Technique for administering medication. Terminologies used often pre-coordinate this term with the route and or form of administration.; (xsd)method:CodeableConcept>?
[]< The amount of medication administered.; (xsd)doseAndRate:ch-core-dosage.doseAndRate>*
< Upper limit on medication per unit of time. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".; (xsd)maxDosePerPeriod:Ratio>?
< Upper limit on medication per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.; (xsd)maxDosePerAdministration:SimpleQuantity>?
< Upper limit on medication per lifetime of the patient.; (xsd)maxDosePerLifetime:SimpleQuantity>?🔗 The amount of medication administered.ch-core-dosage.doseAndRate(xsd)(doc)=
<#base:Dosage.doseAndRate>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The kind of dose or rate specified, for example, ordered or calculated.; (xsd)type:CodeableConcept>?
< Amount of medication per dose. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.; (xsd)dose:(<ch-core-quantity-with-emed-units>
|<ch-core-range-with-emed-units>)>?
< Amount of medication per unit of time. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate.
It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.; (xsd)rate:(<Range>
|<Ratio>
|<SimpleQuantity>)>?🔗 This is basic constraint on Encounter for use in CH Core resources.ch-core-encounter(xsd)(doc)=
<#base:Encounter>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifier(s) by which this encounter is known.; (xsd)identifier:Identifier>*
< planned | arrived | triaged | in-progress | onleave | finished | cancelled +. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).; (xsd)status:code>
[]< The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. The current status is always found in the current version of the resource, not the status history.; (xsd)statusHistory:ch-core-encounter.statusHistory>*
< See mapping from BFS Medizinische Statistik [BFS Encounter Class to FHIR mapping](http://fhir.ch/ig/ch-term/ConceptMap-bfs-encounter-class-to-fhir.html); (xsd)class:Coding>
[]< The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.; (xsd)classHistory:ch-core-encounter.classHistory>*
[]< Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Since there are many ways to further classify encounters, this element is 0..*.; (xsd)type:CodeableConcept>*
< Broad categorization of the service that is to be provided (e.g. cardiology).; (xsd)serviceType:CodeableConcept>?
< Indicates the urgency of the encounter.; (xsd)priority:CodeableConcept>?
< The patient or group present at the encounter. While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).; (xsd)subject:(<Group>
|<ch-core-patient>)>
[]< Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).; (xsd)episodeOfCare:EpisodeOfCare*>*
[]< The request this encounter satisfies (e.g. incoming referral or procedure request).; (xsd)basedOn:ServiceRequest*>*
[]< The list of people responsible for providing the service.; (xsd)participant:ch-core-encounter.participant>*
[]< The appointment that scheduled this encounter.; (xsd)appointment:Appointment*>*
< The start and end time of the encounter. If not (yet) known, the end of the Period may be omitted.; (xsd)period:Period>?
< Quantity of time the encounter lasted. This excludes the time during leaves of absence. May differ from the time the Encounter.period lasted because of leave of absence.; (xsd)length:Duration>?
[]< Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).; (xsd)reasonCode:CodeableConcept>*
[]< Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).; (xsd)reasonReference:(<Condition>
|<ImmunizationRecommendation>
|<Observation>
|<Procedure>)>*
[]< The list of diagnosis relevant to this encounter.; (xsd)diagnosis:ch-core-encounter.diagnosis>*
[]< The set of accounts that may be used for billing for this Encounter. The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.; (xsd)account:Account*>*
< Details about the admission to a healthcare service. An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.
The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.; (xsd)hospitalization:ch-core-encounter.hospitalization>?
[]< List of locations where the patient has been during this encounter. Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".; (xsd)location:ch-core-encounter.location>*
< The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy.; (xsd)serviceProvider:ch-core-organization*>?
< Another Encounter of which this encounter is a part of (administratively or in time). This is also used for associating a child's encounter back to the mother's encounter.
Refer to the Notes section in the Patient resource for further details.; (xsd)partOf:ch-core-encounter*>?
[]< Identifier(s) by which this encounter is known.; (xsd)VisitNumber:ch-core-encounter.VisitNumber>*🔗 The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.ch-core-encounter.classHistory(xsd)(doc)=
<#base:Encounter.classHistory>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< inpatient | outpatient | ambulatory | emergency +.; (xsd)class:Coding>
< The time that the episode was in the specified class.; (xsd)period:Period>🔗 The list of diagnosis relevant to this encounter.ch-core-encounter.diagnosis(xsd)(doc)=
<#base:Encounter.diagnosis>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).; (xsd)condition:(<Condition>
|<Procedure>)>
< Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).; (xsd)use:CodeableConcept>?
< Ranking of the diagnosis (for each role type).; (xsd)rank:positiveInt>?🔗 Details about the admission to a healthcare service. An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.
The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.ch-core-encounter.hospitalization(xsd)(doc)=
<#base:Encounter.hospitalization>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Pre-admission identifier.; (xsd)preAdmissionIdentifier:Identifier>?
< The location/organization from which the patient came before admission.; (xsd)origin:(<ch-core-location>
|<ch-core-organization>)>?
< From where patient was admitted (physician referral, transfer).; (xsd)admitSource:CodeableConcept>?
< Whether this hospitalization is a readmission and why if known.; (xsd)reAdmission:CodeableConcept>?
[]< Diet preferences reported by the patient. For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).; (xsd)dietPreference:CodeableConcept>*
[]< Special courtesies (VIP, board member).; (xsd)specialCourtesy:CodeableConcept>*
[]< Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.; (xsd)specialArrangement:CodeableConcept>*
< Location/organization to which the patient is discharged.; (xsd)destination:(<ch-core-location>
|<ch-core-organization>)>?
< Category or kind of location after discharge.; (xsd)dischargeDisposition:CodeableConcept>?
< Optional Extension Element - found in all resources.; (xsd)BfsAdmitRole:ch-ext-bfs-ms-admitrole>?
< Extension to define an encounter is caused by an accident and at which time the accident happened; (xsd)accident:ch-ext-accident>?
< Optional Extension Element - found in all resources.; (xsd)readmission:ch-ext-encounter-susp-readmission>?
< Optional Extension Element - found in all resources.; (xsd)BfsDischargeDecision:ch-ext-bfs-ms-dischargedecision>?
< Optional Extension Element - found in all resources.; (xsd)BfsDischargeDestination:ch-ext-bfs-ms-dischargedestination>?🔗 List of locations where the patient has been during this encounter. Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".ch-core-encounter.location(xsd)(doc)=
<#base:Encounter.location>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The location where the encounter takes place.; (xsd)location:ch-core-location*>
< The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.; (xsd)status:code>?
< This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.
There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.; (xsd)physicalType:CodeableConcept>?
< Time period during which the patient was present at the location.; (xsd)period:Period>?🔗 The list of people responsible for providing the service.ch-core-encounter.participant(xsd)(doc)=
<#base:Encounter.participant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Role of participant in encounter. The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.; (xsd)type:CodeableConcept>*
< The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.; (xsd)period:Period>?
< Persons involved in the encounter other than the patient.; (xsd)individual:(<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?🔗 The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. The current status is always found in the current version of the resource, not the status history.ch-core-encounter.statusHistory(xsd)(doc)=
<#base:Encounter.statusHistory>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< planned | arrived | triaged | in-progress | onleave | finished | cancelled +.; (xsd)status:code>
< The time that the episode was in the specified status.; (xsd)period:Period>🔗 Identifier(s) by which this encounter is known.ch-core-encounter.VisitNumber(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive.; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.ch-core-epr-consent(xsd)(doc)=
<#base:Consent>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Unique identifier for this copy of the Consent Statement. This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.; (xsd)identifier:Identifier>*
< Indicates the current state of this consent. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.; (xsd)status:code>
< A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible.; (xsd)scope:CodeableConcept>
[]< A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.; (xsd)category:CodeableConcept>+
< The patient/healthcare consumer to whom this consent applies. Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.; (xsd)patient:ch-core-patient*>
< When this Consent was issued / created / indexed. This is not the time of the original consent, but the time that this statement was made or derived.; (xsd)dateTime>?
[]< Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions. Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.; (xsd)performer:(<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>*
[]< The organization that manages the consent, and the framework within which it is executed.; (xsd)organization:ch-core-organization*>*
< The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document. The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.; (xsd)source:(<Attachment>
|<Consent>
|<Contract>
|<DocumentReference>
|<QuestionnaireResponse>)>?
[]< The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.; (xsd)policy:ch-core-epr-consent.policy>*
< A reference to the specific base computable regulation or policy. If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.; (xsd)policyRule:CodeableConcept>?
[]< Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.; (xsd)verification:ch-core-epr-consent.verification>*
< An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.; (xsd)provision:ch-core-epr-consent.provision>?
< A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.; (xsd)VSCat:ch-core-epr-consent.VSCat>🔗 The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.ch-core-epr-consent.policy(xsd)(doc)=
<#base:Consent.policy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives.; (xsd)authority:uri>?
< The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law. This element is for discoverability / documentation and does not modify or qualify the policy rules.; (xsd)uri>?🔗 An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.ch-core-epr-consent.provision(xsd)(doc)=
<#base:Consent.provision>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Encounters can be added here where the consent for the EPR does not apply. deny; (xsd)type:code>
< The timeframe in this rule is valid.; (xsd)period:Period>?
[]< Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').; (xsd)actor:ch-core-epr-consent.provision.actor>*
[]< Actions controlled by this Rule. Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.; (xsd)action:CodeableConcept>*
[]< A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.; (xsd)securityLabel:Coding>*
[]< The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. When the purpose of use tag is on the data, access request purpose of use shall not conflict.; (xsd)purpose:Coding>*
[]< The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to. Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.; (xsd)class:Coding>*
[]< If this code is found in an instance, then the rule applies. Typical use of this is a Document code with class = CDA.; (xsd)code:CodeableConcept>*
< Clinical or Operational Relevant period of time that bounds the data controlled by this rule. This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.; (xsd)dataPeriod:Period>?
[]< The resources controlled by this rule if specific resources are referenced.; (xsd)data:ch-core-epr-consent.provision.data>*
[]< Rules which provide exceptions to the base rule or subrules.; (xsd)provision:Consent.provision>*🔗 Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').ch-core-epr-consent.provision.actor(xsd)(doc)=
<#base:Consent.provision.actor>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< How the individual is involved in the resources content that is described in the exception.; (xsd)role:CodeableConcept>
< The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').; (xsd)reference:(<CareTeam>
|<Device>
|<Group>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>🔗 The resources controlled by this rule if specific resources are referenced.ch-core-epr-consent.provision.data(xsd)(doc)=
<#base:Consent.provision.data>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< How the resource reference is interpreted when testing consent restrictions. instance; (xsd)meaning:code>
< A reference to the encounter where the consent for the EPR does not apply.; (xsd)reference:ch-core-encounter*>🔗 Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.ch-core-epr-consent.verification(xsd)(doc)=
<#base:Consent.verification>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Has the instruction been verified.; (xsd)verified:boolean>
< Who verified the instruction (Patient, Relative or other Authorized Person).; (xsd)verifiedWith:(<Patient>
|<RelatedPerson>)>?
< Date verification was collected.; (xsd)verificationDate:dateTime>?🔗 A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.ch-core-epr-consent.VSCat(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:ch-core-epr-consent.VSCat.coding>+
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-epr-consent.VSCat.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. http://terminology.hl7.org/CodeSystem/v3-ActCode; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). IDSCL; (xsd)code>
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-epr-spid-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.30.1.127.3.10.3; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 Extension to make a reference beween resources as entries in i.e. document bundles.ch-core-ext-entry-resource-cross-references(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>{3,2147483647}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-ext-entry-resource-cross-references; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>){0,0}
< Reference to the related entry.; (xsd)entry:ch-core-ext-entry-resource-cross-references.entry>
< Reference to the related container resource; (xsd)container:ch-core-ext-entry-resource-cross-references.container>
< Reference to the related document; (xsd)relationcode:ch-core-ext-entry-resource-cross-references.relationcode>🔗 Reference to the related container resourcech-core-ext-entry-resource-cross-references.container(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. container; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueReference:(<ch-core-ext-entry-resource-cross-references.container.valueReference>
|<Resource>)>?🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-core-ext-entry-resource-cross-references.container.valueReference(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>{0,0}
< The resource type of the container containing the referenced entry This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>
< A identifier of the container containing the referenced entry When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Reference to the related entry.ch-core-ext-entry-resource-cross-references.entry(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. entry; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueReference:(<ch-core-ext-entry-resource-cross-references.entry.valueReference>
|<Resource>)>?🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-core-ext-entry-resource-cross-references.entry.valueReference(xsd)(doc)=
<#base:Reference>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.; (xsd)reference:string>{0,0}
< The resource type of the referenced entry This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.; (xsd)type:uri>
< A identifier of the referenced entry When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).; (xsd)identifier:Identifier>
< Plain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.; (xsd)display:string>?🔗 Reference to the related documentch-core-ext-entry-resource-cross-references.relationcode(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. relationcode; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueCode:code>🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-gln-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.51.1.3; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A human's name with the ability to identify parts and usage. Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.ch-core-humanname(xsd)(doc)=
<#base:HumanName>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Identifies the purpose for this name. Applications can assume that a name is current unless it explicitly says that it is temporary or old.; (xsd)use:code>?
< Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts. Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.; (xsd)text:string>?
< The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).; (xsd)family:ch-core-humanname.family>?
[]< Given name. If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.; (xsd)given:ch-core-humanname.given>*
[]< Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.; (xsd)prefix:ch-core-humanname.prefix>*
[]< Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.; (xsd)suffix:string>*
< Indicates the period of time when this name was valid for the named person.; (xsd)period:Period>?🔗 The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).ch-core-humanname.family(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< Extension for eCH-0011 - namedatatype; (xsd)ech11name:ch-ext-ech-11-name>?🔗 Given name. If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.ch-core-humanname.given(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
< eCH-0011: Extension to define first name type; (xsd)ech11firstname:ch-ext-ech-11-firstname>?🔗 Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.ch-core-humanname.prefix(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
[]< A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. Used to indicate additional information about the name part and how it should be used.; (xsd)salutationandtitle:iso21090-EN-qualifier>*🔗 Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.ch-core-immunization(xsd)(doc)=
<#base:Immunization>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A unique identifier assigned to this immunization record.; (xsd)identifier:Identifier>*
< Indicates the current status of the immunization event. Will generally be set to show that the immunization has been completed or not done. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
< Indicates the reason the immunization event was not performed. This is generally only used for the status of "not-done". The reason for performing the immunization event is captured in reasonCode, not here.; (xsd)statusReason:CodeableConcept>?
< Vaccine that was administered or was to be administered.; (xsd)vaccineCode:ch-core-immunization.vaccineCode>
< The patient who either received or did not receive the immunization.; (xsd)patient:ch-core-patient*>
< The visit or admission or other contact between patient and health care provider the immunization was performed as part of.; (xsd)encounter:ch-core-encounter*>?
< Date vaccine administered or was to be administered. When immunizations are given a specific date and time should always be known. When immunizations are patient reported, a specific date might not be known. Although partial dates are allowed, an adult patient might not be able to recall the year a childhood immunization was given. An exact date is always preferable, but the use of the String data type is acceptable when an exact date is not known. A small number of vaccines (e.g. live oral typhoid vaccine) are given as a series of patient self-administered dose over a span of time. In cases like this, often, only the first dose (typically a provider supervised dose) is recorded with the occurrence indicating the date/time of the first dose.; (xsd)occurrence:(<dateTime>
|<string>)>
< The date the occurrence of the immunization was first captured in the record - potentially significantly after the occurrence of the event.; (xsd)recorded:dateTime>?
< An indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded. Reflects the “reliability” of the content.; (xsd)primarySource:boolean>?
< The source of the data when the report of the immunization event is not based on information from the person who administered the vaccine. Should not be populated if primarySource = True, not required even if primarySource = False.; (xsd)reportOrigin:CodeableConcept>?
< The service delivery location where the vaccine administration occurred.; (xsd)location:Location*>?
< Name of vaccine manufacturer.; (xsd)manufacturer:Organization*>?
< Lot number of the vaccine product.; (xsd)lotNumber:string>?
< Date vaccine batch expires.; (xsd)expirationDate:date>?
< Body site where vaccine was administered.; (xsd)site:CodeableConcept>?
< The path by which the vaccine product is taken into the body.; (xsd)route:CodeableConcept>?
< The quantity of vaccine product that was administered.; (xsd)doseQuantity:SimpleQuantity>?
[]< Indicates who performed the immunization event.; (xsd)performer:ch-core-immunization.performer>*
[]< Extra information about the immunization that is not conveyed by the other attributes.; (xsd)note:Annotation>*
[]< Reasons why the vaccine was administered.; (xsd)reasonCode:CodeableConcept>*
[]< Condition, Observation or DiagnosticReport that supports why the immunization was administered.; (xsd)reasonReference:(<Condition>
|<DiagnosticReport>
|<Observation>)>*
< Indication if a dose is considered to be subpotent. By default, a dose should be considered to be potent. Typically, the recognition of the dose being sub-potent is retrospective, after the administration (ex. notification of a manufacturer recall after administration). However, in the case of a partial administration (the patient moves unexpectedly and only some of the dose is actually administered), subpotency may be recognized immediately, but it is still important to record the event.; (xsd)isSubpotent:boolean>?
[]< Reason why a dose is considered to be subpotent.; (xsd)subpotentReason:CodeableConcept>*
[]< Educational material presented to the patient (or guardian) at the time of vaccine administration.; (xsd)education:ch-core-immunization.education>*
[]< Indicates a patient's eligibility for a funding program.; (xsd)programEligibility:CodeableConcept>*
< Indicates the source of the vaccine actually administered. This may be different than the patient eligibility (e.g. the patient may be eligible for a publically purchased vaccine but due to inventory issues, vaccine purchased with private funds was actually administered).; (xsd)fundingSource:CodeableConcept>?
[]< Categorical data indicating that an adverse event is associated in time to an immunization. A reaction may be an indication of an allergy or intolerance and, if this is determined to be the case, it should be recorded as a new AllergyIntolerance resource instance as most systems will not query against past Immunization.reaction elements.; (xsd)reaction:ch-core-immunization.reaction>*
[]< The protocol (set of recommendations) being followed by the provider who administered the dose.; (xsd)protocolApplied:ch-core-immunization.protocolApplied>*
< The recorder Reference of the immunization. May be a Practitioner or a Patient; (xsd)recorder:ch-ext-author>?🔗 Educational material presented to the patient (or guardian) at the time of vaccine administration.ch-core-immunization.education(xsd)(doc)=
<#base:Immunization.education>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Identifier of the material presented to the patient.; (xsd)documentType:string>?
< Reference pointer to the educational material given to the patient if the information was on line.; (xsd)reference:uri>?
< Date the educational material was published.; (xsd)publicationDate:dateTime>?
< Date the educational material was given to the patient.; (xsd)presentationDate:dateTime>?🔗 Indicates who performed the immunization event.ch-core-immunization.performer(xsd)(doc)=
<#base:Immunization.performer>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Describes the type of performance (e.g. ordering provider, administering provider, etc.).; (xsd)function:CodeableConcept>?
< The practitioner or organization who performed the action. When the individual practitioner who performed the action is known, it is best to send.; (xsd)actor:(<ch-core-organization>
|<ch-core-practitioner>
|<ch-core-practitionerrole>)>🔗 The protocol (set of recommendations) being followed by the provider who administered the dose.ch-core-immunization.protocolApplied(xsd)(doc)=
<#base:Immunization.protocolApplied>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< One possible path to achieve presumed immunity against a disease - within the context of an authority.; (xsd)series:string>?
< Indicates the authority who published the protocol (e.g. ACIP) that is being followed.; (xsd)authority:Organization*>?
[]< The vaccine preventable disease the dose is being administered against.; (xsd)targetDisease:CodeableConcept>*
< Nominal position in a series. The use of an integer is preferred if known. A string should only be used in cases where an integer is not available (such as when documenting a recurring booster dose).; (xsd)doseNumber:(<positiveInt>
|<string>)>
< The recommended number of doses to achieve immunity. The use of an integer is preferred if known. A string should only be used in cases where an integer is not available (such as when documenting a recurring booster dose).; (xsd)seriesDoses:(<positiveInt>
|<string>)>?🔗 Categorical data indicating that an adverse event is associated in time to an immunization. A reaction may be an indication of an allergy or intolerance and, if this is determined to be the case, it should be recorded as a new AllergyIntolerance resource instance as most systems will not query against past Immunization.reaction elements.ch-core-immunization.reaction(xsd)(doc)=
<#base:Immunization.reaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Date of reaction to the immunization.; (xsd)date:dateTime>?
< Details of the reaction.; (xsd)detail:Observation*>?
< Self-reported indicator.; (xsd)reported:boolean>?🔗 Vaccine that was administered or was to be administered.ch-core-immunization.vaccineCode(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
< Swiss Vaccine Code Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)swissVaccines:Coding>?
< Vaccine Code by SNOMED CT Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)snomedctVaccines:Coding>?🔗 A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification.ch-core-immunization-recommendation(xsd)(doc)=
<#base:ImmunizationRecommendation>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A unique identifier assigned to this particular recommendation record.; (xsd)identifier:Identifier>*
< The patient the recommendation(s) are for.; (xsd)patient:ch-core-patient*>
< The date the immunization recommendation(s) were created.; (xsd)date:dateTime>
< Indicates the authority who published the protocol (e.g. ACIP).; (xsd)authority:ch-core-organization*>?
[]< Vaccine administration recommendations.; (xsd)recommendation:ch-core-immunization-recommendation.recommendation>+🔗 Vaccine administration recommendations.ch-core-immunization-recommendation.recommendation(xsd)(doc)=
<#base:ImmunizationRecommendation.recommendation>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Vaccine(s) or vaccine group that pertain to the recommendation.; (xsd)vaccineCode:CodeableConcept>*
< The targeted disease for the recommendation.; (xsd)targetDisease:CodeableConcept>?
[]< Vaccine(s) which should not be used to fulfill the recommendation.; (xsd)contraindicatedVaccineCode:CodeableConcept>*
< Indicates the patient status with respect to the path to immunity for the target disease.; (xsd)forecastStatus:CodeableConcept>
[]< The reason for the assigned forecast status.; (xsd)forecastReason:CodeableConcept>*
[]< Vaccine date recommendations. For example, earliest date to administer, latest date to administer, etc.; (xsd)dateCriterion:ch-core-immunization-recommendation.recommendation.dateCriterion>*
< Contains the description about the protocol under which the vaccine was administered.; (xsd)description:string>?
< One possible path to achieve presumed immunity against a disease - within the context of an authority.; (xsd)series:string>?
< Nominal position of the recommended dose in a series (e.g. dose 2 is the next recommended dose). The use of an integer is prefered if known. A string should only be used in cases where an interger is not available (such as when documenting a recurring booster dose).; (xsd)doseNumber:(<positiveInt>
|<string>)>?
< The recommended number of doses to achieve immunity. The use of an integer is prefered if known. A string should only be used in cases where an interger is not available (such as when documenting a recurring booster dose).; (xsd)seriesDoses:(<positiveInt>
|<string>)>?
[]< Immunization event history and/or evaluation that supports the status and recommendation.; (xsd)supportingImmunization:(<ch-core-immunization>
|<ImmunizationEvaluation>)>*
[]< Patient Information that supports the status and recommendation. This includes patient observations, adverse reactions and allergy/intolerance information.; (xsd)supportingPatientInformation:Resource*>*🔗 Vaccine date recommendations. For example, earliest date to administer, latest date to administer, etc.ch-core-immunization-recommendation.recommendation.dateCriterion(xsd)(doc)=
<#base:ImmunizationRecommendation.recommendation.dateCriterion>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Date classification of recommendation. For example, earliest date to give, latest date to give, etc.; (xsd)code:CodeableConcept>
< The date whose meaning is specified by dateCriterion.code.; (xsd)value:dateTime>🔗 Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.ch-core-location(xsd)(doc)=
<#base:Location>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Unique code or number identifying the location to its users.; (xsd)identifier:Identifier>*
< The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location.; (xsd)status:code>?
< The operational status covers operation values most relevant to beds (but can also apply to rooms/units/chairs/etc. such as an isolation unit/dialysis chair). This typically covers concepts such as contamination, housekeeping, and other activities like maintenance.; (xsd)operationalStatus:Coding>?
< Name of the location as used by humans. Does not need to be unique. If the name of a location changes, consider putting the old name in the alias column so that it can still be located through searches.; (xsd)name:string>
[]< A list of alternate names that the location 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 location.; (xsd)alias:string>*
< Description of the Location, which helps in finding or referencing the place.; (xsd)description:string>?
< Indicates whether a resource instance represents a specific location or a class of locations. This is labeled as a modifier because whether or not the location is a class of locations changes how it can be used and understood.; (xsd)mode:code>?
[]< Indicates the type of function performed at the location.; (xsd)type:CodeableConcept>*
[]< The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.; (xsd)telecom:ch-core-location.telecom>*
< Physical location. Additional addresses should be recorded using another instance of the Location resource, or via the Organization.; (xsd)address:ch-core-address-ech-10>?
< Physical form of the location, e.g. building, room, vehicle, road.; (xsd)physicalType:CodeableConcept>?
< The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML).; (xsd)position:ch-core-location.position>?
< The organization responsible for the provisioning and upkeep of the location. This can also be used as the part of the organization hierarchy where this location provides services. These services can be defined through the HealthcareService resource.; (xsd)managingOrganization:ch-core-organization*>?
< Another Location of which this Location is physically a part of.; (xsd)partOf:Location*>?
[]< What days/times during a week is this location usually open. This type of information is commonly found published in directories and on websites informing customers when the facility is available.
Specific services within the location may have their own hours which could be shorter (or longer) than the locations hours.; (xsd)hoursOfOperation:ch-core-location.hoursOfOperation>*
< A description of when the locations opening ours are different to normal, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as detailed in the opening hours Times.; (xsd)availabilityExceptions:string>?
[]< Technical endpoints providing access to services operated for the location.; (xsd)endpoint:Endpoint*>*
[]< The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.; (xsd)internet:ch-core-contactpoint-ech-46-internet>*🔗 What days/times during a week is this location usually open. This type of information is commonly found published in directories and on websites informing customers when the facility is available.
Specific services within the location may have their own hours which could be shorter (or longer) than the locations hours.ch-core-location.hoursOfOperation(xsd)(doc)=
<#base:Location.hoursOfOperation>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Indicates which days of the week are available between the start and end Times.; (xsd)daysOfWeek:code>*
< The Location is open all day.; (xsd)allDay:boolean>?
< Time that the Location opens.; (xsd)openingTime:time>?
< Time that the Location closes.; (xsd)closingTime:time>?🔗 The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML).ch-core-location.position(xsd)(doc)=
<#base:Location.position>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Longitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below).; (xsd)longitude:decimal>
< Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below).; (xsd)latitude:decimal>
< Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below).; (xsd)altitude:decimal>?🔗 The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.ch-core-location.telecom(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.ch-core-medication(xsd)(doc)=
<#base:Medication>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this medication. The serial number could be included as an identifier.; (xsd)identifier:Identifier>*
< A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) will have the coding.userSelected set to true. As described in the coding datatype: "A coding may be marked as a "userSelected" if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).; (xsd)code:ch-core-medication.code>?
< A code to indicate if the medication is in active use. This status is intended to identify if the medication in a local system is in active use within a drug database or inventory. For example, a pharmacy system may create a new drug file record for a compounded product "ABC Hospital Special Cream" with an active status. At some point in the future, it may be determined that the drug record was created with an error and the status is changed to "entered in error". This status is not intended to specify if a medication is part of a particular formulary. It is possible that the drug record may be referenced by multiple formularies or catalogues and each of those entries would have a separate status.; (xsd)status:code>?
< Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product.; (xsd)manufacturer:Organization*>?
< Describes the form of the item. Powder; tablets; capsule. When Medication is referenced from MedicationRequest, this is the ordered form. When Medication is referenced within MedicationDispense, this is the dispensed form. When Medication is referenced within MedicationAdministration, this is administered form.; (xsd)form:CodeableConcept>?
< Specific amount of the drug in the packaged product. For example, when specifying a product that has the same strength (For example, Insulin glargine 100 unit per mL solution for injection), this attribute provides additional clarification of the package amount (For example, 3 mL, 10mL, etc.).; (xsd)amount:ch-emed-ratio-with-emed-units>?
[]< Identifies a particular constituent of interest in the product. The ingredients need not be a complete list. If an ingredient is not specified, this does not indicate whether an ingredient is present or absent. If an ingredient is specified it does not mean that all ingredients are specified. It is possible to specify both inactive and active ingredients.; (xsd)ingredient:ch-core-medication.ingredient>*
< Information that only applies to packages (not products).; (xsd)batch:ch-core-medication.batch>?🔗 Information that only applies to packages (not products).ch-core-medication.batch(xsd)(doc)=
<#base:Medication.batch>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The assigned lot number of a batch of the specified product.; (xsd)lotNumber:string>?
< When this specific batch of product will expire.; (xsd)expirationDate:dateTime>?🔗 A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) will have the coding.userSelected set to true. As described in the coding datatype: "A coding may be marked as a "userSelected" if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).ch-core-medication.code(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)GTIN:ch-core-medication.code.GTIN>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)ATC:ch-core-medication.code.ATC>*🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-medication.code.ATC(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. http://www.whocc.no/atc; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-core-medication.code.GTIN(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. urn:oid:2.51.1.1; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 Identifies a particular constituent of interest in the product. The ingredients need not be a complete list. If an ingredient is not specified, this does not indicate whether an ingredient is present or absent. If an ingredient is specified it does not mean that all ingredients are specified. It is possible to specify both inactive and active ingredients.ch-core-medication.ingredient(xsd)(doc)=
<#base:Medication.ingredient>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The actual ingredient - either a substance (simple ingredient) or another medication of a medication.; (xsd)item:(<CodeableConcept>
|<ch-core-medication>
|<Substance>)>
< Indication of whether this ingredient affects the therapeutic action of the drug.; (xsd)isActive:boolean>?
< Specifies how many (or how much) of the items there are in this Medication. For example, 250 mg per tablet. This is expressed as a ratio where the numerator is 250mg and the denominator is 1 tablet.; (xsd)strength:ch-emed-ratio-with-emed-units>?🔗 Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner.ch-core-medicationadministration(xsd)(doc)=
<#base:MedicationAdministration>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifiers associated with this Medication Administration that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.; (xsd)identifier:Identifier>*
[]< A protocol, guideline, orderset, or other definition that was adhered to in whole or in part by this event.; (xsd)instantiates:uri>*
[]< A larger event of which this particular event is a component or step.; (xsd)partOf:(<MedicationAdministration>
|<Procedure>)>*
< Will generally be set to show that the administration has been completed. For some long running administrations such as infusions, it is possible for an administration to be started but not completed or it may be paused while some other process is under way. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
[]< A code indicating why the administration was not performed.; (xsd)statusReason:CodeableConcept>*
< Indicates where the medication is expected to be consumed or administered.; (xsd)category:CodeableConcept>?
< Identifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.; (xsd)medication:(<CodeableConcept>
|<ch-core-medication>)>
< The person or animal or group receiving the medication.; (xsd)subject:(<Group>
|<ch-core-patient>)>
< The visit, admission, or other contact between patient and health care provider during which the medication administration was performed.; (xsd)context:(<Encounter>
|<EpisodeOfCare>)>?
[]< Additional information (for example, patient height and weight) that supports the administration of the medication.; (xsd)supportingInformation:Resource*>*
< A specific date/time or interval of time during which the administration took place (or did not take place, when the 'notGiven' attribute is true). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate.; (xsd)effective:(<dateTime>
|<Period>)>
[]< Indicates who or what performed the medication administration and how they were involved.; (xsd)performer:ch-core-medicationadministration.performer>*
[]< A code indicating why the medication was given.; (xsd)reasonCode:CodeableConcept>*
[]< Condition or observation that supports why the medication was administered. This is a reference to a condition that is the reason for the medication request. If only a code exists, use reasonCode.; (xsd)reasonReference:(<Condition>
|<DiagnosticReport>
|<Observation>)>*
< The original request, instruction or authority to perform the administration. This is a reference to the MedicationRequest where the intent is either order or instance-order. It should not reference MedicationRequests where the intent is any other value.; (xsd)request:MedicationRequest*>?
[]< The device used in administering the medication to the patient. For example, a particular infusion pump.; (xsd)device:Device*>*
[]< Extra information about the medication administration that is not conveyed by the other attributes.; (xsd)note:Annotation>*
< Describes the medication dosage information details e.g. dose, rate, site, route, etc.; (xsd)dosage:ch-core-medicationadministration.dosage>?
[]< A summary of the events of interest that have occurred, such as when the administration was verified. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.; (xsd)eventHistory:Provenance*>*🔗 Describes the medication dosage information details e.g. dose, rate, site, route, etc.ch-core-medicationadministration.dosage(xsd)(doc)=
<#base:MedicationAdministration.dosage>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Free text dosage can be used for cases where the dosage administered is too complex to code. When coded dosage is present, the free text dosage may still be present for display to humans.
The dosage instructions should reflect the dosage of the medication that was administered.; (xsd)text:string>?
< A coded specification of the anatomic site where the medication first entered the body. For example, "left arm". If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.; (xsd)site:CodeableConcept>?
< A code specifying the route or physiological path of administration of a therapeutic agent into or onto the patient. For example, topical, intravenous, etc.; (xsd)route:CodeableConcept>?
< A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. For example, Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequently.; (xsd)method:CodeableConcept>?
< The amount of the medication given at one administration event. Use this value when the administration is essentially an instantaneous event such as a swallowing a tablet or giving an injection. If the administration is not instantaneous (rate is present), this can be specified to convey the total amount administered over period of time of a single administration.; (xsd)dose:ch-core-quantity-with-emed-units>?
< Identifies the speed with which the medication was or will be introduced into the patient. Typically, the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time, e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. If the rate changes over time, and you want to capture this in MedicationAdministration, then each change should be captured as a distinct MedicationAdministration, with a specific MedicationAdministration.dosage.rate, and the date time when the rate change occurred. Typically, the MedicationAdministration.dosage.rate element is not used to convey an average rate.; (xsd)rate:(<ch-core-quantity-with-emed-units>
|<ch-emed-ratio-with-emed-units>)>?🔗 Indicates who or what performed the medication administration and how they were involved.ch-core-medicationadministration.performer(xsd)(doc)=
<#base:MedicationAdministration.performer>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Distinguishes the type of involvement of the performer in the medication administration.; (xsd)function:CodeableConcept>?
< Indicates who or what performed the medication administration.; (xsd)actor:(<Device>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>🔗 Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.ch-core-medicationdispense(xsd)(doc)=
<#base:MedicationDispense>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifiers associated with this Medication Dispense that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.; (xsd)identifier:Identifier>*
[]< The procedure that trigger the dispense.; (xsd)partOf:Procedure*>*
< A code specifying the state of the set of dispense events. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
< Indicates the reason why a dispense was not performed.; (xsd)statusReason:(<CodeableConcept>
|<DetectedIssue>)>?
< Indicates the type of medication dispense (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)). The category can be used to include where the medication is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind.; (xsd)category:CodeableConcept>?
< Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.; (xsd)medication:(<CodeableConcept>
|<ch-core-medication>)>
< A link to a resource representing the person or the group to whom the medication will be given. SubstanceAdministration->subject->Patient.; (xsd)subject:(<Group>
|<ch-core-patient>)>?
< The encounter or episode of care that establishes the context for this event.; (xsd)context:(<Encounter>
|<EpisodeOfCare>)>?
[]< Additional information that supports the medication being dispensed.; (xsd)supportingInformation:Resource*>*
[]< Indicates who or what performed the event.; (xsd)performer:ch-core-medicationdispense.performer>*
< The principal physical location where the dispense was performed.; (xsd)location:Location*>?
[]< Indicates the medication order that is being dispensed against. Maps to basedOn in Event logical model.; (xsd)authorizingPrescription:MedicationRequest*>*
< Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.; (xsd)type:CodeableConcept>?
< The amount of medication that has been dispensed. Includes unit of measure.; (xsd)quantity:SimpleQuantity>?
< The amount of medication expressed as a timing amount.; (xsd)daysSupply:SimpleQuantity>?
< The time when the dispensed product was packaged and reviewed.; (xsd)whenPrepared:dateTime>?
< The time the dispensed product was provided to the patient or their representative.; (xsd)whenHandedOver:dateTime>?
< Identification of the facility/location where the medication was shipped to, as part of the dispense event.; (xsd)destination:Location*>?
[]< Identifies the person who picked up the medication. This will usually be a patient or their caregiver, but some cases exist where it can be a healthcare professional.; (xsd)receiver:(<Patient>
|<Practitioner>)>*
[]< Extra information about the dispense that could not be conveyed in the other attributes.; (xsd)note:Annotation>*
[]< Indicates how the medication is to be used by the patient. When the dose or rate is intended to change over the entire administration period (e.g. Tapering dose prescriptions), multiple instances of dosage instructions will need to be supplied to convey the different doses/rates.
The pharmacist reviews the medication order prior to dispense and updates the dosageInstruction based on the actual product being dispensed.; (xsd)dosageInstruction:ch-core-dosage>*
< Indicates whether or not substitution was made as part of the dispense. In some cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done.; (xsd)substitution:ch-core-medicationdispense.substitution>?
[]< Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. drug-drug interaction, duplicate therapy, dosage alert etc. This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.; (xsd)detectedIssue:DetectedIssue*>*
[]< A summary of the events of interest that have occurred, such as when the dispense was verified. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).; (xsd)eventHistory:Provenance*>*
[]< Optional Extension Element - found in all resources.; (xsd)treatmentReason:ch-emed-ext-treatmentreason>*🔗 Indicates who or what performed the event.ch-core-medicationdispense.performer(xsd)(doc)=
<#base:MedicationDispense.performer>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Distinguishes the type of performer in the dispense. For example, date enterer, packager, final checker.; (xsd)function:CodeableConcept>?
< The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the medication.; (xsd)actor:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>🔗 Indicates whether or not substitution was made as part of the dispense. In some cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done.ch-core-medicationdispense.substitution(xsd)(doc)=
<#base:MedicationDispense.substitution>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< True if the dispenser dispensed a different drug or product from what was prescribed.; (xsd)wasSubstituted:boolean>
< A code signifying whether a different drug was dispensed from what was prescribed.; (xsd)type:CodeableConcept>?
[]< Indicates the reason for the substitution (or lack of substitution) from what was prescribed.; (xsd)reason:CodeableConcept>*
[]< The person or organization that has primary responsibility for the substitution.; (xsd)responsibleParty:(<Practitioner>
|<PractitionerRole>)>*🔗 An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.ch-core-medicationrequest(xsd)(doc)=
<#base:MedicationRequest>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.; (xsd)identifier:Identifier>*
< A code specifying the current state of the order. Generally, this will be active or completed state. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
< Captures the reason for the current state of the MedicationRequest. This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.; (xsd)statusReason:CodeableConcept>?
< Whether the request is a proposal, plan, or an original order. It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.
An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.
This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.; (xsd)intent:code>
[]< Indicates the type of medication request (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)). The category can be used to include where the medication is expected to be consumed or other types of requests.; (xsd)category:CodeableConcept>*
< Indicates how quickly the Medication Request should be addressed with respect to other requests.; (xsd)priority:code>?
< If true indicates that the provider is asking for the medication request not to occur. If do not perform is not specified, the request is a positive request e.g. "do perform".; (xsd)doNotPerform:boolean>?
< Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.; (xsd)reported:(<boolean>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?
< Identifies the medication being requested. This is a link to a resource that represents the medication which may be the details of the medication or simply an attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the Medication resource is recommended. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.; (xsd)medication:(<CodeableConcept>
|<ch-core-medication>)>
< A link to a resource representing the person or set of individuals to whom the medication will be given. The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified.; (xsd)subject:(<Group>
|<ch-core-patient>)>
< The Encounter during which this [x] was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension.; (xsd)encounter:Encounter*>?
[]< Include additional information (for example, patient height and weight) that supports the ordering of the medication.; (xsd)supportingInformation:Resource*>*
< The date (and perhaps time) when the prescription was initially written or authored on.; (xsd)authoredOn:dateTime>?
< The individual, organization, or device that initiated the request and has responsibility for its activation.; (xsd)requester:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
< The specified desired performer of the medication treatment (e.g. the performer of the medication administration).; (xsd)performer:(<CareTeam>
|<Device>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?
< Indicates the type of performer of the administration of the medication. If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available.; (xsd)performerType:CodeableConcept>?
< The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.; (xsd)recorder:(<Practitioner>
|<PractitionerRole>)>?
[]< The reason or the indication for ordering or not ordering the medication. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.; (xsd)reasonCode:CodeableConcept>*
[]< Condition or observation that supports why the medication was ordered. This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode.; (xsd)reasonReference:(<Condition>
|<Observation>)>*
[]< The URL pointing to a protocol, guideline, orderset, or other definition that is adhered to in whole or in part by this MedicationRequest.; (xsd)instantiatesCanonical:canonical>*
[]< The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this MedicationRequest.; (xsd)instantiatesUri:uri>*
[]< A plan or request that is fulfilled in whole or in part by this medication request.; (xsd)basedOn:(<CarePlan>
|<ImmunizationRecommendation>
|<MedicationRequest>
|<ServiceRequest>)>*
< A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition or prescription.; (xsd)groupIdentifier:Identifier>?
< The description of the overall patte3rn of the administration of the medication to the patient. This attribute should not be confused with the protocol of the medication.; (xsd)courseOfTherapyType:CodeableConcept>?
[]< Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.; (xsd)insurance:(<ClaimResponse>
|<Coverage>)>*
[]< Extra information about the prescription that could not be conveyed by the other attributes.; (xsd)note:Annotation>*
[]< Indicates how the medication is to be used by the patient. There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.; (xsd)dosageInstruction:ch-core-dosage>*
< Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.; (xsd)dispenseRequest:ch-core-medicationrequest.dispenseRequest>?
< Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done.; (xsd)substitution:ch-core-medicationrequest.substitution>?
< A link to a resource representing an earlier order related order or prescription.; (xsd)priorPrescription:MedicationRequest*>?
[]< Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, duplicate therapy, dosage alert etc. This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.; (xsd)detectedIssue:DetectedIssue*>*
[]< Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).; (xsd)eventHistory:Provenance*>*🔗 Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.ch-core-medicationrequest.dispenseRequest(xsd)(doc)=
<#base:MedicationRequest.dispenseRequest>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Indicates the quantity or duration for the first dispense of the medication. If populating this element, either the quantity or the duration must be included.; (xsd)initialFill:ch-core-medicationrequest.dispenseRequest.initialFill>?
< The minimum period of time that must occur between dispenses of the medication.; (xsd)dispenseInterval:Duration>?
< This indicates the validity period of a prescription (stale dating the Prescription). It reflects the prescribers' perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.; (xsd)validityPeriod:Period>?
< An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense. If displaying "number of authorized fills", add 1 to this number.; (xsd)numberOfRepeatsAllowed:unsignedInt>?
< The amount that is to be dispensed for one fill.; (xsd)quantity:SimpleQuantity>?
< Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last. In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued, e.g. 90 days supply of medication (based on an ordered dosage). When possible, it is always better to specify quantity, as this tends to be more precise. expectedSupplyDuration will always be an estimate that can be influenced by external factors.; (xsd)expectedSupplyDuration:Duration>?
< Indicates the intended dispensing Organization specified by the prescriber.; (xsd)performer:Organization*>?🔗 Indicates the quantity or duration for the first dispense of the medication. If populating this element, either the quantity or the duration must be included.ch-core-medicationrequest.dispenseRequest.initialFill(xsd)(doc)=
<#base:MedicationRequest.dispenseRequest.initialFill>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The amount or quantity to provide as part of the first dispense.; (xsd)quantity:SimpleQuantity>?
< The length of time that the first dispense is expected to last.; (xsd)duration:Duration>?🔗 Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done.ch-core-medicationrequest.substitution(xsd)(doc)=
<#base:MedicationRequest.substitution>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< True if the prescriber allows a different drug to be dispensed from what was prescribed. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.; (xsd)allowed:(<boolean>
|<CodeableConcept>)>
< Indicates the reason for the substitution, or why substitution must or must not be performed.; (xsd)reason:CodeableConcept>?
< True if the prescriber allows a different drug to be dispensed from what was prescribed. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.; (xsd)allowedCodeableConcept:CodeableConcept>?🔗 A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.
The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered:
MedicationStatement.status + MedicationStatement.wasNotTaken
Status=Active + NotTaken=T = Not currently taking
Status=Completed + NotTaken=T = Not taken in the past
Status=Intended + NotTaken=T = No intention of taking
Status=Active + NotTaken=F = Taking, but not as prescribed
Status=Active + NotTaken=F = Taking
Status=Intended +NotTaken= F = Will be taking (not started)
Status=Completed + NotTaken=F = Taken in past
Status=In Error + NotTaken=N/A = In Error.ch-core-medicationstatement(xsd)(doc)=
<#base:MedicationStatement>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifiers associated with this Medication Statement that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.; (xsd)identifier:Identifier>*
[]< A plan, proposal or order that is fulfilled in whole or in part by this event.; (xsd)basedOn:(<CarePlan>
|<MedicationRequest>
|<ServiceRequest>)>*
[]< A larger event of which this particular event is a component or step.; (xsd)partOf:(<MedicationAdministration>
|<MedicationDispense>
|<MedicationStatement>
|<Observation>
|<Procedure>)>*
< A code representing the patient or other source's judgment about the state of the medication used that this statement is about. Generally, this will be active or completed. MedicationStatement is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for MedicationStatement.status contains codes that assert the status of the use of the medication by the patient (for example, stopped or on hold) as well as codes that assert the status of the medication statement itself (for example, entered in error).
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
[]< Captures the reason for the current state of the MedicationStatement. This is generally only used for "exception" statuses such as "not-taken", "on-hold", "cancelled" or "entered-in-error". The reason for performing the event at all is captured in reasonCode, not here.; (xsd)statusReason:CodeableConcept>*
< Indicates where the medication is expected to be consumed or administered.; (xsd)category:CodeableConcept>?
< Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.; (xsd)medication:(<CodeableConcept>
|<ch-core-medication>)>
< The person, animal or group who is/was taking the medication.; (xsd)subject:(<Group>
|<ch-core-patient>)>
< The encounter or episode of care that establishes the context for this MedicationStatement.; (xsd)context:(<Encounter>
|<EpisodeOfCare>)>?
< The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No). This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the "end" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.; (xsd)effective:(<dateTime>
|<Period>)>?
< The date when the medication statement was asserted by the information source.; (xsd)dateAsserted:dateTime>?
< The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest.; (xsd)informationSource:(<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
[]< Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from.; (xsd)derivedFrom:Resource*>*
[]< A reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference.; (xsd)reasonCode:CodeableConcept>*
[]< Condition or observation that supports why the medication is being/was taken. This is a reference to a condition that is the reason why the medication is being/was taken. If only a code exists, use reasonForUseCode.; (xsd)reasonReference:(<Condition>
|<DiagnosticReport>
|<Observation>)>*
[]< Provides extra information about the medication statement that is not conveyed by the other attributes.; (xsd)note:Annotation>*
[]< Indicates how the medication is/was or should be taken by the patient. The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, "from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily." It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest.; (xsd)dosage:ch-core-dosage>*
< Optional Extension Element - found in all resources.; (xsd)substitution:ch-emed-ext-substitution>?🔗 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.ch-core-organization(xsd)(doc)=
<#base:Organization>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)identifier:Identifier>*
< 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.; (xsd)active:boolean>?
[]< The kind(s) of organization that this is. 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.; (xsd)type:CodeableConcept>*
< 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.; (xsd)name:string>?
[]< 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.; (xsd)alias:string>*
[]< A contact detail for the organization. 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.; (xsd)telecom:ch-core-organization.telecom>*
[]< An address for the organization. Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used.; (xsd)address:ch-core-address>*
< The organization of which this organization forms a part.; (xsd)partOf:Organization*>?
[]< 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.; (xsd)contact:ch-core-organization.contact>*
[]< Technical endpoints providing access to services operated for the organization.; (xsd)endpoint:Endpoint*>*
< See [BER](http://fhir.ch/ig/ch-term/NamingSystem/ber); (xsd)BER:ch-core-ber-identifier>?
< See [UIDB](http://fhir.ch/ig/ch-term/NamingSystem/uidb); (xsd)UIDB:ch-core-uidb-identifier>?
< See [ZSR/RCC](http://fhir.ch/ig/ch-term/NamingSystem/zsr); (xsd)ZSR:ch-core-zsr-identifier>?
< See [GLN](http://fhir.ch/ig/ch-term/NamingSystem/gln); (xsd)GLN:ch-core-gln-identifier>?
[]< A contact detail for the organization. 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.; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail for the organization. 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.; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail for the organization. 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.; (xsd)internet:ch-core-contactpoint-ech-46-internet>*🔗 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.ch-core-organization.contact(xsd)(doc)=
<#base:Organization.contact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Indicates a purpose for which the contact can be reached.; (xsd)purpose:CodeableConcept>?
< A name associated with the contact.; (xsd)name:HumanName>?
[]< A contact detail (e.g. a telephone number or an email address) by which the party may be contacted.; (xsd)telecom:ContactPoint>*
< Visiting or postal addresses for the contact.; (xsd)address:Address>?🔗 A contact detail for the organization. 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.ch-core-organization.telecom(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 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.ch-core-organization-epr(xsd)(doc)=
<#base:ch-core-organization>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)identifier:Identifier>*
< 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.; (xsd)active:boolean>?
[]< The kind(s) of organization that this is. 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.; (xsd)type:CodeableConcept>*
< 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.; (xsd)name:string>?
[]< 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.; (xsd)alias:string>*
[]< A contact detail for the organization. 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.; (xsd)telecom:ch-core-organization-epr.telecom>*
< An address for the organization. Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used.; (xsd)address:ch-core-address>?
< The organization of which this organization forms a part.; (xsd)partOf:Organization*>?
[]< 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.; (xsd)contact:ch-core-organization-epr.contact>*
[]< Technical endpoints providing access to services operated for the organization.; (xsd)endpoint:Endpoint*>*
< See [BER](http://fhir.ch/ig/ch-term/NamingSystem/ber); (xsd)BER:ch-core-ber-identifier>?
< See [UIDB](http://fhir.ch/ig/ch-term/NamingSystem/uidb); (xsd)UIDB:ch-core-uidb-identifier>?
< See [ZSR/RCC](http://fhir.ch/ig/ch-term/NamingSystem/zsr); (xsd)ZSR:ch-core-zsr-identifier>?
< See [GLN](http://fhir.ch/ig/ch-term/NamingSystem/gln); (xsd)GLN:ch-core-gln-identifier>?
[]< A contact detail for the organization. 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.; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail for the organization. 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.; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail for the organization. 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.; (xsd)internet:ch-core-contactpoint-ech-46-internet>*🔗 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.ch-core-organization-epr.contact(xsd)(doc)=
<#base:Organization.contact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Indicates a purpose for which the contact can be reached.; (xsd)purpose:CodeableConcept>?
< A name associated with the contact.; (xsd)name:HumanName>?
[]< A contact detail (e.g. a telephone number or an email address) by which the party may be contacted.; (xsd)telecom:ContactPoint>*
< Visiting or postal addresses for the contact.; (xsd)address:Address>?🔗 A contact detail for the organization. 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.ch-core-organization-epr.telecom(xsd)(doc)=
<#base:ch-core-organization.telecom>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 The CH Core Patient is based upon the core FHIR Patient Resource and designed to meet the applicable patient demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further informationch-core-patient(xsd)(doc)=
<#base:Patient>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier for this patient.; (xsd)identifier:Identifier>*
< Whether this patient record is in active use.
Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules.
It is often used to filter patient lists to exclude inactive patients
Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.; (xsd)active:boolean>?
[]< A name associated with the individual. A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns.; (xsd)name:ch-core-humanname>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)telecom:ch-core-patient.telecom>*
< Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.; (xsd)gender:code>?
< The date of birth for the individual. At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).; (xsd)birthDate:date>?
< Indicates if the individual is deceased or not. If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.; (xsd)deceased:(<boolean>
|<dateTime>)>?
[]< An address for the individual. Patient may have multiple addresses with different uses or applicable periods.; (xsd)address:ch-core-address>*
< This field contains a patient's most recent marital (civil) status.; (xsd)maritalStatus:ch-core-patient.maritalStatus>?
< Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).; (xsd)multipleBirth:(<boolean>
|<integer>)>?
[]< Image of the patient. Guidelines:
* Use id photos, not clinical photos.
* Limit dimensions to thumbnail.
* Keep byte count low to ease resource updates.; (xsd)photo:Attachment>*
[]< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)contact:ch-core-patient.contact>*
[]< A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.; (xsd)communication:ch-core-patient.communication>*
[]< Patient's nominated care provider. This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.
Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.
Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.; (xsd)generalPractitioner:(<Organization>
|<Practitioner>
|<PractitionerRole>)>*
< Organization that is the custodian of the patient record. There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).; (xsd)managingOrganization:Organization*>?
[]< Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.; (xsd)link:ch-core-patient.link>*
< The registered place of birth of the patient.; (xsd)placeOfBirth:ch-core-patient-ech-11-placeofbirth>?
[]< The registered place of origin of the patient.; (xsd)placeOfOrigin:ch-core-patient-ech-11-placeoforigin>*
[]< The content of the country code element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, if the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.; (xsd)citizenship:patient-citizenship>*
< The patient's professed religious affiliations.; (xsd)religion:patient-religion>?
[]< EPR-SPID: The Central Compensation Office (ZAS; CCO) assigns and manages the new patient identification number according to the EPRA (EPR-SPID), which is only linked internally in the CCO with the AHV number. It maintains the UPI identification database (Unique Personal Identifier Database), which the EPR communities may access. The law regulates how the the EPR-SPID can be used. SR 816.111 states (Art. 10 para. 3 EPDV) that communities must ensure that the EPR-SPID number cannot be not stored in document repositories or document registries.; (xsd)EPR-SPID:ch-core-epr-spid-identifier>*
[]< The AHVN13 / NAVS13 - (abbreviation for new thirteen-digit Social Security number) - is an administrative identifier for natural persons in Switzerland. It is issued, announced and administered by the Central Compensation Office. It is available to all organisations and communities for which there is a legal basis.; (xsd)AHVN13:ch-core-ahvn13-identifier>*
[]< An identifier for this patient.; (xsd)LocalPid:ch-core-patient.LocalPid>*
[]< Cardnumber Swiss insurance card v1; (xsd)insuranceCardNumber:ch-core-veka-identifier>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)internet:ch-core-contactpoint-ech-46-internet>*
< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)contactSlice2:ch-core-patient.contactSlice2>?
[]< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)nameOfParent:ch-core-patient.nameOfParent>*
< A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.; (xsd)languageOfCorrespondence:ch-core-patient.languageOfCorrespondence>?🔗 A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.ch-core-patient.communication(xsd)(doc)=
<#base:Patient.communication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)language:CodeableConcept>
< Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). This language is specifically identified for communicating healthcare information.; (xsd)preferred:boolean>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient.contact(xsd)(doc)=
<#base:Patient.contact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>*
< A name associated with the contact person.; (xsd)name:HumanName>?
[]< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>*
< Address for the contact person.; (xsd)address:Address>?
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient.contactSlice2(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>
< A name associated with the contact person.; (xsd)name:HumanName>?
< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>{0,0}
< Address for the contact person.; (xsd)address:ch-core-address-ech-10>
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.ch-core-patient.languageOfCorrespondence(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)language:CodeableConcept>
< Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). This language is specifically identified for communicating healthcare information. value; (xsd)preferred:boolean>🔗 Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.ch-core-patient.link(xsd)(doc)=
<#base:Patient.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The other patient resource that the link refers to. Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual.; (xsd)other:(<Patient>
|<RelatedPerson>)>
< The type of link between this patient resource and another patient resource.; (xsd)type:code>🔗 An identifier for this patient.ch-core-patient.LocalPid(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive.; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 This field contains a patient's most recent marital (civil) status.ch-core-patient.maritalStatus(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
< Extension for eCH-0011 - MaritalData - separation; (xsd)maritalDataSeparation:ch-ext-ech-11-maritaldata-separation>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient.nameOfParent(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>
< A name associated with the contact person.; (xsd)name:HumanName>
[]< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>*
< Address for the contact person.; (xsd)address:Address>?
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).ch-core-patient.telecom(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 The registered place of birth of the patient.ch-core-patient-ech-11-placeofbirth(xsd)(doc)=
<#base:patient-birthPlace>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/patient-birthPlace; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:ch-core-address-ech-11-placeofbirth>🔗 The registered place of origin of the patient.ch-core-patient-ech-11-placeoforigin(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-patient-ech-11-placeoforigin; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueAddress:ch-core-address-ech-11-placeoforigin>?🔗 The CH Core Patient is based upon the core FHIR Patient Resource and designed to meet the applicable patient demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further informationch-core-patient-epr(xsd)(doc)=
<#base:ch-core-patient>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier for this patient.; (xsd)identifier:Identifier>+
< Whether this patient record is in active use.
Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules.
It is often used to filter patient lists to exclude inactive patients
Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.; (xsd)active:boolean>?
[]< A name associated with the individual. A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns.; (xsd)name:ch-core-humanname>+
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)telecom:ch-core-patient-epr.telecom>*
< Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.; (xsd)gender:code>
< The date of birth for the individual. At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).; (xsd)birthDate:date>
< Indicates if the individual is deceased or not. If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.; (xsd)deceased:(<boolean>
|<dateTime>)>?
[]< An address for the individual. Patient may have multiple addresses with different uses or applicable periods.; (xsd)address:ch-core-address>*
< This field contains a patient's most recent marital (civil) status.; (xsd)maritalStatus:ch-core-patient-epr.maritalStatus>?
< Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).; (xsd)multipleBirth:(<boolean>
|<integer>)>?
[]< Image of the patient. Guidelines:
* Use id photos, not clinical photos.
* Limit dimensions to thumbnail.
* Keep byte count low to ease resource updates.; (xsd)photo:Attachment>*
[]< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)contact:ch-core-patient-epr.contact>*
[]< A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.; (xsd)communication:ch-core-patient-epr.communication>*
[]< Patient's nominated care provider. This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.
Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.
Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.; (xsd)generalPractitioner:(<Organization>
|<Practitioner>
|<PractitionerRole>)>*
< Organization that is the custodian of the patient record. There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).; (xsd)managingOrganization:Organization*>?
[]< Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.; (xsd)link:ch-core-patient-epr.link>*
< The registered place of birth of the patient.; (xsd)placeOfBirth:ch-core-patient-ech-11-placeofbirth>?
[]< The registered place of origin of the patient.; (xsd)placeOfOrigin:ch-core-patient-ech-11-placeoforigin>*
[]< The content of the country code element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, if the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.; (xsd)citizenship:patient-citizenship>*
< The patient's professed religious affiliations.; (xsd)religion:patient-religion>?
< EPR-SPID: The Central Compensation Office (ZAS; CCO) assigns and manages the new patient identification number according to the EPRA (EPR-SPID), which is only linked internally in the CCO with the AHV number. It maintains the UPI identification database (Unique Personal Identifier Database), which the EPR communities may access. The law regulates how the the EPR-SPID can be used. SR 816.111 states (Art. 10 para. 3 EPDV) that communities must ensure that the EPR-SPID number cannot be not stored in document repositories or document registries.; (xsd)EPR-SPID:ch-core-epr-spid-identifier>{0,0}
< The AHVN13 / NAVS13 - (abbreviation for new thirteen-digit Social Security number) - is an administrative identifier for natural persons in Switzerland. It is issued, announced and administered by the Central Compensation Office. It is available to all organisations and communities for which there is a legal basis.; (xsd)AHVN13:ch-core-ahvn13-identifier>{0,0}
[]< An identifier for this patient.; (xsd)LocalPid:ch-core-patient-epr.LocalPid>*
[]< Cardnumber Swiss insurance card v1; (xsd)insuranceCardNumber:ch-core-veka-identifier>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).; (xsd)internet:ch-core-contactpoint-ech-46-internet>*
< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)contactSlice2:ch-core-patient-epr.contactSlice2>?
[]< A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.; (xsd)nameOfParent:ch-core-patient-epr.nameOfParent>*
< A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.; (xsd)languageOfCorrespondence:ch-core-patient-epr.languageOfCorrespondence>?🔗 A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.ch-core-patient-epr.communication(xsd)(doc)=
<#base:Patient.communication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)language:CodeableConcept>
< Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). This language is specifically identified for communicating healthcare information.; (xsd)preferred:boolean>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient-epr.contact(xsd)(doc)=
<#base:Patient.contact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>*
< A name associated with the contact person.; (xsd)name:HumanName>?
[]< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>*
< Address for the contact person.; (xsd)address:Address>?
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient-epr.contactSlice2(xsd)(doc)=
<#base:ch-core-patient.contactSlice2>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>
< A name associated with the contact person.; (xsd)name:HumanName>?
< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>{0,0}
< Address for the contact person.; (xsd)address:ch-core-address-ech-10>
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A language which may be used to communicate with the patient about his or her health. If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.ch-core-patient-epr.languageOfCorrespondence(xsd)(doc)=
<#base:ch-core-patient.languageOfCorrespondence>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)language:CodeableConcept>
< Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). This language is specifically identified for communicating healthcare information. value; (xsd)preferred:boolean>🔗 Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.ch-core-patient-epr.link(xsd)(doc)=
<#base:Patient.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The other patient resource that the link refers to. Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual.; (xsd)other:(<Patient>
|<RelatedPerson>)>
< The type of link between this patient resource and another patient resource.; (xsd)type:code>🔗 An identifier for this patient.ch-core-patient-epr.LocalPid(xsd)(doc)=
<#base:ch-core-patient.LocalPid>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive.; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 This field contains a patient's most recent marital (civil) status.ch-core-patient-epr.maritalStatus(xsd)(doc)=
<#base:ch-core-patient.maritalStatus>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?
< Extension for eCH-0011 - MaritalData - separation; (xsd)maritalDataSeparation:ch-ext-ech-11-maritaldata-separation>?🔗 A contact party (e.g. guardian, partner, friend) for the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.ch-core-patient-epr.nameOfParent(xsd)(doc)=
<#base:ch-core-patient.nameOfParent>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The nature of the relationship between the patient and the contact person.; (xsd)relationship:CodeableConcept>
< A name associated with the contact person.; (xsd)name:HumanName>
[]< A contact detail for the person, e.g. a telephone number or an email address. Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.; (xsd)telecom:ContactPoint>*
< Address for the contact person.; (xsd)address:Address>?
< Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< Organization on behalf of which the contact is acting or for which the contact is working.; (xsd)organization:Organization*>?
< The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>?🔗 A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).ch-core-patient-epr.telecom(xsd)(doc)=
<#base:ch-core-patient.telecom>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 The CH Core Practitioner is based upon the core FHIR Practitioner Resource and designed to meet the applicable practitioner demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further informationch-core-practitioner(xsd)(doc)=
<#base:Practitioner>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier that applies to this person in this role.; (xsd)identifier:Identifier>*
< Whether this practitioner's record is in active use. If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.; (xsd)active:boolean>?
[]< The name(s) associated with the practitioner. The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate.
In general, select the value to be used in the ResourceReference.display based on this:
1. There is more than 1 name
2. Use = usual
3. Period is current to the date of the usage
4. Use = official
5. Other order as decided by internal business rules.; (xsd)name:ch-core-humanname>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)telecom:ch-core-practitioner.telecom>*
[]< Address(es) of the practitioner that are not role specific (typically home address).
Work addresses are not typically entered in this property as they are usually role dependent. The PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address).; (xsd)address:ch-core-address>*
< Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< The date of birth for the practitioner.; (xsd)birthDate:date>?
[]< Image of the person.; (xsd)photo:Attachment>*
[]< The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.; (xsd)qualification:ch-core-practitioner.qualification>*
[]< A language the practitioner can use in patient communication. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)communication:CodeableConcept>*
< See [GLN](http://fhir.ch/ig/ch-term/NamingSystem/gln); (xsd)GLN:ch-core-gln-identifier>?
[]< The [ZSR/RCC](http://fhir.ch/ig/ch-term/NamingSystem/zsr) number is issued to self-employed, natural or legal persons (organisations) who can and want to work at the expense of health insurance.; (xsd)ZSR:ch-core-zsr-identifier>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)internet:ch-core-contactpoint-ech-46-internet>*🔗 The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.ch-core-practitioner.qualification(xsd)(doc)=
<#base:Practitioner.qualification>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier that applies to this person's qualification in this role.; (xsd)identifier:Identifier>*
< Coded representation of the qualification.; (xsd)code:CodeableConcept>
< Period during which the qualification is valid.; (xsd)period:Period>?
< Organization that regulates and issues the qualification.; (xsd)issuer:Organization*>?🔗 A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.ch-core-practitioner.telecom(xsd)(doc)=
<#base:ContactPoint>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 The CH Core Practitioner is based upon the core FHIR Practitioner Resource and designed to meet the applicable practitioner demographic data elements in Switzerland. See also https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html for further informationch-core-practitioner-epr(xsd)(doc)=
<#base:ch-core-practitioner>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier that applies to this person in this role.; (xsd)identifier:Identifier>+
< Whether this practitioner's record is in active use. If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.; (xsd)active:boolean>?
[]< The name(s) associated with the practitioner. The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate.
In general, select the value to be used in the ResourceReference.display based on this:
1. There is more than 1 name
2. Use = usual
3. Period is current to the date of the usage
4. Use = official
5. Other order as decided by internal business rules.; (xsd)name:ch-core-humanname>+
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)telecom:ch-core-practitioner-epr.telecom>*
[]< Address(es) of the practitioner that are not role specific (typically home address).
Work addresses are not typically entered in this property as they are usually role dependent. The PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address).; (xsd)address:ch-core-address>*
< Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.; (xsd)gender:code>?
< The date of birth for the practitioner.; (xsd)birthDate:date>?
[]< Image of the person.; (xsd)photo:Attachment>*
[]< The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.; (xsd)qualification:ch-core-practitioner-epr.qualification>*
[]< A language the practitioner can use in patient communication. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.; (xsd)communication:CodeableConcept>*
< See [GLN](http://fhir.ch/ig/ch-term/NamingSystem/gln); (xsd)GLN:ch-core-gln-identifier>
[]< The [ZSR/RCC](http://fhir.ch/ig/ch-term/NamingSystem/zsr) number is issued to self-employed, natural or legal persons (organisations) who can and want to work at the expense of health insurance.; (xsd)ZSR:ch-core-zsr-identifier>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)email:ch-core-contactpoint-ech-46-email>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)phone:ch-core-contactpoint-ech-46-phone>*
[]< A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.; (xsd)internet:ch-core-contactpoint-ech-46-internet>*🔗 The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.ch-core-practitioner-epr.qualification(xsd)(doc)=
<#base:Practitioner.qualification>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< An identifier that applies to this person's qualification in this role.; (xsd)identifier:Identifier>*
< Coded representation of the qualification.; (xsd)code:CodeableConcept>
< Period during which the qualification is valid.; (xsd)period:Period>?
< Organization that regulates and issues the qualification.; (xsd)issuer:Organization*>?🔗 A contact detail for the practitioner, e.g. a telephone number or an email address. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.ch-core-practitioner-epr.telecom(xsd)(doc)=
<#base:ch-core-practitioner.telecom>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Telecommunications form for contact point - what communications system is required to make use of the contact.; (xsd)system:code>
< 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.; (xsd)value:string>
< 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.; (xsd)use:code>?
< 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.; (xsd)rank:positiveInt>?
< Time period when the contact point was/is in use.; (xsd)period:Period>?🔗 A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.ch-core-practitionerrole(xsd)(doc)=
<#base:PractitionerRole>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business Identifiers that are specific to a role/location.; (xsd)identifier:Identifier>*
< Whether this practitioner role 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.; (xsd)active:boolean>?
< The period during which the person is authorized to act as a practitioner in these role(s) for the organization.; (xsd)period:Period>?
< Practitioner that is able to provide the defined services for the organization.; (xsd)practitioner:ch-core-practitioner*>?
< The organization where the Practitioner performs the roles associated.; (xsd)organization:ch-core-organization*>?
[]< Roles which this practitioner is authorized to perform for the organization. A person may have more than one role.; (xsd)code:CodeableConcept>*
[]< Specific specialty of the practitioner.; (xsd)specialty:CodeableConcept>*
[]< The location(s) at which this practitioner provides care.; (xsd)location:ch-core-location*>*
[]< The list of healthcare services that this worker provides for this role's Organization/Location(s).; (xsd)healthcareService:HealthcareService*>*
[]< Contact details that are specific to the role/location/service.; (xsd)telecom:ContactPoint>*
[]< A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. More detailed availability information may be provided in associated Schedule/Slot resources.; (xsd)availableTime:ch-core-practitionerrole.availableTime>*
[]< The practitioner is not available or performing this role during this period of time due to the provided reason.; (xsd)notAvailable:ch-core-practitionerrole.notAvailable>*
< A description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times.; (xsd)availabilityExceptions:string>?
[]< Technical endpoints providing access to services operated for the practitioner with this role.; (xsd)endpoint:Endpoint*>*🔗 A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. More detailed availability information may be provided in associated Schedule/Slot resources.ch-core-practitionerrole.availableTime(xsd)(doc)=
<#base:PractitionerRole.availableTime>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Indicates which days of the week are available between the start and end Times.; (xsd)daysOfWeek:code>*
< Is this always available? (hence times are irrelevant) e.g. 24 hour service.; (xsd)allDay:boolean>?
< The opening time of day. Note: If the AllDay flag is set, then this time is ignored. The timezone is expected to be for where this HealthcareService is provided at.; (xsd)availableStartTime:time>?
< The closing time of day. Note: If the AllDay flag is set, then this time is ignored. The timezone is expected to be for where this HealthcareService is provided at.; (xsd)availableEndTime:time>?🔗 The practitioner is not available or performing this role during this period of time due to the provided reason.ch-core-practitionerrole.notAvailable(xsd)(doc)=
<#base:PractitionerRole.notAvailable>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The reason that can be presented to the user as to why this time is not available.; (xsd)description:string>
< Service is not available (seasonally or for a public holiday) from this date.; (xsd)during:Period>?🔗 A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.ch-core-practitionerrole-epr(xsd)(doc)=
<#base:ch-core-practitionerrole>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business Identifiers that are specific to a role/location.; (xsd)identifier:Identifier>*
< Whether this practitioner role 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.; (xsd)active:boolean>?
< The period during which the person is authorized to act as a practitioner in these role(s) for the organization.; (xsd)period:Period>?
< Practitioner that is able to provide the defined services for the organization.; (xsd)practitioner:ch-core-practitioner-epr*>?
< The organization where the Practitioner performs the roles associated.; (xsd)organization:ch-core-organization-epr*>?
[]< Roles which this practitioner is authorized to perform for the organization. A person may have more than one role.; (xsd)code:CodeableConcept>*
[]< Specific specialty of the practitioner.; (xsd)specialty:CodeableConcept>*
[]< The location(s) at which this practitioner provides care.; (xsd)location:ch-core-location*>*
[]< The list of healthcare services that this worker provides for this role's Organization/Location(s).; (xsd)healthcareService:HealthcareService*>*
[]< Contact details that are specific to the role/location/service.; (xsd)telecom:ContactPoint>*
[]< A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. More detailed availability information may be provided in associated Schedule/Slot resources.; (xsd)availableTime:ch-core-practitionerrole-epr.availableTime>*
[]< The practitioner is not available or performing this role during this period of time due to the provided reason.; (xsd)notAvailable:ch-core-practitionerrole-epr.notAvailable>*
< A description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times.; (xsd)availabilityExceptions:string>?
[]< Technical endpoints providing access to services operated for the practitioner with this role.; (xsd)endpoint:Endpoint*>*🔗 A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. More detailed availability information may be provided in associated Schedule/Slot resources.ch-core-practitionerrole-epr.availableTime(xsd)(doc)=
<#base:PractitionerRole.availableTime>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Indicates which days of the week are available between the start and end Times.; (xsd)daysOfWeek:code>*
< Is this always available? (hence times are irrelevant) e.g. 24 hour service.; (xsd)allDay:boolean>?
< The opening time of day. Note: If the AllDay flag is set, then this time is ignored. The timezone is expected to be for where this HealthcareService is provided at.; (xsd)availableStartTime:time>?
< The closing time of day. Note: If the AllDay flag is set, then this time is ignored. The timezone is expected to be for where this HealthcareService is provided at.; (xsd)availableEndTime:time>?🔗 The practitioner is not available or performing this role during this period of time due to the provided reason.ch-core-practitionerrole-epr.notAvailable(xsd)(doc)=
<#base:PractitionerRole.notAvailable>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The reason that can be presented to the user as to why this time is not available.; (xsd)description:string>
< Service is not available (seasonally or for a public holiday) from this date.; (xsd)during:Period>?🔗 The comparator is not used on a SimpleQuantity The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.ch-core-quantity-with-emed-units(xsd)(doc)=
<#base:SimpleQuantity>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The value of the measured amount. The value includes an implicit precision in the presentation of the value. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).; (xsd)value:decimal>
< Not allowed to be used in this context; (xsd)comparator:code>{0,0}
< A human-readable form of the unit.; (xsd)unit:string>
< The identification of the system that provides the coded form of the unit.; (xsd)system:uri>
< A computer processable form of the unit in some unit representation system. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.; (xsd)code>🔗 A set of ordered Quantities defined by a low and high limit. The stated low and high value are assumed to have arbitrarily high precision when it comes to determining which values are in the range. I.e. 1.99 is not in the range 2 -> 3.ch-core-range-with-emed-units(xsd)(doc)=
<#base:Range>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The low limit. The boundary is inclusive. If the low element is missing, the low boundary is not known.; (xsd)low:ch-core-quantity-with-emed-units>?
< The high limit. The boundary is inclusive. If the high element is missing, the high boundary is not known.; (xsd)high:ch-core-quantity-with-emed-units>?🔗 A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.ch-core-servicerequest(xsd)(doc)=
<#base:ServiceRequest>
< 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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.; (xsd)implicitRules:uri>?
< 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).; (xsd)language:code>?
< 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.; (xsd)text:Narrative>?
[]< 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.; (xsd)contained:Resource>*
[]< 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.; (xsd)identifier:Identifier>*
[]< The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Note: This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; (xsd)instantiatesCanonical:canonical>*
[]< The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.; (xsd)instantiatesUri:uri>*
[]< Plan/proposal/order fulfilled by this request.; (xsd)basedOn:(<CarePlan>
|<ch-core-medicationrequest>
|<ch-core-servicerequest>)>*
[]< The request takes the place of the referenced completed or terminated request(s).; (xsd)replaces:ServiceRequest*>*
< A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; (xsd)requisition:Identifier>?
< The status of the order. The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](http://hl7.org/fhir/R4/event.html) for general discussion) or using the [Task](http://hl7.org/fhir/R4/task.html) resource.; (xsd)status:code>
< Whether the request is a proposal, plan, an original order or a reflex order. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.; (xsd)intent:code>
[]< A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.; (xsd)category:CodeableConcept>*
< Indicates how quickly the ServiceRequest should be addressed with respect to other requests.; (xsd)priority:code>?
< Set this to true if the record is saying that the service/procedure should NOT be performed. In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.; (xsd)doNotPerform:boolean>?
< A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.; (xsd)code:CodeableConcept>?
[]< Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. For information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element.; (xsd)orderDetail:CodeableConcept>*
< An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction).; (xsd)quantity:(<Quantity>
|<Range>
|<Ratio>)>?
< On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).; (xsd)subject:(<Device>
|<Group>
|<ch-core-location>
|<ch-core-patient>)>
< An encounter that provides additional information about the healthcare context in which this request is made.; (xsd)encounter:ch-core-encounter*>?
< The date/time at which the requested service should occur.; (xsd)occurrence:(<dateTime>
|<Period>
|<Timing>)>?
< If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc.; (xsd)asNeeded:(<boolean>
|<CodeableConcept>)>?
< When the request transitioned to being actionable.; (xsd)authoredOn:dateTime>?
< The individual who initiated the request and has responsibility for its activation. This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.; (xsd)requester:(<Device>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>?
< Desired type of performer for doing the requested service. This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.; (xsd)performerType:CodeableConcept>?
[]< The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order. If order of preference is needed use the [request-performerOrder extension](http://hl7.org/fhir/R4/extension-request-performerorder.html). Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).; (xsd)performer:(<CareTeam>
|<Device>
|<HealthcareService>
|<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<ch-core-practitionerrole>
|<RelatedPerson>)>*
[]< The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center.; (xsd)locationCode:CodeableConcept>*
[]< A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center.; (xsd)locationReference:Location*>*
[]< An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).; (xsd)reasonCode:CodeableConcept>*
[]< Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in `supportingInfo`. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise when referencing *DiagnosticReport* it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).; (xsd)reasonReference:(<DiagnosticReport>
|<ch-core-condition>
|<ch-core-documentreference>
|<Observation>)>*
[]< Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service.; (xsd)insurance:(<ClaimResponse>
|<ch-core-coverage>)>*
[]< Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. To represent information about how the services are to be delivered use the `instructions` element.; (xsd)supportingInfo:Resource*>*
[]< One or more specimens that the laboratory procedure will use. Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](http://hl7.org/fhir/R4/specimen.html) resource points to the ServiceRequest.; (xsd)specimen:Specimen*>*
[]< Anatomic location where the procedure should be performed. This is the target site. Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension [procedure-targetBodyStructure](http://hl7.org/fhir/R4/extension-procedure-targetbodystructure.html).; (xsd)bodySite:CodeableConcept>*
[]< Any other notes and comments made about the service request. For example, internal billing notes.; (xsd)note:Annotation>*
< Instructions in terms that are understood by the patient or consumer.; (xsd)patientInstruction:string>?
[]< Key events in the history of the request. This might not include provenances for all versions of the request – only those deemed “relevant” or important.
This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude
All Provenances should have some historical version of this Request as their subject.; (xsd)relevantHistory:Provenance*>*🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-uidb-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.35; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-veka-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.30.1.123.100.1.1.1; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:ch-core-veka-identifier.period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 Time period during which identifier is/was valid for use.ch-core-veka-identifier.period(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.ch-core-zsr-identifier(xsd)(doc)=
<#base:Identifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The purpose of this identifier. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.; (xsd)use:code>?
< A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.; (xsd)type:CodeableConcept>?
< Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Identifier.system is always case sensitive. urn:oid:2.16.756.5.30.1.123.100.2.1.1; (xsd)system:uri>
< The portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.; (xsd)value:string>
< Time period during which identifier is/was valid for use.; (xsd)period:Period>?
< Organization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.; (xsd)assigner:Organization*>?🔗 A relationship of two Quantity values - expressed as a numerator and a denominator. The Ratio datatype should only be used to express a relationship of two numbers if the relationship cannot be suitably expressed using a Quantity and a common unit. Where the denominator value is known to be fixed to "1", Quantity should be used instead of Ratio.ch-emed-ratio-with-emed-units(xsd)(doc)=
<#base:Ratio>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The value of the numerator.; (xsd)numerator:ch-core-quantity-with-emed-units>
< The value of the denominator.; (xsd)denominator:ch-core-quantity-with-emed-units>🔗 Extension to define an encounter is caused by an accident and at which time the accident happenedch-ext-accident(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-accident; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>){0,0}
< An Extension; (xsd)tag:ch-ext-accident.tag>?
< An Extension; (xsd)dateTime:ch-ext-accident.dateTime>?🔗 An Extensionch-ext-accident.dateTime(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. dateTime; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:dateTime>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueDateTime:dateTime>🔗 An Extensionch-ext-accident.tag(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. tag; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueBoolean:boolean>🔗 Optional Extension Element - found in all resources.ch-ext-author(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-author; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Resource*>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueReference:(<ch-core-patient>
|<ch-core-practitionerrole>
|<RelatedPerson>)>🔗 Optional Extension Element - found in all resources.ch-ext-bfs-ms-admitrole(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-bfs-ms-admitrole; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).; (xsd)valueCoding:Coding>?🔗 Optional Extension Element - found in all resources.ch-ext-bfs-ms-dischargedecision(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-bfs-ms-dischargedecision; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).; (xsd)valueCoding:Coding>?🔗 Optional Extension Element - found in all resources.ch-ext-bfs-ms-dischargedestination(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-bfs-ms-dischargedestination; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).; (xsd)valueCoding:Coding>?🔗 Optional Extension Element - found in all resources.ch-ext-biller(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-biller; (xsd)url:string>
(<valueCh-core-organization:ch-core-organization>
|<valueCh-core-practitioner:ch-core-practitioner>
|<valueCh-core-practitionerrole:ch-core-practitionerrole>)🔗 eCH-0010: Extension to define line types for an addressch-ext-ech-10-linetype(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-10-linetype; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).; (xsd)valueCode:code>?🔗 eCH-0011: Extension to define first name typech-ext-ech-11-firstname(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-11-firstname; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).; (xsd)valueCode:code>?🔗 Extension for eCH-0011 - MaritalData - separationch-ext-ech-11-maritaldata-separation(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-11-maritaldata-separation; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< CodeableConcept for separation type; (xsd)valueCodeableConcept:CodeableConcept>?🔗 Extension for eCH-0011 - namedatatypech-ext-ech-11-name(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-11-name; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).; (xsd)valueCode:code>?🔗 Optional Extension Element - found in all resources.ch-ext-ech-46-emailcategory(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-46-emailcategory; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:CodeableConcept>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueCodeableConcept:ch-ext-ech-46-emailcategory.valueCodeableConcept>🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-ext-ech-46-emailcategory.valueCodeableConcept(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?🔗 Optional Extension Element - found in all resources.ch-ext-ech-46-internetcategory(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-46-internetcategory; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:CodeableConcept>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueCodeableConcept:ch-ext-ech-46-internetcategory.valueCodeableConcept>🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-ext-ech-46-internetcategory.valueCodeableConcept(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?🔗 Optional Extension Element - found in all resources.ch-ext-ech-46-phonecategory(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-46-phonecategory; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:CodeableConcept>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueCodeableConcept:ch-ext-ech-46-phonecategory.valueCodeableConcept>🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-ext-ech-46-phonecategory.valueCodeableConcept(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:Coding>*
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?🔗 Extension for eCH-0011 - bfs number (ministry of statistics number)ch-ext-ech-7-municipalityid(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-ech-7-municipalityid; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< BFS number; (xsd)valueString:string>?🔗 Optional Extension Element - found in all resources.ch-ext-encounter-susp-readmission(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-encounter-susp-readmission; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>)?
< True if it is a suspected readmission, false otherwise; (xsd)valueBoolean:boolean>?🔗 Extension to define the confidentiality code of the documentch-ext-epr-confidentialitycode(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-epr-confidentialitycode; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:CodeableConcept>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueCodeableConcept:ch-ext-epr-confidentialitycode.valueCodeableConcept>🔗 Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).ch-ext-epr-confidentialitycode.valueCodeableConcept(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:ch-ext-epr-confidentialitycode.valueCodeableConcept.coding>
< A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?🔗 A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.ch-ext-epr-confidentialitycode.valueCodeableConcept.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
< A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?🔗 Extension to define the information about the person and organization that entered data and the time of the data inputch-ext-epr-dataenterer(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>+
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-epr-dataenterer; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCanonical:canonical>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueContributor:Contributor>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>){0,0}
< An Extension; (xsd)enterer:ch-ext-epr-dataenterer.enterer>
< Extension to define the timestamp of the authorship/data input; (xsd)timestamp:ch-ext-epr-time>?🔗 An Extensionch-ext-epr-dataenterer.enterer(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. enterer; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Resource*>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueReference:ch-core-practitionerrole*>🔗 Extension to define the information about the recipientch-ext-epr-informationrecipient(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-epr-informationrecipient; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Resource*>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueReference:(<ch-core-organization>
|<ch-core-patient>
|<ch-core-practitioner>
|<RelatedPerson>)>🔗 Extension to define the timestamp of the authorship/data inputch-ext-epr-time(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-epr-time; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:dateTime>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)valueDateTime:dateTime>🔗 Optional Extension Element - found in all resources.ch-ext-responsible(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://fhir.ch/ig/ch-core/StructureDefinition/ch-ext-responsible; (xsd)url:string>
(<valueCh-core-organization:ch-core-organization>
|<valueCh-core-practitioner:ch-core-practitioner>
|<valueCh-core-practitionerrole:ch-core-practitionerrole>)