Kalendārs (Schedule)
Schedule resurss apraksta kalendāra avotu, pie kura tiek veidoti laika sloti – piemēram, konkrēta ārsta darba grafiku vai pakalpojuma pieejamību noteiktā vietā. Tas satur atsauces uz PractitionerRole (ārsta līgumattiecība), HealthcareService (pakalpojums) u.c., un tiek izmantots kā bāze pieejamības strukturēšanai.
| Schedule | I | Schedule | There are no (further) constraints on this element Element idSchedule A container for slots of time that may be available for booking appointments Alternate namesAvailability DefinitionA container for slots of time that may be available for booking appointments.
| |
| id | Σ | 0..1 | id | Element idSchedule.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. //Iekšējais e-pieraksta ID. Tiek sagaidīts tikai UPDATE pieprasījumos. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSchedule.meta Metadata about the resource DefinitionThe 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.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSchedule.implicitRules A set of rules under which this content was created DefinitionA 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 its narrative along with other profiles, value sets, etc.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSchedule.language Language of the resource content DefinitionThe 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). IETF language tag for a human language
| |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idSchedule.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
|
| contained | I | 0..* | Resource | There are no (further) constraints on this element Element idSchedule.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. 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.
|
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 1..1 | Identifier | Element idSchedule.identifier External Ids for this item DefinitionExternal Ids for this item. //Izmantot, lai meklētu pēc ID. Netiek definēta iestāde, ID var sakritst starp dažādām iestādēm.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.identifier.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.identifier.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| use | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idSchedule.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
|
| type | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idSchedule.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. 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. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
|
| system | Σ | 0..0 | uri | There are no (further) constraints on this element Element idSchedule.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
|
| value | Σ I | 1..1 | string | Element idSchedule.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. //Ierobežojums uz 20 simboliem. 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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.
20 General 123456 Mappings
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idSchedule.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idSchedule.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization 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.
|
| active | Σ ?! | 1..1 | boolean | Element idSchedule.active Whether this schedule is in active use DefinitionWhether this schedule record is in active use or should not be used (such as was entered in error). //Norāda vai kalendārs ir - aktīvs vai neaktīvs. This element is labeled as a modifier because it may be used to mark that the resource was created in error. This resource is generally assumed to be active if no value is provided for the active element
|
| serviceCategory | Σ | 1..1 | CodeableConcept | Element idSchedule.serviceCategory High-level category DefinitionA broad categorization of the service that is to be performed during this appointment. //Ir izveidotas 2 kategorijas, kas apzīmē pakalpojumu saraksta hierarhiju. 1 - pakalpojumu grupa, 2 - pakalpojumu veids. Unordered, Closed, by coding.system(Value) Binding Constraints
|
| majorCategory | Σ | 1..1 | CodeableConcept | Element idSchedule.serviceCategory:majorCategory High-level category DefinitionA broad categorization of the service that is to be performed during this appointment. //Major kategorija nosaka pakalpojumu grupu. Piemēram: ambulatorie pakalpojumi, stacionārie pakalpojumi, dienas stacionāra pakalpojumi, laboratorijas pakalpojumi u.c.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 1..1 | Coding | Element idSchedule.serviceCategory:majorCategory.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. //Pasaka, ka te jāsūta vērtība no klasifikatora Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idSchedule.serviceCategory:majorCategory.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. //Pasaka, ka vērtības jāņem no 1.3.6.1.4.1.38760.2.914 Need to be unambiguous about the source of the definition of the symbol. 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
uri:1.3.6.1.4.1.38760.2.914
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.coding.version Version of the system - if relevant DefinitionThe 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.
|
| code | Σ I | 1..1 | code | Element idSchedule.serviceCategory:majorCategory.coding.code Symbol in syntax defined by the system DefinitionA 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). //Klasifikatora vērtības kods. Need to refer to a particular code in the system.
|
| display | Σ I | 1..1 | string | Element idSchedule.serviceCategory:majorCategory.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. //Klasifikatora vērtības display name. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
| text | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:majorCategory.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| minorCategory | Σ | 1..1 | CodeableConcept | Element idSchedule.serviceCategory:minorCategory High-level category DefinitionA broad categorization of the service that is to be performed during this appointment. //Minor kategorija nosaka pakalpojumu veidu. Piemēram: Konsultācijas, Izmeklējumi, Funkcionālie izmeklējumi, Specializēti kabineti u.c.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 1..1 | Coding | Element idSchedule.serviceCategory:minorCategory.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. // Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idSchedule.serviceCategory:minorCategory.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. //Šim jāizveido klasifikators. (Piemēram: 1.3.6.1.4.1.38760.2.nnn) Need to be unambiguous about the source of the definition of the symbol. 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
uri:1.3.6.1.4.1.38760.2.nnn
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.coding.version Version of the system - if relevant DefinitionThe 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.
|
| code | Σ I | 1..1 | code | Element idSchedule.serviceCategory:minorCategory.coding.code Symbol in syntax defined by the system DefinitionA 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). //Klasifikatora vērtības kods. Need to refer to a particular code in the system.
|
| display | Σ I | 1..1 | string | Element idSchedule.serviceCategory:minorCategory.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. //Klasifikatora vērtības display name. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
| text | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:minorCategory.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| serviceType | Σ | 1..5 | CodeableReference(HealthcareService) | Element idSchedule.serviceType Specific service DefinitionThe specific service that is to be performed during this appointment. //Pakalpojumu klasifikators, MVP kārtā satur tikai konsultācijas, piemēram: Alergologa konsultācija, Ķirurga konsultācija, Neirologa konsultācija u.c. CodeableReference(HealthcareService) Binding Constraints
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceType.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceType.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| concept | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idSchedule.serviceType.concept Reference to a concept (by class) DefinitionA reference to a concept - e.g. the information is identified by its general class to the degree of precision found in the terminology.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceType.concept.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceType.concept.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idSchedule.serviceType.concept.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. //Jaunais pakalpojumu klasifikators - ķirurga, neirologa, ginekologa konsultācija u.c. Need to be unambiguous about the source of the definition of the symbol. 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
uri:1.3.6.1.4.1.38760.2.nnn
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.version Version of the system - if relevant DefinitionThe 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.
|
| code | Σ I | 1..1 | code | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system.
|
| display | Σ I | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idSchedule.serviceType.concept.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
| text | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceType.concept.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| reference | Σ | 1..1 | Reference() | There are no (further) constraints on this element Element idSchedule.serviceType.reference Reference to a resource (by instance) DefinitionA reference to a resource the provides exact details about the information being referenced.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.serviceType.reference.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceType.reference.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceType.reference.reference Literal reference, Relative, internal or absolute URL DefinitionA 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.
|
| type | Σ | 1..1 | uriBindingFixed Value | Element idSchedule.serviceType.reference.type Type the reference refers to (e.g. "Patient") - must be a resource in resources DefinitionThe 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 known RESTful URL) or by resolving the target of the reference. Aa resource (or, for logical models, the URI of the logical model).
HealthcareService
|
| identifier | Σ I | 0..0 | Identifier | There are no (further) constraints on this element Element idSchedule.serviceType.reference.identifier Logical reference, when literal reference is not known DefinitionAn 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). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.
|
| display | Σ I | 0..0 | string | There are no (further) constraints on this element Element idSchedule.serviceType.reference.display Text alternative for the resource DefinitionPlain 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.
|
| specialty | Σ | 1..1 | CodeableConceptBinding | Element idSchedule.specialty Type of specialty needed DefinitionThe specialty of a practitioner that would be required to perform the service requested in this appointment. //Definē kurai ārsta specialitātei šis kalendārs pieder. Additional details about where the content was created (e.g. clinical specialty).
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.specialty.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idSchedule.specialty.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.specialty.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idSchedule.specialty.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. //Izmantots klasifikators: 1.3.6.1.4.1.38760.2.38 Need to be unambiguous about the source of the definition of the symbol. 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
uri:1.3.6.1.4.1.38760.2.38
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.specialty.coding.version Version of the system - if relevant DefinitionThe 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.
|
| code | Σ I | 1..1 | code | Element idSchedule.specialty.coding.code Symbol in syntax defined by the system DefinitionA 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). //Klasifikatora vērtības kods. Need to refer to a particular code in the system.
|
| display | Σ I | 1..1 | string | Element idSchedule.specialty.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. //Klasifikatora vērtības nosaukums. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idSchedule.specialty.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
| text | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.specialty.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| name | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.name Human-readable label DefinitionFurther description of the schedule as it would be presented to a consumer while searching. This MAY be used to describe what the schedule is for where it is clearer than just the name of the single actor.
|
| actor | Σ | 1..1 | Reference(PractitionerRole) | Element idSchedule.actor Resource(s) that availability information is being provided for DefinitionSlots that reference this schedule resource provide the availability details to these referenced resource(s). //Ārsta līgumattiecība. Ārsts, kurš sniegs pakalpojumu. The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.actor.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | Element idSchedule.actor.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. //Pievienots extensions valodām There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element idSchedule.actor.reference Literal reference, Relative, internal or absolute URL DefinitionA 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.
|
| type | Σ | 1..1 | uriBindingFixed Value | Element idSchedule.actor.type Type the reference refers to (e.g. "Patient") - must be a resource in resources DefinitionThe 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 known RESTful URL) or by resolving the target of the reference. Aa resource (or, for logical models, the URI of the logical model).
PractitionerRole
|
| identifier | Σ I | 0..0 | Identifier | There are no (further) constraints on this element Element idSchedule.actor.identifier Logical reference, when literal reference is not known DefinitionAn 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). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.
|
| display | Σ I | 0..0 | string | There are no (further) constraints on this element Element idSchedule.actor.display Text alternative for the resource DefinitionPlain 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.
|
| planningHorizon | Σ | 1..1 | Period | There are no (further) constraints on this element Element idSchedule.planningHorizon Period of time covered by schedule DefinitionThe period of time that the slots that reference this Schedule resource cover (even if none exist). These cover the amount of time that an organization's planning horizon; the interval for which they are currently accepting appointments. This does not define a "template" for planning outside these dates.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.planningHorizon.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.planningHorizon.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| start | Σ I | 1..1 | dateTime | Element idSchedule.planningHorizon.start Starting time with inclusive boundary DefinitionThe start of the period. The boundary is inclusive. //Sagaidām datumu un laiku If the low element is missing, the meaning is that the low boundary is not known.
|
| end | Σ I | 1..1 | dateTime | Element idSchedule.planningHorizon.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. //Sagaidām datumu un laiku The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
| comment | 0..1 | markdown | Element idSchedule.comment Comments on availability DefinitionComments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated. //Tiek sagaidīti vecuma ierobežojumi - kādās vecuma robežās ārsts pieņems pacientus. Piemēram 1-7; 1-18; 18+; u.c.
|
Datu lauki
| Datu lauks | FHIR lauks | Obligātums (Cardinality) | FHIR lauka apraksts | Detaļas |
|---|---|---|---|---|
| Kalendāra ID | Schedule.id | 0..1 | Kalendāra unikālais ID, sagaidāms tikai UPDATE pieprasījumos. | - |
| Kalendāra identifikators | Schedule.identifier | 1..1 | Identifikators starp dažādām iestādēm, unikāls sistēmas ietvaros. | - |
| Identifikatora vērtība | Schedule.identifier.value | 1..1 | ID vērtība, ierobežojums līdz 20 simboliem. | - |
| Identifikatora piešķīrējs | Schedule.identifier.assigner.type | 1..1 | Piešķīrējs norādīts kā Organization. | - |
| Aktīvs kalendārs | Schedule.active | 1..1 | Norāda, vai kalendārs ir aktīvs vai nē. | - |
| Pakalpojuma grupa | Schedule.serviceCategory:majorCategory | 1..1 | Pakalpojuma grupas klasifikators. | No klasifikatora 1.3.6.1.4.1.38760.2.914. |
| Pakalpojuma veids | Schedule.serviceCategory:minorCategory | 1..1 | Pakalpojuma veida klasifikators. | No klasifikatora 1.3.6.1.4.1.38760.2.nnn. |
| Pakalpojuma tips | Schedule.serviceType | 1..5 | Veicamie pakalpojumi. | Konsultācijas. |
| Pakalpojuma tips (concept) | Schedule.serviceType.concept | 1..1 | Pakalpojuma tips ar kodētu vērtību. | - |
| Pakalpojuma tips (reference) | Schedule.serviceType.reference | 1..1 | Atsauce uz HealthcareService resursu. | - |
| Ārsta specialitāte | Schedule.specialty | 1..1 | Ārsta specialitāte. | No klasifikatora 1.3.6.1.4.1.38760.2.38. |
| Līguma attiecība | Schedule.actor | 1..1 | Atsauce uz ārsta PractitionerRole. | - |
| Kalendāra pieejamības sākums | Schedule.planningHorizon.start | 1..1 | Kalendāra pieejamības sākuma datums un laiks. | - |
| Kalendāra pieejamības beigas | Schedule.planningHorizon.end | 1..1 | Kalendāra pieejamības beigu datums un laiks. | - |
| Vecuma ierobežojums | Schedule.comment | 0..1 | Norādīti vecuma ierobežojumi pacientiem. | Piemēram: 1-7, 18+. |
Piemērs: Schedule
{
"resourceType": "Schedule",
"id": "sch-001",
"identifier": {
"value": "SCHED123456"
},
"active": true,
"serviceCategory": [
{
"coding": [
{
"system": "uri:1.3.6.1.4.1.38760.2.914",
"code": "AMB",
"display": "Ambulatorie pakalpojumi"
}
]
},
{
"coding": [
{
"system": "uri:1.3.6.1.4.1.38760.2.nnn",
"code": "CONS",
"display": "Konsultācijas"
}
]
}
],
"serviceType": [
{
"concept": {
"coding": [
{
"system": "uri:1.3.6.1.4.1.38760.2.nnn",
"code": "KIR",
"display": "Ķirurga konsultācija"
}
]
},
"reference": {
"reference": "HealthcareService/hs-001",
"type": "HealthcareService"
}
}
],
"specialty": [
{
"coding": [
{
"system": "uri:1.3.6.1.4.1.38760.2.38",
"code": "P03",
"display": "Ķirurgs"
}
]
}
],
"actor": [
{
"reference": "PractitionerRole/pr-001",
"type": "PractitionerRole"
}
],
"planningHorizon": {
"start": "2025-05-01T08:00:00+02:00",
"end": "2025-05-01T16:00:00+02:00"
},
"comment": "Pieņem pacientus vecumā no 18 gadiem."
}