Generated Narrative: StructureDefinition EncounterUrg Name Flags Card. Type Description & Constraints Encounter C 0..* EncounterCL An interaction during which services are provided to the patient acompanante-slice: Si la extensión Acompanante es 'true', entonces el participante Acompanante debe estar presente. motivo-consulta: Si el estado del encuentro es distinto de 'arrived', entonces el motivo de la consulta debe estar presente. categorizacion: Si el encuentro tiene el estado 'triaged', entonces el participante Categorizador debe estar presente. Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url Acompanante S 1..1 boolean Indica si el paciente acude con acompañante URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/Acompanante LeyPrevisional S 0..1 CodeableConcept Ley previsional que financia la atención de urgencia URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/LeyPrevisional Binding: Ley Previsional (required) identifier 1..1 Identifier Identificador del encuentro de urgencia value S 1..1 string Valor del identificador, compuesto por Código DEIS de establecimiento - Id único del evento asignado por el establecimiento Slices for statusHistory 1..* BackboneElement List of past encounter statuses Slice: Unordered, Open by value:status statusHistory:Admision S 1..1 BackboneElement Estado de admisión de la atención de urgencia status S 1..1 code planned | arrived | triaged | in-progress | onleave | finished | cancelled + Required Pattern: arrived period S 1..1 Period The time that the episode was in the specified status start S 1..1 dateTime Fecha y hora de admisión statusHistory:Categorizacion S 0..1 BackboneElement Estado de categorización de la atención de urgencia status S 1..1 code planned | arrived | triaged | in-progress | onleave | finished | cancelled + Required Pattern: triaged period S 1..1 Period The time that the episode was in the specified status start S 1..1 dateTime Fecha y hora de categorización statusHistory:Atencion S 0..1 BackboneElement Estado de atención de la atención de urgencia status S 1..1 code planned | arrived | triaged | in-progress | onleave | finished | cancelled + Required Pattern: in-progress period S 1..1 Period The time that the episode was in the specified status start S 1..1 dateTime Fecha y hora de inicio de atención de urgencia statusHistory:Egreso S 0..1 BackboneElement Estado de egreso de la atención de urgencia status S 1..1 code planned | arrived | triaged | in-progress | onleave | finished | cancelled + Required Pattern: finished period S 1..1 Period The time that the episode was in the specified status start S 1..1 dateTime Fecha y hora de egreso end S 0..1 dateTime Fecha y hora de egreso efectivo class 1..1 Coding Tipo de encuentro de urgencia Required Pattern: At least the following system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ActCode code 1..1 code Symbol in syntax defined by the system Fixed Value: EMER priority S 1..1 CodeableConcept Categorización de prioridad de atención de urgencia Binding: Categorización Urgencia (required) coding S 1..1 Coding Code defined by a terminology system system S 1..1 uri Sistema de categorización de la prioridad de atención de urgencia code S 1..1 code Código de categorización de la prioridad display S 0..1 string Definición de la categorización de la prioridad subject 1..1 Reference(Paciente Urgencia) Paciente Slices for participant 1..* BackboneElement Participantes involucrados en el encuentro sin considerar al paciente Slice: Unordered, Open by value:type participant:All Slices Content/Rules for all slices type 0..* CodeableConcept Rol del participante en el encuentro Binding: Tipo Participante Encuentro Urgencia (required) participant:Acompanante S 0..1 BackboneElement Acompañante del paciente type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/participant-type version 1..1 string Version of the system - if relevant Fixed Value: 4.0.1 code 1..1 code Symbol in syntax defined by the system Fixed Value: emergency individual 1..1 Reference(Acompañante Urgencia) Referencia al acompañante del paciente participant:Admisionista S 1..1 BackboneElement Personal administrativo que realiza la admisión de urgencia type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType code 1..1 code Symbol in syntax defined by the system Fixed Value: ADM period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora de admisión individual 1..1 Reference(Prestador Administrativo) Referencia al participante participant:Categorizador S 0..* BackboneElement Profesional que categoriza al paciente type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/CodeSystem/TipoParticipanteUrgencia code 1..1 code Symbol in syntax defined by the system Fixed Value: triage period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora de categorización individual 1..1 Reference(Prestador Profesional) Referencia al profesional que categoriza participant:Atendedor S 0..* BackboneElement Profesional que atiende al paciente type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType code 1..1 code Symbol in syntax defined by the system Fixed Value: ATND period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora de atención individual 1..1 Reference(Prestador Profesional) Referencia al profesional que atiende participant:AtendedorSecundario S 0..* BackboneElement Profesional que atiende al paciente pero no es el principal type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType code 1..1 code Symbol in syntax defined by the system Fixed Value: SPRF period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora de atención individual 1..1 Reference(Prestador Profesional) Referencia al profesional que atiende participant:Especialista S 0..* BackboneElement Profesional especialista que atiende al paciente type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType code 1..1 code Symbol in syntax defined by the system Fixed Value: CON period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora de atención individual 1..1 Reference(Prestador Profesional) Referencia al profesional especialista que atiende <a href="StructureDefinition-EncounterUrg-definitions.html#Encounter.participant:Egresador" title="Slice Egresador: Es la individualización del médico u odontólogo tratante del usuario, a cargo del proceso de atención. Solo en atenciones de Servicios de Urgencia Rural (SUR), en que no se cuente con personal médico ni odontológico, será el otro profesional o el TENS, quien cierre la atención y otorgue el alta.">participant:Egresador S 0..1 BackboneElement Profesional que autoriza el egresa del paciente type 1..1 CodeableConcept Rol del participante en el encuentro Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType code 1..1 code Symbol in syntax defined by the system Fixed Value: DIS period S 1..1 Period Period of time during the encounter that the participant participated start S 1..1 dateTime Fecha y hora que se registra la decisión de egreso individual 1..1 Reference(Prestador Profesional) Referencia al profesional que autoriza el egreso period 1..1 Period La hora de inicio y finalización del encuentro start 1..1 dateTime Fecha y hora de que se realiza la admisión de urgencia end 0..1 dateTime Fecha y hora de que se cierra el dato de urgencia reasonCode 0..1 CodeableConcept Motivo de la atención de urgencia text S 1..1 string Texto libre del motivo de la atención de urgencia indicado por el paciente Slices for diagnosis 0..* BackboneElement Diagnóstico relevante para este encuentro Slice: Unordered, Open by value:use diagnosis:HipotesisDiagnostica S 0..* BackboneElement Hipótesis diagnóstica condition S 1..1 Reference(Condition Diagnostico) Referencia a la hipótesis diagnóstica use S 1..1 CodeableConcept Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/diagnosis-role code 1..1 code Symbol in syntax defined by the system Fixed Value: AD rank S 0..1 positiveInt Si es la hipótesis diagnóstica principal se debe registrar el valor 1. diagnosis:Comorbilidades S 0..* BackboneElement Comorbilidades condition S 1..1 Reference(Condition Diagnostico) Referencia a la comorbilidad use S 1..1 CodeableConcept Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/diagnosis-role code 1..1 code Symbol in syntax defined by the system Fixed Value: CM diagnosis:DiagnosticoEgreso S 0..1 BackboneElement Diagnóstico de egreso condition S 1..1 Reference(Condition Diagnostico) Referencia al diagnóstico de egreso use S 1..1 CodeableConcept Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/diagnosis-role code 1..1 code Symbol in syntax defined by the system Fixed Value: DD hospitalization 0..1 BackboneElement Información de admisión y egreso de la atención de urgencia Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url MedioDeLlegada S 1..1 CodeableConcept Medio de llegada del paciente al servicio de urgencia URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/MedioDeLlegada Binding: Medio de Llegada (required) ConsultaPorAccidente S 1..1 boolean Consulta por accidente URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/ConsultaPorAccidente admitSource S 1..1 CodeableConcept Lugar físico desde donde proviene el paciente cuando concurre a la atención de urgencia Binding: Procedencia (required) dischargeDisposition S 0..1 CodeableConcept Tipo de egreso de la atención de urgencia Binding: Tipo Egreso (required) Slices for extension Content/Rules for all slices IndicacionHospitalizacion S 0..1 (Complex) Indicación de hospitalización URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/IndicacionHospitalizacion IndicacionAlta S 0..1 (Complex) Indicación de alta URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/IndicacionAlta IndicacionDerivacion S 0..1 (Complex) Indicación de derivación a otro centro asistencial URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/IndicacionDerivacion Abandono S 0..1 Coding Tipo de abandono URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/Abandono Binding: Abandono (required) Fallecido S 0..1 (Complex) Fallecido URL: https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/Fallecido serviceProvider 1..1 Reference(Establecimiento Urgencia) Establecimiento de salud Documentation for this format
Recurso que representa la atención de urgencia de un paciente en un establecimiento de salud.
An interaction during which services are provided to the patient
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Si la extensión Acompanante es 'true', entonces el participante Acompanante debe estar presente.
extension('https://interoperabilidad.minsal.cl/fhir/ig/urgencia/StructureDefinition/Acompanante').value.single() = true implies participant.type.coding.exists(system = 'http://terminology.hl7.org/CodeSystem/v3-ParticipationType' and code = 'ESC')
Si el estado del encuentro es distinto de 'arrived', entonces el motivo de la consulta debe estar presente.
reasonCode.exists() or status = 'arrived'
Si el encuentro tiene el estado 'triaged', entonces el participante Categorizador debe estar presente.
status = 'triaged' implies participant.exists(type.coding.exists(system = 'https://interoperabilidad.minsal.cl/fhir/ig/urgencia/CodeSystem/TipoParticipanteUrgencia' and code = 'triage'))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Indica si el paciente acude con acompañante
Extensión empleada para indicar si el paciente acude con acompañante a la atención de urgencia.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Ley previsional que financia la atención de urgencia
Extensión empleada para indicar la ley previsional que financia la atención de urgencia.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Es el número de identificación del encuentro realizado
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
Valor del identificador, compuesto por Código DEIS de establecimiento - Id único del evento asignado por el establecimiento
Identificador de la consulta de urgencia. Este debe estar compuesto por Código DEIS de establecimiento - Id único del evento asignado por el establecimiento
El valor del identificador debe ser único por evento de urgencia
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
planned | arrived | triaged | in-progress | onleave | finished | cancelled
Determina el estado del encuentro remoto conforme a los códigos definidos por el estándar
Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16
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.
The current status is always found in the current version of the resource, not the status history.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
planned | arrived | triaged | in-progress | onleave | finished | cancelled +
planned | arrived | triaged | in-progress | onleave | finished | cancelled +.
The time that the episode was in the specified status
The time that the episode was in the specified status.
Estado de admisión de la atención de urgencia
Corresponde al día, mes, año y hora en que se realiza la admisión. Sigue el formato de fecha larga normado en la norma 231 de Estándares de Información de Salud.
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. 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.
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
Estado de categorización de la atención de urgencia
Corresponde al día, mes, año y hora en que se realiza la categorización. Sigue el formato de fecha larga normado en la norma 231 de Estándares de Información de Salud.
Estado de atención de la atención de urgencia
Fecha y hora de inicio de atención de urgencia
Corresponde al registro del tiempo en que se inicia el proceso de atención de urgencia, se considera como inicio el primer registro en sistema conducente a diagnosticar y reestablecer el estado de salud del usuario posterior al proceso de categorización.
Estado de egreso de la atención de urgencia
Corresponde al día, el mes y la hora en que luego de cumplir con la completitud de los datos requeridos y el registro por parte del equipo de salud de las intervenciones realizadas, el médico u odontólogo, cierra el dato de urgencia.
Corresponde al día, el mes y la hora en que luego de cumplir con termino de atención de urgencia y el cierre del dato de urgencia, el usuario egresa efectivamente de la unidad de urgencia.
Clasificación del encuentro con el paciente
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 transitions 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 kind of discharge from emergency to inpatient.
inpatient | outpatient | ambulatory | emergency +
inpatient | outpatient | ambulatory | emergency +.
The time that the episode was in the specified class
The time that the episode was in the specified class.
Since there are many ways to further classify encounters, this element is 0..*.
Tipo de servicio que se realiza en el Encuentro
Categorización del servicio que se va a prestar en el encuentro (por ejemplo, servicio de Ginecología)
Categorización de prioridad de atención de urgencia
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Sistema de categorización de la prioridad de atención de urgencia
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
Código de categorización de la prioridad
Código de categorización de la prioridad de atención de urgencia
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
Definición de la categorización de la prioridad
Definición de la categorización de la prioridad de atención de urgencia
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Paciente que recibe atención de urgencia
While the encounter is always about the patient, the patient might 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).
Episode(s) of care that this encounter should be recorded against
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).
The ServiceRequest that initiated this encounter
The request this encounter satisfies (e.g. incoming referral or procedure request).
Participantes involucrados en el encuentro sin considerar al paciente
The list of people responsible for providing the service.
The participant type indicates how an individual participates 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.
Period of time during the encounter that the participant participated
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.
Persons involved in the encounter other than the patient.
Acompañante del paciente que recibe atención de urgencia
Personal administrativo que realiza la admisión de urgencia
Corresponde al personal administrativo que realiza la admisión de urgencia
The start of the period. The boundary is inclusive.
Profesional que categoriza al paciente en un servicio de urgencia
Referencia al profesional que categoriza
Profesional que atiende al paciente en un servicio de urgencia
Profesional que atiende al paciente pero no es el principal
Profesional que atiende al paciente en un servicio de urgencia pero no es el principal
Profesional especialista que atiende al paciente
Profesional especialista que atiende al paciente en un servicio de urgencia
Referencia al profesional especialista que atiende
Profesional que autoriza el egresa del paciente
Es la individualización del médico u odontólogo tratante del usuario, a cargo del proceso de atención. Solo en atenciones de Servicios de Urgencia Rural (SUR), en que no se cuente con personal médico ni odontológico, será el otro profesional o el TENS, quien cierre la atención y otorgue el alta.
Fecha y hora que se registra la decisión de egreso
Referencia al profesional que autoriza el egreso
Reserva de un evento de atención médica entre paciente(s), profesional(es), persona(s) relacionada(s) y/o dispositivo(s)
Cita o agendamiento médico, la cual es resultado de un encuentro
.outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
La hora de inicio y finalización del encuentro
If not (yet) known, the end of the Period may be omitted.
Fecha y hora de que se realiza la admisión de urgencia
Fecha y hora de que se cierra el dato de urgencia
Cantidad de tiempo que duró el encuentro (menos tiempo ausente)
May differ from the time the Encounter.period lasted because of leave of absence.
(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes
Razón codificada por la que tiene lugar el Encuentro
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).
EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
Texto libre del motivo de la atención de urgencia indicado por el paciente
Reason the encounter takes place (reference)
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
Diagnóstico relevante para este encuentro
El diagnóstico o procedimiento relevante para el encuentro
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.
Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively.
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).
The type of diagnosis this condition represents.
Ranking of the diagnosis (for each role type)
Ranking of the diagnosis (for each role type).
Hipótesis diagnóstica del paciente en el contexto de atención de urgencia
Referencia a la hipótesis diagnóstica del paciente en el contexto de atención de urgencia
Si es la hipótesis diagnóstica principal se debe registrar el valor 1.
Comorbilidades del paciente en el contexto de atención de urgencia
Referencia a la comorbilidad del paciente en el contexto de atención de urgencia
Diagnóstico de egreso del paciente en el contexto de atención de urgencia
Referencia al diagnóstico de egreso del paciente en el contexto de atención de urgencia
The set of accounts that may be used for billing for this Encounter
The set of accounts that may be used for billing for this Encounter.
The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.
Información de admisión y egreso de la atención de urgencia
Details about the admission to a healthcare service.
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.
.outboundRelationship[typeCode=COMP].target[classCode=ENC, moodCode=EVN]
Medio de llegada del paciente al servicio de urgencia
Extensión empleada para indicar el medio de llegada del paciente al servicio de urgencia. Este dato es capturado durante la admisión de urgencia.
Extensión que registra si la atención de urgencia se debe a un accidente. Este dato es capturado durante la admisión de urgencia.
The location/organization from which the patient came before admission
The location/organization from which the patient came before admission.
Lugar físico desde donde proviene el paciente cuando concurre a la atención de urgencia
Lugar físico desde donde proviene el paciente cuando concurre a la atención de urgencia. Este dato es capturado durante la admisión de urgencia.
The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Whether this hospitalization is a readmission and why if known.
The reason for re-admission of this hospitalization encounter.
Diet preferences reported by the patient
Diet preferences reported by the patient.
For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).
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.
Medical, cultural or ethical food preferences to help with catering requirements.
.outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.
Location/organization to which the patient is discharged
Location/organization to which the patient is discharged.
Tipo de egreso de la atención de urgencia
Corresponde a la decisión del médico u odontólogo del destino que debe seguir el usuario en virtud de su evaluación y situación clínica antes de cerrar el proceso de urgencia.
Extensión que registra la indicación de hospitalización en el contexto de un encuentro de atención de urgencia.
Extensión que registra la indicación de alta en el contexto de un encuentro de atención de urgencia.
Indicación de derivación a otro centro asistencial
Extensión que registra la indicación de derivación a otro centro asistencial en el contexto de un encuentro de atención de urgencia.
Usuarios que, habiendo iniciado el proceso de atención de urgencia, y habiéndose generado un DAU, no terminaron el proceso, en cualquiera de sus etapas.
Extensión que registra la información de un paciente fallecido en el contexto de un encuentro de atención de urgencia.
List of locations where the patient has been
List of locations where the patient has been during this encounter.
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".
The location where the encounter takes place.
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
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.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.
Time period during which the patient was present at the location
Time period during which the patient was present at the location.
Establecimiento de salud donde se realiza la atención de urgencia
Another Encounter this encounter is part of
Another Encounter of which this encounter is a part of (administratively or in time).
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.
.inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]