Generated Narrative: DefinicionDeEstructura DispensacionMedicamentoCl2 Name Flags Card. Type Description & Constraints MedicationDispense 0..* MedicationDispense Dispensing a medication to a named patient #xD; id S 0..1 id Identificador único del recurso de dispensación #xD; meta S 0..1 Meta Metadata about the resource #xD; versionId S 0..1 id Identificador de versión del recurso #xD; lastUpdated S 0..1 instant Fecha y hora de la última actualización del recurso #xD; identifier S 0..1 Identifier Se usará en caso que se realice una dispensación con Id Local #xD; system S 0..1 uri Namespace de id de local #xD; value S 0..1 string Número identificador #xD; assigner S 0..1 Reference(Organization) Organización que asigna el identificador #xD; identifier S 0..1 Identifier El identificador de la Farmacia que ha dado el código 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 Estado de la dispensación según estándar: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown #xD; Slices for statusReason[x] 0..1 CodeableConcept, Reference(DetectedIssue) Why a dispense was not performed Slice: Unordered, Open by type:$this #xD; statusReason[x]:statusReasonCodeableConcept S 0..1 CodeableConcept Razón por la cual se ha modificado el estado de la dispensación #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Identidad del sistema terminológico #xD; code S 0..1 code Código referente a la razón de cambio de estado Binding: Razón del cambio de estado (Dispensación) (extensible) #xD; display S 0..1 string Glosa del código #xD; text S 0..1 string Razón de la modificación en texto libre #xD; Slices for medication[x] 1..1 CodeableConcept, Reference(Medication) What medication was supplied Slice: Unordered, Open by type:$this #xD; medication[x]:medicationReference S 0..1 Reference(Medication) Medicamento comercial dispensado (https://api-receta.minsal.cl/v2/Medication) #xD; reference S 0..1 string URL del medicamento dispensado (https://api-receta.minsal.cl/v2/Medication) #xD; display S 0..1 string Nombre del medicamento dispensado según TFC (Tabla de Medicamentos) #xD; subject S 1..1 Reference(CL Paciente) Referencia al Paciente para el cual se realiza la dispensación #xD; reference S 0..1 string URL de la referencia del recurso del paciente (https://api-receta.minsal.cl/v2/Patient) #xD; display S 0..1 string Nombre del Paciente #xD; Slices for performer S 1..2 BackboneElement Profesional, técnico o auxiliar que ejecutó alguna acción sobre la dispensación Slice: Unordered, Closed by value:function.coding.code #xD; performer:dispensador S 1..1 BackboneElement Aquel individuo que realiza la entrega de medicamentos #xD; function S 1..1 CodeableConcept Función que desarrolla el Performer: dispensador #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Identity of the terminology system #xD; code S 1..1 code Código del tipo de dispensador. El valor obligado es 'dispensador' Required Pattern: dispensador #xD; display S 0..1 string Representation defined by the system #xD; actor S 1..1 Reference(CL Prestador) Identificación del individuo que realiza la dispensación (https://api-receta.minsal.cl/v2/Practitioner) #xD; reference S 0..1 string URL del Practitioner (https://api-receta.minsal.cl/v2/Practitioner) #xD; display S 0..1 string Nombre del individuo que ejecuta la dispensación #xD; performer:validador S 0..1 BackboneElement Aquel profesional que realiza la validación previa a la entrega de medicamentos #xD; function S 1..1 CodeableConcept Función que desarrolla el validador #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Identity of the terminology system #xD; code S 1..1 code Código de validador. Debe ser 'validador' Required Pattern: validador #xD; display S 0..1 string Representation defined by the system #xD; actor S 1..1 Reference(CL Prestador) Profesional que realiza la validación (https://api-receta.minsal.cl/v2/Practitioner) #xD; reference S 0..1 string URL del Practitioner (https://api-receta.minsal.cl/v2/Practitioner) #xD; display S 0..1 string Nombre de quien valida la receta antes de la entrega #xD; location S 1..1 Reference(Location) Ubicación Georreferenciada donde se realiza la dispensación #xD; reference S 0..1 string URL del recurso Location (https://api-receta.minsal.cl/v2/Location) #xD; display S 0..1 string Descripción de la ubicación o localización donde se realiza la dispensación #xD; authorizingPrescription S 1..1 Reference(MedicationRequest) Referencia a la prescripción que autoriza la dispensación #xD; reference S 0..1 string URL de la prescripción (https://api-receta.minsal.cl/v2/MedicationRequest) #xD; display S 0..1 string Identificador o descripción de la prescripción #xD; quantity S 1..1 SimpleQuantity(4.0.1) Cantidad de medicamento dispensado #xD; value S 0..1 decimal Valor numérico de la cantidad #xD; system S 0..1 uri Sistema de unidades de medida (ej: http://unitsofmeasure.org) #xD; whenHandedOver S 1..1 dateTime Fecha y hora cuando el medicamento fue dispensado #xD; receiver S 0..1 Reference(CL Paciente) Persona a la cual se le hace entrega de los fármacos #xD; reference S 0..1 string URL del recurso Paciente o tercero #xD; display S 0..1 string Nombre completo de quien recibe el medicamento #xD; note S 0..* Annotation Notas adicionales sobre la dispensación #xD; dosageInstruction S 0..* Dosage Cómo se debe administrar el medicamento #xD; sequence S 1..1 integer Secuencia de administración del medicamento #xD; text S 0..1 string Instrucción de dosificación en texto libre #xD; patientInstruction S 0..1 string Instrucciones para el paciente #xD; timing S 0..1 Timing When medication should be administered #xD; repeat S 0..1 Element Patrón de repetición de la administración #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 Duración total del tratamiento #xD; value S 0..1 decimal Valor numérico de la duración #xD; unit S 0..1 string Unidad de duración (ej: d para días) #xD; system S 0..1 uri Sistema de codificación: http://unitsofmeasure.org #xD; code S 0..1 code Código de la unidad (ej: d) #xD; frequency S 0..1 positiveInt Cantidad de repeticiones en el período #xD; period S 0..1 decimal Período en el cual se realizan las repeticiones #xD; periodMax S 0..1 decimal Período máximo en el cual se realizan las repeticiones #xD; periodUnit S 0..1 code Unidad de tiempo: s | min | h | d | wk | mo | a (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 S 0..1 boolean Indica si el medicamento se puede usar bajo demanda (SOS) #xD; route S 0..1 CodeableConcept Vía de administración del medicamento #xD; coding S 0..* Coding Code defined by a terminology system #xD; system 0..1 uri Sistema de codificación: 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 de la vía de administración #xD; method S 0..1 CodeableConcept Técnica para administrar el medicamento #xD; coding S 0..* Coding Code defined by a terminology system #xD; system 0..1 uri Sistema de codificación: SNOMED-CT #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 método de administración #xD; doseAndRate S 0..* Element Definición de la cantidad de fármaco a consumir #xD; type S 0..1 CodeableConcept Tipo de tasa de dosificación #xD; coding S 0..* Coding Code defined by a terminology system #xD; system 0..1 uri Sistema de codificación para tipo de dosis #xD; code S 0..1 code Código del tipo de dosis (ej: ordered) #xD; display S 0..1 string Descripción del tipo de dosis #xD; Slices for dose[x] S 0..1 Dosis expresada como cantidad simple o rango Slice: Unordered, Open by type:$this #xD; doseRange Range S(RangeCL) #xD; doseQuantity Quantity S(SimpleQuantityCL) #xD; dose[x]:doseQuantity S 0..1 SimpleQuantityCL Cantidad simple de la dosis #xD; value S 0..1 decimal Valor numérico de la dosis #xD; unit 0..1 string Representación de la unidad de dosis #xD; system 0..1 uri Sistema de codificación de unidades #xD; code 0..1 code Código de la unidad de dosis #xD; dose[x]:doseRange S 0..1 RangeCL Rango de dosis permitido #xD; low 0..1 SimpleQuantityCL Límite inferior del rango de dosis #xD; value S 0..1 decimal Valor numérico del límite inferior #xD; unit 0..1 string Unidad de dosis mínima #xD; system 0..1 uri Sistema de codificación de la unidad #xD; code 0..1 code Código de la unidad #xD; high 0..1 SimpleQuantityCL Límite superior del rango de dosis #xD; value S 0..1 decimal Valor numérico del límite superior #xD; unit 0..1 string Unidad de dosis máxima #xD; system 0..1 uri Sistema de codificación de la unidad #xD; code 0..1 code Código de la unidad #xD; detectedIssue S 0..* Reference(DetectedIssue) Evento adverso detectado como contraindicación al fármaco dispensado #xD; reference S 0..1 string Referencia al recurso de evento adverso #xD; display S 0..1 string Descripción del evento adverso en texto libre #xD; Documentation for this format
Este Perfil ha sido desarrollado para cubrir las necesidades del Caso de Uso del Sistema Nacional de Receta Electrónica desde la visión de la TFC que se utilizará para poder manejar fármacos que cuentan con autorización de comercialización en el país, los cuales deberán ser consultados por los prestadores a la hora de prescribir alguno o mantener una base local actualizada.
Dispensing a medication to a named patient
Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.
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
whenHandedOver cannot be before whenPrepared
whenHandedOver.empty() or whenPrepared.empty() or whenHandedOver >= whenPrepared
not(exists(f:whenHandedOver/@value)) or not(exists(f:whenPrepared/@value)) or ( f:whenHandedOver/@value >= f:whenPrepared/@value)
Identificador único del recurso de dispensación
Identificador único del recurso de dispensación generado por el sistema
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())
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Número de versión del recurso para control de cambios
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
Fecha y hora de la última actualización del recurso
Indica cuándo fue actualizado por última vez el recurso
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R4/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R4/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](http://hl7.org/fhir/R4/structuredefinition-definitions.html#StructureDefinition.url).
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
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.
May be used to represent additional information that is not part of the basic definition of the resource. 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.
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).
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
Se usará en caso que se realice una dispensación con Id Local
Es el número de Id Local, generado a nivel del dispensador.
This is a business identifier, not a resource identifier.
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 .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
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.
Namespace de id de local que identifica al sistema que genera el identificador local
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.
Número identificador único dentro del sistema local
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
Organización que asigna el identificador
Referencia a la organización (Farmacia) que ha generado el identificador
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
Literal reference, Relative, internal or absolute URL
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).
El identificador de la Farmacia que ha dado el código identificador
El identificador de la Farmacia que ha dado el código identificador a la dispensación
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
Nombre amigable de la farmacia o punto de dispensación
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.
The procedure that trigger the dispense.
Estado de la dispensación según estándar: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown
Estado actual de la dispensación. Los valores válidos son: preparation (preparación), in-progress (en proceso), cancelled (cancelada), on-hold (en espera), completed (completada), entered-in-error (entrada por error), stopped (detenida), declined (rechazada), unknown (desconocida)
Si bien los códigos FHIR para este elemento son más que los mostrados en esta guía, solo se considerarán los estados definidos para el caso local
This element is labelled 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
A coded concept specifying the state of the dispense event.
Indicates the reason why a dispense was not performed.
A code describing why a dispense was not performed.
.outboundRelationship[typeCode=RSON]/target[classCode=OBS,moodCode=EVN, code="not done reason"].value
Razón por la cual se ha modificado el estado de la dispensación
Razón clínica o administrativa por la cual se ha modificado el estado de la dispensación (ej: medicamento agotado, paciente no comparece, etc.)
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
Identidad del sistema terminológico (ej: http://minsal.cl/razon-de-no-dispensacion)
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
Código referente a la razón de cambio de estado
Código que especifica la razón por la cual se modificó la dispensación
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
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 ]
Razón de la modificación explicada en texto libre
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
Indicates the type of medication dispense (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)).
The category can be used to include where the medication is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind.
A code describing where the dispensed medication is expected to be consumed or administered.
.inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="type of medication dispense"].value
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 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, then you must reference the Medication resource.
A coded concept identifying which substance or product can be dispensed.
Medicamento comercial dispensado (https://api-receta.minsal.cl/v2/Medication)
Medicamento dispensado que corresponde al Producto Comercial que fue entregado a quien lo retira. Este se describe mediante el recurso Medication desde el repositorio nacional. Solo se agrega en caso de ser dispensado el medicamento
URL del medicamento dispensado (https://api-receta.minsal.cl/v2/Medication)
URL del recurso Medication que representa el producto comercial específico dispensado
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.
Nombre del medicamento dispensado según TFC (Tabla de Medicamentos)
Nombre comercial del medicamento según la Tabla de Medicamentos de Chile
Referencia al Paciente para el cual se realiza la dispensación
La referencia en este caso solo se hace sobre el paciente al cual se le receta el fármaco, independiente de que sea otra la persona que hace retiro de estos. Se usa el repositorio https://api-receta.minsal.cl/v2/Patient
URL de la referencia del recurso del paciente (https://api-receta.minsal.cl/v2/Patient)
URL completa hacia el recurso del paciente en el repositorio centralizado
Nombre completo del paciente para quien se realiza la dispensación
Encounter / Episode associated with event
The encounter or episode of care that establishes the context for this event.
.inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN, code="type of encounter or episode"]
Information that supports the dispensing of the medication
Additional information that supports the medication being dispensed.
.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)]
Profesional, técnico o auxiliar que ejecutó alguna acción sobre la dispensación
Profesional que realizó o validó la entrega de la orden de fármacos. Se definen dos roles posibles: dispensador (obligatorio) y validador (opcional)
Se definen dos tipos de dispensador, no excluyentes mutuamente. El primero es el dispensador del fármaco, el segundo es el validador. El dispensador es obligatorio. Ambos roles tienen la misma estructura, solo cambia el valor del código en la ruta performer.function.coding.code
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
Who performed the dispense and what they did
Distinguishes the type of performer in the dispense. For example, date enterer, packager, final checker.
Allows disambiguation of the types of involvement of different performers.
A code describing the role an individual played in dispensing a medication.
The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the medication.
Aquel individuo que realiza la entrega de medicamentos
Se entiende por dispensador al individuo que entrega los medicamentos a quien los solicite en el punto de entrega. Siempre en el proceso de dispensación existe un dispensador. Puede ser un químico farmacéutico, técnico farmacéutico o auxiliar de farmacia
Función que desarrolla el Performer: dispensador
Indica que este performer es quien realiza la dispensación física del medicamento
The identification of the code system that defines the meaning of the symbol in the code.
Código del tipo de dispensador. El valor obligado es 'dispensador'
Código según tabla maestra que identifica la función de dispensador
A representation of the meaning of the code in the system, following the rules of the system.
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.
Identificación del individuo que realiza la dispensación (https://api-receta.minsal.cl/v2/Practitioner)
Referencia al recurso Practitioner que representa al profesional o técnico que realiza la dispensación
URL del Practitioner (https://api-receta.minsal.cl/v2/Practitioner)
La referencia del recurso especificado debe ser al EndPoint https://api-receta.minsal.cl/v2/Practitioner
Nombre del individuo que ejecuta la dispensación
Nombre completo del dispensador para identificación visual
Aquel profesional que realiza la validación previa a la entrega de medicamentos
Se entiende por validador al profesional (típicamente Químico Farmacéutico) que valida la entrega de los medicamentos a quien los solicite en el punto de entrega. Este rol es opcional
Indica que este performer es quien realiza la validación previa a la entrega del medicamento
Código de validador. Debe ser 'validador'
Código según tabla maestra que identifica la función de validador
Profesional que realiza la validación (https://api-receta.minsal.cl/v2/Practitioner)
Referencia al recurso Practitioner que representa al Químico Farmacéutico u otro profesional que valida
Nombre de quien valida la receta antes de la entrega
Nombre completo del validador para identificación visual
Ubicación Georreferenciada donde se realiza la dispensación
La ubicación física principal en la cual se desarrolló la dispensación (farmacia, punto de dispensación, etc.)
URL del recurso Location (https://api-receta.minsal.cl/v2/Location)
El repositorio Central tendrá listada la ubicación de todos los dispensadores en recurso Location. Estas deberán ser alcanzadas desde https://api-receta.minsal.cl/v2/Location
Descripción de la ubicación o localización donde se realiza la dispensación
Nombre o descripción amigable del lugar (farmacia) donde se realizó la dispensación
Referencia a la prescripción que autoriza la dispensación
Referencia al recurso MedicationRequest involucrado en la receta presentada al momento de la dispensación. Este es un elemento obligatorio que vincula la dispensación con la prescripción
URL de la prescripción (https://api-receta.minsal.cl/v2/MedicationRequest)
Referencia a la receta electrónica que autoriza la dispensación en el repositorio https://api-receta.minsal.cl/v2/MedicationRequest
Identificador o descripción de la prescripción
Identificador o descripción legible de la prescripción que autoriza
Trial fill, partial fill, emergency fill, etc.
Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.
Cantidad total del medicamento dispensado, expresada con su unidad de medida
RXD-4-Actual Dispense Amount / RXD-5.1-Actual Dispense Units.code / RXD-5.3-Actual Dispense Units.name of coding system
Número que representa la cantidad de medicamento dispensado
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).
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.
Sistema de unidades de medida (ej: http://unitsofmeasure.org)
Sistema de codificación de unidades según UCUM (Unified Code for Units of Measure) o sistemas equivalentes
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
Amount of medication expressed as a timing amount
The amount of medication expressed as a timing amount.
TQ1.6 Timing/Quantity Segment Service Duration. Prior to v2.5, ORC.7.3 Common Order Segment / Quantity/Timing / Duration component. This is a formatted string, first character for the time unit (e.g., D=days), followed by the value. For example, “D14” represents “14 days supply” From v2.5 on, TQ1.6 Timing/Quantity Segment / Service Duration. This is a CQ data type (<Quantity (NM)> ^ <Units (CWE)>), thus for days supply, assuming the unit of measure is “days”, the numeric value is TQ1.6.1 (…|14^ For backwards compatibility, ORC.7 was permitted through v2.6. Both forms (field and segment) may be present in v2.5, v2.5.1, and v2.6
The time when the dispensed product was packaged and reviewed.
Fecha y hora cuando el medicamento fue dispensado
Fecha y hora exacta en la que el medicamento fue entregado físicamente al paciente o su representante. Formato: YYYY-MM-DDThh:mm:ss±zz:zz
Identification of the facility/location where the medication was shipped to, as part of the dispense event.
RXD-13 Dispense-to Location; RXD-30 Dispense to Pharmacy; RXD-31 Dispense to Pharmacy Address
Persona a la cual se le hace entrega de los fármacos
Persona física que recibe la entrega de los medicamentos. Puede ser el paciente o un tercero autorizado. Este elemento si bien no es obligatorio debería serlo en el servicio público
Se debe agregar la URL del recurso Paciente o la persona autorizada que recibe la medicación
Nombre completo de quien recibe el medicamento
Nombre y apellido completo de quien recibe físicamente el medicamento. Debe incluirse solo en caso de que el receptor sea diferente del paciente
Debe ser obligatorio en dispensaciones realizadas en el sector de salud Público
Información adicional, observaciones o comentarios relevantes sobre la dispensación del medicamento
Instrucciones detalladas sobre cómo el paciente debe tomar o usar el medicamento. Este elemento se completa automáticamente al vincularse con el recurso MedicationRequest
Este elemento y todos sus subelementos se completan de manera automática al vincularse este recurso con un recurso MedicationRequest. No es deber del dispensador llenar estos campos manualmente
.outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=INT]
Secuencia de administración del medicamento
Indica el orden en el que se deben aplicar o interpretar las instrucciones de dosificación cuando hay múltiples instrucciones
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.
Instrucción de dosificación en texto libre
Instrucción de dosificación expresada en texto libre comprensible para profesionales (ej: 'una-dos pastillas cada 4-6 horas en caso de dolor')
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 con detalle o lenguaje que los pacientes puedan comprender fácilmente
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.
Patrón de repetición de la administración
Administración del medicamento en temporalidad definida
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.
La cantidad total de tiempo que el paciente debe tomar el medicamento (ej: 10 días)
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 codificación: http://unitsofmeasure.org
Identificación del sistema de codificación de unidades
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
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
Duración del período base (número que se multiplica por periodUnit)
Período máximo en el cual se realizan las repeticiones
Duración máxima del período (rango superior)
Unidad de tiempo: s | min | h | d | wk | mo | a (UCUM)
Unidad de tiempo según Unidades de Tiempo definidas en UCUM (Unified Code for Units of Measure)
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
Indica si el medicamento se puede usar bajo demanda (SOS)
Para indicar si el fármaco se puede usar sin respetar directamente lo prescrito en el dosaje, como por ejemplo medicamentos que se pueden usar en caso de 'según sea necesario'
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 (cómo debe el fármaco entrar al cuerpo: oral, intramuscular, intravenosa, etc.)
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.
Namespace de SNOMED-CT (http://snomed.info/sct)
Código de la vía por medio de subset de SNOMED-CT
Código SNOMED-CT que especifica la vía de administración
Nombre legible de la vía de administración (ej: 'Vía Oral')
Valor codificado que indica el método mediante el cual se introduce el medicamento en el cuerpo o sobre él. Más comúnmente utilizado para inyecciones (ej: empuje lento, inyección profunda IV)
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 SNOMED-CT (http://snomed.info/sct)
Códigos del Set de Valores definidos desde SNOMED-CT
Código SNOMED-CT correspondiente al método de administración
Descripción del método de administración
Nombre legible del método de administración
Definición de la cantidad de fármaco a consumir
Cantidad del medicamento a administrar por dosis
Clasificación de si esta es una dosis ordenada, permitida, etc.
If the type is not populated, assume to be "ordered".
Sistema de codificación para tipo de dosis
Típicamente http://terminology.hl7.org/CodeSystem/dose-rate-type
Código que identifica si la dosis fue ordenada, es permitida, etc.
Dosis expresada como cantidad simple o rango
La dosis del medicamento puede ser una cantidad simple (doseQuantity) o un rango (doseRange)
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.
La cantidad (con unidades) de la dosis del medicamento cuando es una cantidad única sin rango
El valor numérico de la dosis (ej: 1, 2, 500)
Representación de la unidad de la cantidad de dosis (ej: TAB, mg, ml, comprimido)
Identificación del sistema de codificación para la unidad (ej: http://unitsofmeasure.org, http://terminology.hl7.org/CodeSystem/v3-orderableDrugForm)
Un código que especifica la unidad utilizada según el sistema definido (ej: TAB, mg)
La dosis cuando se expresa como un rango (dosis mínima y máxima)
If the low element is missing, the low boundary is not known.
Sistema de codificación para la unidad (ej: http://terminology.hl7.org/CodeSystem/v3-orderableDrugForm)
If the high element is missing, the high boundary is not known.
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.
Whether a substitution was performed on the dispense
Indicates whether or not substitution was made as part of the dispense. In some cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done.
.outboundRelationship[typeCode=COMP].target[classCode=SUBST, moodCode=EVN]
Whether a substitution was or was not performed on the dispense
True if the dispenser dispensed a different drug or product from what was prescribed.
Code signifying whether a different drug was dispensed from what was prescribed
A code signifying whether a different drug was dispensed from what was prescribed.
A coded concept describing whether a different medicinal product may be dispensed other than the product as specified exactly in the prescription.
RXO-9-Allow Substitutions / RXE-9-Substitution Status
Indicates the reason for the substitution (or lack of substitution) from what was prescribed.
A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.
The person or organization that has primary responsibility for the substitution.
Evento adverso detectado como contraindicación al fármaco dispensado
Indica un problema clínico real o potencial con acciones clínicas posibles (ej: interacción fármaco-fármaco, doble dosis, alergia conocida)
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.
URL o referencia al recurso que documenta el evento adverso o contraindicación detectada
Descripción del evento adverso en texto libre
Descripción legible del potencial evento adverso o contraindicación. Por el momento solo se considera la redacción en texto libre de este campo
A summary of the events of interest that have occurred, such as when the dispense was verified.
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]