Procedure
Estrutura FHIR para troca de informações de procedimentos realizados em membros da Sami.
OBS: As informações são compartilhadas apenas perante o consentimento prévio do membro.
Snapshot
Procedure | I | Procedure | |
id | Σ | 0..1 | string |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | I | 0..* | Extension |
ProcedureQuantity | I | 0..* | Extension |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | ||
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
modifierExtension | ?! I | 0..* | Extension |
identifier | Σ | 0..0 | Identifier |
instantiatesCanonical | Σ | 0..0 | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
instantiatesUri | Σ | 0..0 | uri |
basedOn | Σ I | 0..0 | Reference(CarePlan | ServiceRequest) |
partOf | Σ I | 0..0 | Reference(Procedure | Observation | MedicationAdministration) |
status | Σ ?! | 1..1 | codeBinding |
statusReason | Σ | 0..0 | CodeableConcept |
category | Σ | 0..1 | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..0 | uri |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..1 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
code | Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..0 | uri |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..1 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
subject | Σ I | 1..1 | Reference(Patient | Group) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
encounter | Σ I | 0..1 | Reference(Encounter) |
performed[x] | Σ | 0..1 | |
performedDateTime | dateTime | ||
performedPeriod | Period | ||
performedString | string | ||
performedAge | Age | ||
performedRange | Range | ||
recorder | Σ I | 0..0 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
asserter | Σ I | 0..0 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
performer | Σ | 0..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
function | Σ | 0..0 | CodeableConcept |
actor | Σ I | 1..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | stringFixed Value |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
onBehalfOf | I | 0..0 | Reference(Organization) |
location | Σ I | 0..0 | Reference(Location) |
reasonCode | Σ | 0..0 | CodeableConcept |
reasonReference | Σ I | 0..0 | Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
bodySite | Σ | 0..0 | CodeableConcept |
outcome | Σ | 0..1 | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..0 | uri |
version | Σ | 0..0 | string |
code | Σ | 0..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
report | I | 0..0 | Reference(DiagnosticReport | DocumentReference | Composition) |
complication | 0..0 | CodeableConcept | |
complicationDetail | I | 0..* | Reference(Condition) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
followUp | 0..0 | CodeableConcept | |
note | 0..0 | Annotation | |
focalDevice | 0..0 | BackboneElement | |
usedReference | I | 0..0 | Reference(Device | Medication | Substance) |
usedCode | 0..0 | CodeableConcept |
Procedure | .. | |
Procedure.extension | 0.. | |
Procedure.extension | Extension | 0..* |
Procedure.extension.value[x] | .. | |
Procedure.identifier | ..0 | |
Procedure.instantiatesCanonical | ..0 | |
Procedure.instantiatesUri | ..0 | |
Procedure.basedOn | ..0 | |
Procedure.partOf | ..0 | |
Procedure.status | .. | |
Procedure.statusReason | ..0 | |
Procedure.category | .. | |
Procedure.category.coding | .. | |
Procedure.category.coding.system | ..0 | |
Procedure.category.coding.version | ..0 | |
Procedure.category.coding.code | .. | |
Procedure.category.coding.display | .. | |
Procedure.category.coding.userSelected | ..0 | |
Procedure.category.text | ..0 | |
Procedure.code | .. | |
Procedure.code.coding | .. | |
Procedure.code.coding.system | ..0 | |
Procedure.code.coding.version | ..0 | |
Procedure.code.coding.code | .. | |
Procedure.code.coding.display | .. | |
Procedure.code.coding.userSelected | ..0 | |
Procedure.code.text | ..0 | |
Procedure.subject | .. | |
Procedure.subject.reference | .. | |
Procedure.subject.type | .. | |
Procedure.subject.identifier | ..0 | |
Procedure.subject.display | ..0 | |
Procedure.encounter | .. | |
Procedure.performed[x] | .. | |
Procedure.recorder | ..0 | |
Procedure.asserter | ..0 | |
Procedure.performer | .. | |
Procedure.performer.function | ..0 | |
Procedure.performer.actor | .. | |
Procedure.performer.actor.reference | .. | |
Procedure.performer.actor.type | .. | |
Procedure.performer.actor.identifier | ..0 | |
Procedure.performer.actor.display | ..0 | |
Procedure.performer.onBehalfOf | ..0 | |
Procedure.location | ..0 | |
Procedure.reasonCode | ..0 | |
Procedure.reasonReference | ..0 | |
Procedure.bodySite | ..0 | |
Procedure.outcome | .. | |
Procedure.outcome.coding | .. | |
Procedure.outcome.coding.system | ..0 | |
Procedure.outcome.coding.version | ..0 | |
Procedure.outcome.coding.code | .. | |
Procedure.outcome.coding.display | .. | |
Procedure.outcome.coding.userSelected | ..0 | |
Procedure.outcome.text | ..0 | |
Procedure.report | ..0 | |
Procedure.complication | ..0 | |
Procedure.complicationDetail | .. | |
Procedure.complicationDetail.reference | .. | |
Procedure.complicationDetail.type | .. | |
Procedure.complicationDetail.identifier | ..0 | |
Procedure.complicationDetail.display | ..0 | |
Procedure.followUp | ..0 | |
Procedure.note | ..0 | |
Procedure.focalDevice | ..0 | |
Procedure.usedReference | ..0 | |
Procedure.usedCode | ..0 |
Procedure | |
Definition | Uma ação que é ou foi executada em ou para um paciente. Pode ser uma intervenção física, como uma cirurgia, ou menos invasiva, como serviços de longo prazo, consultas, aconselhamento ou hipnoterapia, etc. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Procedure.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Procedure.meta | |
Definition | 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.implicitRules | |
Definition | 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Mappings |
|
Procedure.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Procedure.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.extension:ProcedureQuantity | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Procedure.extension:ProcedureQuantity.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.extension:ProcedureQuantity.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.extension:ProcedureQuantity.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://example.org/fhir/StructureDefinition/procedure-quantity |
Mappings |
|
Procedure.extension:ProcedureQuantity.value[x] | |
Definition | Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista). |
Cardinality | 0...1 |
Type | base64Binary |
Invariants |
|
Mappings |
|
Procedure.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.identifier | |
Definition | Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Requirements | Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers. |
Comments | This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number. |
Invariants |
|
Mappings |
|
Procedure.instantiatesCanonical | |
Definition | The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0...0 |
Type | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
Summary | True |
Comments | |
Invariants |
|
Mappings |
|
Procedure.instantiatesUri | |
Definition | The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0...0 |
Type | uri |
Summary | True |
Comments | This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
Invariants |
|
Mappings |
|
Procedure.basedOn | |
Definition | A reference to a resource that contains details of the request for this procedure. |
Cardinality | 0...0 |
Type | Reference(CarePlan | ServiceRequest) |
Summary | True |
Alias | fulfills |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.partOf | |
Definition | A larger event of which this particular procedure is a component or step. |
Cardinality | 0...0 |
Type | Reference(Procedure | Observation | MedicationAdministration) |
Summary | True |
Alias | container |
Comments | The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration). |
Invariants |
|
Mappings |
|
Procedure.status | |
Definition | Um código que especifica o estado do procedimento. Geralmente, este será o estado em andamento ou concluído. |
Cardinality | 1...1 |
Type | code |
Binding | Um código que especifica o estado do procedimento. |
Modifier | True |
Summary | True |
Comments | O código "desconhecido" não deve ser usado para transmitir outros status. O código "desconhecido" deve ser usado quando um dos status se aplica, mas o sistema de autoria não conhece o estado atual do procedimento. Este elemento é rotulado como um modificador porque o status contém códigos que marcam o recurso como não válido no momento. |
Invariants |
|
Mappings |
|
Procedure.statusReason | |
Definition | Captures the reason for the current state of the procedure. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure was not performed. |
Summary | True |
Alias | Suspended Reason, Cancelled Reason |
Comments | This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. |
Invariants |
|
Mappings |
|
Procedure.category | |
Definition | Um código que classifica o procedimento para fins de pesquisa, classificação e exibição (por exemplo, "Procedimento cirúrgico"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Um código que classifica um procedimento para fins de pesquisa, classificação e exibição. |
Summary | True |
Comments | Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação. |
Invariants |
|
Mappings |
|
Procedure.category.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.category.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.category.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Binding | condition-status (required) |
Summary | True |
Requirements | Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Procedure.category.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.category.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.category.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...0 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.category.coding.version | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.category.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | condition-status (required) |
Summary | True |
Requirements | Precisa se referir a um código específico no sistema. |
Comments | Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho |
Invariants |
|
Mappings |
|
Procedure.category.coding.display | |
Definition | Uma representação do significado do código no sistema, seguindo as regras do sistema. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema. |
Comments | Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho. |
Invariants |
|
Mappings |
|
Procedure.category.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.category.text | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.code | |
Definition | O procedimento específico executado. Use texto se a natureza exata do procedimento não puder ser codificada (por exemplo, "Apendicectomia laparoscópica"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Um código para identificar um procedimento específico. |
Summary | True |
Alias | type |
Requirements | 0..1 para contabilizar principalmente recursos narrativos apenas. |
Comments | Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação. |
Invariants |
|
Mappings |
|
Procedure.code.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.code.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.code.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Binding | Código TUSS do Procedimento |
Summary | True |
Requirements | Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Procedure.code.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.code.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.code.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...0 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.coding.version | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | Código TUSS do Procedimento |
Summary | True |
Requirements | Precisa se referir a um código específico no sistema. |
Comments | Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho |
Invariants |
|
Mappings |
|
Procedure.code.coding.display | |
Definition | Uma representação do significado do código no sistema, seguindo as regras do sistema. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema. |
Comments | Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho |
Invariants |
|
Mappings |
|
Procedure.code.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.text | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.subject | |
Definition | A pessoa, animal ou grupo no qual o procedimento foi realizado. |
Cardinality | 1...1 |
Type | Reference(Patient | Group) |
Summary | True |
Alias | patient |
Comments | As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local. |
Invariants |
|
Mappings |
|
Procedure.subject.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.subject.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.subject.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Procedure.subject.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Invariants |
|
Mappings |
|
Procedure.subject.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Procedure.subject.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Procedure.encounter | |
Definition | O Encontro durante o qual este Procedimento foi criado ou executado ou ao qual a criação deste registro está estreitamente associada. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Summary | True |
Comments | Normalmente será o encontro em que o evento ocorreu, mas algumas atividades podem ser iniciadas antes ou depois da conclusão oficial de um encontro, mas ainda assim estar vinculadas ao contexto do encontro. |
Invariants |
|
Mappings |
|
Procedure.performed[x] | |
Definition | Data estimada ou real, data-hora, período ou idade em que o procedimento foi realizado. Permite um período para suportar procedimentos complexos que abrangem mais de uma data e também permite que a duração do procedimento seja capturada. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | A idade é geralmente usada quando o paciente relata a idade em que o procedimento foi realizado. A faixa é geralmente usada quando o paciente relata uma faixa etária quando o procedimento foi realizado, como em algum momento entre 20-25 anos de idade. dateTime oferece suporte a uma faixa de precisão devido a alguns procedimentos sendo relatados como procedimentos anteriores que podem não ter precisão de milissegundos, enquanto outros procedimentos executados e documentados durante o encontro podem ter carimbos de data / hora UTC mais precisos com fuso horário. |
Invariants |
|
Mappings |
|
Procedure.recorder | |
Definition | Individual who recorded the record and takes responsibility for its content. |
Cardinality | 0...0 |
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.asserter | |
Definition | Individual who is making the procedure statement. |
Cardinality | 0...0 |
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performer | |
Definition | Limitado a pessoas "reais" e não a equipamentos. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.performer.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.performer.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performer.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Procedure.performer.function | |
Definition | Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | A code that identifies the role of a performer of the procedure. |
Summary | True |
Requirements | Allows disambiguation of the types of involvement of different performers. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.performer.actor | |
Definition | The practitioner who was involved in the procedure. |
Cardinality | 1...1 |
Type | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) |
Summary | True |
Requirements | A reference to Device supports use cases, such as pacemakers. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performer.actor.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.performer.actor.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performer.actor.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Fixed Value | Practitioner |
Mappings |
|
Procedure.performer.actor.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | Este elemento é usado para indicar o tipo de destino de referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela referência da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência acima fornecida, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Invariants |
|
Mappings |
|
Procedure.performer.actor.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Procedure.performer.actor.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Procedure.performer.onBehalfOf | |
Definition | The organization the device or practitioner was acting on behalf of. |
Cardinality | 0...0 |
Type | Reference(Organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.location | |
Definition | The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. |
Cardinality | 0...0 |
Type | Reference(Location) |
Summary | True |
Requirements | Ties a procedure to where the records are likely kept. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.reasonCode | |
Definition | The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure is required. |
Summary | True |
Comments | Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. |
Invariants |
|
Mappings |
|
Procedure.reasonReference | |
Definition | The justification of why the procedure was performed. |
Cardinality | 0...0 |
Type | Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
Summary | True |
Comments | It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use). Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure. |
Invariants |
|
Mappings |
|
Procedure.bodySite | |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. |
Summary | True |
Comments | If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension procedure-targetbodystructure. |
Invariants |
|
Mappings |
|
Procedure.outcome | |
Definition | O resultado do procedimento - resolveu as razões para o procedimento que está sendo executado? |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Um resultado de um procedimento - se foi resolvido ou não. |
Summary | True |
Comments | If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.outcome.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.outcome.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.outcome.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Binding | resolution-state (example) |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.outcome.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...0 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.version | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | resolution-state (example) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.display | |
Definition | Uma representação do significado do código no sistema, seguindo as regras do sistema. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema. |
Comments | Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho |
Invariants |
|
Mappings |
|
Procedure.outcome.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.outcome.text | |
Definition | 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. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.report | |
Definition | This could be a histology result, pathology report, surgical report, etc. |
Cardinality | 0...0 |
Type | Reference(DiagnosticReport | DocumentReference | Composition) |
Comments | There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
Invariants |
|
Mappings |
|
Procedure.complication | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | Codes describing complications that resulted from a procedure. |
Comments | If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. |
Cardinality | 0...* |
Type | Reference(Condition) |
Requirements | This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.complicationDetail.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.complicationDetail.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Procedure.complicationDetail.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Procedure.followUp | |
Definition | If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | Specific follow up required for a procedure e.g. removal of sutures. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.note | |
Definition | Any other notes and comments about the procedure. |
Cardinality | 0...0 |
Type | Annotation |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
Procedure.focalDevice | |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Cardinality | 0...0 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Procedure.focalDevice.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Procedure.focalDevice.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.focalDevice.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.action | |
Definition | The kind of change that happened to the device during the procedure. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A kind of change that happened to the device during the procedure. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.manipulated | |
Definition | The device that was manipulated (changed) during the procedure. |
Cardinality | 1...1 |
Type | Reference(Device) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.usedReference | |
Definition | Identifies medications, devices and any other substance used as part of the procedure. |
Cardinality | 0...0 |
Type | Reference(Device | Medication | Substance) |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|
Procedure.usedCode | |
Definition | Identifies coded items that were used as part of the procedure. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | Codes describing items used during a procedure. |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|
JSON
{ "resourceType": "StructureDefinition", "url": "https://www.samisaude.com.br/fhir/r4/StructureDefinition/MyProcedure", "name": "Procedimento", "status": "active", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Procedure", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Procedure", "derivation": "constraint", "differential": { "element": [ { "id": "Procedure", "path": "Procedure", "short": "Uma ação que está sendo ou foi realizada em um paciente", "definition": "Uma ação que é ou foi executada em ou para um paciente. Pode ser uma intervenção física, como uma cirurgia, ou menos invasiva, como serviços de longo prazo, consultas, aconselhamento ou hipnoterapia, etc." }, { "id": "Procedure.extension", "path": "Procedure.extension", "slicing": { "discriminator": [ { "type": "value", "path": "url" } ], "rules": "open" }, "min": 0 }, { "id": "Procedure.extension:ProcedureQuantity", "path": "Procedure.extension", "sliceName": "ProcedureQuantity", "min": 0, "max": "*", "type": [ { "code": "Extension", "profile": [ "https://example.org/fhir/StructureDefinition/procedure-quantity" ] } ] }, { "id": "Procedure.extension:ProcedureQuantity.value[x]", "path": "Procedure.extension.value[x]", "short": "Valor da Extensão: quantidade do procedimento", "definition": "Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista)." }, { "id": "Procedure.identifier", "path": "Procedure.identifier", "max": "0" }, { "id": "Procedure.instantiatesCanonical", "path": "Procedure.instantiatesCanonical", "max": "0" }, { "id": "Procedure.instantiatesUri", "path": "Procedure.instantiatesUri", "max": "0" }, { "id": "Procedure.basedOn", "path": "Procedure.basedOn", "max": "0" }, { "id": "Procedure.partOf", "path": "Procedure.partOf", "max": "0" }, { "id": "Procedure.status", "path": "Procedure.status", "short": "Concluído | Solicitado | Suspenso | Falta do Paciente | Cancelado | Desconhecido", "definition": "Um código que especifica o estado do procedimento. Geralmente, este será o estado em andamento ou concluído.", "comment": "O código \"desconhecido\" não deve ser usado para transmitir outros status. O código \"desconhecido\" deve ser usado quando um dos status se aplica, mas o sistema de autoria não conhece o estado atual do procedimento.\n\nEste elemento é rotulado como um modificador porque o status contém códigos que marcam o recurso como não válido no momento.", "isModifierReason": "Este elemento é rotulado como um modificador porque é um elemento de status que contém o status inserido com erro, o que significa que o recurso não deve ser tratado como válido.", "binding": { "strength": "required", "description": "Um código que especifica o estado do procedimento.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/procedure-status" } }, { "id": "Procedure.statusReason", "path": "Procedure.statusReason", "max": "0" }, { "id": "Procedure.category", "path": "Procedure.category", "short": "Classificação do procedimento", "definition": "Um código que classifica o procedimento para fins de pesquisa, classificação e exibição (por exemplo, \"Procedimento cirúrgico\").", "comment": "Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação.", "binding": { "strength": "example", "description": "Um código que classifica um procedimento para fins de pesquisa, classificação e exibição.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/condition-status" } }, { "id": "Procedure.category.coding", "path": "Procedure.category.coding", "short": "Código definido por um sistema de terminologia", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true.", "requirements": "Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código.", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/condition-status" } }, { "id": "Procedure.category.coding.system", "path": "Procedure.category.coding.system", "max": "0" }, { "id": "Procedure.category.coding.version", "path": "Procedure.category.coding.version", "max": "0" }, { "id": "Procedure.category.coding.code", "path": "Procedure.category.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "comment": "Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho", "requirements": "Precisa se referir a um código específico no sistema.", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/condition-status" } }, { "id": "Procedure.category.coding.display", "path": "Procedure.category.coding.display", "short": "Representação definida pelo sistema", "definition": "Uma representação do significado do código no sistema, seguindo as regras do sistema.", "comment": "Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho.", "requirements": "Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema." }, { "id": "Procedure.category.coding.userSelected", "path": "Procedure.category.coding.userSelected", "max": "0" }, { "id": "Procedure.category.text", "path": "Procedure.category.text", "max": "0" }, { "id": "Procedure.code", "path": "Procedure.code", "short": "Identificação do Procedimento", "definition": "O procedimento específico executado. Use texto se a natureza exata do procedimento não puder ser codificada (por exemplo, \"Apendicectomia laparoscópica\").", "comment": "Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação.", "requirements": "0..1 para contabilizar principalmente recursos narrativos apenas.", "binding": { "strength": "required", "description": "Um código para identificar um procedimento específico.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/tuss" } }, { "id": "Procedure.code.coding", "path": "Procedure.code.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true.", "requirements": "Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código.", "binding": { "strength": "required", "description": "Código TUSS do Procedimento", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/tuss" } }, { "id": "Procedure.code.coding.system", "path": "Procedure.code.coding.system", "max": "0" }, { "id": "Procedure.code.coding.version", "path": "Procedure.code.coding.version", "max": "0" }, { "id": "Procedure.code.coding.code", "path": "Procedure.code.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "comment": "Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho", "requirements": "Precisa se referir a um código específico no sistema.", "binding": { "strength": "required", "description": "Código TUSS do Procedimento", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/tuss" } }, { "id": "Procedure.code.coding.display", "path": "Procedure.code.coding.display", "short": "Representação definida pelo sistema", "definition": "Uma representação do significado do código no sistema, seguindo as regras do sistema.", "comment": "Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho", "requirements": "Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema." }, { "id": "Procedure.code.coding.userSelected", "path": "Procedure.code.coding.userSelected", "max": "0" }, { "id": "Procedure.code.text", "path": "Procedure.code.text", "max": "0" }, { "id": "Procedure.subject", "path": "Procedure.subject", "short": "Em quem o procedimento foi realizado", "definition": "A pessoa, animal ou grupo no qual o procedimento foi realizado.", "comment": "As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local." }, { "id": "Procedure.subject.reference", "path": "Procedure.subject.reference", "short": "Patient", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Procedure.subject.type", "path": "Procedure.subject.type", "short": "Patient", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Procedure.subject.identifier", "path": "Procedure.subject.identifier", "max": "0" }, { "id": "Procedure.subject.display", "path": "Procedure.subject.display", "max": "0" }, { "id": "Procedure.encounter", "path": "Procedure.encounter", "short": "Encontro criado como parte de", "definition": "O Encontro durante o qual este Procedimento foi criado ou executado ou ao qual a criação deste registro está estreitamente associada.", "comment": "Normalmente será o encontro em que o evento ocorreu, mas algumas atividades podem ser iniciadas antes ou depois da conclusão oficial de um encontro, mas ainda assim estar vinculadas ao contexto do encontro." }, { "id": "Procedure.performed[x]", "path": "Procedure.performed[x]", "short": "Quando o procedimento foi realizado", "definition": "Data estimada ou real, data-hora, período ou idade em que o procedimento foi realizado. Permite um período para suportar procedimentos complexos que abrangem mais de uma data e também permite que a duração do procedimento seja capturada.", "comment": "A idade é geralmente usada quando o paciente relata a idade em que o procedimento foi realizado. A faixa é geralmente usada quando o paciente relata uma faixa etária quando o procedimento foi realizado, como em algum momento entre 20-25 anos de idade. dateTime oferece suporte a uma faixa de precisão devido a alguns procedimentos sendo relatados como procedimentos anteriores que podem não ter precisão de milissegundos, enquanto outros procedimentos executados e documentados durante o encontro podem ter carimbos de data / hora UTC mais precisos com fuso horário." }, { "id": "Procedure.recorder", "path": "Procedure.recorder", "max": "0" }, { "id": "Procedure.asserter", "path": "Procedure.asserter", "max": "0" }, { "id": "Procedure.performer", "path": "Procedure.performer", "short": "As pessoas que realizaram o procedimento", "definition": "Limitado a pessoas \"reais\" e não a equipamentos." }, { "id": "Procedure.performer.function", "path": "Procedure.performer.function", "max": "0" }, { "id": "Procedure.performer.actor.reference", "path": "Procedure.performer.actor.reference", "short": "Practitioner", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful.", "fixedString": "Practitioner" }, { "id": "Procedure.performer.actor.type", "path": "Procedure.performer.actor.type", "short": "Practitioner", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino de referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela referência da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência acima fornecida, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Procedure.performer.actor.identifier", "path": "Procedure.performer.actor.identifier", "max": "0" }, { "id": "Procedure.performer.actor.display", "path": "Procedure.performer.actor.display", "max": "0" }, { "id": "Procedure.performer.onBehalfOf", "path": "Procedure.performer.onBehalfOf", "max": "0" }, { "id": "Procedure.location", "path": "Procedure.location", "max": "0" }, { "id": "Procedure.reasonCode", "path": "Procedure.reasonCode", "max": "0" }, { "id": "Procedure.reasonReference", "path": "Procedure.reasonReference", "max": "0" }, { "id": "Procedure.bodySite", "path": "Procedure.bodySite", "max": "0" }, { "id": "Procedure.outcome", "path": "Procedure.outcome", "short": "Resultado do procedimento", "definition": "O resultado do procedimento - resolveu as razões para o procedimento que está sendo executado?", "binding": { "strength": "example", "description": "Um resultado de um procedimento - se foi resolvido ou não.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/resolution-state" } }, { "id": "Procedure.outcome.coding", "path": "Procedure.outcome.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "binding": { "strength": "example", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/resolution-state" } }, { "id": "Procedure.outcome.coding.system", "path": "Procedure.outcome.coding.system", "max": "0" }, { "id": "Procedure.outcome.coding.version", "path": "Procedure.outcome.coding.version", "max": "0" }, { "id": "Procedure.outcome.coding.code", "path": "Procedure.outcome.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "binding": { "strength": "example", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/resolution-state" } }, { "id": "Procedure.outcome.coding.display", "path": "Procedure.outcome.coding.display", "short": "Representação definida pelo sistema", "definition": "Uma representação do significado do código no sistema, seguindo as regras do sistema.", "comment": "Observe que as strings FHIR NÃO DEVEM exceder 1 MB de tamanho", "requirements": "Precisa ser capaz de transportar um significado legível do código para leitores que não conhecem o sistema." }, { "id": "Procedure.outcome.coding.userSelected", "path": "Procedure.outcome.coding.userSelected", "max": "0" }, { "id": "Procedure.outcome.text", "path": "Procedure.outcome.text", "max": "0" }, { "id": "Procedure.report", "path": "Procedure.report", "max": "0" }, { "id": "Procedure.complication", "path": "Procedure.complication", "max": "0" }, { "id": "Procedure.complicationDetail.reference", "path": "Procedure.complicationDetail.reference", "short": "Condition", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Procedure.complicationDetail.type", "path": "Procedure.complicationDetail.type", "short": "Condition", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Procedure.complicationDetail.identifier", "path": "Procedure.complicationDetail.identifier", "max": "0" }, { "id": "Procedure.complicationDetail.display", "path": "Procedure.complicationDetail.display", "max": "0" }, { "id": "Procedure.followUp", "path": "Procedure.followUp", "max": "0" }, { "id": "Procedure.note", "path": "Procedure.note", "max": "0" }, { "id": "Procedure.focalDevice", "path": "Procedure.focalDevice", "max": "0" }, { "id": "Procedure.usedReference", "path": "Procedure.usedReference", "max": "0" }, { "id": "Procedure.usedCode", "path": "Procedure.usedCode", "max": "0" } ] } }