Generated Narrative: DefinicionDeEstructura RecetaPrescripcionCl Name Flags Card. Type Description & Constraints MedicationRequest 0..* MedicationRequest Ordering of medication for patient or group #xD; Slices for extension 0..* Extension Determinación del medicamento en Producto Comercial Slice: Unordered, Open by value:url #xD; extension:ProdComercial S 0..1 Reference() Identificación de un medicamento bajo su marca comercial URL: https://interoperabilidad.minsal.cl/fhir/ig/snre/StructureDefinition/ProdComercial #xD; identifier S 0..2 Identifier Pueden ser 3 tipos de identificación de Receta: Id_Local| Id_Cheque| Id_Receta_Grafica #xD; type S 0..1 CodeableConcept Identifica el tipo de Prescripción códigos válidos Id_Local| Id_Cheque| Id_Receta_Grafica #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Identidad del sistema de codificación #xD; code S 0..1 code Símbolo o sintaxis definida en el sistema Binding: Tipo de Prescripción (required) #xD; display S 0..1 string Texto representativo del código #xD; system S 0..1 uri Namespace del identificador #xD; value S 0..1 string Código Identificador #xD; assigner S 0..1 Reference(Organization) Organization that issued id (may be just text) #xD; reference S 0..1 string Referencia a la organización que le dio el numero identificador #xD; display S 0..1 string Nombre de la organización a la cual se hace la referencia #xD; status S 1..1 code active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown código del estado de la receta del medicamento prescrito (requerido) Binding: medicationrequest Status (required) #xD; statusReason S 0..1 CodeableConcept Este dato es Obligatorio condicional a que haya un cambio de estado de la Receta (R2). Es la razón por la cual se cambia el estado de la receta #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Sistema de códigos a ocupar. #xD; code S 0..1 code Código relacionado al estado. Binding: Razón del cambio de estado (Prescripción) (extensible) #xD; display S 0..1 string Descripción del código. #xD; text S 0..1 string Texto que representa el concepto. Si el código es #otra entonces debe describirse aquí la razón #xD; intent S 1..1 code proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Intención para la cual es indicado el medicamento (requerido). Se Forzará siempre a order Binding: medicationRequest Intent (required) Required Pattern: order #xD; category S 0..* CodeableConcept Tipo de Acto clínico en el cual se realiza la Prescripción. #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Namespace para códigos #xD; code S 0..1 code Código relacionado Binding: Codificación de la categoría de una prescripción (extensible) #xD; display S 0..1 string Glosa del código #xD; Slices for medication[x] 1..1 CodeableConcept, Reference(Medication) Medication to be taken Slice: Unordered, Open by type:$this #xD; medication[x]:medicationReference S 0..1 Reference(Medication) Referencia al medicamento que se prescribe. #xD; reference S 0..1 string uri del recurso. Para el caso el repositorio se encuentra en "https:////api-receta.minsal.cl/v2/Medication" #xD; display S 0..1 string Descripción del fármaco, según definición TFC #xD; subject S 1..1 Reference(CL Paciente) Referencia al paciente a quien se le prescribe #xD; reference S 0..1 string Referencia al recurso del paciente. "https://api-receta.minsal.cl/v2/Patient" #xD; display S 0..1 string Nombre paciente #xD; authoredOn S 0..1 dateTime Fecha y hora en la cual fue prescrito el medicamento en formato YYYY-MM-DDThh:mm:ss+zz:zz #xD; requester S 1..1 Reference(CL Prestador) Referencia al Prescriptor #xD; reference S 0..1 string Recurso asociado al Prescriptor "https://api-receta.minsal.cl/v2/Practitioner" #xD; display S 0..1 string Nombre Prescriptor #xD; recorder S 0..1 Reference(CL Prestador) Referencia a un sujeto, que será el que registra la receta #xD; reference S 0..1 string Recurso asociado "http://api-receta.minsal.cl/v2/Practitioner" #xD; display S 0..1 string Nombre de quien registra la prescripción #xD; groupIdentifier S 1..1 Identifier Código identificador de grupo que debe ser el mismo con el cual se identificará el RequestGroup de la receta. Se genera como un NanoId. #xD; value S 1..1 string Identificador de grupo. #xD; courseOfTherapyType S 0..1 CodeableConcept Expresa el patrón en la administración del medicamento #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Sistema de códigos a ocupar, se hará uso sel set de valores de hl7 MedicationRequest-course-of-therapy #xD; code S 0..1 code Código relacionado con el patrón de administración Binding: medicationRequest Course of Therapy Codes (required) #xD; display S 0..1 string Descripción del código #xD; note S 0..* Annotation Texto libre en donde se expresan las instrucciones de como el medicamento debe ser administrado #xD; dosageInstruction S 1..* Dosage Instrucciones del dosaje del medicamento #xD; sequence S 0..1 integer Secuencia de administracion del medicamento #xD; text S 0..1 string Instucciones en texto libre #xD; patientInstruction S 0..1 string Instrucciones adicionales orientadas al paciente #xD; timing S 0..1 Timing When medication should be administered #xD; repeat S 0..1 Element Administración del medicamento en temporalidad #xD; Slices for bounds[x] 0..1 Duration, Range, Period Length/Range of lengths, or (Start and/or end) limits Slice: Unordered, Open by type:$this #xD; bounds[x]:boundsDuration S 0..1 Duration Length/Range of lengths, or (Start and/or end) limits #xD; bounds[x]:boundsRange S 0..1 Range Length/Range of lengths, or (Start and/or end) limits #xD; bounds[x]:boundsPeriod S 0..1 Period Length/Range of lengths, or (Start and/or end) limits #xD; frequency S 0..1 positiveInt Cantidad de repeticiones #xD; period S 0..1 decimal Período en el cual se realizan las repeticiones #xD; periodMax S 0..1 decimal Periodo máximo en el cual se realizan las repeticiones #xD; periodUnit S 0..1 code s | min | h | d | wk | mo | a - unidad de tiempo (UCUM) Binding: UnitsOfTime (required) #xD; Slices for asNeeded[x] 0..1 boolean, CodeableConcept Take "as needed" (for x) Slice: Unordered, Open by type:$this #xD; asNeeded[x]:asNeededBoolean 0..1 boolean Se define para uso de fármaco sin receta o indicación en esta. #xD; route S 0..1 CodeableConcept Vía por la cual es administrado el medicamento #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Namespace de SNOMED-CT #xD; code S 0..1 code Código de la vía por medio de subset de SNOMED-CT Binding: Vías de Administración (extensible) #xD; display S 0..1 string Descripción del código #xD; method S 0..1 CodeableConcept Forma exacta en la que el fármaco ingresa al organismo #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Namespace de los códigos desde VS local. Definir URl Local para validar #xD; code S 0..1 code Códigos del Set de Valores definidos desde SNOMED-CT Binding: Métodos de Administración (extensible) #xD; display S 0..1 string Descripción del código #xD; doseAndRate S 0..* Element Definición de la cantidad de fármaco a consumir por uso indicado #xD; dose[x] S 0..1 Amount of medication per dose #xD; doseRange Range S #xD; doseQuantity Quantity S(SimpleQuantity) #xD; dispenseRequest S 1..1 BackboneElement Autorización de la dispensación #xD; validityPeriod S 1..1 Period Periodo de validez de la Prescripción #xD; start S 1..1 dateTime Fecha de inicio de la validez de la prescripción. El formato es YYYY-MM-DD #xD; end S 1..1 dateTime Fecha de fin de la validez de la prescripción. El formato es YYYY-MM-DD #xD; quantity S 0..1 SimpleQuantity(4.0.1) Cantidad de medicamento sugerido para dispensar #xD; value S 0..1 decimal Valor de la cantidad del medicamento sugerido para dispensar. Obligatorio para fármacos sujetos a condición de expendio receta retenida con control de existencia o receta cheque. #xD; expectedSupplyDuration S 0..1 Duration Número de días que se espera que alcance lo que se dispensará #xD; value S 0..1 decimal Valor de la unidad de duración #xD; unit S 0..1 string Unidad temporal según UCUM #xD; system S 0..1 uri Sistema de códigos temporales según UCUM #xD; code S 0..1 code Código según UCUM Binding: CommonUCUMCodesForAge (required) #xD; performer S 0..1 Reference(Organization) Recinto donde se direcciona para que dispense. Obligatorio en Sector Público #xD; reference S 0..1 string Recurso referenciado. #xD; display S 0..1 string Nombre de la organización a la cual se direcciona sea donde se dispense #xD; priorPrescription 0..1 Reference(MedicationRequest) Prescripción u orden a la cual esta reemplaza #xD; reference S 0..1 string Recurso MedicationDispense que se reemplaza. #xD; display S 0..1 string Detalle de la orden o prescripción a la cual esta reemplaza. #xD; Documentation for this format
Este Perfil describe la información contenida en la Prescripción de un medicamento para el Sistema Nacional de Receta Electrónica del MINSAL
Ordering of medication for patient or group
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.
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
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
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
The base language in which the resource is written.
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).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
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.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
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.
Determinación del medicamento en Producto Comercial
Determinación de un medicamento en Producto Comercial. Para eso esta extensión define una Referencia solo a un recurso de medication.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Identificación de un medicamento bajo su marca comercial
Indicación de un Medicamento bajo su Marca Comercial
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Pueden ser 3 tipos de identificación de Receta: Id_Local| Id_Cheque| Id_Receta_Grafica
La identificación local puede ser dada localmente, puede ser la de la Receta Cheque o la identificación dada al ser escaneada una receta a papel. En cualquir caso no pueden ir aparejadas una identificación de receta cheque con una de receta gráfica
This is a business identifier, not a resource identifier.
ORC-2-Placer Order Number / ORC-3-Filler Order Number
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
Identifica el tipo de Prescripción códigos válidos Id_Local| Id_Cheque| Id_Receta_Grafica
Se consideran 3 códgos externos al ValueSet dado la extensibilidad del binding
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
A reference to a code defined by a terminology system.
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
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
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 o sintaxis definida en el sistema
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
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
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
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 ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
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
URL sobre la cual se determina el formato y procedencia del valor del identificador
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Referencia a la organización que le dio el numero identificador
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
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.
Type the reference refers to (e.g. "Patient")
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
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).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
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).
Nombre de la organización a la cual se hace la referencia
Organización en texto libre que dio el número identificador. DEBE ser informado en caso que la identificación sea de tipo Local
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.
active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown código del estado de la receta del medicamento prescrito (requerido)
A code specifying the current state of the order. Generally, this will be active or completed state.
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
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
Este dato es Obligatorio condicional a que haya un cambio de estado de la Receta (R2). Es la razón por la cual se cambia el estado de la receta
Captures the reason for the current state of the MedicationRequest.
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.
.inboundRelationship[typeCode=SUBJ].source[classCode=CACT, moodCode=EVN].reasonCOde
The identification of the code system that defines the meaning of the symbol in the code.
Texto que representa el concepto. Si el código es #otra entonces debe describirse aquí la razón
proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Intención para la cual es indicado el medicamento (requerido). Se Forzará siempre a order
Whether the request is a proposal, plan, or an original order.
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.
This element changes the interpretation of all descriptive attributes. For example "the time the request is recommended to occur" vs. "the time the request is authorized to occur" or "who is recommended to perform the request" vs. "who is authorized to perform the request
.moodCode (nuances beyond PRP/PLAN/RQO would need to be elsewhere)
Tipo de Acto clínico en el cual se realiza la Prescripción.
Se reconoce según la tabla de Hl7 cual es el tipo de acto clínico en el cual se desarrollan las prescripciones
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.
Message/Body/NewRx/MedicationPrescribed/Directions or Message/Body/NewRx/MedicationPrescribed/StructuredSIG
.inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="type of medication usage"].value
CodeSystem de donde pertenecen los códigos a usar
Glosa del código según su definición de la tabla de HL7
Indicates how quickly the Medication Request should be addressed with respect to other requests.
Identifies the level of importance to be assigned to actioning the request.
If true indicates that the provider is asking for the medication request not to occur.
If do not perform is not specified, the request is a positive request e.g. "do perform".
This element is labeled as a modifier because this element negates the request to occur (ie, this is a request for the medication not to be ordered or prescribed, etc)
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.
Identifies the medication being requested. This is a link to a resource that represents the medication which may be the details of the medication or simply an attribute carrying a code that identifies the medication from a known list of medications.
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 coded concept identifying substance or product that can be ordered.
Message/Body/NewRx/MedicationPrescribed Medication.code.coding.code = Message/Body/NewRx/MedicationPrescribed/DrugCoded/ProductCode Medication.code.coding.system = Message/Body/NewRx/MedicationPrescribed/DrugCoded/ProductCodeQualifier Medication.code.coding.display = Message/Body/NewRx/MedicationPrescribed/DrugDescription
RXE-2-Give Code / RXO-1-Requested Give Code / RXC-2-Component Code
Referencia al medicamento que se prescribe.
Referencia al medicamento que se prescribe, la cual se encuentra disponible en el //servicio de la TFC.
uri del recurso. Para el caso el repositorio se encuentra en "https:////api-receta.minsal.cl/v2/Medication"
Descripción del fármaco, según definición TFC
Plain text narrative that identifies the resource in addition to the resource reference.
Referencia al paciente a quien se le prescribe
La referencia en este caso solo se hace sobre el paciente al cual se le prescribe el fármaco independiente que sea otra la persona que hace retiro de estos
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.
Message/Body/NewRx/Patient (need detail to link to specific patient … Patient.Identification in SCRIPT)
Referencia al recurso del paciente. "https://api-receta.minsal.cl/v2/Patient"
Encounter created as part of encounter/admission/stay
The Encounter during which this [x] was created or to which the creation of this record is tightly associated.
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.
.inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN, code="type of encounter or episode"]
Information to support ordering of the medication
Include additional information (for example, patient height and weight) that supports the ordering of the medication.
.outboundRelationship[typeCode=PERT].target[A_SupportingClinicalStatement CMET minimal with many different choices of classCodes(ORG, ENC, PROC, SPLY, SBADM, OBS) and each of the act class codes draws from one or more of the following moodCodes (EVN, DEF, INT PRMS, RQO, PRP, APT, ARQ, GOL)]
Fecha y hora en la cual fue prescrito el medicamento en formato YYYY-MM-DDThh:mm:ss+zz:zz
RXE-32-Original Order Date/Time / ORC-9-Date/Time of Transaction
En este caso la referencia será sobre una persona que es Prescritpr validado por la SIS
Recurso asociado al Prescriptor "https://api-receta.minsal.cl/v2/Practitioner"
The specified desired performer of the medication treatment (e.g. the performer of the medication administration).
Desired kind of performer of the medication administration
Indicates the type of performer of the administration of the medication.
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.
Referencia a un sujeto, que será el que registra la receta
En este caso la referencia será sobre una persona que es un prescriptor validado por la SIS
.participation[typeCode=TRANS].role[classCode=ASSIGNED].code (HealthcareProviderType)
Recurso asociado "http://api-receta.minsal.cl/v2/Practitioner"
Nombre de quien registra la prescripción
Reason or indication for ordering or not ordering the medication
The reason or the indication for ordering or not ordering the medication.
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.
ORC-16-Order Control Code Reason /RXE-27-Give Indication/RXO-20-Indication / RXD-21-Indication / RXG-22-Indication / RXA-19-Indication
Condition or observation that supports why the prescription is being written
Condition or observation that supports why the medication was ordered.
This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode.
Instantiates FHIR protocol or definition
The URL pointing to a protocol, guideline, orderset, or other definition that is adhered to in whole or in part by this MedicationRequest.
Instantiates external protocol or definition
The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this MedicationRequest.
A plan or request that is fulfilled in whole or in part by this medication request.
.outboundRelationship[typeCode=FLFS].target[classCode=SBADM or PROC or PCPR or OBS, moodCode=RQO orPLAN or PRP]
Código identificador de grupo que debe ser el mismo con el cual se identificará el RequestGroup de la receta. Se genera como un NanoId.
Este número vincula el contenedor (RequestGroup) con todos los fármacos prescritos durante la atención del paciente (medicationRequest). Este hará el uso de Receta y el grupo de fármacos co misma identificación grupal. El formato debe ser NanoId.
El elemento groupIdentifier de los recursos MedicationRequest generados durante el mismo acto clínico deberán coincidir con el que se genere en el recurso RequestGroup. Este identificador debe ser generado como un valor NanoId.
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.
.outboundRelationship(typeCode=COMP].target[classCode=SBADM, moodCode=INT].id
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Expresa el patrón en la administración del medicamento
La descripción del patrón general de la administración del medicamento al paciente.
This attribute should not be confused with the protocol of the medication.
Identifies the overall pattern of medication administratio.
Act.code where classCode = LIST and moodCode = EVN
Sistema de códigos a ocupar, se hará uso sel set de valores de hl7 MedicationRequest-course-of-therapy
Código relacionado con el patrón de administración
Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.
Texto libre en donde se expresan las instrucciones de como el medicamento debe ser administrado
Información adicional sobre la prescripción que no puede ser transmitida por los otros atributos.
Instrucciones del dosaje del medicamento
Indica cómo debe utilizar el paciente el medicamento.
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.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Secuencia de administracion del medicamento
Indica el orden en el que se deben aplicar o interpretar las instrucciones de dosificación.
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.
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.
Supplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"
Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps").
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.
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.
A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".
Instrucciones adicionales orientadas al paciente
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.
Identifies specific times when the event occurs.
In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.
Administración del medicamento en temporalidad
A set of rules that describe when the event is scheduled.
Many timing schedules are determined by regular repetitions.
if there's a duration, there needs to be duration units
duration.empty() or durationUnit.exists()
not(exists(f:duration)) or exists(f:durationUnit)
if there's a period, there needs to be period units
not(exists(f:period)) or exists(f:periodUnit)
f:duration/@value >= 0 or not(f:duration/@value)
f:period/@value >= 0 or not(f:period/@value)
If there's a periodMax, there must be a period
not(exists(f:periodMax)) or exists(f:period)
If there's a durationMax, there must be a duration
durationMax.empty() or duration.exists()
not(exists(f:durationMax)) or exists(f:duration)
If there's a countMax, there must be a count
not(exists(f:countMax)) or exists(f:count)
If there's an offset, there must be a when (and not C, CM, CD, CV)
offset.empty() or (when.exists() and ((when in ('C' | 'CM' | 'CD' | 'CV')).not()))
If there's a timeOfDay, there cannot be a when, or vice versa
not(exists(f:timeOfDay)) or not(exists(f:when))
Length/Range of lengths, or (Start and/or end) limits
Either a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.
A total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values.
If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.
Repetitions may be limited by end time or total occurrences.
If present, indicates that the count is a range - so to perform the action between [count] and [countMax] times.
How long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration.
For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
Some activities are not instantaneous and need to be maintained for a period of time.
If present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length.
s | min | h | d | wk | mo | a - unit of time (UCUM)
The units of time for the duration, in UCUM units.
El número de veces que se debe repetir la acción dentro del periodo especificado. Si frequencyMax está presente, este elemento indica el límite inferior del rango permitido de la frecuencia.
If no frequency is stated, the assumption is that the event occurs once per period, but systems SHOULD always be specific about this
Event occurs up to frequencyMax times per period
If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range.
Período en el cual se realizan las repeticiones
Periodo máximo en el cual se realizan las repeticiones
s | min | h | d | wk | mo | a - unidad de tiempo (UCUM)
Unidad de tiempo según Unidades de Tiempo definidias en UCUM
If one or more days of week is provided, then the action happens only on the specified day(s).
If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.
Specified time of day for action to take place.
When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.
An approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur.
When more than one event is listed, the event is tied to the union of the specified events.
Timings are frequently determined by occurrences such as waking, eating and sleep.
Real world event relating to the schedule.
The number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event.
BID | TID | QID | AM | PM | QD | QOD | +
A code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code).
BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times).
Code for a known / defined timing pattern.
Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept).
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.
.outboundRelationship[typeCode=PRCN].target[classCode=OBS, moodCode=EVN, code="as needed"].value=boolean or codable concept
Se define para uso de fármaco sin receta o indicación en esta.
Para indicar si el fármaco se puede usar sin respetar diretamente lo presctito en el dosaje, como por ejemplo medicamentos que se pueden usar en caso de SOS
If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.
A coded specification of the anatomic site where the medication first enters the body.
A coded concept describing the site location the medicine enters into or onto the body.
Vía por la cual es administrado el medicamento
Como se debe administrar el medicamento (Vía de administración o como debe el farmaco entrar al cuerpo)
A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.
A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
Código de la vía por medio de subset de SNOMED-CT
Forma exacta en la que el fármaco ingresa al organismo
Forma exacta en la que el fármaco ingresa al organismo. En este caso se define la ruta plausible para vías de administración
Terminologies used often pre-coordinate this term with the route and or form of administration.
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.
A coded concept describing the technique by which the medicine is administered.
Namespace de los códigos desde VS local. Definir URl Local para validar
Namespace de los códigos desde SNOMED-CT.
Códigos del Set de Valores definidos desde SNOMED-CT
Código en SNOMED-CT correspondiente al método
Definición de la cantidad de fármaco a consumir por uso indicado
Cantidad de los medicamentos a administrar
The kind of dose or rate specified, for example, ordered or calculated.
If the type is not populated, assume to be "ordered".
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.
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.
Upper limit on medication per unit of time
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.
Upper limit on medication per administration
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.
Upper limit on medication per lifetime of the patient
The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject.
Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.
Indicates the quantity or duration for the first dispense of the medication.
If populating this element, either the quantity or the duration must be included.
SubstanceAdministration -> ActRelationship[sequenceNumber = '1'] -> Supply
The amount or quantity to provide as part of the first dispense.
The length of time that the first dispense is expected to last.
Minimum period of time between dispenses
The minimum period of time that must occur between dispenses of the medication.
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.
Fecha de inicio de la validez de la prescripción. El formato es YYYY-MM-DD
If the low element is missing, the meaning is that the low boundary is not known.
Fecha de fin de la validez de la prescripción. El formato es YYYY-MM-DD
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.
If the end of the period is missing, it means that the period is ongoing
An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense.
If displaying "number of authorized fills", add 1 to this number.
Cantidad de medicamento sugerido para dispensar
The amount that is to be dispensed for one fill.
RXD-4-Actual Dispense Amount / RXD-5.1-Actual Dispense Units.code / RXD-5.3-Actual Dispense Units.name of coding system
Valor de la cantidad del medicamento sugerido para dispensar. Obligatorio para fármacos sujetos a condición de expendio receta retenida con control de existencia o receta cheque.
Precision is handled implicitly in almost all cases of measurement.
PQ.value, CO.value, MO.value, IVL.high or IVL.low depending on the value
< | <= | >= | > - how to understand the value
Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.
If there is no comparator, then there is no modification of the value
This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value
How the Quantity should be understood and represented.
There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.
The identification of the system that provides the coded form of the unit.
Need to know the system that defines the coded form of the unit.
CO.codeSystem, PQ.translation.codeSystem
A computer processable form of the unit in some unit representation system.
The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.
PQ.code, MO.currency, PQ.translation.code
Número de días que se espera que alcance lo que se dispensará
Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.
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.
The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.
Sistema de códigos temporales según UCUM
Recinto donde se direcciona para que dispense. Obligatorio en Sector Público
Se debe referenciar a la API disponible. Obligatorio si es prescriptor público
.outboundRelationship[typeCode=COMP].target[classCode=SPLY, moodCode=RQO] .participation[typeCode=PRF].role[scoper.determinerCode=INSTANCE]
Nombre de la organización a la cual se direcciona sea donde se dispense
Any restrictions on medication substitution
Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done.
specific values within Message/Body/NewRx/MedicationPrescribed/Substitutions
True if the prescriber allows a different drug to be dispensed from what was prescribed.
This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.
Identifies the type of substitution allowed.
RXO-9-Allow Substitutions / RXE-9-Substitution Status
Indicates the reason for the substitution, or why substitution must or must not be performed.
A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.
Prescripción u orden a la cual esta reemplaza
.outboundRelationship[typeCode=?RPLC or ?SUCC]/target[classCode=SBADM,moodCode=RQO]
Recurso MedicationDispense que se reemplaza.
Detalle de la orden o prescripción a la cual esta reemplaza.
Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, duplicate therapy, dosage alert etc.
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.
A list of events of interest in the lifecycle
Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.
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.).
.inboundRelationship(typeCode=SUBJ].source[classCode=CACT, moodCode=EVN]