Procesos
Egresos Hospitalarios
Aquí se presentan todos los recursos que se utilizaron para mapear la información de los egresos hospitalarios.
- Definición de estructura para los datos de los egresos hospitalarios, aqui se definen principalmente los campos utilizados del recurso Encounter de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/encounteregresoshospv3.
Encounter | Encounter | ||
status | |||
subject | Reference(Patient_apimin_v3) | ||
period | |||
end | |||
length | |||
diagnosis | |||
condition | Reference(Condition_egresosHosp_apimin_v3) | ||
location | |||
location | Reference(Location_apimin_v3) |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/Patientapiminv3.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
- Definición de estructura para los datos del establecimiento. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/organizationapimin.
Location | Location | ||
identifier | |||
system | |||
value | |||
name | |||
address | |||
text |
- Definición de estructura para los datos de las condiciones crónicas. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/conditionegresoshospapiminv3.
Condition | Condition | ||
code | |||
coding | |||
code | |||
display | |||
text | S |
Búsquedas
Parámetros de Búsqueda Egresos Hospitalarios
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
subject | token | Utilizado como el rut del paciente sin dígito verificador | Encounter.subject | subject.identifier=1111111 |
_profile | token | Utilizado como parametro identificador de esquema de datos por minsal y perfil FHIR | _profile | _profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios |
date | date | Fecha de egreso en formato YYYY-MM-DD | Encounter.date | date=ge2018-10-12 date=lt2018-10-12 date=2018-10-12 |
reason | token | Selección de tipo de egreso(intento de suicidio, condición crónica) | Encounter.reason | reason=condicionesCronicas reason=intentosSuicidio |
Prefijos implementados para búsquedas por fecha
Expresión | Definición | Ejemplo | Significado |
---|---|---|---|
ge | Mayor o Igual que | ge2018-10-12 | Resultados con fecha posterior o igual a 2018-10-12 |
lt | Menor que | lt2018-10-12 | Resultados con fecha anterior a 2018-10-12 |
Referencia: Documentación completa en FHIR
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/Encounter?subject.identifier=10533196&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios
- Búsqueda por rut y rango de fechas
GET [base]/Encounter?subject.identifier=10533196&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios&date=ge2017-06-12&date=lt2017-06-14
- Búsqueda de condiciones crónicas por rut
GET [base]/Encounter?subject:Patient.identifier=19824900&reason=condicionesCronicas&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios
- Búsqueda de intentos de suicidio por rut
GET [base]/Encounter?subject:Patient.identifier=19824900&reason=intentosSuicidio&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios
- Búsqueda de condiciones crónicas por rut y fecha
GET [base]/Encounter?subject.identifier=10533196&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios&date=ge2017-06-12&date=lt2017-06-14&reason=condicionesCronicas
- Búsqueda de intentos de suicidio por rut y fecha
GET [base]/Encounter?subject.identifier=10533196&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-egresosHospitalarios&date=ge2017-06-12&date=lt2017-06-14&reason=intentosSuicidio
Ejemplo de response
{ "resourceType": "Bundle", "id": "c2fa3bd1-59c0-488b-bfa0-7ef82e2907c8", "meta": { "lastUpdated": "2019-01-14T23:08:04.032-03:00" }, "type": "searchset", "total": 1, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Encounter?_profile=http%3A%2F%2Fcens.cl%2Ffhir%2FStructureDefinition%2Fhospitaldigital-egresosHospitalarios&date=ge2017-06-12&date=lt2017-06-14&subject.identifier=10533196" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Encounter/339776154", "resource": { "resourceType": "Encounter", "id": "339776154", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10533196" } ] }, { "resourceType": "Condition", "id": "con1", "code": { "text": "COLECISTITIS CRÓNICA/CÁLCULOS BILIARES" } }, { "resourceType": "Condition", "id": "con2", "code": { "coding": [ { "code": "K802", "display": "CALCULO DE LA VESICULA BILIAR SIN COLECISTITIS" } ], "text": "Diagnostico Principal" } }, { "resourceType": "Condition", "id": "con3", "code": { "text": "Causa Externa" } }, { "resourceType": "Location", "id": "loc", "identifier": [ { "system": "http://www.deis.cl", "value": "111295" } ], "name": "Clínica Bicentenario" } ], "status": "finished", "type": [ { "coding": [ { "system": "http://browser.ihtsdotools.org", "code": "27624003", "display": "enfermedad crónica" } ] } ], "subject": { "reference": "#p1" }, "period": { "start": "2017-06-12T00:00:00-04:00", "end": "2017-06-13T00:00:00-04:00" }, "length": { "value": 1 }, "diagnosis": [ { "condition": { "reference": "#con1" } }, { "condition": { "reference": "#con2" } }, { "condition": { "reference": "#con3" } } ], "location": [ { "location": { "reference": "#loc" } } ] } } ] }
Dicccionario de Datos
Diccionario de Encounter
Encounter | |
Definition | An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. |
Cardinality | 0...* |
Alias | Visit |
Invariants |
|
Mappings |
|
Encounter.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Encounter.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Encounter.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
Encounter.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
Encounter.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Encounter.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.identifier | |
Definition | Identifier(s) by which this encounter is known. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.status | |
Definition | Se define el estado del encuentro. |
Cardinality | 1...1 |
Type | code |
Binding | Current state of the encounter ?? (required) |
Modifier | True |
Summary | True |
Comments | Note that internal business rules will detemine the appropraite transitions that may occur between statuses (and also classes). This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid. |
Invariants |
|
Mappings |
|
Encounter.statusHistory | |
Definition | The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | The current status is always found in the current version of the resource, not the status history. |
Invariants |
|
Mappings |
|
Encounter.statusHistory.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.statusHistory.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.statusHistory.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.statusHistory.status | |
Definition | planned | arrived | triaged | in-progress | onleave | finished | cancelled +. |
Cardinality | 1...1 |
Type | code |
Binding | Current state of the encounter ?? (required) |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.statusHistory.period | |
Definition | The time that the episode was in the specified status. |
Cardinality | 1...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.class | |
Definition | inpatient | outpatient | ambulatory | emergency +. |
Cardinality | 0...1 |
Type | Coding |
Binding | Classification of the encounter ?? (extensible) |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory | |
Definition | The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Encounter.classHistory.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.classHistory.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.classHistory.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory.class | |
Definition | inpatient | outpatient | ambulatory | emergency +. |
Cardinality | 1...1 |
Type | Coding |
Binding | Classification of the encounter ?? (extensible) |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory.period | |
Definition | The time that the episode was in the specified class. |
Cardinality | 1...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.type | |
Definition | Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The type of encounter ?? (example) |
Summary | True |
Comments | Since there are many ways to further classify encounters, this element is 0..*. |
Invariants |
|
Mappings |
|
Encounter.priority | |
Definition | Indicates the urgency of the encounter. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Indicates the urgency of the encounter. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.subject | |
Definition | A quien hace referencia el encuentro. Usualmente es a un paciente, pero no siempre es así. |
Cardinality | 0...1 |
Type | Reference(Patient_apimin_v3) |
Summary | True |
Alias | patient |
Comments | While the encounter is always about the patient, the patient may not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked). |
Invariants |
|
Mappings |
|
Encounter.episodeOfCare | |
Definition | Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.incomingReferral | |
Definition | The referral request this encounter satisfies (incoming referral). |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/ReferralRequest) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.participant | |
Definition | The list of people responsible for providing the service. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.participant.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.participant.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.participant.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.participant.type | |
Definition | Role of participant in encounter. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Role of participant in encounter ?? (extensible) |
Summary | True |
Comments | The participant type indicates how an individual partitipates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc. |
Invariants |
|
Mappings |
|
Encounter.participant.period | |
Definition | The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. |
Cardinality | 0...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.participant.individual | |
Definition | Persons involved in the encounter other than the patient. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner | http://hl7.org/fhir/StructureDefinition/RelatedPerson) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.appointment | |
Definition | The appointment that scheduled this encounter. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Appointment) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.period | |
Definition | The start and end time of the encounter. |
Cardinality | 0...1 |
Type | Period |
Comments | If not (yet) known, the end of the Period may be omitted. |
Invariants |
|
Mappings |
|
Encounter.period.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.period.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.period.start | |
Definition | The start of the period. The boundary is inclusive. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | If the low element is missing, the meaning is that the low boundary is not known. |
Invariants |
|
Mappings |
|
Encounter.period.end | |
Definition | The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
Invariants |
|
Mappings |
|
Encounter.length | |
Definition | Cantidad de días en que se llevo a cabo el encuentro. |
Cardinality | 0...1 |
Type | Duration |
Comments | May differ from the time the Encounter.period lasted because of leave of absence. |
Invariants |
|
Mappings |
|
Encounter.reason | |
Definition | Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Reason why the encounter takes place. ?? (preferred) |
Summary | True |
Alias | Indication, Admission diagnosis |
Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). |
Invariants |
|
Mappings |
|
Encounter.diagnosis | |
Definition | The list of diagnosis relevant to this encounter. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.diagnosis.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.diagnosis.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.diagnosis.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition | |
Definition | Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. |
Cardinality | 1...1 |
Type | Reference(Condition_egresosHosp_apimin_v3) |
Alias | Admission diagnosis, discharge diagnosis, indication |
Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). |
Invariants |
|
Mappings |
|
Encounter.diagnosis.role | |
Definition | Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The type of diagnosis this condition represents ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.rank | |
Definition | Ranking of the diagnosis (for each role type). |
Cardinality | 0...1 |
Type | positiveInt |
Comments | 32 bit number; for values larger than this, use decimal |
Invariants |
|
Mappings |
|
Encounter.account | |
Definition | The set of accounts that may be used for billing for this Encounter. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Account) |
Comments | The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules. |
Invariants |
|
Mappings |
|
Encounter.hospitalization | |
Definition | Details about the admission to a healthcare service. |
Cardinality | 0...1 |
Type | BackboneElement |
Comments | An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.hospitalization.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.hospitalization.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.preAdmissionIdentifier | |
Definition | Pre-admission identifier. |
Cardinality | 0...1 |
Type | Identifier |
Invariants |
|
Mappings |
|
Encounter.hospitalization.origin | |
Definition | The location from which the patient came before admission. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Location) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.admitSource | |
Definition | From where patient was admitted (physician referral, transfer). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | From where the patient was admitted. ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.reAdmission | |
Definition | Whether this hospitalization is a readmission and why if known. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The reason for re-admission of this hospitalization encounter. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.dietPreference | |
Definition | Diet preferences reported by the patient. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Medical, cultural or ethical food preferences to help with catering requirements. ?? (example) |
Requirements | Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter. |
Comments | For example a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). |
Invariants |
|
Mappings |
|
Encounter.hospitalization.specialCourtesy | |
Definition | Special courtesies (VIP, board member). |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Special courtesies ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.specialArrangement | |
Definition | Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Special arrangements ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.destination | |
Definition | Location to which the patient is discharged. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Location) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.dischargeDisposition | |
Definition | Category or kind of location after discharge. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Discharge Disposition ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.location | |
Definition | List of locations where the patient has been during this encounter. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". |
Invariants |
|
Mappings |
|
Encounter.location.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.location.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.location.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.location.location | |
Definition | The location where the encounter takes place. |
Cardinality | 1...1 |
Type | Reference(Location_apimin_v3) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.location.status | |
Definition | The status of the participants' presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time. |
Cardinality | 0...1 |
Type | code |
Binding | The status of the location. ?? (required) |
Comments | When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. |
Invariants |
|
Mappings |
|
Encounter.location.period | |
Definition | Time period during which the patient was present at the location. |
Cardinality | 0...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider | |
Definition | An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.partOf | |
Definition | Another Encounter of which this encounter is a part of (administratively or in time). |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter) |
Comments | This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details. |
Invariants |
|
Mappings |
|
Intervenciones Quirurgicas
Aquí se presentan todos los recursos que se utilizaron para mapear la información de las intervenciones quirurgicas.
- Definición de estructura para los datos de las intervenciones quirurgicas, aqui se definen principalmente los campos utilizados del recurso Procedure de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/procedureinterqv3.
Procedure | Procedure | ||
status | |||
code | |||
coding | |||
code | |||
display | |||
subject | Reference(Patient_apimin_v3) | ||
performedPeriod | Period | ||
end |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/patientapimin.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
Búsquedas
Parámetros de Búsqueda Intervenciones Quirúrgicas
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
subject | token | Utilizado como el rut del paciente sin dígito verificador | Procedure.subject | subject:Patient.identifier=1111111 |
_profile | token | Utilizado como parametro identificador de esquema de datos por minsal y perfil FHIR | _profile | _profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-interQuirurgicas |
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/Procedure?subject:Patient.identifier=12434844&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-interQuirurgicas
Ejemplo de response
{ "resourceType": "Bundle", "id": "0920d64e-0ba9-4405-93a9-1c96000caa40", "meta": { "lastUpdated": "2019-01-14T23:12:24.929-03:00" }, "type": "searchset", "total": 1, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Procedure?_profile=http%3A%2F%2Fcens.cl%2Ffhir%2FStructureDefinition%2Fhospitaldigital-interQuirurgicas&subject%3APatient.identifier=12434844" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Procedure/3852914", "resource": { "resourceType": "Procedure", "id": "3852914", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "12434844" } ] } ], "status": "completed", "code": { "coding": [ { "code": "1103048", "display": "Neurotomía facetaria percutanea, incluye bloqueo facetario " }, { "code": "N/A", "display": "N/A" }, { "code": "N/A", "display": "N/A" } ] }, "subject": { "reference": "#p1" }, "performedPeriod": { "end": "2017-08-23T00:00:00-03:00" } } } ] }
Dicccionario de Datos
Diccionario de Procedure
Procedure | |
Definition | An action that is or was performed on a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Procedure.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Procedure.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Procedure.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
Procedure.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
Procedure.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Procedure.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.identifier | |
Definition | This records identifiers associated with this procedure that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Requirements | Need to allow connection to a wider workflow. |
Invariants |
|
Mappings |
|
Procedure.definition | |
Definition | A protocol, guideline, orderset or other definition that was adhered to in whole or in part by this procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/PlanDefinition | http://hl7.org/fhir/StructureDefinition/ActivityDefinition | http://hl7.org/fhir/StructureDefinition/HealthcareService) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.basedOn | |
Definition | A reference to a resource that contains details of the request for this procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/CarePlan | http://hl7.org/fhir/StructureDefinition/ProcedureRequest | http://hl7.org/fhir/StructureDefinition/ReferralRequest) |
Summary | True |
Alias | fulfills |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.partOf | |
Definition | A larger event of which this particular procedure is a component or step. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Procedure | http://hl7.org/fhir/StructureDefinition/Observation | http://hl7.org/fhir/StructureDefinition/MedicationAdministration) |
Summary | True |
Alias | container |
Comments | The MedicationAdministration has a partOf reference to Procedure, but this is not a circular reference. For a surgical procedure, the anesthesia related medicationAdministration is part of the procedure. For an IV medication administration, the procedure to insert the IV port is part of the medication administration. |
Invariants |
|
Mappings |
|
Procedure.status | |
Definition | Se define el estado del procedimiento. |
Cardinality | 1...1 |
Type | code |
Binding | A code specifying the state of the procedure. ?? (required) |
Modifier | True |
Summary | True |
Comments | The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
Procedure.notDone | |
Definition | Set this to true if the record is saying that the procedure was NOT performed. |
Cardinality | 0...1 |
Type | boolean |
Modifier | True |
Summary | True |
Comments | If true, it means the procedure did not occur as described. Typically it would be accompanied by attributes describing the type of activity. It might also be accompanied by body site information or time information (i.e. no procedure was done to the left arm or no procedure was done in this 2-year period). Specifying additional information such as performer, outcome, etc. is generally inappropriate. For example, it's not that useful to say "There was no appendectomy done at 12:03pm June 6th by Dr. Smith with a successful outcome" as it implies that there could have been an appendectomy done at any other time, by any other clinician or with any other outcome. This element is labeled as a modifier because it indicates that a procedure didn't happen. |
Invariants |
|
Mappings |
|
Procedure.notDoneReason | |
Definition | A code indicating why the procedure was not performed. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure was not performed. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.category | |
Definition | A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that classifies a procedure for searching, sorting and display purposes. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.code | |
Definition | The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code to identify a specific procedure . ?? (example) |
Summary | True |
Alias | type |
Requirements | 0..1 to account for primarily narrative only resources. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.code.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.code.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.code.coding | |
Definition | Códigos que hacen referencia a algún sistema de codificación. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.coding.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.code.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.code.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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 de-reference to some definition that establish the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Procedure.code.coding.version | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.coding.code | |
Definition | Aquí se ingresa el valor del código de la intervención. |
Cardinality | 0...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.code.coding.display | |
Definition | Nombre completo que hace referencia al código de la intervención. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.code.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.code.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.subject | |
Definition | The person, animal or group on which the procedure was performed. |
Cardinality | 1...1 |
Type | Reference(Patient_apimin_v3) |
Summary | True |
Alias | patient |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.context | |
Definition | The encounter during which the procedure was performed. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter | http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) |
Summary | True |
Alias | encounter |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performed[x]:performedPeriod | |
Definition | Periodo durante el cual el procedimiento fue realizado |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.performed[x]:performedPeriod.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.performed[x]:performedPeriod.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performed[x]:performedPeriod.start | |
Definition | The start of the period. The boundary is inclusive. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | If the low element is missing, the meaning is that the low boundary is not known. |
Invariants |
|
Mappings |
|
Procedure.performed[x]:performedPeriod.end | |
Definition | Fecha en que se término el periodo de realización del procedimiento. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
Invariants |
|
Mappings |
|
Procedure.performer | |
Definition | Limited to 'real' people rather than equipment. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.performer.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.performer.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performer.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.performer.role | |
Definition | For example: surgeon, anaethetist, endoscopist. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that identifies the role of a performer of the procedure. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.performer.actor | |
Definition | The practitioner who was involved in the procedure. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner | http://hl7.org/fhir/StructureDefinition/Organization | http://hl7.org/fhir/StructureDefinition/Patient | http://hl7.org/fhir/StructureDefinition/RelatedPerson | http://hl7.org/fhir/StructureDefinition/Device) |
Summary | True |
Requirements | A reference to Device supports use cases, such as pacemakers. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performer.onBehalfOf | |
Definition | The organization the device or practitioner was acting on behalf of. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.location | |
Definition | The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Location) |
Summary | True |
Requirements | Ties a procedure to where the records are likely kept. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.reasonCode | |
Definition | The coded reason why the procedure was performed. This may be coded entity of some type, or may simply be present as text. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure is required. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.reasonReference | |
Definition | The condition that is the reason why the procedure was performed. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition | http://hl7.org/fhir/StructureDefinition/Observation) |
Summary | True |
Comments | e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic. |
Invariants |
|
Mappings |
|
Procedure.bodySite | |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.outcome | |
Definition | The outcome of the procedure - did it resolve reasons for the procedure being performed? |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | An outcome of a procedure - whether it was resolved or otherwise. ?? (example) |
Summary | True |
Comments | If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.report | |
Definition | This could be a histology result, pathology report, surgical report, etc.. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport) |
Comments | There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
Invariants |
|
Mappings |
|
Procedure.complication | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing complications that resulted from a procedure. ?? (example) |
Comments | If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition) |
Requirements | This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.followUp | |
Definition | If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or could potentially be more complex in which case the CarePlan resource can be used. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Specific follow up required for a procedure e.g. removal of sutures. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.note | |
Definition | Any other notes about the procedure. E.g. the operative notes. |
Cardinality | 0...* |
Type | Annotation |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
Procedure.focalDevice | |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Procedure.focalDevice.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.focalDevice.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.focalDevice.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.action | |
Definition | The kind of change that happened to the device during the procedure. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A kind of change that happened to the device during the procedure. ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.manipulated | |
Definition | The device that was manipulated (changed) during the procedure. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Device) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.usedReference | |
Definition | Identifies medications, devices and any other substance used as part of the procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Device | http://hl7.org/fhir/StructureDefinition/Medication | http://hl7.org/fhir/StructureDefinition/Substance) |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|
Procedure.usedCode | |
Definition | Identifies coded items that were used as part of the procedure. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing items used during a procedure ?? (example) |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|
Ingresos Urgencias
Aquí se presentan todos los recursos que se utilizaron para mapear la información de los Ingresos de Urgencias.
- Definición de estructura para los datos de las ingresos de urgencias, aqui se definen principalmente los campos utilizados del recurso Encounter de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/encounteringresosurgenciasv3.
Encounter | Encounter | ||
status | |||
subject | Reference(http://hl7.org/fhir/StructureDefinition/Patient | Patient_apimin_v3) | ||
period | |||
start | |||
end | |||
reason | |||
text | |||
diagnosis | |||
condition | Reference(http://hl7.org/fhir/StructureDefinition/Condition | Condition_ingresosUrgencias_v3) | ||
location | |||
location | Reference(Location_apimin_v3) |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/Patientapiminv3.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
- Definición de estructura para los datos del encuentro. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/encounterapimin.
Encounter | Encounter | ||
period | |||
start | |||
end | |||
reason | |||
text | |||
serviceProvider | Reference(Organization_apimin) |
- Definición de estructura para los datos del establecimiento. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/Locationapiminv3.
Location | Location | ||
identifier | |||
system | |||
value | |||
name | |||
address | |||
text |
- Definición estructura para datos de diagnosticos en ingresos de urgencias. Con mas detalle podemos observar como se exponen los datos en https://simplifier.net/test-api-minsal/ConditioningresosUrgenciasv3.
Condition | Condition | ||
code | |||
coding | |||
code | |||
display | |||
text | S |
Búsquedas
Parámetros de Búsqueda Ingresos Urgencias
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
subject | token | Utilizado como el rut del paciente sin dígito verificador | DiagnosticReport.subject | subject.identifier=1111111 |
_profile | token | Utilizado como parametro identificador de esquema de datos por minsal y perfil FHIR | _profile | _profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-ingresosUrgencia |
date | date | Fecha de atención en formato YYYY-MM-DD | Encounter.date | date=ge2018-10-12 date=lt2018-10-12 date=2018-10-12 |
Prefijos implementados para búsquedas por fecha
Expresión | Definición | Ejemplo | Significado |
---|---|---|---|
ge | Mayor o Igual que | ge2018-10-12 | Resultados con fecha posterior o igual a 2018-10-12 |
lt | Menor que | lt2018-10-12 | Resultados con fecha anterior a 2018-10-12 |
Referencia: Documentación completa en FHIR
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/Encounter?subject.identifier=12803572&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-ingresosUrgencia
- Búsqueda por rut y rango de fechas
GET [base]/Encounter?subject.identifier=12803572&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-ingresosUrgencia&date=ge2016-01-01&date=lt2016-01-18
Ejemplo de response
{ "resourceType": "Bundle", "id": "f396846f-d872-498e-aad1-c6dc6470d28a", "meta": { "lastUpdated": "2019-01-14T23:15:47.781-03:00" }, "type": "searchset", "total": 2, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Encounter?_profile=http%3A%2F%2Fcens.cl%2Ffhir%2FStructureDefinition%2Fhospitaldigital-ingresosUrgencia&subject.identifier=12803572" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Encounter/2453", "resource": { "resourceType": "Encounter", "id": "2453", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "12803572" } ] }, { "resourceType": "Condition", "id": "con1", "code": { "coding": [ { "code": "A09" }, { "display": "DIARREA Y GASTROENTERITIS DE PRESUNTO ORIGEN INFECCIOSO" } ], "text": "Hipotesis Diagnostica" } }, { "resourceType": "Condition", "id": "con2", "code": { "coding": [ { "code": "A09" }, { "display": "DIARREA Y GASTROENTERITIS DE PRESUNTO ORIGEN INFECCIOSO" } ], "text": "Diagnostico Final" } }, { "resourceType": "Location", "id": "loc", "identifier": [ { "system": "http://www.deis.cl", "value": "101303" } ], "name": "Centro de Salud Familiar Iris Véliz Hume (Ex Oriente)" } ], "status": "?", "subject": { "reference": "#p1" }, "period": { "start": "2016-01-10T00:00:00-03:00", "end": "2016-01-10T00:00:00-03:00" }, "reason": [ { "text": "VOMITOS NAUSEAS DOLOR DE CABEZA" } ], "diagnosis": [ { "condition": { "reference": "#con1" } }, { "condition": { "reference": "#con2" } } ], "location": [ { "location": { "reference": "#loc" } } ] } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Encounter/2454", "resource": { "resourceType": "Encounter", "id": "2454", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "12803572" } ] }, { "resourceType": "Condition", "id": "con1", "code": { "text": "Hipotesis Diagnostica" } }, { "resourceType": "Condition", "id": "con2", "code": { "text": "Diagnostico Final" } }, { "resourceType": "Location", "id": "loc", "identifier": [ { "system": "http://www.deis.cl", "value": "101303" } ], "name": "Centro de Salud Familiar Iris Véliz Hume (Ex Oriente)" } ], "status": "?", "subject": { "reference": "#p1" }, "period": { "start": "2016-01-19T00:00:00-03:00", "end": "2016-01-19T00:00:00-03:00" }, "reason": [ { "text": "DOLOR AL ORINAR Y DOLOR DE ESPALDA, Y VOMITO" } ], "diagnosis": [ { "condition": { "reference": "#con1" } }, { "condition": { "reference": "#con2" } } ], "location": [ { "location": { "reference": "#loc" } } ] } } ] }
Dicccionario de Datos
Diccionario de Encounter
Encounter | |
Definition | An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. |
Cardinality | 0...* |
Alias | Visit |
Invariants |
|
Mappings |
|
Encounter.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Encounter.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Encounter.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
Encounter.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
Encounter.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Encounter.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.identifier | |
Definition | Identifier(s) by which this encounter is known. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.status | |
Definition | Se define el estado del encuentro. |
Cardinality | 1...1 |
Type | code |
Binding | Current state of the encounter ?? (required) |
Modifier | True |
Summary | True |
Comments | Note that internal business rules will detemine the appropraite transitions that may occur between statuses (and also classes). This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid. |
Invariants |
|
Mappings |
|
Encounter.statusHistory | |
Definition | The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | The current status is always found in the current version of the resource, not the status history. |
Invariants |
|
Mappings |
|
Encounter.statusHistory.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.statusHistory.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.statusHistory.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.statusHistory.status | |
Definition | planned | arrived | triaged | in-progress | onleave | finished | cancelled +. |
Cardinality | 1...1 |
Type | code |
Binding | Current state of the encounter ?? (required) |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.statusHistory.period | |
Definition | The time that the episode was in the specified status. |
Cardinality | 1...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.class | |
Definition | inpatient | outpatient | ambulatory | emergency +. |
Cardinality | 0...1 |
Type | Coding |
Binding | Classification of the encounter ?? (extensible) |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory | |
Definition | The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Encounter.classHistory.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.classHistory.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.classHistory.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory.class | |
Definition | inpatient | outpatient | ambulatory | emergency +. |
Cardinality | 1...1 |
Type | Coding |
Binding | Classification of the encounter ?? (extensible) |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.classHistory.period | |
Definition | The time that the episode was in the specified class. |
Cardinality | 1...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.type | |
Definition | Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The type of encounter ?? (example) |
Summary | True |
Comments | Since there are many ways to further classify encounters, this element is 0..*. |
Invariants |
|
Mappings |
|
Encounter.priority | |
Definition | Indicates the urgency of the encounter. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Indicates the urgency of the encounter. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.subject | |
Definition | The patient ro group present at the encounter. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Patient | Patient_apimin_v3) |
Summary | True |
Alias | patient |
Comments | While the encounter is always about the patient, the patient may not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked). |
Invariants |
|
Mappings |
|
Encounter.episodeOfCare | |
Definition | Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.incomingReferral | |
Definition | The referral request this encounter satisfies (incoming referral). |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/ReferralRequest) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.participant | |
Definition | The list of people responsible for providing the service. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.participant.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.participant.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.participant.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.participant.type | |
Definition | Role of participant in encounter. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Role of participant in encounter ?? (extensible) |
Summary | True |
Comments | The participant type indicates how an individual partitipates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc. |
Invariants |
|
Mappings |
|
Encounter.participant.period | |
Definition | The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. |
Cardinality | 0...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.participant.individual | |
Definition | Persons involved in the encounter other than the patient. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner | http://hl7.org/fhir/StructureDefinition/RelatedPerson) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.appointment | |
Definition | The appointment that scheduled this encounter. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Appointment) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.period | |
Definition | The start and end time of the encounter. |
Cardinality | 0...1 |
Type | Period |
Comments | If not (yet) known, the end of the Period may be omitted. |
Invariants |
|
Mappings |
|
Encounter.period.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.period.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.period.start | |
Definition | Fecha en la cual comienza la atención del paciente. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | If the low element is missing, the meaning is that the low boundary is not known. |
Invariants |
|
Mappings |
|
Encounter.period.end | |
Definition | Fecha en la cual finaliza la atención del paciente (Fecha de alta médica). |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
Invariants |
|
Mappings |
|
Encounter.length | |
Definition | Quantity of time the encounter lasted. This excludes the time during leaves of absence. |
Cardinality | 0...1 |
Type | Duration |
Comments | May differ from the time the Encounter.period lasted because of leave of absence. |
Invariants |
|
Mappings |
|
Encounter.reason | |
Definition | Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Reason why the encounter takes place. ?? (preferred) |
Summary | True |
Alias | Indication, Admission diagnosis |
Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). |
Invariants |
|
Mappings |
|
Encounter.reason.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.reason.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.reason.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.reason.text | |
Definition | Razón por la cual el paciente acude al centro de atención. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Encounter.diagnosis | |
Definition | The list of diagnosis relevant to this encounter. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.diagnosis.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.diagnosis.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.diagnosis.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition | |
Definition | Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition | Condition_ingresosUrgencias_v3) |
Alias | Admission diagnosis, discharge diagnosis, indication |
Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). |
Invariants |
|
Mappings |
|
Encounter.diagnosis.role | |
Definition | Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The type of diagnosis this condition represents ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.rank | |
Definition | Ranking of the diagnosis (for each role type). |
Cardinality | 0...1 |
Type | positiveInt |
Comments | 32 bit number; for values larger than this, use decimal |
Invariants |
|
Mappings |
|
Encounter.account | |
Definition | The set of accounts that may be used for billing for this Encounter. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Account) |
Comments | The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules. |
Invariants |
|
Mappings |
|
Encounter.hospitalization | |
Definition | Details about the admission to a healthcare service. |
Cardinality | 0...1 |
Type | BackboneElement |
Comments | An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.hospitalization.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.hospitalization.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.preAdmissionIdentifier | |
Definition | Pre-admission identifier. |
Cardinality | 0...1 |
Type | Identifier |
Invariants |
|
Mappings |
|
Encounter.hospitalization.origin | |
Definition | The location from which the patient came before admission. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Location) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.admitSource | |
Definition | From where patient was admitted (physician referral, transfer). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | From where the patient was admitted. ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.reAdmission | |
Definition | Whether this hospitalization is a readmission and why if known. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The reason for re-admission of this hospitalization encounter. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.dietPreference | |
Definition | Diet preferences reported by the patient. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Medical, cultural or ethical food preferences to help with catering requirements. ?? (example) |
Requirements | Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter. |
Comments | For example a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). |
Invariants |
|
Mappings |
|
Encounter.hospitalization.specialCourtesy | |
Definition | Special courtesies (VIP, board member). |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Special courtesies ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.specialArrangement | |
Definition | Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Special arrangements ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.destination | |
Definition | Location to which the patient is discharged. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Location) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.hospitalization.dischargeDisposition | |
Definition | Category or kind of location after discharge. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Discharge Disposition ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.location | |
Definition | List of locations where the patient has been during this encounter. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". |
Invariants |
|
Mappings |
|
Encounter.location.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.location.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.location.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.location.location | |
Definition | The location where the encounter takes place. |
Cardinality | 1...1 |
Type | Reference(Location_apimin_v3) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.location.status | |
Definition | The status of the participants' presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time. |
Cardinality | 0...1 |
Type | code |
Binding | The status of the location. ?? (required) |
Comments | When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. |
Invariants |
|
Mappings |
|
Encounter.location.period | |
Definition | Time period during which the patient was present at the location. |
Cardinality | 0...1 |
Type | Period |
Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider | |
Definition | An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.partOf | |
Definition | Another Encounter of which this encounter is a part of (administratively or in time). |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter) |
Comments | This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details. |
Invariants |
|
Mappings |
|
FOFAR Medicamentos Programados y Dispensados
Aquí se presentan todos los recursos que se utilizaron para mapear la información de FOFAR Medicamentos Programados y Dispensados.
- Definición de estructura para los datos de FOFAR Medicamentos Programados y Dispensados, aqui se definen principalmente los campos utilizados del recurso MedicationRequest de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/medicationrequestmedicamentosv3.
MedicationRequest | MedicationRequest | ||
medicationReference | Reference(Medication_apimin) | ||
subject | Reference(Patient_apimin_v3) | ||
authoredOn | |||
dosageInstruction | |||
rate[x] | |||
rateQuantity | http://hl7.org/fhir/StructureDefinition/SimpleQuantity | ||
rateRatio | Ratio_apimin_v3 | ||
dispenseRequest | |||
validityPeriod | |||
end | |||
numberOfRepeatsAllowed |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/patientapimin.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
- Definición de estructura para los datos de los medicamentos. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/medicationapiminv3.
Medication | Medication | ||
code | |||
coding | |||
system | |||
code | |||
text |
- Definición del tipo de dato Ratio para la utilización en MedicationRequest. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/ratioapiminv3.
Ratio | Ratio | ||
numerator | |||
value | |||
denominator | |||
value |
Búsquedas
Parámetros de Búsqueda Medicamentos
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
patient | token | Utilizado como el rut del paciente sin dígito verificador | MedicationRequest.subject | patient.identifier=1111111 |
authoredOn | date | Fecha de la emisión de la receta YYYY-MM-DD | MedicationRequest.authoredOn | date=2018-10-12 date=ge2018-10-12 date=lt2018-10-12 |
Prefijos implementados para búsquedas por fecha
Expresión | Definición | Ejemplo | Significado | |
---|---|---|---|---|
ge | Mayor o Igual que | ge2018-10-12 | Resultados con fecha posterior o igual a 2018-10-12 | |
lt | Menor que | lt2018-10-12 | Resultados con fecha anterior a 2018-10-12 |
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/MedicationRequest?patient.identifer=10029459
- Búsqueda por rut y rango de fechas
GET [base]/MedicationRequest?patient.identifer=10029459&authoredon=ge2014-04-24&authoredon=lt2018-01-03
Referencia: Documentación completa en FHIR
Ejemplo de response
{ "resourceType": "Bundle", "id": "fb23e782-b968-4aa5-80d5-2af06ebac9dc", "meta": { "lastUpdated": "2019-01-14T23:28:33.363-03:00" }, "type": "searchset", "total": 5, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest?authoredon=ge2017-11-24&authoredon=lt2017-12-24&patient.identifer=10029459" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest/35387266", "resource": { "resourceType": "MedicationRequest", "id": "35387266", "contained": [ { "resourceType": "Medication", "id": "med1", "code": { "coding": [ { "system": "https://www.whocc.no/atc_ddd_index/", "code": "C08CA05" }, { "system": "http://www.minsal.cl/", "code": "1951" } ], "text": "nifedipino 20 mg comprimido liberación modificada" } }, { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10029459" } ] } ], "medicationReference": { "reference": "#med1" }, "subject": { "reference": "#p1" }, "authoredOn": "2017-12-23T00:00:00-03:00", "dosageInstruction": [ { "rateRatio": { "numerator": { "value": 1, "unit": "Dosis" }, "denominator": { "value": 2, "unit": "Frecuencia" } } } ], "dispenseRequest": { "validityPeriod": { "end": "2018-12-23T00:00:00-03:00" }, "numberOfRepeatsAllowed": 23 } } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest/35387271", "resource": { "resourceType": "MedicationRequest", "id": "35387271", "contained": [ { "resourceType": "Medication", "id": "med1", "code": { "coding": [ { "system": "https://www.whocc.no/atc_ddd_index/", "code": "C03AA03" }, { "system": "http://www.minsal.cl/", "code": "1805" } ], "text": "hidroclorotiazida 50 mg comprimido" } }, { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10029459" } ] } ], "medicationReference": { "reference": "#med1" }, "subject": { "reference": "#p1" }, "authoredOn": "2017-12-23T00:00:00-03:00", "dosageInstruction": [ { "rateRatio": { "numerator": { "value": 0, "unit": "Dosis" }, "denominator": { "value": 1, "unit": "Frecuencia" } } } ], "dispenseRequest": { "validityPeriod": { "end": "2018-12-23T00:00:00-03:00" }, "numberOfRepeatsAllowed": 23 } } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest/35387290", "resource": { "resourceType": "MedicationRequest", "id": "35387290", "contained": [ { "resourceType": "Medication", "id": "med1", "code": { "coding": [ { "system": "https://www.whocc.no/atc_ddd_index/", "code": "B01AC06" }, { "system": "http://www.minsal.cl/", "code": "1968" } ], "text": "ácido acetilsalicílico 100 mg comprimido" } }, { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10029459" } ] } ], "medicationReference": { "reference": "#med1" }, "subject": { "reference": "#p1" }, "authoredOn": "2017-12-23T00:00:00-03:00", "dosageInstruction": [ { "rateRatio": { "numerator": { "value": 1, "unit": "Dosis" }, "denominator": { "value": 1, "unit": "Frecuencia" } } } ], "dispenseRequest": { "validityPeriod": { "end": "2018-12-23T00:00:00-03:00" }, "numberOfRepeatsAllowed": 23 } } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest/35387343", "resource": { "resourceType": "MedicationRequest", "id": "35387343", "contained": [ { "resourceType": "Medication", "id": "med1", "code": { "coding": [ { "system": "https://www.whocc.no/atc_ddd_index/", "code": "C09CA01" }, { "system": "http://www.minsal.cl/", "code": "1692" } ], "text": "losartán potásico 50 mg comprimido" } }, { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10029459" } ] } ], "medicationReference": { "reference": "#med1" }, "subject": { "reference": "#p1" }, "authoredOn": "2017-12-23T00:00:00-03:00", "dosageInstruction": [ { "rateRatio": { "numerator": { "value": 1, "unit": "Dosis" }, "denominator": { "value": 2, "unit": "Frecuencia" } } } ], "dispenseRequest": { "validityPeriod": { "end": "2018-12-23T00:00:00-03:00" }, "numberOfRepeatsAllowed": 23 } } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/MedicationRequest/35387605", "resource": { "resourceType": "MedicationRequest", "id": "35387605", "contained": [ { "resourceType": "Medication", "id": "med1", "code": { "coding": [ { "system": "https://www.whocc.no/atc_ddd_index/", "code": "A10BA02" }, { "system": "http://www.minsal.cl/", "code": "88" } ], "text": "metformina 850 mg comprimido" } }, { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "10029459" } ] } ], "medicationReference": { "reference": "#med1" }, "subject": { "reference": "#p1" }, "authoredOn": "2017-12-23T00:00:00-03:00", "dosageInstruction": [ { "rateRatio": { "numerator": { "value": 1, "unit": "Dosis" }, "denominator": { "value": 2, "unit": "Frecuencia" } } } ], "dispenseRequest": { "validityPeriod": { "end": "2018-12-23T00:00:00-03:00" }, "numberOfRepeatsAllowed": 23 } } } ] }
Dicccionario de Datos
Diccionario de MedicationRequest
MedicationRequest | |
Definition | 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. |
Cardinality | 0...* |
Alias | Prescription, Order |
Invariants |
|
Mappings |
|
MedicationRequest.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
MedicationRequest.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
MedicationRequest.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
MedicationRequest.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
MedicationRequest.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
MedicationRequest.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
MedicationRequest.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.identifier | |
Definition | This records identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. For example a re-imbursement system might issue its own id for each prescription that is created. This is particularly important where FHIR only provides part of an entire workflow process where records must be tracked through an entire system. |
Cardinality | 0...* |
Type | Identifier |
Invariants |
|
Mappings |
|
MedicationRequest.definition | |
Definition | Protocol or definition followed by this request. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/ActivityDefinition | http://hl7.org/fhir/StructureDefinition/PlanDefinition) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.basedOn | |
Definition | A plan or request that is fulfilled in whole or in part by this medication request. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/CarePlan | http://hl7.org/fhir/StructureDefinition/MedicationRequest | http://hl7.org/fhir/StructureDefinition/ProcedureRequest | http://hl7.org/fhir/StructureDefinition/ReferralRequest) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.groupIdentifier | |
Definition | A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition or prescription. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Requirements | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.status | |
Definition | A code specifying the current state of the order. Generally this will be active or completed state. |
Cardinality | 0...1 |
Type | code |
Binding | A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription ?? (required) |
Modifier | True |
Summary | True |
Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
MedicationRequest.intent | |
Definition | Whether the request is a proposal, plan, or an original order. |
Cardinality | 1...1 |
Type | code |
Binding | The kind of medication order ?? (required) |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.category | |
Definition | Indicates the type of medication order and where the medication is expected to be consumed or administered. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept identifying where the medication ordered is expected to be consumed or administered ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
MedicationRequest.priority | |
Definition | Indicates how quickly the Medication Request should be addressed with respect to other requests. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the level of importance to be assigned to actioning the request ?? (required) |
Summary | True |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.medication[x]:medicationReference | |
Definition | 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. |
Cardinality | 1...1 |
Type | Reference(Medication_apimin) |
Summary | True |
Comments | 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. . |
Invariants |
|
Mappings |
|
MedicationRequest.subject | |
Definition | Referencia a quien se le entrega el medicamento. |
Cardinality | 1...1 |
Type | Reference(Patient_apimin_v3) |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.context | |
Definition | A link to an encounter, or episode of care, that identifies the particular occurrence or set occurrences of contact between patient and health care provider. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter | http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) |
Comments | SubstanceAdministration->component->EncounterEvent. |
Invariants |
|
Mappings |
|
MedicationRequest.supportingInformation | |
Definition | Include additional information (for example, patient height and weight) that supports the ordering of the medication. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Resource) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.authoredOn | |
Definition | Fecha en que el médico emitió la receta. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Invariants |
|
Mappings |
|
MedicationRequest.requester | |
Definition | The individual, organization or device that initiated the request and has responsibility for its activation. |
Cardinality | 0...1 |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
MedicationRequest.requester.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.requester.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.requester.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.requester.agent | |
Definition | The healthcare professional responsible for authorizing the initial prescription. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner | http://hl7.org/fhir/StructureDefinition/Organization | http://hl7.org/fhir/StructureDefinition/Patient | http://hl7.org/fhir/StructureDefinition/RelatedPerson | http://hl7.org/fhir/StructureDefinition/Device) |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.requester.onBehalfOf | |
Definition | The organization the device or practitioner was acting on behalf of. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Summary | True |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.recorder | |
Definition | The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.reasonCode | |
Definition | The reason or the indication for ordering the medication. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A coded concept indicating why the medication was ordered. ?? (example) |
Comments | This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. |
Invariants |
|
Mappings |
|
MedicationRequest.reasonReference | |
Definition | Condition or observation that supports why the medication was ordered. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition | http://hl7.org/fhir/StructureDefinition/Observation) |
Comments | This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode. |
Invariants |
|
Mappings |
|
MedicationRequest.note | |
Definition | Extra information about the prescription that could not be conveyed by the other attributes. |
Cardinality | 0...* |
Type | Annotation |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction | |
Definition | Indicates how the medication is to be used by the patient. |
Cardinality | 0...* |
Type | Dosage |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.sequence | |
Definition | Indicates the order in which the dosage instructions should be applied or interpreted. |
Cardinality | 0...1 |
Type | integer |
Summary | True |
Requirements | 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. |
Comments | 32 bit number; for values larger than this, use decimal |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.text | |
Definition | Free text dosage instructions e.g. SIG. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.additionalInstruction | |
Definition | Supplemental instruction - e.g. "with meals". |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". ?? (example) |
Summary | True |
Requirements | Additional instruction such as "Swallow with plenty of water" which may or may not be coded. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.patientInstruction | |
Definition | Instructions in terms that are understood by the patient or consumer. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.timing | |
Definition | When medication should be administered. |
Cardinality | 0...1 |
Type | Timing |
Summary | True |
Requirements | The timing schedule for giving the medication to the patient. The Schedule 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. |
Comments | This attribute may 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.asNeeded[x] | |
Definition | 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). |
Cardinality | 0...1 |
Type | boolean, CodeableConcept |
Binding | 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. ?? (example) |
Summary | True |
Comments | 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". |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.site | |
Definition | Body site to administer to. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept describing the site location the medicine enters into or onto the body. ?? (example) |
Summary | True |
Requirements | A coded specification of the anatomic site where the medication first enters the body. |
Comments | If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.route | |
Definition | How drug should enter body. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. ?? (example) |
Summary | True |
Requirements | A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.method | |
Definition | Technique for administering medication. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept describing the technique by which the medicine is administered. ?? (example) |
Summary | True |
Requirements | 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. |
Comments | Terminologies used often pre-coordinate this term with the route and or form of administration. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.dose[x] | |
Definition | Amount of medication per dose. |
Cardinality | 0...1 |
Type | Range, http://hl7.org/fhir/StructureDefinition/SimpleQuantity |
Summary | True |
Requirements | The amount of therapeutic or other substance given at one administration event. |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.maxDosePerPeriod | |
Definition | Upper limit on medication per unit of time. |
Cardinality | 0...1 |
Type | Ratio |
Summary | True |
Requirements | 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. |
Comments | 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". |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.maxDosePerAdministration | |
Definition | Upper limit on medication per administration. |
Cardinality | 0...1 |
Type | http://hl7.org/fhir/StructureDefinition/SimpleQuantity |
Summary | True |
Requirements | The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.maxDosePerLifetime | |
Definition | Upper limit on medication per lifetime of the patient. |
Cardinality | 0...1 |
Type | http://hl7.org/fhir/StructureDefinition/SimpleQuantity |
Summary | True |
Requirements | The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
MedicationRequest.dosageInstruction.rate[x] | |
Definition | Cantidad de medicamento por cantidad de tiempo. |
Cardinality | 0...1 |
Type | http://hl7.org/fhir/StructureDefinition/SimpleQuantity, Ratio_apimin_v3 |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest | |
Definition | 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. |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.validityPeriod | |
Definition | This indicates the validity period of a prescription (stale dating the Prescription). |
Cardinality | 0...1 |
Type | Period |
Requirements | Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription. |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.validityPeriod.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.validityPeriod.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.validityPeriod.start | |
Definition | The start of the period. The boundary is inclusive. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | If the low element is missing, the meaning is that the low boundary is not known. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.validityPeriod.end | |
Definition | Fecha hasta que la receta se mantiene vigente, según la duración del tratamiento señalada en las prescripciones. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.numberOfRepeatsAllowed | |
Definition | Número de veces que la receta se debe despachar. |
Cardinality | 0...1 |
Type | positiveInt |
Comments | If displaying "number of authorized fills", add 1 to this number. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.quantity | |
Definition | The amount that is to be dispensed for one fill. |
Cardinality | 0...1 |
Type | http://hl7.org/fhir/StructureDefinition/SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.expectedSupplyDuration | |
Definition | 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. |
Cardinality | 0...1 |
Type | Duration |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.dispenseRequest.performer | |
Definition | Indicates the intended dispensing Organization specified by the prescriber. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.substitution | |
Definition | 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. |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
MedicationRequest.substitution.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicationRequest.substitution.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MedicationRequest.substitution.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
MedicationRequest.substitution.allowed | |
Definition | True if the prescriber allows a different drug to be dispensed from what was prescribed. |
Cardinality | 1...1 |
Type | boolean |
Modifier | True |
Comments | This element is labeled as a modifer because whether substitution is allow or not cannot be ignored. |
Invariants |
|
Mappings |
|
MedicationRequest.substitution.reason | |
Definition | Indicates the reason for the substitution, or why substitution must or must not be performed. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
MedicationRequest.priorPrescription | |
Definition | A link to a resource representing an earlier order related order or prescription. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/MedicationRequest) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.detectedIssue | |
Definition | 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. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/DetectedIssue) |
Alias | Contraindication, Drug Utilization Review (DUR), Alert |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MedicationRequest.eventHistory | |
Definition | 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. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Provenance) |
Comments | This may 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.). |
Invariants |
|
Mappings |
|
Vacunas
Aquí se presentan todos los recursos que se utilizaron para mapear la información de las Vacunas.
- Definición de estructura para los datos de las Vacunas, aqui se definen principalmente los campos utilizados del recurso Immunization de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/immunizationvacunasv3.
Immunization | Immunization | ||
status | |||
vaccineCode | |||
coding | |||
code | |||
display | |||
text | |||
patient | Reference(Patient_apimin_v3) | ||
date | |||
location | Reference(Location_apimin_v3) | ||
lotNumber | |||
doseQuantity | |||
explanation | |||
reason | |||
text | |||
reaction | |||
detail | Reference(Observation_apimin_v3) | ||
vaccinationProtocol | |||
series |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/patientapiminv3.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/observationapiminv3.
Observation | Observation | ||
category | |||
coding | |||
system | |||
code | |||
code | |||
text | |||
value[x] | |||
valueQuantity | Quantity | ||
valueString | string |
- Definición de estructura para los datos del lugar el cual pertenece a la organización que relizó la vacuna. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/locationapiminv3.
Location | Location | ||
identifier | |||
system | |||
value | |||
name | |||
address | |||
text |
Parámetros de Búsqueda Vacunas
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
patient | token | Utilizado como el rut del paciente sin dígito verificador | Immunization.patient | patient.identifier=1111111 |
date | date | Fecha de la vacuna en formato YYYY-MM-DD | Immunization.date | date=2018-10-12 date=ge2018-10-12 date=lt2018-10-12 |
vaccine-code | token | Tipo de programa de Vacuna | Immunization.vaccineCode | vaccine-code=INTERNACIONAL |
Prefijos implementados para búsquedas por fecha
Expresión | Definición | Ejemplo | Significado |
---|---|---|---|
ge | Mayor o Igual que | ge2018-10-12 | Resultados con fecha posterior o igual a 2018-10-12 |
lt | Menor que | lt2018-10-12 | Resultados con fecha anterior a 2018-10-12 |
Referencia: Documentación completa en FHIR
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/Immunization?patient.identifer=23504868
- Búsqueda por rut y rango de fechas
GET [base]/Immunization?patient.identifer=23504868&date=ge2016-01-03&date=lt2018-01-03
- Búsqueda por rut y tipo de vacunas
GET [base]/Immunization?patient.identifer=23504868&vaccine-code=INTERNACIONAL
- Búsqueda por rut, rango de fechas y tipo
GET [base]/Immunization?patient.identifer=23504868&vaccine-code=INTERNACIONAL&date=ge2016-01-03&date=lt2018-01-03
Ejemplo de response
{ "resourceType": "Bundle", "id": "819c58ce-44ff-475a-9a76-c9f0c59b35a2", "meta": { "lastUpdated": "2019-01-15T09:43:35.354-03:00" }, "type": "searchset", "total": 2, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Immunization?patient.identifer=23504868&vaccine-code=INTERNACIONAL" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Immunization/v242254420", "resource": { "resourceType": "Immunization", "id": "v242254420", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "23504868" } ] }, { "resourceType": "Location", "id": "l1", "identifier": [ { "system": "http://www.deis.cl", "value": "9999" } ], "name": "Clínica Alemana" }, { "resourceType": "Observation", "id": "ob1", "status": "registered", "code": { "text": "indeterminado" }, "valueString": "SinReaccion" } ], "status": "completed", "vaccineCode": { "coding": [ { "system": "https://vacunas.minsal.cl", "display": "VACUNA FIEBRE AMARILLA" } ] }, "patient": { "reference": "#p1" }, "date": "2016-01-05T00:00:00-03:00", "location": { "reference": "#l1" }, "lotNumber": "L5058-3", "doseQuantity": { "code": "Única (0,5ml)" }, "reaction": [ { "detail": { "reference": "#ob1" } } ], "vaccinationProtocol": [ { "series": "INTERNACIONAL" } ] } }, { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Immunization/v242322222", "resource": { "resourceType": "Immunization", "id": "v242322222", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "23504868" } ] }, { "resourceType": "Location", "id": "l1", "identifier": [ { "system": "http://www.deis.cl", "value": "9999" } ], "name": "Clínica Alemana" }, { "resourceType": "Observation", "id": "ob1", "status": "registered", "code": { "text": "indeterminado" }, "valueString": "SinReaccion" } ], "status": "completed", "vaccineCode": { "coding": [ { "system": "https://vacunas.minsal.cl", "display": "VACUNA FIEBRE AMARILLA" } ] }, "patient": { "reference": "#p1" }, "date": "2016-01-05T00:00:00-03:00", "location": { "reference": "#l1" }, "lotNumber": "L5058-3", "doseQuantity": { "code": "Única (0,5ml)" }, "reaction": [ { "detail": { "reference": "#ob1" } } ], "vaccinationProtocol": [ { "series": "INTERNACIONAL" } ] } } ] }
Dicccionario de Datos
Diccionario de Immunization
Immunization | |
Definition | Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Immunization.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Immunization.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Immunization.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Immunization.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
Immunization.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
Immunization.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Immunization.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.identifier | |
Definition | A unique identifier assigned to this immunization record. |
Cardinality | 0...* |
Type | Identifier |
Invariants |
|
Mappings |
|
Immunization.status | |
Definition | Indicates the current status of the vaccination event. |
Cardinality | 1...1 |
Type | code |
Binding | A set of codes indicating the current status of an Immunization ?? (required) |
Modifier | True |
Summary | True |
Comments | Will generally be set to show that the immunization has been completed. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
Immunization.notGiven | |
Definition | Indicates if the vaccination was or was not given. |
Cardinality | 1...1 |
Type | boolean |
Modifier | True |
Summary | True |
Comments | This element is labeled as a modifier because it indicates that an immunization didn't happen. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode | |
Definition | Vaccine that was administered or was to be administered. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | The code for vaccine product administered ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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 de-reference to some definition that establish the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.version | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.code | |
Definition | Código que representa un valor dentro de un sistema. |
Cardinality | 0...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.display | |
Definition | Texto explicativo del nombre de la vacuna. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.vaccineCode.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Immunization.patient | |
Definition | Paciente al cual se le aplicó la vacuna. |
Cardinality | 1...1 |
Type | Reference(Patient_apimin_v3) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.encounter | |
Definition | The visit or admission or other contact between patient and health care provider the immunization was performed as part of. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.date | |
Definition | Fecha en la que se administro la vacuna. |
Cardinality | 0...1 |
Type | dateTime |
Comments | When immunizations are given a specific date and time should always be known. When immunizations are patient reported, a specific date might not be known. Although partial dates are allowed, an adult patient might not be able to recall the year a childhood immunization was given. |
Invariants |
|
Mappings |
|
Immunization.primarySource | |
Definition | An indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded. |
Cardinality | 1...1 |
Type | boolean |
Comments | Reflects the “reliability” of the content. |
Invariants |
|
Mappings |
|
Immunization.reportOrigin | |
Definition | The source of the data when the report of the immunization event is not based on information from the person who administered the vaccine. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The source of the data for a record which is not from a primary source. ?? (example) |
Comments | Should not be populated if primarySource = True, will not be required even if primarySource = False. |
Invariants |
|
Mappings |
|
Immunization.location | |
Definition | The service delivery location where the vaccine administration occurred. |
Cardinality | 0...1 |
Type | Reference(Location_apimin_v3) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.manufacturer | |
Definition | Name of vaccine manufacturer. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.lotNumber | |
Definition | Número del lote de la vacuna. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.expirationDate | |
Definition | Date vaccine batch expires. |
Cardinality | 0...1 |
Type | date |
Invariants |
|
Mappings |
|
Immunization.site | |
Definition | Body site where vaccine was administered. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The site at which the vaccine was administered ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.route | |
Definition | The path by which the vaccine product is taken into the body. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The route by which the vaccine was administered ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.doseQuantity | |
Definition | La cantidad de la vacuna que se administro. |
Cardinality | 0...1 |
Type | http://hl7.org/fhir/StructureDefinition/SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Immunization.practitioner | |
Definition | Indicates who or what performed the event. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Immunization.practitioner.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.practitioner.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.practitioner.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.practitioner.role | |
Definition | Describes the type of performance (e.g. ordering provider, administering provider, etc.). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The role a practitioner plays in the immunization event ?? (extensible) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.practitioner.actor | |
Definition | The device, practitioner, etc. who performed the action. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.note | |
Definition | Extra information about the immunization that is not conveyed by the other attributes. |
Cardinality | 0...* |
Type | Annotation |
Summary | True |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
Immunization.explanation | |
Definition | Reasons why a vaccine was or was not administered. |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Immunization.explanation.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.explanation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.explanation.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.explanation.reason | |
Definition | Razón o Razones del porque se administro la vacuna. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The reason why a vaccine was administered ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.explanation.reason.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.explanation.reason.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.explanation.reason.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.explanation.reason.text | |
Definition | Razón porque se eligio la vacuna. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Immunization.explanation.reasonNotGiven | |
Definition | Reason why a vaccine was not administered. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The reason why a vaccine was not administered ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.reaction | |
Definition | Categorical data indicating that an adverse event is associated in time to an immunization. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | A reaction may be an indication of an allergy or intolerance and, if this is determined to be the case, it should be recorded as a new AllergyIntolerance resource instance as most systems will not query against past Immunization.reaction elements. |
Invariants |
|
Mappings |
|
Immunization.reaction.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.reaction.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.reaction.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.reaction.date | |
Definition | Date of reaction to the immunization. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
Immunization.reaction.detail | |
Definition | Details of the reaction. |
Cardinality | 0...1 |
Type | Reference(Observation_apimin_v3) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.reaction.reported | |
Definition | Self-reported indicator. |
Cardinality | 0...1 |
Type | boolean |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol | |
Definition | Contains information about the protocol(s) under which the vaccine was administered. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.doseSequence | |
Definition | Nominal position in a series. |
Cardinality | 0...1 |
Type | positiveInt |
Comments | 32 bit number; for values larger than this, use decimal |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.description | |
Definition | Contains the description about the protocol under which the vaccine was administered. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.authority | |
Definition | Indicates the authority who published the protocol. E.g. ACIP. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.series | |
Definition | One possible path to achieve presumed immunity against a disease - within the context of an authority. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.seriesDoses | |
Definition | The recommended number of doses to achieve immunity. |
Cardinality | 0...1 |
Type | positiveInt |
Comments | 32 bit number; for values larger than this, use decimal |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.targetDisease | |
Definition | The targeted disease. |
Cardinality | 1...* |
Type | CodeableConcept |
Binding | The disease target of the vaccination protocol ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.doseStatus | |
Definition | Indicates if the immunization event should "count" against the protocol. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | The status of the vaccination protocol (i.e. should this count) ?? (example) |
Comments | May need to differentiate between status declarations by a provider vs. a CDS engine. |
Invariants |
|
Mappings |
|
Immunization.vaccinationProtocol.doseStatusReason | |
Definition | Provides an explanation as to why an immunization event should or should not count against the protocol. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The reason for the determining if a vaccination should count or why vaccination should not count. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Nacimientos
Aquí se presentan todos los recursos que se utilizaron para mapear la información de los Nacimientos.
- Definición de estructura para los datos de los Nacimientos, aqui se definen principalmente los campos utilizados del recurso Procedure de HL7 FHIR. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/procedurenacimientosv3.
Procedure | Procedure | ||
status | |||
subject | Reference(http://hl7.org/fhir/StructureDefinition/Patient | Group_apimin_v3) | ||
performer | |||
role | |||
text | |||
location | Reference(Location_apimin_v3) | ||
reasonReference | Reference(http://hl7.org/fhir/StructureDefinition/Condition | Observation_apimin_v3) | ||
outcome | |||
text |
- Definición de estructura para los datos de los pacientes en un nacimiento (Hijo y Madre). También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/groupapiminv3.
Group | Group | ||
member | |||
entity | Reference(http://hl7.org/fhir/StructureDefinition/Patient | Patient_apimin_v3) |
- Definición de estructura para los datos del paciente. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/patientapiminv3.
Patient | Patient | ||
identifier | S | 1.. | |
system | |||
value | S | ||
birthDate | S |
- Definición de estructura para los datos de las observaciones dentro del parto. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/observationapiminv3.
Observation | Observation | ||
category | |||
coding | |||
system | |||
code | |||
code | |||
text | |||
value[x] | |||
valueQuantity | Quantity | ||
valueString | string |
- Definición de estructura para los datos del lugar del nacimiento. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/locationapiminv3.
Location | Location | ||
identifier | |||
system | |||
value | |||
name | |||
address | |||
text |
- Definición de estructura para los datos del establecimiento. También puedes encontrar el recurso en https://simplifier.net/test-api-minsal/organizationapimin.
Organization | Organization | ||
identifier | S | 1.. | |
system | S | ||
value | S | ||
name | S |
Parámetros de Búsqueda Nacimientos
Nombre | Tipo | Descripción | Expresión | Ejemplo |
---|---|---|---|---|
subject | token | Utilizado como el rut del paciente sin dígito verificador | Procedure.subject(Group) | subject:Group.member.identifier=1111111 |
_profile | token | Utilizado como parametro identificador de esquema de datos por minsal | _profile | _profile=_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-nacimientos |
date | date | Fecha de nacimiento del hijo en formato YYYY-MM-DD | patient.birthDate | date=ge2018-10-12 date=lt2018-10-12 date=2018-10-12 |
Prefijos implementados para búsquedas por fecha
Expresión | Definición | Ejemplo | Significado |
---|---|---|---|
ge | Mayor o Igual que | ge2018-10-12 | Resultados con fecha posterior o igual a 2018-10-12 |
lt | Menor que | lt2018-10-12 | Resultados con fecha anterior a 2018-10-12 |
Referencia: Documentación completa en FHIR
Ejemplos de búsqueda
- Búsqueda solo por rut
GET [base]/Procedure?subject:Group.member.identifier=25231520&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-nacimientos
- Búsqueda por rut y rango de fechas
GET [base]/Procedure?subject:Group.member.identifier=25231520&_profile=http://cens.cl/fhir/StructureDefinition/hospitaldigital-nacimientos&date=ge2015-01-12&date=lt2018-01-03
Ejemplo de response
{ "resourceType": "Bundle", "id": "05fc9c01-d144-492c-8bbe-8b9a81453c12", "meta": { "lastUpdated": "2019-01-15T09:59:53.206-03:00" }, "type": "searchset", "total": 1, "link": [ { "relation": "self", "url": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Procedure?_profile=http%3A%2F%2Fcens.cl%2Ffhir%2FStructureDefinition%2Fhospitaldigital-nacimientos&date=ge2015-01-12&date=lt2018-01-03&subject%3AGroup.member.identifier=25231520" } ], "entry": [ { "fullUrl": "http://192.168.60.24:8080/hospital-digital-fhir-server-3.0/fhir/Procedure/9884373", "resource": { "resourceType": "Procedure", "id": "9884373", "contained": [ { "resourceType": "Patient", "id": "p1", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "15922059" } ] }, { "resourceType": "Patient", "id": "p2", "identifier": [ { "system": "https://www.srcei.cl/RUT", "value": "25231520" } ], "birthDate": "2015-12-21" }, { "resourceType": "Group", "id": "g1", "member": [ { "entity": { "reference": "#p1", "display": "madre" } }, { "entity": { "reference": "#p2", "display": "hijo" } } ] }, { "resourceType": "Location", "id": "l1", "name": "CLINICA ISAMEDICA", "type": { "text": "Hospital" } }, { "resourceType": "Observation", "id": "ob1", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "vital-signs" } ] } ], "code": { "text": "semanas" }, "valueQuantity": { "value": 40, "unit": "semanas" } }, { "resourceType": "Observation", "id": "ob2", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "procedure" } ] } ], "code": { "text": "peso" }, "valueQuantity": { "value": 4090, "unit": "kg" } }, { "resourceType": "Observation", "id": "ob3", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "procedure" } ] } ], "code": { "text": "talla" }, "valueQuantity": { "value": 50, "unit": "cm" } }, { "resourceType": "Observation", "id": "ob4", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "social-history" } ] } ], "code": { "text": "hijos-vivos" }, "valueQuantity": { "value": 1, "unit": "hijos" } }, { "resourceType": "Observation", "id": "ob5", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "social-history" } ] } ], "code": { "text": "hijos-fallecidos" }, "valueQuantity": { "value": 0, "unit": "hijos" } }, { "resourceType": "Observation", "id": "ob6", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "social-history" } ] } ], "code": { "text": "hijos-total" }, "valueQuantity": { "value": 1, "unit": "hijos" } }, { "resourceType": "Observation", "id": "ob7", "category": [ { "coding": [ { "system": "http://hl7.org/fhir/observation-category", "code": "social-history" } ] } ], "code": { "text": "edad" }, "valueQuantity": { "value": 27, "unit": "años" } } ], "status": "completed", "subject": { "reference": "#g1" }, "performer": [ { "role": { "text": "Matrona" } } ], "location": { "reference": "#l1", "display": "Lugar del Parto" }, "reasonReference": [ { "reference": "#ob1" }, { "reference": "#ob2" }, { "reference": "#ob3" }, { "reference": "#ob4" }, { "reference": "#ob5" }, { "reference": "#ob6" }, { "reference": "#ob7" } ], "outcome": { "text": "Simple" } } } ] }
Dicccionario de Datos
Diccionario de Procedure
Procedure | |
Definition | An action that is or was performed on a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Procedure.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Procedure.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Procedure.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. ?? (extensible) |
Comments | 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). |
Invariants |
|
Mappings |
|
Procedure.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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 in formation is added later. |
Invariants |
|
Mappings |
|
Procedure.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Procedure.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.identifier | |
Definition | This records identifiers associated with this procedure that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Requirements | Need to allow connection to a wider workflow. |
Invariants |
|
Mappings |
|
Procedure.definition | |
Definition | A protocol, guideline, orderset or other definition that was adhered to in whole or in part by this procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/PlanDefinition | http://hl7.org/fhir/StructureDefinition/ActivityDefinition | http://hl7.org/fhir/StructureDefinition/HealthcareService) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.basedOn | |
Definition | A reference to a resource that contains details of the request for this procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/CarePlan | http://hl7.org/fhir/StructureDefinition/ProcedureRequest | http://hl7.org/fhir/StructureDefinition/ReferralRequest) |
Summary | True |
Alias | fulfills |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.partOf | |
Definition | A larger event of which this particular procedure is a component or step. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Procedure | http://hl7.org/fhir/StructureDefinition/Observation | http://hl7.org/fhir/StructureDefinition/MedicationAdministration) |
Summary | True |
Alias | container |
Comments | The MedicationAdministration has a partOf reference to Procedure, but this is not a circular reference. For a surgical procedure, the anesthesia related medicationAdministration is part of the procedure. For an IV medication administration, the procedure to insert the IV port is part of the medication administration. |
Invariants |
|
Mappings |
|
Procedure.status | |
Definition | A code specifying the state of the procedure. Generally this will be in-progress or completed state. |
Cardinality | 1...1 |
Type | code |
Binding | A code specifying the state of the procedure. ?? (required) |
Modifier | True |
Summary | True |
Comments | The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
Procedure.notDone | |
Definition | Set this to true if the record is saying that the procedure was NOT performed. |
Cardinality | 0...1 |
Type | boolean |
Modifier | True |
Summary | True |
Comments | If true, it means the procedure did not occur as described. Typically it would be accompanied by attributes describing the type of activity. It might also be accompanied by body site information or time information (i.e. no procedure was done to the left arm or no procedure was done in this 2-year period). Specifying additional information such as performer, outcome, etc. is generally inappropriate. For example, it's not that useful to say "There was no appendectomy done at 12:03pm June 6th by Dr. Smith with a successful outcome" as it implies that there could have been an appendectomy done at any other time, by any other clinician or with any other outcome. This element is labeled as a modifier because it indicates that a procedure didn't happen. |
Invariants |
|
Mappings |
|
Procedure.notDoneReason | |
Definition | A code indicating why the procedure was not performed. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure was not performed. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.category | |
Definition | A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that classifies a procedure for searching, sorting and display purposes. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.code | |
Definition | The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code to identify a specific procedure . ?? (example) |
Summary | True |
Alias | type |
Requirements | 0..1 to account for primarily narrative only resources. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.subject | |
Definition | The person, animal or group on which the procedure was performed. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Patient | Group_apimin_v3) |
Summary | True |
Alias | patient |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.context | |
Definition | The encounter during which the procedure was performed. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Encounter | http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) |
Summary | True |
Alias | encounter |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performed[x] | |
Definition | The date(time)/period over which the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured. |
Cardinality | 0...1 |
Type | dateTime, Period |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.performer | |
Definition | Limited to 'real' people rather than equipment. |
Cardinality | 0...* |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
Procedure.performer.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.performer.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performer.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.performer.role | |
Definition | For example: surgeon, anaethetist, endoscopist. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code that identifies the role of a performer of the procedure. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.performer.role.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.performer.role.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.performer.role.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.performer.role.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.performer.actor | |
Definition | The practitioner who was involved in the procedure. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Practitioner | http://hl7.org/fhir/StructureDefinition/Organization | http://hl7.org/fhir/StructureDefinition/Patient | http://hl7.org/fhir/StructureDefinition/RelatedPerson | http://hl7.org/fhir/StructureDefinition/Device) |
Summary | True |
Requirements | A reference to Device supports use cases, such as pacemakers. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.performer.onBehalfOf | |
Definition | The organization the device or practitioner was acting on behalf of. |
Cardinality | 0...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.location | |
Definition | The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. |
Cardinality | 0...1 |
Type | Reference(Location_apimin_v3) |
Summary | True |
Requirements | Ties a procedure to where the records are likely kept. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.reasonCode | |
Definition | The coded reason why the procedure was performed. This may be coded entity of some type, or may simply be present as text. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure is required. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.reasonReference | |
Definition | The condition that is the reason why the procedure was performed. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition | Observation_apimin_v3) |
Summary | True |
Comments | e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic. |
Invariants |
|
Mappings |
|
Procedure.bodySite | |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. ?? (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.outcome | |
Definition | The outcome of the procedure - did it resolve reasons for the procedure being performed? |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | An outcome of a procedure - whether it was resolved or otherwise. ?? (example) |
Summary | True |
Comments | If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.outcome.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.outcome.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.outcome.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.outcome.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Procedure.report | |
Definition | This could be a histology result, pathology report, surgical report, etc.. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport) |
Comments | There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
Invariants |
|
Mappings |
|
Procedure.complication | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing complications that resulted from a procedure. ?? (example) |
Comments | If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. |
Invariants |
|
Mappings |
|
Procedure.complicationDetail | |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Condition) |
Requirements | This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.followUp | |
Definition | If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or could potentially be more complex in which case the CarePlan resource can be used. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Specific follow up required for a procedure e.g. removal of sutures. ?? (example) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.note | |
Definition | Any other notes about the procedure. E.g. the operative notes. |
Cardinality | 0...* |
Type | Annotation |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
Procedure.focalDevice | |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Procedure.focalDevice.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Procedure.focalDevice.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Procedure.focalDevice.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Comments | 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. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.action | |
Definition | The kind of change that happened to the device during the procedure. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A kind of change that happened to the device during the procedure. ?? (preferred) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Procedure.focalDevice.manipulated | |
Definition | The device that was manipulated (changed) during the procedure. |
Cardinality | 1...1 |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Device) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Procedure.usedReference | |
Definition | Identifies medications, devices and any other substance used as part of the procedure. |
Cardinality | 0...* |
Type | Reference(http://hl7.org/fhir/StructureDefinition/Device | http://hl7.org/fhir/StructureDefinition/Medication | http://hl7.org/fhir/StructureDefinition/Substance) |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|
Procedure.usedCode | |
Definition | Identifies coded items that were used as part of the procedure. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing items used during a procedure ?? (example) |
Comments | For devices actually implanted or removed, use Procedure.device. |
Invariants |
|
Mappings |
|