Narrativa gerada: StructureDefinition br-core-vitalsigns Nome Bandeiras Card. Tipo Descrição e condicionalismos Observation observation-vitalsigns #xD; id 0..1 id Identificador lógico deste artefato #xD; meta 0..1 Meta Metadados sobre o recurso #xD; implicitRules 0..1 uri Um conjunto de regras sob as quais este conteúdo foi criado #xD; language 0..1 code Idioma do recurso #xD; text 0..1 Narrative Resumo do texto do recurso em linguagem natural #xD; contained 0..* Resource Contained, inline Resources #xD; extension 0..* Extension Extension #xD; modifierExtension 0..* Extension Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas #xD; identifier 0..* Identifier Identificadores externos para este recurso #xD; basedOn 0..* Reference(BRCoreCarePlan | DeviceRequest | ImmunizationRecommendation | br-core-medicationrequest | NutritionOrder | BRCoreServiceRequest) Referência ao pedido ou ao plano de tratamento que gerou este recurso #xD; partOf 0..* Reference(br-core-medicationadministration | br-core-medicationdispense | br-core-medicationstatement | BRCoreProcedure | BRCoreImmunization | ImagingStudy) Referência ao evento do qual este recurso faz parte #xD; status 1..1 code Status atual da observação #xD; category 1..* CodeableConcept Categoria de alto nível da observação #xD; Fatias para category Conteúdo/regras para todas as fatias #xD; category:VSCat 1..1 CodeableConcept Classificação do tipo de observação #xD; id 0..1 string Identificador exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; coding 1..* Coding Código definido por uma terminologia #xD; id 0..1 string Identificador exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; system 1..1 uri Identidade do sistema de terminologia #xD; version 0..1 string Versão do sistema, se relevante #xD; code 1..1 code Símbolo na sintaxe definida pelo sistema #xD; display 0..1 string Representação definida pelo sistema #xD; userSelected 0..1 boolean Se a codificação foi escolhida diretamente pelo usuário #xD; text 0..1 string Representação em texto simples do conceito #xD; code 1..1 CodeableConcept Código definido pela sintaxe do sistema de terminologia Vínculo: BR Sinais Vitais (required) #xD; subject 1..1 Reference(BRCorePatient) Referência ao paciente desta observação #xD; focus 0..* Reference(Resource) Referência à recursos associados #xD; encounter 0..1 Reference(br-core-encounter) Referência ao atendimento desta observação #xD; effective[x] 1..1 dateTime, Period Tempo ou período de tempo clinicamente relevante para os sinais vitais #xD; issued 1..1 instant Data ou hora em que esta versão da observação ficou disponível #xD; performer 0..* Reference(BRCorePractitioner | BRCorePractitionerRole | BRCoreOrganization | CareTeam | BRCorePatient | BRCoreRelatedPerson) O responsável pela captura da observação #xD; value[x] 1..1 Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period Valor dos sinais vitais #xD; dataAbsentReason 0..1 CodeableConcept Por que o resultado não está disponível #xD; interpretation 0..* CodeableConcept Interpretação da observação #xD; note 0..* Annotation Comentários sobre a observação #xD; bodySite 0..1 CodeableConcept Local anatômico associado ao procedimento Vínculo: SNOMEDCTBodyStructures (preferred) #xD; method 0..1 CodeableConcept Método utilizado para capturar o sinal vital #xD; specimen 0..1 Reference(BRCoreSpecimen) Referência à amostra associada nesta observação #xD; device 0..1 Reference(Device | DeviceMetric) Referência ao dispositivo (de medida) associado nesta observação #xD; referenceRange 0..* BackboneElement Limites de referência #xD; id 0..1 string Identificador único para referência cruzada #xD; extension 0..* Extension Extensões adicionais que não fazem parte do modelo de dados básico #xD; modifierExtension 0..* Extension Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas #xD; low 0..1 SimpleQuantity Limite inferior do intervalo de valores de referência #xD; high 0..1 SimpleQuantity Limite superior do intervalo de referência #xD; type 0..1 CodeableConcept Qualificador do valor de referência #xD; appliesTo 0..* CodeableConcept População alvo do intervalo de referência #xD; age 0..1 Range Faixa etária aplicável ao intervalo de referência #xD; text 0..1 string Intervalo de referência em linguagen natural #xD; hasMember 0..* Reference(QuestionnaireResponse | MolecularSequence) Referências utilizadas para relatar componentes do painel de sinais vitais #xD; derivedFrom 0..* Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | BRCoreVitalSigns | MolecularSequence) Referência à medições relacionadas a partir das quais esta observação foi realizada #xD; component 0..* BackboneElement Utilizado para relatar pressão sistólica e diastólica #xD; id 0..1 string Identificador único para referência cruzada #xD; extension 0..* Extension Extensões adicionais que não fazem parte do modelo de dados básico #xD; modifierExtension 0..* Extension Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas #xD; code 1..1 CodeableConcept Tipo de observação de componente #xD; value[x] 0..1 Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period O valor do sinal vital #xD; dataAbsentReason 0..1 CodeableConcept Por que o resultado do componente está faltando #xD; interpretation 0..* CodeableConcept Interpretação da observação #xD; referenceRange 0..* Valores de referência #xD; Documentação para este formato
Este perfil é baseado no perfil [VitalSigns](http://hl7.org/fhir/R4/observation-vitalsigns.html) e define restrições adicionais no recurso Observation para representar Observation de sinais vitais. Ele especifica quais elementos principais, extensões, vocabulários e conjuntos de valores **DEVEM** estar presentes no recurso e restringe como os elementos são usados.
The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.
Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
dataAbsentReason SHALL only be present if Observation.value[x] is not present
dataAbsentReason.empty() or value.empty()
not(exists(f:dataAbsentReason)) or (not(exists(*[starts-with(local-name(.), 'value')])))
If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
value.empty() or component.code.where(coding.intersect(%resource.code.coding).exists()).empty()
not(f:*[starts-with(local-name(.), 'value')] and (for $coding in f:code/f:coding return f:component/f:code/f:coding[f:code/@value=$coding/f:code/@value] [f:system/@value=$coding/f:system/@value]))
If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
(component.empty() and hasMember.empty()) implies (dataAbsentReason.exists() or value.exists())
f:component or f:memberOF or f:*[starts-with(local-name(.), 'value')] or f:dataAbsentReason
Observation[classCode=OBS, moodCode=EVN]
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Um conjunto de regras sob as quais este conteúdo foi criado
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
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).
Resumo do texto do recurso em linguagem natural
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.
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.
Extensões adicionais que não fazem parte do modelo base
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identificadores externos para este recurso
Allows observations to be distinguished and referenced.
OBX.21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
Referência ao pedido ou ao plano de tratamento que gerou este recurso
Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.
Referência ao evento do qual este recurso faz parte
To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below for guidance on referencing another Observation.
active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Need to track the status of individual results. Some results are finalized before the whole report is finalized.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set.
Used for filtering what observations are retrieved and displayed.
Codes for high level observation categories.
.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
Identificador exclusivo para referência entre elementos
Extensions are always sliced by (at least) url
Conteúdo adicional definido por implementações
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
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.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
Símbolo na sintaxe definida pelo sistema
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
Se a codificação foi escolhida diretamente pelo usuário
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Representação em texto simples do conceito
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Código definido pela sintaxe do sistema de terminologia
*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.
5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).
< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.
Observations have no value if you don't know who or what they're about.
Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/extension-observation-focuscode.html).
Referência ao atendimento desta observação
This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
For some observations it may be important to know the link between an observation and a particular encounter.
inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
Tempo ou período de tempo clinicamente relevante para os sinais vitais
At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing](http://hl7.org/fhir/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.
Knowing when an observation was deemed true is important to its relevance as well as determining trends.
if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
$this is dateTime implies $this.toString().length() >= 10
f:effectiveDateTime[matches(@value, '^\d{4}-\d{2}-\d{2}')]
OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
Data ou hora em que esta versão da observação ficou disponível
For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.
OBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)
O responsável pela captura da observação
May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.
OBX.15 / (Practitioner) OBX-16, PRT-5:PRT-4='RO' / (Device) OBX-18 , PRT-10:PRT-4='EQUIP' / (Organization) OBX-23, PRT-8:PRT-4='PO'
An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.
9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).
Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.
For many results it is necessary to handle exceptional values in measurements.
Codes specifying why the result (`Observation.value[x]`) is missing.
Interpretação da observação. Por exemplo: valor alto, baixo, normal
Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.
Codes identifying interpretations of observations.
May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.
Need to be able to provide free text additional information.
NTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)
Local anatômico associado ao procedimento
Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/extension-bodysite.html).
Método utilizado para capturar o sinal vital
Only used if not implicit in code for Observation.code.
In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results.
Referência à amostra associada nesta observação
Should only be used if not implicit in code found in `Observation.code`. Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).
Referência ao dispositivo (de medida) associado nesta observação
Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant.
Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.
Must have at least a low or a high or text
low.exists() or high.exists() or text.exists()
(exists(f:low) or exists(f:high)or exists(f:text))
outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]
Identificador único para referência cruzada
Extensões adicionais que não fazem parte do modelo de dados básico
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Limite inferior do intervalo de valores de referência
Limite superior do intervalo de referência
This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed.
Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation.
Code for the meaning of a reference range.
< 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
População alvo do intervalo de referência
This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed.
Need to be able to identify the target population for proper interpretation.
Codes identifying the population the reference range applies to.
Faixa etária aplicável ao intervalo de referência
Intervalo de referência em linguagen natural
Referências utilizadas para relatar componentes do painel de sinais vitais
When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) into a final score and represent the score as an Observation.
Relationships established by OBX-4 usage
Referência à medições relacionadas a partir das quais esta observação foi realizada
All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below.
Utilizado para relatar pressão sistólica e diastólica
For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.
Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.
If there is no a value a data absent reason must be present
value.exists() or dataAbsentReason.exists()
f:*[starts-with(local-name(.), 'value')] or f:dataAbsentReason
Describes what was observed. Sometimes this is called the observation "code".
*All* code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.
Knowing what kind of observation is being made is essential to understanding the observation.
This identifies the vital sign result type.
Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.
Common UCUM units for recording Vital Signs.
363714003 |Interprets| < 441742003 |Evaluation finding|
Por que o resultado do componente está faltando
"Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "test not done". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Because of these options, use-case agreements are required to interpret general observations for exceptional values.
Interpretação da observação. Por exemplo: valor elevado