Profile/SchedulePTCore.StructureDefinition.json
SchedulePTCore (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 | Σ | 1..1 | id | There are no (further) constraints on this element 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. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | MetaPTCore | 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 it's 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
| |
text | 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 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, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
|
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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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
|
serviceTypePTExtension | I | 0..* | Extension(Reference(https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/HealthcareServicePTCore)) | Element idSchedule.extension:serviceTypePTExtension Optional Extensions Element Alternate namesextensions, user content DefinitionReferencia para o HealthcareService para identificar o serviço de saúde. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/HealthcareServicePTCore)) Extension URLhttps://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/ServiceTypePTExtension Constraints
|
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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | ExtensionIdentifierPTCore | Element idSchedule.identifier An identifier intended for computation DefinitionIdentificadores da agenda na entidade local.
|
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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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..1 | codeBinding | There are no (further) constraints on this element Element idSchedule.identifier.use usual | official | temp | secondary | old (If known) DefinitionPropósito do identificador: official: O identificador considerado mais fiável para a identificação do item. temp: Um identificador temporário. secondary: Um identificador que foi atribuído para identificar o item em um contexto relativo, mas não pode usado em um contexto diferente. old: O identificador já não é considerado válido, mas pode ser relevante para fins de pesquisa. 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.
|
type | Σ | 0..1 | CodeableConceptPTCoreBinding | There are no (further) constraints on this element Element idSchedule.identifier.type Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Allows users to make use of identifiers when the identifier system is not known. Value Set: ExtensionIdentifierType ExtensionIdentifierType (extensible) Constraints
|
id | 0..1 | id | There are no (further) constraints on this element Element idSchedule.identifier.type.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.type.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.identifier.type.coding A reference to a 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.
|
id | 0..1 | id | Element idSchedule.identifier.type.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.identifier.type.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | uri | There are no (further) constraints on this element Element idSchedule.identifier.type.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. 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 reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idSchedule.identifier.type.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element idSchedule.identifier.type.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. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.identifier.type.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. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idSchedule.identifier.type.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 | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.identifier.type.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.
|
system | Σ | 0..1 | 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, a 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. Para sistemas geridos pela SPMS o system tem de seguir a seguinte estrutura: http://spms.min-saude.pt/<sistema>/identifiers/<identifier-id>
General http://www.acme.com/identifiers/patient Mappings
|
value | Σ | 1..1 | string | There are no (further) constraints on this element 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. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. 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.
General 123456 Mappings
|
period | Σ I | 0..1 | PeriodPTCore | There are no (further) constraints on this element Element idSchedule.identifier.period Time range defined by start and end date/time Alternate namesPeriod DefinitionA time period defined by a start and end date and optionally time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..0 | Reference(OrganizationPTCore) | 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 | Σ ?! | 0..1 | boolean | Element idSchedule.active Whether this schedule is in active use DefinitionIdentificar se esta agenda está ativa. 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 | Σ | 0..* | CodeableConceptPTCore | Element idSchedule.serviceCategory Concept - reference to a terminology or just text DefinitionCategorização do serviço. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Unordered, Open, by id(Value) Binding Constraints
|
valencia | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:valencia Concept - reference to a terminology or just text DefinitionNo caso de serviços associados à prestação de cuidados de saúde tem de ser utilizado o conceito de valência conforme valores disponibilizados pela ACSS. O system deve corresponder a https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:valencia.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. valencia
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:valencia.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:valencia.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:valencia.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.
|
subvalencia | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:subvalencia Concept - reference to a terminology or just text DefinitionNo caso de serviços associados à prestação de cuidados de saúde tem de ser utilizado o conceito de sub-valênciacia conforme valores disponibilizados pela ACSS. O system deve corresponder a https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:subvalencia.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. subvalencia
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:subvalencia.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:subvalencia.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:subvalencia.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.
|
patientEncounterStatus | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:patientEncounterStatus Concept - reference to a terminology or just text DefinitionTipo de Atendimento Value Set Name: Patient Encounter Status https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:patientEncounterStatus.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. 2.16.620.1.101.10.4.7.9
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:patientEncounterStatus.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:patientEncounterStatus.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:patientEncounterStatus.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.
|
indirectEncounter | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:indirectEncounter Concept - reference to a terminology or just text DefinitionMeio Utilizado Value Set Name: Indirect Encounter https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:indirectEncounter.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. 2.16.620.1.101.10.4.7.6
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:indirectEncounter.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:indirectEncounter.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:indirectEncounter.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.
|
encounterPresence | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:encounterPresence Concept - reference to a terminology or just text DefinitionIndicação da Presença Física Value Set Name: Encounter Presence https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:encounterPresence.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. encounterPresence
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:encounterPresence.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:encounterPresence.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:encounterPresence.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.
|
communicationType | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.serviceCategory:communicationType Concept - reference to a terminology or just text DefinitionTipo de Comunicação Value Set Name: Communication Type https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:communicationType.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. communicationType
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:communicationType.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.serviceCategory:communicationType.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:communicationType.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.
|
program | Σ | 0..* | CodeableConceptBinding | Element idSchedule.serviceCategory:program High-level category DefinitionA broad categorization of the service that is to be performed during this appointment. Value Set Name: Program https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude (required) Constraints
|
id | 0..1 | idFixed Value | Element idSchedule.serviceCategory:program.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. program
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.serviceCategory:program.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSchedule.serviceCategory:program.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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSchedule.serviceCategory:program.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 | Σ | 0..0 | CodeableConceptPTCore | Element idSchedule.serviceType Concept - reference to a terminology or just text DefinitionTipo de serviço que pode ser realizado, tipicamente associados ao tipo de atividade prestada (consulta, bloco, internamento, entre outros). Value Set Name: Service Type
|
specialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty Concept - reference to a terminology or just text DefinitionUtilizado para representar especialidades, sub-especialidades, títulos profissionais e competências que caracterizam a agenda. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Unordered, Open, by id(Value) BindingAdditional details about where the content was created (e.g. clinical specialty).
|
medicalPhysicsSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:medicalPhysicsSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Medical Physics Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:medicalPhysicsSpecialty.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. medicalPhysicsSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:medicalPhysicsSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:medicalPhysicsSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:medicalPhysicsSpecialty.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.
|
nursingSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:nursingSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Nursing Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:nursingSpecialty.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. nursingSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:nursingSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:nursingSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:nursingSpecialty.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.
|
dentistSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:dentistSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Dentist Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:dentistSpecialty.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. dentistSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:dentistSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:dentistSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:dentistSpecialty.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.
|
medicalSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:medicalSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Medical Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:medicalSpecialty.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. medicalSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:medicalSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:medicalSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:medicalSpecialty.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.
|
pharmaceuticalSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:pharmaceuticalSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Pharmaceutical Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:pharmaceuticalSpecialty.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. pharmaceuticalSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:pharmaceuticalSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:pharmaceuticalSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:pharmaceuticalSpecialty.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.
|
nutritionAndDieteticSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:nutritionAndDieteticSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Nutrition and Dietetic Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:nutritionAndDieteticSpecialty.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. nutritionAndDieteticSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:nutritionAndDieteticSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:nutritionAndDieteticSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:nutritionAndDieteticSpecialty.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.
|
psychologySpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:psychologySpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Psychology Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:psychologySpecialty.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. psychologySpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:psychologySpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:psychologySpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:psychologySpecialty.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.
|
physiotherapySpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:physiotherapySpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Physiotherapy Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:physiotherapySpecialty.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. physiotherapySpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:physiotherapySpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:physiotherapySpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:physiotherapySpecialty.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.
|
psychologySubSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:psychologySubSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Psychology Sub-Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:psychologySubSpecialty.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. psychologySubSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:psychologySubSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:psychologySubSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:psychologySubSpecialty.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.
|
medicalSubSpecialty | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:medicalSubSpecialty Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Medical Sub-Specialty Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:medicalSubSpecialty.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. medicalSubSpecialty
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:medicalSubSpecialty.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:medicalSubSpecialty.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:medicalSubSpecialty.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.
|
professionalTitle | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:professionalTitle Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Professional Title Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:professionalTitle.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. professionalTitle
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:professionalTitle.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:professionalTitle.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:professionalTitle.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.
|
medicalCompetence | Σ | 0..* | CodeableConceptPTCoreBinding | Element idSchedule.specialty:medicalCompetence Concept - reference to a terminology or just text DefinitionA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Value Set Name: Medical Competence Additional details about where the content was created (e.g. clinical specialty).
|
id | 0..1 | idFixed Value | Element idSchedule.specialty:medicalCompetence.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. medicalCompetence
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSchedule.specialty:medicalCompetence.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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that 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 | Σ | 0..* | CodingPTCore | There are no (further) constraints on this element Element idSchedule.specialty:medicalCompetence.coding A reference to a 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.
|
text | Σ | 1..1 | string | There are no (further) constraints on this element Element idSchedule.specialty:medicalCompetence.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.
|
actor | Σ I | 1..* | Reference(PatientPTCore | PractitionerPTCore | PractitionerRolePTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/RelatedPersonPTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/DevicePTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/HealthcareServicePTCore | LocationPTCore) | Element idSchedule.actor Resource(s) that availability information is being provided for DefinitionIdentifica o ator associado à agenda. Para referenciar a agenda do utente deve ser utilizado o recurso Patient, para referenciar a agenda da pessoa relacionada com o utente deve ser utilizado o recurso RelatedPerson, para referenciar a agenda do serviço deve ser utilizado o recurso HealthcareService, para referenciar a agenda do local deve ser utilizado o recurso Location, referenciar a agenda do profissional que exerce funções em determinada entidade deve ser utilizado o recurso PractitionerRole, para referenciar a agenda do equipamento ou dispositivo deve ser utilizado o recurso Device. 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. Reference(PatientPTCore | PractitionerPTCore | PractitionerRolePTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/RelatedPersonPTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/DevicePTCore | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/HealthcareServicePTCore | LocationPTCore) Constraints
|
planningHorizon | Σ I | 0..1 | PeriodPTCore | Element idSchedule.planningHorizon Time range defined by start and end date/time Alternate namesPeriod DefinitionPeríodo de tempo abrangido. Uma data ou data parcial ou data e hora, sendo o formato definido pela ISO8601. Se a hora e minutos forem especificados, descrição da time zone (UTC) DEVE ser preenchida. Os segundos devem ser fornecidos devido a restrições de tipo de esquema, mas podem ser preenchidos com zero. O horário "24:00" não é permitido. Formatos possíveis:
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
comment | 0..1 | string | Element idSchedule.comment Comments on availability DefinitionNotas adicionais à agenda, não identificadas noutra parte do recurso. Note that FHIR strings SHALL NOT exceed 1MB in size
|
Extensions
Nome | Descrição | URL |
---|---|---|
Service Type PT Extension | Referencia para o HealthcareService para indicar identificar o serviço de saúde. | https://spms.min-saude.pt/fhir-r4B/iop/StructureDefinition/ServiceTypePTExtension |
Binding
Path | Strength | ValueSet | Comment | Requirements |
---|---|---|---|---|
Schedule.serviceCategory valencia | required | https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf | O system deve corresponder a https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf | |
Schedule.serviceCategory subvalencia | required | https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf | O system deve corresponder a https://www.acss.min-saude.pt/circulares/Circular_Normativa/2015/Circular_Normativa_20_2015.pdf | |
Schedule.serviceCategory patientEncounterStatus | required | https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo | Value Set Name: Patient Encounter Status | |
Schedule.serviceCategory indirectEncounter | required | https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo | Value Set Name: Indirect Encounter | |
Schedule.serviceCategory encounterPresence | required | https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo | Value Set Name: Encounter Presence | |
Schedule.serviceCategory communicationType | required | https://www.ctc.min-saude.pt/catalogos/apoio-ao-registo-administrativo | Value Set Name: Communication Type | |
Schedule.serviceCategory program | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Program | |
Schedule.specialty medicalPhysicsSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Medical Physics Specialty | |
Schedule.specialty nursingSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Nursing Specialty | |
Schedule.specialty dentistSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Dentist Specialty | |
Schedule.specialty medicalSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Medical Specialty | |
Schedule.specialty pharmaceuticalSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Pharmaceutical Specialty | |
Schedule.specialty nutritionAndDieteticSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Nutrition and Dietetic Specialty | |
Schedule.specialty psychologySpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Psychology Specialty | |
Schedule.specialty physiotherapySpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Physiotherapy Specialty | |
Schedule.specialty psychologySubSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Psychology Sub-Specialty | |
Schedule.specialty medicalSubSpecialty | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Medical Sub-Specialty | |
Schedule.specialty professionalTitle | required | https://www.ctc.min-saude.pt/catalogos/categorias-profissionais-de-saude | Value Set Name: Professional Title | |
Schedule.specialty medicalCompetence | required | https://www.ctc.min-saude.pt/catalogos/especialidades-e-valencias-de-saude | Value Set Name: Medical Competence | |
Identifier.type | extensible | https://spms.min-saude.pt/iop/valueset/ExtensionIdentifierType | Value Set: ExtensionIdentifierType |
system
consultar Systems .Binding do FHIR Required
Path | Strength | ValueSet |
---|---|---|
Schedule: Identifier.use |
required |
IdentifierUse |
Identifiers Type
Estes Identificadores devem ser utilizados no elemento
identifier.type.coding[*]
Regras de implementação
Para além das constraints identificadas pelo FHIR para este recurso devem ser consideradas as constraints que identificamos na tabela infra.