Identificador lógico deste artefato

Metadados sobre o recurso

Conjunto de regras sob as quais este conteúdo foi criado

Idioma do conteúdo do recurso

Resumo do texto do recurso em linguagem natural

Recursos contidos neste artefato

Conteúdo adicional definido por implementações

Extensão que não pode ser ignorada

Identificadores externos para este pedido

Status atual da requisição de medicamento: ativa, em espera, cancelada, concluída, registrada por engano, interrompida, rascunho, desconhecido

Motivo do status atual

Tipo de requisição de medicamento: prescrição, prescrição original, prescrição automática, reposição, refill, planejada, opcional (a critério médico), instância específica da prescrição

Código que identifica a categoria de uso do medicamento requisitado

Identifica o grau de prioridade da requisição de medicamentos: rotina | urgente | o mais rápido possível | emergência

Verdadeiro se a requisição for de proibição de execução

Informado em vez de registro primário

Medicamento prescrito

A quem ou a que grupo se destina a requisição de medicamento

Identificador único para referência entre elementos

Extensões adicionais que não fazem parte do modelo de dados básico

Referência literal. URL relativa, interna ou externa

Tipo de recurso ao qual a referência é feita

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

Alternativa de texto para o recurso

Contato assistencial criado como parte do encontro/admissão/estadia

Informações para apoiar a requisição do medicamento

Quando a requisição foi criada

Quem ou o que solicitou a requisição

Prescritor indicado para a administração

Especialidade do prescritor para a administração do medicamento

Pessoa que registrou a requisição

Motivo ou indicação para solicitar ou não o medicamento. Conceito codificado que indica o motivo pelo qual o medicamento foi solicitado ou não

Condição ou observação que apoia o motivo pelo qual a prescrição está sendo escrita

Instancia do protocolo ou definição FHIR

URI da instancia do protocolo ou a definição externa

o quê a requisição atende

requisição composta da qual esta requisição faz parte

Identifica o padrão de administração de medicamentos

Cobertura de planos/seguros de saúde associada

Informações sobre a requisição

Como o medicamento deve ser usado

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

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

Ordem na requisição

Instruções de dosagem em texto livre, por exemplo, SIG

Instruções suplementares ou advertências ao paciente - por exemplo: 'com as refeições', 'pode ​​causar sonolência'

Instruções orientadas ao paciente ou ao consumidor

Quando a medicamento deve ser administrado

Conceito codificado que identifica a pré-condição que deve ser atendida ou avaliada antes de consumir ou administrar uma dose de medicamento

Local anatômico de administração do medicamento

Conceito - referência a uma terminologia ou apenas texto que representa a via de administração do medicamento

Técnica para a administração do medicamento

Quantidade administrada do medicamento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

O tipo de dose ou taxa de administração especificada

Quantidade de medicamento por dose

Quantidade de medicamento por unidade de tempo

Quantidade máxima de medicamento por unidade de tempo

Quantidade máxima de medicamento por administração

Quantidade máxima de medicamento por toda a vida do paciente

Autorização de fornecimento de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Preenchimento dos primeiros detalhes da autorização de fornecimento de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Quantidade inicial de fornecimento autorizada

Duração da primeira autorização de fornecimento de medicamentos

Período mínimo de tempo entre dispensações de medicamentos autorizado

validade da autorização de fornecimento de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

URL do motivo da ausência do período de validade

Data/Hora de início da validade da autorização (intervalo fechado)

Data/Hora do final da validade da autorização(intervalo fechado), se não for contínuo

Número de refills autorizados

Quantidade de medicamento a ser fornecido por dispensação

Número de dias de fornecimento de medicamentos por dispensação

Organização preferencial para a dispensação

Restrições à substituição de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Informa se a substituição de medicamentos é ou não permitida

Um conceito codificado que descreve a razão pela qual um medicamento diferente deve (ou não) ser substituído daquele que foi prescrito

Requisição anterior que está sendo substituída

Condição Clínica detectada

Uma lista de eventos de interesse na linha do tempo

An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.

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

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 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 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ão que não pode ser ignorada

Identificadores externos para este pedido

This is a business identifier, not a resource identifier.

Status atual da requisição de medicamento: ativa, em espera, cancelada, concluída, registrada por engano, interrompida, rascunho, desconhecido

In the scope of the IPS the entered-in-error concept is not allowed.

A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription.

Motivo do status atual

This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.

Identifies the reasons for a given status.

Tipo de requisição de medicamento: prescrição, prescrição original, prescrição automática, reposição, refill, planejada, opcional (a critério médico), instância específica da prescrição

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.

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

The kind of medication order.

Código que identifica a categoria de uso do medicamento requisitado

The category can be used to include where the medication is expected to be consumed or other types of requests.

A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.

Identifica o grau de prioridade da requisição de medicamentos: rotina | urgente | o mais rápido possível | emergência

Identifies the level of importance to be assigned to actioning the request.

Verdadeiro se a requisição for de proibição de execução

If do not perform is not specified, the request is a positive request e.g. "do perform".

Informado em vez de registro primário

Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.

Medicamento prescrito

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the Medication resource is recommended. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.

SNOMED CT medications (Pharmaceutical / biologic product) or a code for absent/unknown medication

Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code. To improve global interoperability is strongly encouraged that the reference to a medication resource is used, limiting the usage of the medicationCodeableConcept only to the cases in which no other information than a simple code is available.

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the Medication resource is recommended. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.

A quem ou a que grupo se destina a requisição de medicamento

The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified.

Identificador único para referência entre elementos

Extensões adicionais que não fazem parte do modelo de dados básico

Referência literal. URL relativa, interna ou externa

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 de recurso ao qual a referência é feita

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

Alternativa de texto para o 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.

Contato assistencial criado como parte do encontro/admissão/estadia

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension.

Informações para apoiar a requisição do medicamento

Quando a requisição foi criada

Quem ou o que solicitou a requisição

Prescritor indicado para a administração

Especialidade do prescritor para a administração do medicamento

If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available.

Identifies the type of individual that is desired to administer the medication.

Pessoa que registrou a requisição

Motivo ou indicação para solicitar ou não o medicamento. Conceito codificado que indica o motivo pelo qual o medicamento foi solicitado ou não

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.

A coded concept indicating why the medication was ordered.

Condição ou observação que apoia o motivo pelo qual a prescrição está sendo escrita

This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode.

Instancia do protocolo ou definição FHIR

URI da instancia do protocolo ou a definição externa

o quê a requisição atende

requisição composta da qual esta requisição faz parte

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.

Identifica o padrão de administração de medicamentos

This attribute should not be confused with the protocol of the medication.

Identifies the overall pattern of medication administratio.

Cobertura de planos/seguros de saúde associada

Informações sobre a requisição

Como o medicamento deve ser usado

There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

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

Ordem na requisição

If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential.

Instruções de dosagem em texto livre, por exemplo, SIG

Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text.

Instruções suplementares ou advertências ao paciente - por exemplo: 'com as refeições', 'pode ​​causar sonolência'

Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text.

A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".

Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded.

Instruções orientadas ao paciente ou ao consumidor

Quando a medicamento deve ser administrado

This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.

The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.

Conceito codificado que identifica a pré-condição que deve ser atendida ou avaliada antes de consumir ou administrar uma dose de medicamento

Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed".

A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.

Local anatômico de administração do medicamento

If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both.

A coded concept describing the site location the medicine enters into or onto the body.

A coded specification of the anatomic site where the medication first enters the body.

Conceito - referência a uma terminologia ou apenas texto que representa a via de administração do medicamento

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.

EDQM Standards Terms

A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.

Técnica para a administração do medicamento

Terminologies used often pre-coordinate this term with the route and or form of administration.

A coded concept describing the technique by which the medicine is administered.

A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV.

Quantidade administrada do medicamento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

O tipo de dose ou taxa de administração especificada

The kind of dose or rate specified.

If the type is not populated, assume to be "ordered".

Quantidade de medicamento por dose

Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.

The amount of therapeutic or other substance given at one administration event.

Quantidade de medicamento por unidade de tempo

It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate.

It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.

Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.

Quantidade máxima de medicamento por unidade de tempo

This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".

The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours.

Quantidade máxima de medicamento por administração

This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.

The maximum total quantity of a therapeutic substance that may be administered to a subject per administration.

Quantidade máxima de medicamento por toda a vida do paciente

The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject.

Autorização de fornecimento de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Preenchimento dos primeiros detalhes da autorização de fornecimento de medicamentos

If populating this element, either the quantity or the duration must be included.

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Quantidade inicial de fornecimento autorizada

Duração da primeira autorização de fornecimento de medicamentos

Período mínimo de tempo entre dispensações de medicamentos autorizado

validade da autorização de fornecimento de medicamentos

It reflects the prescribers' perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.

Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription.

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido pelas implementações

URL do motivo da ausência do período de validade

Data/Hora de início da validade da autorização (intervalo fechado)

If the low element is missing, the meaning is that the low boundary is not known.

Data/Hora do final da validade da autorização(intervalo fechado), se não for contínuo

The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

Número de refills autorizados

If displaying "number of authorized fills", add 1 to this number.

Quantidade de medicamento a ser fornecido por dispensação

Número de dias de fornecimento de medicamentos por dispensação

In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued, e.g. 90 days supply of medication (based on an ordered dosage). When possible, it is always better to specify quantity, as this tends to be more precise. expectedSupplyDuration will always be an estimate that can be influenced by external factors.

Organização preferencial para a dispensação

Restrições à substituição de medicamentos

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Informa se a substituição de medicamentos é ou não permitida

This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.

Identifies the type of substitution allowed.

Um conceito codificado que descreve a razão pela qual um medicamento diferente deve (ou não) ser substituído daquele que foi prescrito

A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.

Requisição anterior que está sendo substituída

Condição Clínica detectada

This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.

Uma lista de eventos de interesse na linha do tempo

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

An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.

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

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 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 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ão que não pode ser ignorada

Identificadores externos para este pedido

This is a business identifier, not a resource identifier.

Status atual da requisição de medicamento: ativa, em espera, cancelada, concluída, registrada por engano, interrompida, rascunho, desconhecido

In the scope of the IPS the entered-in-error concept is not allowed.

A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription.

Motivo do status atual

This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.

Identifies the reasons for a given status.

Tipo de requisição de medicamento: prescrição, prescrição original, prescrição automática, reposição, refill, planejada, opcional (a critério médico), instância específica da prescrição

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.

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

The kind of medication order.

Código que identifica a categoria de uso do medicamento requisitado

The category can be used to include where the medication is expected to be consumed or other types of requests.

A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.

Identifica o grau de prioridade da requisição de medicamentos: rotina | urgente | o mais rápido possível | emergência