Generated Narrative: StructureDefinition ee-spd-organization Name Flags Card. Type Description & Constraints Organization 0..* EEBaseOrganization(2.0.0) A grouping of people or organizations with a common purpose without substructure #xD; identifier 1..* Identifier Business registry code, VATin code or some other identifying code of organization must be here #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; use 0..0 usual | official | temp | secondary | old (If known) #xD; type 0..0 Description of identifier #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; active 0..1 boolean Status of organization. (ee STAATUS näitab, kas asutus on Äriregistris aktiivne) #xD; Slices for type 1..* CodeableConcept Type of organization. Use slice hospital when expressing hospital type. (ee Asutuse tüüp. Nt.|prov| = TTO, |bus| = kui tegemist on mitte-TTOga. Haigla liik läheb hospital alla.) Slice: Unordered, Open by value:$this #xD; type:All Slices Content/Rules for all slices #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; coding #xD; version 0..0 Version of the system - if relevant #xD; type:organizationType 1..1 CodeableConcept Kind of organization Binding: OrganizationType (required) #xD; coding #xD; userSelected 0..0 If this coding was chosen directly by the user #xD; type:hospitalType 0..1 CodeableConcept As long as there is no VS, use text to describe the hospital type. FAKE codesystem is for slicing purposes. (ee |Taastusravihaigla| Keskhaigla| Üldhaigla| Piirkondlik haigla| Erihaigla| Hooldushaigla| Kohalik haigla|) Binding: https://fhir.ee/ValueSet/medre-haigla-liik (required) #xD; name 1..1 string Name of the organization. (ee Asutuse NIMETUS) #xD; alias 0..0 A list of alternate names that the organization is known as, or was known as in the past #xD; description 0..0 Additional details about the Organization that could be displayed as further information to identify the Organization beyond its name #xD; contact 0..* ExtendedContactDetail Contact details of the organization. (ee Asutuse kontaktandmed, email, telefon. (aadress tuleb locationi alt iga tegevuskoha kohta eraldi)) #xD; purpose 0..0 The type of contact #xD; name 0..0 Name of an individual to contact #xD; Slices for telecom 0..* ContactPoint Contact details (e.g.phone/fax/url) Slice: Unordered, Closed by value:system #xD; telecom:All Slices Content/Rules for all slices #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; use 1..1 code home | work | temp | old | mobile - purpose of this contact point Required Pattern: work #xD; rank 0..0 Specify preferred order of use (1 = highest) #xD; period 0..0 Time period when the contact point was/is in use #xD; telecom:phone 0..* ContactPoint Telefoni number #xD; system 1..1 code phone | fax | email | pager | url | sms | other Required Pattern: phone #xD; telecom:email 0..* ContactPoint E-Mail #xD; system 1..1 code phone | fax | email | pager | url | sms | other Required Pattern: email #xD; address 0..0 Address for the contact #xD; organization 0..0 This contact detail is handled/monitored by a specific organization #xD; period 0..0 Period that this contact was valid for usage #xD; partOf 0..0 The organization of which this organization forms a part #xD; endpoint 0..0 Technical endpoints providing access to services operated for the organization #xD; qualification 0..* BackboneElement Licence(s) to provide healthcare service. (ee TEGEVUSLUBA) #xD; id 0..0 Unique id for inter-element referencing #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:licenceStopped 0..1 Period Period during which healthcare provision licence is STOPPED. URL: https://fhir.ee/spd/StructureDefinition/ee-tis-effective-period #xD; modifierExtension 0..0 Extension #xD; Slices for identifier 0..* Identifier Number of the licence. (ee TEGEVUSLOA NUMBER) Slice: Unordered, Open by value:system #xD; identifier:All Slices Content/Rules for all slices #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; use 0..0 usual | official | temp | secondary | old (If known) #xD; type 0..0 Description of identifier #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; identifier:hcpIdentifier 0..1 Identifier Identifier of hcp licence. (ee TERVISEAMETI LITSENTSI NUMBER) #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; use 0..0 usual | official | temp | secondary | old (If known) #xD; type 0..0 Description of identifier #xD; system 1..1 uri The namespace for the identifier value Fixed Value: https://fhir.ee/sid/org/est/fi #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; identifier:pharmacyIdentifier 0..* Identifier Identifier of pharmacy licence. (ee Apteegi tegevusluba on KOLMEKOHALINE NUMBER mis erineb tegevuskoha koodist.) #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; use 0..0 usual | official | temp | secondary | old (If known) #xD; type 0..0 Description of identifier #xD; system 0..0 The namespace for the identifier value #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; code 1..1 CodeableConcept Field of services this licence allows. (ee TEGEVUSLOA LIIK) #xD; Slices for coding 0..* Coding Code defined by a terminology system Slice: Unordered, Open by value:system #xD; coding:tto 0..* Coding Tegevusloa liik on TTO #xD; system 0..1 uri Identity of the terminology system Binding: https://fhir.ee/ValueSet/medre-tegevusloa-liik (required) #xD; coding:pharmacy 0..* Coding Pharmacy licence #xD; system 0..1 uri Identity of the terminology system Binding: https://fhir.ee/ValueSet/ravimiameti-apteegiteenuse-tegevusloa-liigi-tapsustus (required) #xD; period 0..1 Period Period of the licence validity. (ee TEGEVUSLOA KEHTIVUS) #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; start 1..1 dateTime Starting time with inclusive boundary #xD; issuer 0..0 Organization that regulates and issues the qualification #xD; Documentation for this format
A grouping of people or organizations with a common purpose without substructure
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The organization SHALL at least have a name or an identifier, and possibly more than one
Entity, Role, or Act,Organization(classCode=ORG, determinerCode=INST)
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
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.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have 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.
These 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.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and 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.
Must have either extensions or value[x], not both
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 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](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Business registry code, VATin code or some other identifying code of organization must be here
Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
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.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.
Identifier.system is always case sensitive.
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.
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 [http://hl7.org/fhir/StructureDefinition/rendered-value](http://hl7.org/fhir/extensions/StructureDefinition-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.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
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.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Status of organization. (ee STAATUS näitab, kas asutus on Äriregistris aktiivne)
STAATUS, kas organisatsioon on aktiivne või mitte
This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used. This element is labeled as a modifier because it may be used to mark that the resource was created in error.
Need a flag to indicate a record is no longer to be used and should generally be hidden for the user in the UI.
This resource is generally assumed to be active if no value is provided for the active element
This element is labelled as a modifier because it is a status element that can indicate that a record should not be treated as valid
./Status (however this concept in ServD more covers why the organization is active or not, could be delisted, deregistered, not operational yet) this could alternatively be derived from ./StartDate and ./EndDate and given a context date.
Type of organization. Use slice hospital when expressing hospital type. (ee Asutuse tüüp. Nt.|prov| = TTO, |bus| = kui tegemist on mitte-TTOga. Haigla liik läheb hospital alla.)
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.
Need to be able to track the kind of organization that this is - different organization types have different uses.
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.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
May be 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.
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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
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.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
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).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A 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.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
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.
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.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
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.
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.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
As long as there is no VS, use text to describe the hospital type. FAKE codesystem is for slicing purposes. (ee |Taastusravihaigla| Keskhaigla| Üldhaigla| Piirkondlik haigla| Erihaigla| Hooldushaigla| Kohalik haigla|)
Name of the organization. (ee Asutuse NIMETUS)
If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches.
Need to use the name as the label of the organization.
A list of alternate names that the organization is known as, or was known as in the past
A list of alternate names that the organization is known as, or was known as in the past.
There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the organization.
Over time locations and organizations go through many changes and can be known by different names. For searching knowing previous names that the organization was known by can be very useful.
Additional details about the Organization that could be displayed as further information to identify the Organization beyond its name
Description of the organization, which helps provide additional general context on the organization to ensure that the correct organization is selected.
Humans need additional information to verify a correct Organization has been selected.
.playingEntity[classCode=PLC determinerCode=INSTANCE].desc
Contact details of the organization. (ee Asutuse kontaktandmed, email, telefon. (aadress tuleb locationi alt iga tegevuskoha kohta eraldi))
The contact details of communication devices available relevant to the specific Organization. This can include addresses, phone numbers, fax numbers, mobile numbers, email addresses and web sites.
The address/telecom use code 'home' are not to be used. Note that these contacts are not the contact details of people who provide the service (that would be through PractitionerRole), these are official contacts for the Organization itself for specific purposes. E.g. Mailing Addresses, Billing Addresses, Contact numbers for Booking or Billing Enquiries, general web address, web address for online bookings etc.
Need to keep track of assigned contact points within bigger organization.
The telecom of an organization can never be of use 'home'
The address of an organization can never be of use 'home'
If no purpose is defined, then these contact details may be used for any purpose.
The purpose for which an extended contact detail should be used.
The name of an individual to contact, some types of contact detail are usually blank.
If there is no named individual, the telecom/address information is not generally monitored by a specific individual.
The contact details application for the purpose defined.
phone | fax | email | pager | url | sms | other
Telecommunications form for contact point - what communications system is required to make use of the contact.
Telecommunications form for contact point.
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Need to support legacy numbers that are not in a tightly controlled format.
home | work | temp | old | mobile - purpose of this contact point
Identifies the purpose for the contact point.
Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one
Specify preferred order of use (1 = highest)
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Ranks need not be unique. E.g. it's possible to have multiple contacts with rank=1. If the ranks have different systems or uses, this would be interpreted to mean "X is my most preferred phone number, Y is my most preferred email address" or "X is my preferred home email and Y is my preferred work email". If the system and use for equally-ranked contacts are the same, then the level of preference is equivalent for both repetitions. Ranks need not be sequential and not all repetitions must have a rank. For example, it's possible to have 4 contacts with ranks of 2, 5 and two with no rank specified. That would be interpreted to mean the first is preferred over the second and no preference stated for the remaining contacts.
Time period when the contact point was/is in use
Time period when the contact point was/is in use.
More than 1 address would be for different purposes, and thus should be entered as a different entry,.
This contact detail is handled/monitored by a specific organization
This contact detail is handled/monitored by a specific organization. If the name is provided in the contact, then it is referring to the named individual within this organization.
Some specific types of contact information can be an handled by an organization (eg legal council is via a specific firm).
Period that this contact was valid for usage
Period that this contact was valid for usage.
If the details have multiple periods, then enter in a new ExtendedContact with the new period.
The organization of which this organization forms a part
The organization of which this organization forms a part.
Need to be able to track the hierarchy of organizations within an organization.
Technical endpoints providing access to services operated for the organization
Technical endpoints providing access to services operated for the organization.
Organizations have multiple systems that provide various services and need to be able to define the technical connection details for how to connect to them, and for what purpose.
Licence(s) to provide healthcare service. (ee TEGEVUSLUBA)
Period during which healthcare provision licence is STOPPED.
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Number of the licence. (ee TEGEVUSLOA NUMBER)
An identifier allocated to this qualification for this organization.
Often, specific identities are assigned for the qualification by the assigning organization.
Identifier of hcp licence. (ee TERVISEAMETI LITSENTSI NUMBER)
Identifier of pharmacy licence. (ee Apteegi tegevusluba on KOLMEKOHALINE NUMBER mis erineb tegevuskoha koodist.)
Field of services this licence allows. (ee TEGEVUSLOA LIIK)
Specific qualification the organization has to provide a service.
Period of the licence validity. (ee TEGEVUSLOA KEHTIVUS)
Qualifications are often for a limited period of time, and can be revoked.
The start of the period. The boundary is inclusive.
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The 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
Organization that regulates and issues the qualification
Organization that regulates and issues the qualification.