π This extension allows the entry of an address point according to the RΓIAN registry.address-point-cz(xsd)= <#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. https://hl7.cz/fhir/core/StructureDefinition/address-point-cz; (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:address-point-cz.value[x]>? π 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).address-point-cz.value[x](xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/ruian; (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*>? π Address according to Czech postal conventions. The address can be used both for delivering mail and for locating locations that do not have a valid mailing address. The use of extensions is not mandatory. 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](location.html#) resource).cz-address(xsd)= <#base:Address-eu> < Unique 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>* < Address use 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:cz-address.line>* < The name of the city, town, suburb, village or other community or delivery center.; (xsd)city:string>? < 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:cz-address.country>? < Time period when address was/is in use.; (xsd)period:Period>? < If both the RUIAN code and the address are given, both must match.; (xsd)addressPoint:address-point-cz>? < This extension allows to specify whether or not the address is an official address (permanent address) or to indicate that it is the official address for that country.; (xsd)permanentResidence:permanent-residencer-address-cz>? π 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.cz-address.country(xsd)= <#base:Address-eu.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>? π Provides a coded expression for the content represented in a string.cz-address.country.countryCode(xsd)= <#base:Address-eu.country.countryCode> < Unique 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/iso21090-SC-coding; (xsd)url:string> < Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/extensibility.html) for a list).; (xsd)value:Coding> π This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.cz-address.line(xsd)= <#base:Address-eu.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>? []< 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>* []< A numbered box located in a post station.; (xsd)postBox:iso21090-ADXP-postBox>* π 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.cz-device-observer(xsd)= <#base:Device> < 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 instance identifiers assigned to a device by manufacturers other organizations or owners. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.; (xsd)identifier:Identifier>* < The reference to the definition for the device.; (xsd)definition:DeviceDefinition*>? []< Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](http://hl7.org/fhir/R4/device-mappings.html#udi) for a complete mapping of UDI parts to Device.; (xsd)udiCarrier:cz-device-observer.udiCarrier>* < Status of the Device availability. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.; (xsd)status:code>? []< Reason for the dtatus of the Device availability.; (xsd)statusReason:CodeableConcept>* < The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product. For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFRΒ§1271.290(c)*.; (xsd)distinctIdentifier:string>? < A name of the manufacturer.; (xsd)manufacturer:string>? < The date and time when the device was manufactured.; (xsd)manufactureDate:dateTime>? < The date and time beyond which this device is no longer valid or should not be used (if applicable).; (xsd)expirationDate:dateTime>? < Lot number assigned by the manufacturer.; (xsd)lotNumber:string>? < The serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20.; (xsd)serialNumber:string>? []< This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.; (xsd)deviceName:cz-device-observer.deviceName>* < The model number for the device.; (xsd)modelNumber:string>? < The part number of the device. Alphanumeric Maximum 20.; (xsd)partNumber:string>? < The kind or type of device.; (xsd)type:CodeableConcept>? []< The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.; (xsd)specialization:cz-device-observer.specialization>* []< The actual design of the device or software version running on the device.; (xsd)version:cz-device-observer.version>* []< The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.; (xsd)property:cz-device-observer.property>* < Patient information, If the device is affixed to a person.; (xsd)patient:cz-patient-core*>? < An organization that is responsible for the provision and ongoing maintenance of the device.; (xsd)owner:Organization*>? []< Contact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.; (xsd)contact:ContactPoint>* < The place where the device can be found.; (xsd)location:Location*>? < A network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.; (xsd)url:uri>? []< Descriptive information, usage information or implantation information that is not captured in an existing element.; (xsd)note:Annotation>* []< Provides additional safety characteristics about a medical device. For example devices containing latex.; (xsd)safety:CodeableConcept>* < The parent device.; (xsd)parent:Device*>? π This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.cz-device-observer.deviceName(xsd)= <#base:Device.deviceName> < Unique 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 name of the device.; (xsd)name:string> < The type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName.; (xsd)type:code> π The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.cz-device-observer.property(xsd)= <#base:Device.property> < Unique 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>* < Code that specifies the property DeviceDefinitionPropetyCode (Extensible).; (xsd)type:CodeableConcept> []< Property value as a quantity.; (xsd)valueQuantity:Quantity>* []< Property value as a code, e.g., NTP4 (synced to NTP).; (xsd)valueCode:CodeableConcept>* π The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.cz-device-observer.specialization(xsd)= <#base:Device.specialization> < Unique 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 standard that is used to operate and communicate.; (xsd)systemType:CodeableConcept> < The version of the standard that is used to operate and communicate.; (xsd)version:string>? π Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](http://hl7.org/fhir/R4/device-mappings.html#udi) for a complete mapping of UDI parts to Device.cz-device-observer.udiCarrier(xsd)= <#base:Device.udiCarrier> < Unique 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 device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.; (xsd)deviceIdentifier:string>? < Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, 3) ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di, 4) ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di.; (xsd)issuer:uri>? < The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi.; (xsd)jurisdiction:uri>? < The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.; (xsd)carrierAIDC:base64Binary>? < The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.; (xsd)carrierHRF:string>? < A coded entry to indicate how the data was entered.; (xsd)entryType:code>? π The actual design of the device or software version running on the device.cz-device-observer.version(xsd)= <#base:Device.version> < Unique 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 the device version.; (xsd)type:CodeableConcept>? < A single component of the device version.; (xsd)component:Identifier>? < The version text.; (xsd)value:string> π Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.cz-location-base(xsd)= <#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:ContactPoint>* < Physical location. Additional addresses should be recorded using another instance of the Location resource, or via the Organization.; (xsd)address:cz-address>? < 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:cz-location-base.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:cz-organization-base*>? < 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:cz-location-base.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*>* π 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.cz-location-base.hoursOfOperation(xsd)= <#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).cz-location-base.position(xsd)= <#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>? π Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.cz-location-core(xsd)= <#base:cz-location-base> < 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:ContactPoint>* < Physical location. Additional addresses should be recorded using another instance of the Location resource, or via the Organization.; (xsd)address:cz-address>? < 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:cz-location-core.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:cz-organization-core*>? < 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:cz-location-core.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*>* π 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.cz-location-core.hoursOfOperation(xsd)= <#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).cz-location-core.position(xsd)= <#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>? π 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. This profile applies the rules defined by NCEZ for representing the UDI in the FHIR standard, by the document "HL7 IG: UDI Pattern R2"cz-medical-device(xsd)= <#base:Device> < 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 instance identifiers assigned to a device by manufacturers other organizations or owners. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.; (xsd)identifier:Identifier>* < The reference to the definition for the device.; (xsd)definition:DeviceDefinition*>? []< Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](http://hl7.org/fhir/R4/device-mappings.html#udi) for a complete mapping of UDI parts to Device.; (xsd)udiCarrier:cz-medical-device.udiCarrier>* < Status of the Device availability. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.; (xsd)status:code>? []< Reason for the dtatus of the Device availability.; (xsd)statusReason:CodeableConcept>* < The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product. For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFRΒ§1271.290(c)*.; (xsd)distinctIdentifier:string>? < A name of the manufacturer.; (xsd)manufacturer:string>? < The date and time when the device was manufactured.; (xsd)manufactureDate:dateTime>? < The date and time beyond which this device is no longer valid or should not be used (if applicable).; (xsd)expirationDate:dateTime>? < Lot number assigned by the manufacturer.; (xsd)lotNumber:string>? < The serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20.; (xsd)serialNumber:string>? []< This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.; (xsd)deviceName:cz-medical-device.deviceName>* < The model number for the device.; (xsd)modelNumber:string>? < The part number of the device. Alphanumeric Maximum 20.; (xsd)partNumber:string>? < The kind or type of device.; (xsd)type:CodeableConcept>? []< The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.; (xsd)specialization:cz-medical-device.specialization>* []< The actual design of the device or software version running on the device.; (xsd)version:cz-medical-device.version>* []< The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.; (xsd)property:cz-medical-device.property>* < Patient information, If the device is affixed to a person.; (xsd)patient:cz-patient-core*> < An organization that is responsible for the provision and ongoing maintenance of the device.; (xsd)owner:Organization*>? []< Contact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.; (xsd)contact:ContactPoint>* < The place where the device can be found.; (xsd)location:Location*>? < A network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.; (xsd)url:uri>? []< Descriptive information, usage information or implantation information that is not captured in an existing element.; (xsd)note:Annotation>* []< Provides additional safety characteristics about a medical device. For example devices containing latex.; (xsd)safety:CodeableConcept>* < The parent device.; (xsd)parent:Device*>? π This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.cz-medical-device.deviceName(xsd)= <#base:Device.deviceName> < Unique 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 name of the device.; (xsd)name:string> < The type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName.; (xsd)type:code> π Patient information, If the device is affixed to a person.cz-medical-device.patient(xsd)= <#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 actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.cz-medical-device.property(xsd)= <#base:Device.property> < Unique 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>* < Code that specifies the property DeviceDefinitionPropetyCode (Extensible).; (xsd)type:CodeableConcept> []< Property value as a quantity.; (xsd)valueQuantity:Quantity>* []< Property value as a code, e.g., NTP4 (synced to NTP).; (xsd)valueCode:CodeableConcept>* π The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.cz-medical-device.specialization(xsd)= <#base:Device.specialization> < Unique 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 standard that is used to operate and communicate.; (xsd)systemType:CodeableConcept> < The version of the standard that is used to operate and communicate.; (xsd)version:string>? π Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](http://hl7.org/fhir/R4/device-mappings.html#udi) for a complete mapping of UDI parts to Device.cz-medical-device.udiCarrier(xsd)= <#base:Device.udiCarrier> < Unique 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 device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.; (xsd)deviceIdentifier:string>? < Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, 3) ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di, 4) ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di.; (xsd)issuer:uri>? < The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi.; (xsd)jurisdiction:uri>? < The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.; (xsd)carrierAIDC:base64Binary>? < The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.; (xsd)carrierHRF:string>? < A coded entry to indicate how the data was entered.; (xsd)entryType:code>? π The actual design of the device or software version running on the device.cz-medical-device.version(xsd)= <#base:Device.version> < Unique 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 the device version.; (xsd)type:CodeableConcept>? < A single component of the device version.; (xsd)component:Identifier>? < The version text.; (xsd)value:string> π 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.cz-organization-base(xsd)= <#base:organization-eu> < 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. Typically, an NRPZS value and/or IΔO or IΔZ/IΔP value are given. Other systems are allowed, however use of NRPZS Id is preferred. Flows in organizations will most likely want to also include a local identifier, using its own identification system. A type can be added if needed. When it is given, a consumer SHALL NOT ignore it.; (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. . Type should be taken from DRZAR value set. 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:ContactPoint>* []< 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:cz-address>* < The organization of which this organization forms a part.; (xsd)partOf:organization-eu*>? []< 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:cz-organization-base.contact>* []< Technical endpoints providing access to services operated for the organization.; (xsd)endpoint:Endpoint*>* < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)NRPZS:cz-organization-base.NRPZS>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICO:cz-organization-base.ICO>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICZ:cz-organization-base.ICZ>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICP:cz-organization-base.ICP>? []< 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)DRZAR:cz-organization-base.DRZAR>* π 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.cz-organization-base.contact(xsd)= <#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>? π 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.cz-organization-base.DRZAR(xsd)= <#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:cz-organization-base.DRZAR.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.cz-organization-base.DRZAR.coding(xsd)= <#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. https://ncez.mzcr.cz/fhir/CodeSystem/cz-drzar; (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>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-base.ICO(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/ico; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-base.ICP(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/icp; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-base.ICZ(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/icz; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-base.NRPZS(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/nrpzs; (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 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.cz-organization-core(xsd)= <#base:cz-organization-base> < 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. Typically, an NRPZS value and/or IΔO or IΔZ/IΔP value are given. Other systems are allowed, however use of NRPZS Id is preferred. Flows in organizations will most likely want to also include a local identifier, using its own identification system. A type can be added if needed. When it is given, a consumer SHALL NOT ignore it.; (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. . Type should be taken from DRZAR value set. 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:ContactPoint>* []< 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:cz-address>* < The organization of which this organization forms a part.; (xsd)partOf:cz-organization-core*>? []< 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:cz-organization-core.contact>* []< Technical endpoints providing access to services operated for the organization.; (xsd)endpoint:Endpoint*>* < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)NRPZS:cz-organization-core.NRPZS>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICO:cz-organization-core.ICO>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICZ:cz-organization-core.ICZ>? < Identifier for the organization that is used to identify the organization across multiple disparate systems.; (xsd)ICP:cz-organization-core.ICP>? []< 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)DRZAR:cz-organization-core.DRZAR>* π 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.cz-organization-core.contact(xsd)= <#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>? π 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.cz-organization-core.DRZAR(xsd)= <#base:cz-organization-base.DRZAR> < Unique 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:cz-organization-core.DRZAR.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.cz-organization-core.DRZAR.coding(xsd)= <#base:cz-organization-base.DRZAR.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. https://ncez.mzcr.cz/fhir/CodeSystem/cz-drzar; (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>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-core.ICO(xsd)= <#base:cz-organization-base.ICO> < Unique 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. https://ncez.mzcr.cz/fhir/sid/ico; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-core.ICP(xsd)= <#base:cz-organization-base.ICP> < Unique 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. https://ncez.mzcr.cz/fhir/sid/icp; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-core.ICZ(xsd)= <#base:cz-organization-base.ICZ> < Unique 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. https://ncez.mzcr.cz/fhir/sid/icz; (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*>? π Identifier for the organization that is used to identify the organization across multiple disparate systems.cz-organization-core.NRPZS(xsd)= <#base:cz-organization-base.NRPZS> < Unique 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. https://ncez.mzcr.cz/fhir/sid/nrpzs; (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*>? π Demographics and other administrative information about an individual or animal receiving care or other health-related services.cz-patient-animal(xsd)= <#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:HumanName>* < A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. Animals do not have phones, their contacts do. Contact.telecom should be used.; (xsd)telecom:ContactPoint>{0,0} < 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:Address>* < This field contains a patient's most recent marital (civil) status.; (xsd)maritalStatus:CodeableConcept>{0,0} < 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:cz-patient-animal.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:cz-patient-animal.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:cz-patient-animal.link>* < This patient is known to be an animal. The absence of the animal extension does not imply that the patient is a human. If a system requires such a positive assertion that the patient is human, an extension will be required. (Do not use a species of homo-sapiens in animal species, as this would incorrectly infer that the patient is an animal).; (xsd)patient-animal> < A sex or gender property for the individual from a document or other record; (xsd)recordedSexOrGender:Extension>? π 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.cz-patient-animal.communication(xsd)= <#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.cz-patient-animal.contact(xsd)= <#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>? π Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.cz-patient-animal.link(xsd)= <#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> π Demographics and other administrative information about an individual or animal receiving care or other health-related services.cz-patient-base(xsd)= <#base:patient-eu> < 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>* []< Patient identifier. When available, one of the national identifiers (patient number from the national patient register, birth number (RC), insurance number) is usually used. Organisations may also provide a local identifier using their own identification system. If necessary, the type of identifier can also be added.; (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:HumanName-eu>* []< 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:ContactPoint>* < 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:cz-patient-base.birthDate>? < Death information either by symptom or date of death It is RECOMMENDED to include death information in all relevant cases. 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. It is RECOMMENDED to include an address when available. Patient may have multiple addresses with different uses or applicable periods.; (xsd)address:cz-address>* < This field contains a patient's most recent marital (civil) status.; (xsd)maritalStatus:CodeableConcept>? < 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. It is RECOMMENDED to include this when available and considered relevant for the patientcare. (e.g. a parent of a young 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:cz-patient-base.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:cz-patient-base.communication>* []< Patient's nominated care provider. Take note this does not automatically imply any legal form of therapeutic link or consent relationship with this GP. It is RECOMMENDED to include this when available if the flow is in any way medical. Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this GP can be found. Alternatively, there is only an internal reference and the GP is included as a βcontained resourceβ (cfr. the HL7 FHIR specifications in what cases this applies). This may be a primary or specialist outpatient care provider, or it may be a patient-designated carer in a community or disability setting, or an organisation that provides people to act as care providers. If it is a registering provider, the reference will also be included in the "registeringProvider" extension. This element should not be used to register care teams, these should be in the CareTeam resource, which can be linked to the CarePlan or EpisodeOfCare resources. Multiple providers may be recorded for a patient for different reasons, for example a student who has their GP listed alongside their GP at the university, or a worker who has a GP listed alongside their GP at the workplace to keep them informed of health issues.; (xsd)generalPractitioner:( <cz-organization-base> | <cz-practitioner-base> | <cz-practitionerrole-base>)>* < Organization that is the custodian of the patient record. This SHOULD be included when available. Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this Organization can be found. Alternatively, there is only an internal reference and the Organization is included as a βcontained resourceβ (cfr. the HL7 FHIR specifications in what cases this applies). 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:cz-organization-base*>? []< Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.; (xsd)link:cz-patient-base.link>* < The registered place of birth of the patient. A sytem may use the address.text if they don't store the birthPlace address in discrete elements.; (xsd)birthPlace:patient-birthPlace>? []< A parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc..; (xsd)sex-for-clinical-use:Extension>* []< The patient's legal status as citizen of a country.; (xsd)patient-citizenship>* []< The nationality of the patient.; (xsd)patient-nationality>* < Patient identifier assigned under the Czech Population Registration Act.; (xsd)RC:cz-rodcis-identifier>? < An unique patient identifier (resortnΓ identifikΓ‘tor) according to the National Patient Register; (xsd)RID:cz-patient-base.RID>? < An unique patient identifier (ΔΓslo pojiΕ‘tΔnce) according to the National Health Insurance Register; (xsd)CPOJ:cz-patient-base.CPOJ>? < An unique patient identifier (National ID Card Number) issued by the ministry of interior; (xsd)OP:cz-patient-base.OP>? []< An unique patient identifier (Passport Number); (xsd)PAS:cz-patient-base.PAS>* π 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).cz-patient-base.birthDate(xsd)= <#base:date> < unique id for the element within a resource (for internal references); (xsd)id:string>? []< An Extension; (xsd)extension:Extension>* < The actual value; (xsd)value:date>? < The time of day that the Patient was born. This includes the date to ensure that the timezone information can be communicated effectively.; (xsd)birthTime:patient-birthTime>? π 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.cz-patient-base.communication(xsd)= <#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. It is RECOMMENDED to include this when available and considered relevant for the patientcare. (e.g. a parent of a young 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.cz-patient-base.contact(xsd)= <#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-eu>? []< 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:cz-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:cz-organization-base*>? < The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>? π An unique patient identifier (ΔΓslo pojiΕ‘tΔnce) according to the National Health Insurance Registercz-patient-base.CPOJ(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/cpoj; (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*>? π Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.cz-patient-base.link(xsd)= <#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 unique patient identifier (National ID Card Number) issued by the ministry of interiorcz-patient-base.OP(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/op; (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 unique patient identifier (Passport Number)cz-patient-base.PAS(xsd)= <#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*>? π An unique patient identifier (resortnΓ identifikΓ‘tor) according to the National Patient Registercz-patient-base.RID(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/rid; (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*>? π Demographics and other administrative information about an individual or animal receiving care or other health-related services.cz-patient-core(xsd)= <#base:cz-patient-base> < 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>* []< Patient identifier. When available, one of the national identifiers (patient number from the national patient register, birth number (RC), insurance number) is usually used. Organisations may also provide a local identifier using their own identification system. If necessary, the type of identifier can also be added.; (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:HumanName-eu>+ []< 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:ContactPoint>* < 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:cz-patient-core.birthDate>? < Death information either by symptom or date of death It is RECOMMENDED to include death information in all relevant cases. 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. It is RECOMMENDED to include an address when available. Patient may have multiple addresses with different uses or applicable periods.; (xsd)address:cz-address>* < This field contains a patient's most recent marital (civil) status.; (xsd)maritalStatus:CodeableConcept>? < 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. It is RECOMMENDED to include this when available and considered relevant for the patientcare. (e.g. a parent of a young 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:cz-patient-core.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:cz-patient-core.communication>* []< Patient's nominated care provider. Take note this does not automatically imply any legal form of therapeutic link or consent relationship with this GP. It is RECOMMENDED to include this when available if the flow is in any way medical. Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this GP can be found. Alternatively, there is only an internal reference and the GP is included as a βcontained resourceβ (cfr. the HL7 FHIR specifications in what cases this applies). This may be a primary or specialist outpatient care provider, or it may be a patient-designated carer in a community or disability setting, or an organisation that provides people to act as care providers. If it is a registering provider, the reference will also be included in the "registeringProvider" extension. This element should not be used to register care teams, these should be in the CareTeam resource, which can be linked to the CarePlan or EpisodeOfCare resources. Multiple providers may be recorded for a patient for different reasons, for example a student who has their GP listed alongside their GP at the university, or a worker who has a GP listed alongside their GP at the workplace to keep them informed of health issues.; (xsd)generalPractitioner:( <cz-organization-base> | <cz-practitioner-base> | <cz-practitionerrole-base>)>* < Organization that is the custodian of the patient record. This SHOULD be included when available. Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this Organization can be found. Alternatively, there is only an internal reference and the Organization is included as a βcontained resourceβ (cfr. the HL7 FHIR specifications in what cases this applies). 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:cz-organization-base*>? []< Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.; (xsd)link:cz-patient-core.link>* < The registered place of birth of the patient. A sytem may use the address.text if they don't store the birthPlace address in discrete elements.; (xsd)birthPlace:patient-birthPlace>? []< A parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc..; (xsd)sex-for-clinical-use:Extension>* []< The patient's legal status as citizen of a country.; (xsd)patient-citizenship>* []< The nationality of the patient.; (xsd)patient-nationality>* []< A registering provider means an ambulatory care provider in the field of general practice medicine, in the field of practice medicine for children and adolescents, in the field of dentistry or in the field of gynecology and obstetrics, who accepted a patient for the purpose of providing primary ambulatory care. At any one time, a patient may have no more than one general practitioner or paediatric and adolescent practitioner and one dental registrar. Female patients may also have no more than one registered provider in gynaecology and obstetrics.; (xsd)registeringProvider:registering-provider-cz>* < Patient identifier assigned under the Czech Population Registration Act.; (xsd)RC:cz-rodcis-identifier>? < An unique patient identifier (resortnΓ identifikΓ‘tor) according to the National Patient Register; (xsd)RID:cz-patient-core.RID>? < An unique patient identifier (ΔΓslo pojiΕ‘tΔnce) according to the National Health Insurance Register; (xsd)CPOJ:cz-patient-core.CPOJ>? < An unique patient identifier (National ID Card Number) issued by the ministry of interior; (xsd)OP:cz-patient-core.OP>? []< An unique patient identifier (Passport Number); (xsd)PAS:cz-patient-core.PAS>* π 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).cz-patient-core.birthDate(xsd)= <#base:cz-patient-base.birthDate> < unique id for the element within a resource (for internal references); (xsd)id:string>? []< An Extension; (xsd)extension:Extension>* < The actual value; (xsd)value:date>? < The time of day that the Patient was born. This includes the date to ensure that the timezone information can be communicated effectively.; (xsd)birthTime:patient-birthTime>? π 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.cz-patient-core.communication(xsd)= <#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. It is RECOMMENDED to include this when available and considered relevant for the patientcare. (e.g. a parent of a young 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.cz-patient-core.contact(xsd)= <#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-eu>? []< 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:cz-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:cz-organization-base*>? < The period during which this contact person or organization is valid to be contacted relating to this patient.; (xsd)period:Period>? π An unique patient identifier (ΔΓslo pojiΕ‘tΔnce) according to the National Health Insurance Registercz-patient-core.CPOJ(xsd)= <#base:cz-patient-base.CPOJ> < Unique 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. https://ncez.mzcr.cz/fhir/sid/cpoj; (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*>? π Link to another patient resource that concerns the same actual patient. There is no assumption that linked patient records have mutual links.cz-patient-core.link(xsd)= <#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 unique patient identifier (National ID Card Number) issued by the ministry of interiorcz-patient-core.OP(xsd)= <#base:cz-patient-base.OP> < Unique 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. https://ncez.mzcr.cz/fhir/sid/op; (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 unique patient identifier (Passport Number)cz-patient-core.PAS(xsd)= <#base:cz-patient-base.PAS> < Unique 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*>? π An unique patient identifier (resortnΓ identifikΓ‘tor) according to the National Patient Registercz-patient-core.RID(xsd)= <#base:cz-patient-base.RID> < Unique 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. https://ncez.mzcr.cz/fhir/sid/rid; (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 person who is directly or indirectly involved in the provisioning of healthcare.cz-practitioner-base(xsd)= <#base:practitioner-eu> < 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. Typically, a NRZP value is given and/or CLK identifier provided by the Czech Medical Chamber or identifier of Pharmacist (PharmID) provided by the Czech Chamber of Pharmacists, however use of NRZP Id is preferred. Other systems remain allowed. Flows in organizations will most likely want to also include a local identifier, using its own system. A type can be added if needed. When it is given, a consumer SHALL NOT ignore it.; (xsd)identifier:Identifier>* < Whether this practitioner's record is in active use. It is RECOMMENDED to keep the value βtrueβ as long as the practitioner is still being treated by the provider of the data. 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:HumanName-eu>* []< 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:ContactPoint>* []< 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:cz-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:cz-practitioner-base.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>* []< An identifier that applies to this person in this role.; (xsd)NRZP:cz-practitioner-base.NRZP>* []< An identifier that applies to this person in this role.; (xsd)CLK:cz-practitioner-base.CLK>* []< An identifier that applies to this person in this role.; (xsd)CLeK:cz-practitioner-base.CLeK>* π An identifier that applies to this person in this role.cz-practitioner-base.CLeK(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/clek; (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 that applies to this person in this role.cz-practitioner-base.CLK(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/clk; (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 that applies to this person in this role.cz-practitioner-base.NRZP(xsd)= <#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. https://ncez.mzcr.cz/fhir/sid/nrzp; (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*>? π 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.cz-practitioner-base.qualification(xsd)= <#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 person who is directly or indirectly involved in the provisioning of healthcare.cz-practitioner-core(xsd)= <#base:cz-practitioner-base> < 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. Typically, a NRZP value is given and/or CLK identifier provided by the Czech Medical Chamber or identifier of Pharmacist (PharmID) provided by the Czech Chamber of Pharmacists, however use of NRZP Id is preferred. Other systems remain allowed. Flows in organizations will most likely want to also include a local identifier, using its own system. A type can be added if needed. When it is given, a consumer SHALL NOT ignore it.; (xsd)identifier:Identifier>* < Whether this practitioner's record is in active use. It is RECOMMENDED to keep the value βtrueβ as long as the practitioner is still being treated by the provider of the data. 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. Typically RECOMMENDED to include one familyname and at least one given name and to define this use as βofficialβ. 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:HumanName-eu>+ []< A contact detail for the practitioner, e.g. a telephone number or an email address. It is RECOMMENDED to at least add one phone or 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:ContactPoint>* []< 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:cz-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:cz-practitioner-core.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>* []< An identifier that applies to this person in this role.; (xsd)NRZP:cz-practitioner-core.NRZP>* []< An identifier that applies to this person in this role.; (xsd)CLK:cz-practitioner-core.CLK>* []< An identifier that applies to this person in this role.; (xsd)CLeK:cz-practitioner-core.CLeK>* π An identifier that applies to this person in this role.cz-practitioner-core.CLeK(xsd)= <#base:cz-practitioner-base.CLeK> < Unique 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. https://ncez.mzcr.cz/fhir/sid/clek; (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 that applies to this person in this role.cz-practitioner-core.CLK(xsd)= <#base:cz-practitioner-base.CLK> < Unique 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. https://ncez.mzcr.cz/fhir/sid/clk; (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 that applies to this person in this role.cz-practitioner-core.NRZP(xsd)= <#base:cz-practitioner-base.NRZP> < Unique 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. https://ncez.mzcr.cz/fhir/sid/nrzp; (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*>? π 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.cz-practitioner-core.qualification(xsd)= <#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 specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.cz-practitionerrole-base(xsd)= <#base:practitionerRole-eu> < 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:cz-practitioner-base*>? < The organization where the Practitioner performs the roles associated.; (xsd)organization:cz-organization-base*>? []< Roles which this practitioner is authorized to perform for the organization. For compatibility reasons, CD-HCPARTY is described here to express the role of the practitioner. Other coding systems remain allowed. Towards the future, the use of SNOMED-CT codes is also RECOMMENDED here. In the future, other ways to codfy might however be also proposed. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system. A person may have more than one role.; (xsd)code:CodeableConcept>* []< Specific specialty of the practitioner. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.; (xsd)specialty:CodeableConcept>* []< The location(s) at which this practitioner provides care.; (xsd)location: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:cz-practitionerrole-base.availableTime>* []< The practitioner is not available or performing this role during this period of time due to the provided reason.; (xsd)notAvailable:cz-practitionerrole-base.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*>* []< Roles which this practitioner is authorized to perform for the organization according to the National registry of healthcare practitioners. A person may have more than one role.; (xsd)NRZP_POVOLANI:cz-practitionerrole-base.NRZP_POVOLANI>* []< Specific specialty of the practitioner.; (xsd)SNOMED-CT:cz-practitionerrole-base.SNOMED-CT>* π 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.cz-practitionerrole-base.availableTime(xsd)= <#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.cz-practitionerrole-base.notAvailable(xsd)= <#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>? π Roles which this practitioner is authorized to perform for the organization according to the National registry of healthcare practitioners. A person may have more than one role.cz-practitionerrole-base.NRZP_POVOLANI(xsd)= <#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:cz-practitionerrole-base.NRZP_POVOLANI.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.cz-practitionerrole-base.NRZP_POVOLANI.coding(xsd)= <#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. https://ncez.mzcr.cz/fhir/CodeSystem/nrzp-povolani; (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>? π Specific specialty of the practitioner.cz-practitionerrole-base.SNOMED-CT(xsd)= <#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:cz-practitionerrole-base.SNOMED-CT.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.cz-practitionerrole-base.SNOMED-CT.coding(xsd)= <#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://snomed.info/sct; (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). If needed codes can be used from a different system, SNOMED-CT is preferred.; (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 specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.cz-practitionerrole-core(xsd)= <#base:cz-practitionerrole-base> < 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:cz-practitioner-core*>? < The organization where the Practitioner performs the roles associated.; (xsd)organization:cz-organization-core*>? []< Roles which this practitioner is authorized to perform for the organization. For compatibility reasons, CD-HCPARTY is described here to express the role of the practitioner. Other coding systems remain allowed. Towards the future, the use of SNOMED-CT codes is also RECOMMENDED here. In the future, other ways to codfy might however be also proposed. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system. A person may have more than one role.; (xsd)code:CodeableConcept>* []< Specific specialty of the practitioner. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.; (xsd)specialty:CodeableConcept>* []< The location(s) at which this practitioner provides care.; (xsd)location: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:cz-practitionerrole-core.availableTime>* []< The practitioner is not available or performing this role during this period of time due to the provided reason.; (xsd)notAvailable:cz-practitionerrole-core.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*>* []< Roles which this practitioner is authorized to perform for the organization according to the National registry of healthcare practitioners. A person may have more than one role.; (xsd)NRZP_POVOLANI:cz-practitionerrole-core.NRZP_POVOLANI>* []< Specific specialty of the practitioner.; (xsd)SNOMED-CT:cz-practitionerrole-core.SNOMED-CT>* π 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.cz-practitionerrole-core.availableTime(xsd)= <#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.cz-practitionerrole-core.notAvailable(xsd)= <#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>? π Roles which this practitioner is authorized to perform for the organization according to the National registry of healthcare practitioners. A person may have more than one role.cz-practitionerrole-core.NRZP_POVOLANI(xsd)= <#base:cz-practitionerrole-base.NRZP_POVOLANI> < Unique 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:cz-practitionerrole-core.NRZP_POVOLANI.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.cz-practitionerrole-core.NRZP_POVOLANI.coding(xsd)= <#base:cz-practitionerrole-base.NRZP_POVOLANI.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. https://ncez.mzcr.cz/fhir/CodeSystem/nrzp-povolani; (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>? π Specific specialty of the practitioner.cz-practitionerrole-core.SNOMED-CT(xsd)= <#base:cz-practitionerrole-base.SNOMED-CT> < Unique 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:cz-practitionerrole-core.SNOMED-CT.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.cz-practitionerrole-core.SNOMED-CT.coding(xsd)= <#base:cz-practitionerrole-base.SNOMED-CT.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://snomed.info/sct; (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). If needed codes can be used from a different system, SNOMED-CT is preferred.; (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.cz-rodcis-identifier(xsd)= <#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. official; (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. https://ncez.mzcr.cz/fhir/sid/rcis; (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 extension allows to specify whether or not the address is an official address (permanent address) or to indicate that it is the official address for that country.permanent-residencer-address-cz(xsd)= <#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. https://hl7.cz/fhir/core/StructureDefinition/permanent-residencer-address-cz; (xsd)url:string> ( <valueBoolean:boolean> | <valueCodeableConcept: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: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)valueBoolean:boolean>? π This extension allows the entry of information on the registering provider and their category/specialty of care (general practice, paediatric and adolescent practice, dentistry or gynaecology and obstetrics) who has admitted the patient for primary outpatient care.registering-provider-cz(xsd)= <#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>{2,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. https://hl7.cz/fhir/core/StructureDefinition/registering-provider-cz; (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 registering provider. The type of registering provider is specified in the category element. At any given time, a patient may have no more than one registering provider in general practice or pediatric practice and one registering provider in dentistry. Patients may also have a maximum of one registered provider in the field of gynecology and obstetrics.; (xsd)value:registering-provider-cz.value> < Type of registering healthcare provider: registering general practitioner, general practitioner for children and adolescents, registering gynecologist or registering dentist.; (xsd)category:registering-provider-cz.category> π Type of registering healthcare provider: registering general practitioner, general practitioner for children and adolescents, registering gynecologist or registering dentist.registering-provider-cz.category(xsd)= <#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. category; (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> π Reference to the registering provider. The type of registering provider is specified in the category element. At any given time, a patient may have no more than one registering provider in general practice or pediatric practice and one registering provider in dentistry. Patients may also have a maximum of one registered provider in the field of gynecology and obstetrics.registering-provider-cz.value(xsd)= <#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. value; (xsd)url:string> ( <valueCz-organization-core:cz-organization-core> | <valueCz-practitionerrole-core:cz-practitionerrole-core>)