ID lógico deste artefato

Metadados sobre este recurso

Um conjunto de regras sob as quais este conteúdo foi criado

Idioma do conteúdo do recurso

Resumo do texto do recurso, para interpretação humana

Recursos contidos neste artefato

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas

Identificador(es) das imagem (ns)

Procedimento que causou a criação desta mídia

Parte do evento referenciado

Status: preparação | em andamento | não feito | em espera | parou | concluído | inserido com erro | desconhecido

Código do tipo mídia

O tipo de equipamento/processo na aquisição da imagem

Projeção da imagem, por exemplo: lateral ou antero-posterior

De quem/o quê está registrado nesta mídia

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Tipo ao qual a referência se refere (por exemplo: Paciente)

Referência lógica, quando a referência literal não é conhecida

Texto alternativo para este recurso

Atendimento associado à esta mídia

Quando a mídia foi capturada

Data/hora em que esta versão foi disponibilizada

A pessoa responsável pela geração da imagem

Motivo pelo qual a mídia foi criada

Parte anatômica observada

Nome do dispositivo/fabricante

Dispositivo utilizado para capturar a imagem

Altura da imagem em pixels (foto/vídeo)

Largura da imagem em pixels (foto/vídeo)

Número de frames, se maior que 1 (foto)

Duração em segundos (áudio / vídeo)

Mídia - referência ou dado

Comentários sobre a mídia

A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference.

ID lógico deste artefato

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

Metadados sobre este recurso

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.

Idioma do conteúdo do recurso

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).

A human language.

Resumo do texto do recurso, para interpretação humana

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.

Recursos contidos neste artefato

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.

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas

Identificador(es) das imagem (ns)

The identifier label and use can be used to determine what kind of identifier it is.

Procedimento que causou a criação desta mídia

Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.

Parte do evento referenciado

Not to be used to link an event to an Encounter - use Media.encounter for that.

[The allowed reference resources may be adjusted as appropriate for the event resource].

E.g. Drug administration as part of a procedure, procedure as part of observation, etc.

Status: preparação | em andamento | não feito | em espera | parou | concluído | inserido com erro | desconhecido

A nominal state-transition diagram can be found in the [[event.html#statemachine | Event pattern]] documentation

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.

Codes identifying the lifecycle stage of an event.

Código do tipo mídia

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.

Codes for high level media categories.

Used for filtering what observations are retrieved and displayed.

O tipo de equipamento/processo na aquisição da imagem

Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it.

Projeção da imagem, por exemplo: lateral ou antero-posterior

Imaging view (projection) used when collecting an image.

De quem/o quê está registrado nesta mídia

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

Tipo ao qual a referência se refere (por exemplo: Paciente)

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Referência lógica, quando a referência literal não é conhecida

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).

Texto alternativo para este recurso

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.

Atendimento associado à esta mídia

This will typically be the encounter the media occurred within.

Links the Media to the Encounter context.

Quando a mídia foi capturada

Data/hora em que esta versão foi disponibilizada

It may be the same as the 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 does not require the new version to be reviewed and verified again.

A pessoa responsável pela geração da imagem

Motivo pelo qual a mídia foi criada

Textual reasons can be captured using reasonCode.text.

The reason for the media.

Parte anatômica observada

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.

Codes describing anatomical locations. May include laterality.

Nome do dispositivo/fabricante

Dispositivo utilizado para capturar a imagem

An extension should be used if further typing of the device is needed. Secondary devices used to support collecting a media can be represented using either extension or through the Observation.related element.

Altura da imagem em pixels (foto/vídeo)

Largura da imagem em pixels (foto/vídeo)

Número de frames, se maior que 1 (foto)

if the number of frames is not supplied, the value may be unknown. Applications should not assume that there is only one frame unless it is explicitly stated.

Duração em segundos (áudio / vídeo)

The duration might differ from occurrencePeriod if recording was paused.

Mídia - referência ou dado

Recommended content types: image/jpeg, image/png, image/tiff, video/mpeg, audio/mp4, application/dicom. Application/dicom can contain the transfer syntax as a parameter. For media that covers a period of time (video/sound), the content.creationTime is the end time. Creation time is used for tracking, organizing versions and searching.

Comentários sobre a mídia

Not to be used for observations, conclusions, etc. Instead use an Observation based on the Media/ImagingStudy resource.

A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference.

ID lógico deste artefato

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

Metadados sobre este recurso

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.

Idioma do conteúdo do recurso

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).

A human language.

Resumo do texto do recurso, para interpretação humana

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.

Recursos contidos neste artefato

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.

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas

Identificador(es) das imagem (ns)

The identifier label and use can be used to determine what kind of identifier it is.

Procedimento que causou a criação desta mídia

Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.

Parte do evento referenciado

Not to be used to link an event to an Encounter - use Media.encounter for that.

[The allowed reference resources may be adjusted as appropriate for the event resource].

E.g. Drug administration as part of a procedure, procedure as part of observation, etc.

Status: preparação | em andamento | não feito | em espera | parou | concluído | inserido com erro | desconhecido

A nominal state-transition diagram can be found in the [[event.html#statemachine | Event pattern]] documentation

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.

Codes identifying the lifecycle stage of an event.

Código do tipo mídia

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.

Codes for high level media categories.

Used for filtering what observations are retrieved and displayed.

O tipo de equipamento/processo na aquisição da imagem

Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it.

Projeção da imagem, por exemplo: lateral ou antero-posterior

Imaging view (projection) used when collecting an image.

De quem/o quê está registrado nesta mídia

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

Tipo ao qual a referência se refere (por exemplo: Paciente)

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Referência lógica, quando a referência literal não é conhecida

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).

Texto alternativo para este recurso

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.

Atendimento associado à esta mídia

This will typically be the encounter the media occurred within.

Links the Media to the Encounter context.

Quando a mídia foi capturada

Data/hora em que esta versão foi disponibilizada

It may be the same as the 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 does not require the new version to be reviewed and verified again.

A pessoa responsável pela geração da imagem

Motivo pelo qual a mídia foi criada

Textual reasons can be captured using reasonCode.text.

The reason for the media.

Parte anatômica observada

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.

Codes describing anatomical locations. May include laterality.

Nome do dispositivo/fabricante

Dispositivo utilizado para capturar a imagem

An extension should be used if further typing of the device is needed. Secondary devices used to support collecting a media can be represented using either extension or through the Observation.related element.

Altura da imagem em pixels (foto/vídeo)

Largura da imagem em pixels (foto/vídeo)

Número de frames, se maior que 1 (foto)

if the number of frames is not supplied, the value may be unknown. Applications should not assume that there is only one frame unless it is explicitly stated.

Duração em segundos (áudio / vídeo)

The duration might differ from occurrencePeriod if recording was paused.

Mídia - referência ou dado

Recommended content types: image/jpeg, image/png, image/tiff, video/mpeg, audio/mp4, application/dicom. Application/dicom can contain the transfer syntax as a parameter. For media that covers a period of time (video/sound), the content.creationTime is the end time. Creation time is used for tracking, organizing versions and searching.

Comentários sobre a mídia

Not to be used for observations, conclusions, etc. Instead use an Observation based on the Media/ImagingStudy resource.