Identificador lógico deste artefato

Metadados sobre o recurso

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

Idioma do recurso

Resumo do texto do recurso em linguagem natural

Recursos contidos no recurso

Extensões adicionais que não fazem parte do modelo base

Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas

Identificadores externos para este recurso

Instancia o protocolo ou definição FHIR

Instancia protocolo externo ou definição

Referência aos planos de cuidado/solicitações/medicamentos associados a esta requisição

Referência à requisição a ser substituida

Identificador da requisição

Status da requisição

Código da intencionalidade desta requisição

Categoria desta requisição

Prioridade desta requisição

Verdadeiro se o serviço/procedimento não deve ser executado

Código do procedimento solicitado

Informações adicionais da requesição

Quantidade de procedimento solicitados

Referência ao paciente/grupo/localidade/dispositivo associado a esta requisição

Referência ao atendimento relacionado a esta requisição

Quando o procedimento deve ocorrer

Pré-condições para a realização do procedimento

Data de assinatura da requisição

Referência ao profissional/organização/paciente/dispotivo/pessoa relacionada que está solicitando o procedimento

Função do profissional executante solicitado

Referência ao profissional executante solicitado

Localização solicitada

ReferÇencia à localização solicitada

Explicação/Justificativa para procedimento ou serviço

Referência à explicação/justificativa para serviço ou procedimento

Referência às coberturas associadas

Referência às informações adicionais

Referência à amostras associadas

Local anatômico associado ao procedimento

Comentários

Instruções para o paciente

Referência ao recurso Provenance

A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.

Identificador 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 o 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 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 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.

Recursos contidos no recurso

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

Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas

Identificadores externos para este recurso

The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.

Instancia o protocolo ou definição FHIR

Note: 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 a Person resource instance might share the same social insurance number.

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Referência aos planos de cuidado/solicitações/medicamentos associados a esta requisição

Referência à requisição a ser substituida

Identificador da requisição

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes.

Status da requisição

The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see Event Pattern for general discussion) or using the Task resource.

The status of a service order.

Código da intencionalidade desta requisição

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

The kind of service request.

Categoria desta requisição

There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.

Used for filtering what service request are retrieved and displayed.

Prioridade desta requisição

Verdadeiro se o serviço/procedimento não deve ser executado

In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.

Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc.

Código do procedimento solicitado

Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.

Informações adicionais da requesição

For information from the medical record intended to support the delivery of the requested services, use the supportingInformation element.

Codified order entry details which are based on order context.

Quantidade de procedimento solicitados

When ordering a service the number of service items may need to be specified separately from the the service item.

Referência ao paciente/grupo/localidade/dispositivo associado a esta requisição

Referência ao atendimento relacionado a esta requisição

Quando o procedimento deve ocorrer

Pré-condições para a realização do procedimento

A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

Data de assinatura da requisição

Referência ao profissional/organização/paciente/dispotivo/pessoa relacionada que está solicitando o procedimento

This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.

Função do profissional executante solicitado

This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.

Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

Referência ao profissional executante solicitado

If multiple performers are present, it is interpreted as a list of alternative performers without any preference regardless of order. If order of preference is needed use the request-performerOrder extension. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B).

Localização solicitada

A location type where services are delivered.

ReferÇencia à localização solicitada

Explicação/Justificativa para procedimento ou serviço

This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use CodeableConcept.text element if the data is free (uncoded) text as shown in the CT Scan example.

Diagnosis or problem codes justifying the reason for requesting the service investigation.

Referência à explicação/justificativa para serviço ou procedimento

This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in DiagnosticReport.conclusion and/or DiagnosticReport.conclusionCode. When using a reference to DocumentReference, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in ServiceRequest.reasonCode if the data is free (uncoded) text as shown in the CT Scan example.

Referência às coberturas associadas

Referência às informações adicionais

To represent information about how the services are to be delivered use the instructions element.

Referência à amostras associadas

Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest.

Local anatômico associado ao procedimento

Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure.

Knowing where the procedure is performed is important for tracking if multiple sites are possible.

Comentários

Instruções para o paciente

Referência ao recurso Provenance

This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.

A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.

Identificador 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 o 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 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 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.

Recursos contidos no recurso

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

Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas

Identificadores externos para este recurso

The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.

Instancia o protocolo ou definição FHIR

Note: 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 a Person resource instance might share the same social insurance number.

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Referência aos planos de cuidado/solicitações/medicamentos associados a esta requisição

Referência à requisição a ser substituida

Identificador da requisição

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes.

Status da requisição

The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see Event Pattern for general discussion) or using the Task resource.

The status of a service order.

Código da intencionalidade desta requisição

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

The kind of service request.

Categoria desta requisição

There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.

Used for filtering what service request are retrieved and displayed.

Prioridade desta requisição

Verdadeiro se o serviço/procedimento não deve ser executado

In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.

Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc.

Código do procedimento solicitado

Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.

Informações adicionais da requesição

For information from the medical record intended to support the delivery of the requested services, use the supportingInformation element.

Codified order entry details which are based on order context.

Quantidade de procedimento solicitados

When ordering a service the number of service items may need to be specified separately from the the service item.

Referência ao paciente/grupo/localidade/dispositivo associado a esta requisição

Referência ao atendimento relacionado a esta requisição

Quando o procedimento deve ocorrer

Pré-condições para a realização do procedimento

A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

Data de assinatura da requisição

Referência ao profissional/organização/paciente/dispotivo/pessoa relacionada que está solicitando o procedimento

This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.

Função do profissional executante solicitado

This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.

Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

Referência ao profissional executante solicitado

If multiple performers are present, it is interpreted as a list of alternative performers without any preference regardless of order. If order of preference is needed use the request-performerOrder extension. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B).

Localização solicitada

A location type where services are delivered.

ReferÇencia à localização solicitada

Explicação/Justificativa para procedimento ou serviço

This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use CodeableConcept.text element if the data is free (uncoded) text as shown in the CT Scan example.

Diagnosis or problem codes justifying the reason for requesting the service investigation.

Referência à explicação/justificativa para serviço ou procedimento

This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in DiagnosticReport.conclusion and/or DiagnosticReport.conclusionCode. When using a reference to DocumentReference, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in ServiceRequest.reasonCode if the data is free (uncoded) text as shown in the CT Scan example.

Referência às coberturas associadas

Referência às informações adicionais

To represent information about how the services are to be delivered use the instructions element.

Referência à amostras associadas

Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest.

Local anatômico associado ao procedimento

Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure.

Knowing where the procedure is performed is important for tracking if multiple sites are possible.

Comentários

Instruções para o paciente

Referência ao recurso Provenance

This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.