Guía de Implementación Hackathon HLF 2023
1.0.1 - release

Guía de Implementación Hackathon HLF 2023 - Local Development build (v1.0.1). See the Directory of published versions

Resource Profile: Registro de Episodios de Hospitalización

Official URL: https://hlf.cl/fhir/ig/hackaton/StructureDefinition/registro-hosp Version: 1.0.1
Draft as of 2023-07-24 Computable Name: RegistroHospitalizacion

Perfil del recurso Encounter para el registro de episodios hospitalizaciones de paciente

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Encounter

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... status S1..1codeplanned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
Required Pattern: completed
... class S1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... coding S1..1CodingCode defined by a terminology system
..... system 1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... code 1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display 1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
... subject 1..1Reference(Patient)Paciente al que se le realiza la atencion
.... start 1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end 0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)
NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... contained 0..*ResourceContained, inline Resources
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
... class SΣ1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... coding SΣ1..1CodingCode defined by a terminology system
..... system Σ1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... code ΣC1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display ΣC1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
... subject Σ1..1Reference(Patient)Paciente al que se le realiza la atencion
... actualPeriod S1..1PeriodPeríodo en el cual el/la Paciente fue hospitalizado/a
.... start ΣC1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end ΣC0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Encounter.statusrequiredPattern: completed
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorEncounterIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorEncounterIf 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().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorEncounterIf 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()
dom-5errorEncounterIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceEncounterA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: AllLanguages (required): IETF language tag for a human language

... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
Binding: EncounterStatus (required): Current state of the encounter.


Required Pattern: completed
... class SΣ1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding SΣ1..1CodingCode defined by a terminology system
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system Σ1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... version Σ0..1stringVersion of the system - if relevant
..... code ΣC1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display ΣC1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ActPriority (example): Indicates the urgency of the encounter.

... type Σ0..*CodeableConceptSpecific type of encounter (e.g. e-mail consultation, surgical day-care, ...)
Binding: EncounterType (example): A specific code indicating type of service provided


... serviceType Σ0..*CodeableReference(HealthcareService)Specific type of service
Binding: ServiceType (example): Broad categorization of the service that is to be provided.


... subject Σ1..1Reference(Patient)Paciente al que se le realiza la atencion
... subjectStatus 0..1CodeableConceptThe current status of the subject in relation to the Encounter
Binding: EncounterSubjectStatus (example): Current status of the subject within the encounter.

... episodeOfCare Σ0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn 0..*Reference(CarePlan | DeviceRequest | MedicationRequest | ServiceRequest)The request that initiated this encounter
... careTeam 0..*Reference(CareTeam)The group(s) that are allocated to participate in this encounter
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of
... serviceProvider 0..1Reference(Organization)The organization (facility) responsible for this encounter
... participant ΣC0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type ΣC0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... period 0..1PeriodPeriod of time during the encounter that the participant participated
.... actor ΣC0..1Reference(Patient | Group | RelatedPerson | Practitioner | PractitionerRole | Device | HealthcareService)The individual, device, or service participating in the encounter
... appointment Σ0..*Reference(Appointment)The appointment that scheduled this encounter
... virtualService 0..*VirtualServiceDetailConnection details of a virtual service (e.g. conference call)
... actualPeriod S1..1PeriodPeríodo en el cual el/la Paciente fue hospitalizado/a
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... start ΣC1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end ΣC0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
... plannedStartDate 0..1dateTimeThe planned start date/time (or admission date) of the encounter
... plannedEndDate 0..1dateTimeThe planned end date/time (or discharge date) of the encounter
... length 0..1DurationActual quantity of time the encounter lasted (less time absent)
... reason Σ0..*BackboneElementThe list of medical reasons that are expected to be addressed during the episode of care
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... use Σ0..*CodeableConceptWhat the reason value should be used for/as
Binding: EncounterReasonUse (example)
.... value Σ0..*CodeableReference(Condition | DiagnosticReport | Observation | ImmunizationRecommendation | Procedure)Reason the encounter takes place (core or reference)
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... diagnosis Σ0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition Σ0..*CodeableReference(Condition)The diagnosis relevant to the encounter
Binding: ConditionProblemDiagnosisCodes (example)
.... use 0..*CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: EncounterDiagnosisUse (preferred): The type of diagnosis this condition represents.


... account 0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: EncounterDiet (example): Medical, cultural or ethical food preferences to help with catering requirements.


... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc
Binding: SpecialArrangements (preferred): Special arrangements.


... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred): Special courtesies.


... admission 0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource 0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred): From where the patient was admitted.

.... reAdmission 0..1CodeableConceptIndicates that the patient is being re-admitted
Binding: hl7VS-re-admissionIndicator (example): The reason for re-admission of this admission encounter.

.... destination 0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition 0..1CodeableConceptCategory or kind of location after discharge
Binding: DischargeDisposition (example): Discharge Disposition.

... location 0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location 1..1Reference(Location)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required): The status of the location.

.... form 0..1CodeableConceptThe physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.)
Binding: LocationForm (example): Physical form of the location.

.... period 0..1PeriodTime period during which the patient was present at the location

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Encounter.languagerequiredAllLanguages
Encounter.statusrequiredPattern: completed
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)
Encounter.priorityexampleActPriority
Encounter.typeexampleEncounterType
Encounter.serviceTypeexampleServiceType
Encounter.subjectStatusexampleEncounterSubjectStatus
Encounter.participant.typeextensibleParticipantType
Encounter.reason.useexampleEncounterReasonUse
Encounter.reason.valuepreferredEncounterReasonCodes
Encounter.diagnosis.conditionexampleConditionProblemDiagnosisCodes
Encounter.diagnosis.usepreferredEncounterDiagnosisUse
Encounter.dietPreferenceexampleEncounterDiet
Encounter.specialArrangementpreferredSpecialArrangements
Encounter.specialCourtesypreferredSpecialCourtesy
Encounter.admission.admitSourcepreferredAdmitSource
Encounter.admission.reAdmissionexampleHl7VSReAdmissionIndicator
Encounter.admission.dischargeDispositionexampleDischargeDisposition
Encounter.location.statusrequiredEncounterLocationStatus
Encounter.location.formexampleLocationForm

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
enc-1errorEncounter.participantA type must be provided when no explicit actor is specified
: actor.exists() or type.exists()
enc-2errorEncounter.participantA type cannot be provided for a patient or group participant
: actor.exists(resolve() is Patient or resolve() is Group) implies type.exists().not()
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from Encounter

Summary

Mandatory: 8 elements
Must-Support: 4 elements

Differential View

This structure is derived from Encounter

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... status S1..1codeplanned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
Required Pattern: completed
... class S1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... coding S1..1CodingCode defined by a terminology system
..... system 1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... code 1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display 1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
... subject 1..1Reference(Patient)Paciente al que se le realiza la atencion
.... start 1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end 0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... contained 0..*ResourceContained, inline Resources
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
... class SΣ1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... coding SΣ1..1CodingCode defined by a terminology system
..... system Σ1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... code ΣC1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display ΣC1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
... subject Σ1..1Reference(Patient)Paciente al que se le realiza la atencion
... actualPeriod S1..1PeriodPeríodo en el cual el/la Paciente fue hospitalizado/a
.... start ΣC1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end ΣC0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Encounter.statusrequiredPattern: completed
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorEncounterIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorEncounterIf 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().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorEncounterIf 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()
dom-5errorEncounterIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceEncounterA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: AllLanguages (required): IETF language tag for a human language

... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown
Binding: EncounterStatus (required): Current state of the encounter.


Required Pattern: completed
... class SΣ1..1CodeableConceptClasificación del encuentro
Binding: Códigos para tipos de atención (required)
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding SΣ1..1CodingCode defined by a terminology system
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system Σ1..1uriuri de la terminología
Required Pattern: https://hlf.cl/fhir/ig/hackaton/CodeSystem/ClaseAtencionCS
..... version Σ0..1stringVersion of the system - if relevant
..... code ΣC1..1codeCódigo de clase de atención en este caso siempre Hospitalizada
Required Pattern: 1
..... display ΣC1..1stringGlosa que describe el código
Required Pattern: Hospitalizada
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ActPriority (example): Indicates the urgency of the encounter.

... type Σ0..*CodeableConceptSpecific type of encounter (e.g. e-mail consultation, surgical day-care, ...)
Binding: EncounterType (example): A specific code indicating type of service provided


... serviceType Σ0..*CodeableReference(HealthcareService)Specific type of service
Binding: ServiceType (example): Broad categorization of the service that is to be provided.


... subject Σ1..1Reference(Patient)Paciente al que se le realiza la atencion
... subjectStatus 0..1CodeableConceptThe current status of the subject in relation to the Encounter
Binding: EncounterSubjectStatus (example): Current status of the subject within the encounter.

... episodeOfCare Σ0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn 0..*Reference(CarePlan | DeviceRequest | MedicationRequest | ServiceRequest)The request that initiated this encounter
... careTeam 0..*Reference(CareTeam)The group(s) that are allocated to participate in this encounter
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of
... serviceProvider 0..1Reference(Organization)The organization (facility) responsible for this encounter
... participant ΣC0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type ΣC0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... period 0..1PeriodPeriod of time during the encounter that the participant participated
.... actor ΣC0..1Reference(Patient | Group | RelatedPerson | Practitioner | PractitionerRole | Device | HealthcareService)The individual, device, or service participating in the encounter
... appointment Σ0..*Reference(Appointment)The appointment that scheduled this encounter
... virtualService 0..*VirtualServiceDetailConnection details of a virtual service (e.g. conference call)
... actualPeriod S1..1PeriodPeríodo en el cual el/la Paciente fue hospitalizado/a
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... start ΣC1..1dateTimeDía/Hora en el cual se realizó la hospitalización. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
.... end ΣC0..1dateTimeDía/Hora en el cual se cerró el episodio. Formato YYYY-MM-DD ó YYYY-MM-DDThh:mm:ss+zz:zz
... plannedStartDate 0..1dateTimeThe planned start date/time (or admission date) of the encounter
... plannedEndDate 0..1dateTimeThe planned end date/time (or discharge date) of the encounter
... length 0..1DurationActual quantity of time the encounter lasted (less time absent)
... reason Σ0..*BackboneElementThe list of medical reasons that are expected to be addressed during the episode of care
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... use Σ0..*CodeableConceptWhat the reason value should be used for/as
Binding: EncounterReasonUse (example)
.... value Σ0..*CodeableReference(Condition | DiagnosticReport | Observation | ImmunizationRecommendation | Procedure)Reason the encounter takes place (core or reference)
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... diagnosis Σ0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition Σ0..*CodeableReference(Condition)The diagnosis relevant to the encounter
Binding: ConditionProblemDiagnosisCodes (example)
.... use 0..*CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: EncounterDiagnosisUse (preferred): The type of diagnosis this condition represents.


... account 0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: EncounterDiet (example): Medical, cultural or ethical food preferences to help with catering requirements.


... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc
Binding: SpecialArrangements (preferred): Special arrangements.


... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred): Special courtesies.


... admission 0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource 0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred): From where the patient was admitted.

.... reAdmission 0..1CodeableConceptIndicates that the patient is being re-admitted
Binding: hl7VS-re-admissionIndicator (example): The reason for re-admission of this admission encounter.

.... destination 0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition 0..1CodeableConceptCategory or kind of location after discharge
Binding: DischargeDisposition (example): Discharge Disposition.

... location 0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location 1..1Reference(Location)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required): The status of the location.

.... form 0..1CodeableConceptThe physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.)
Binding: LocationForm (example): Physical form of the location.

.... period 0..1PeriodTime period during which the patient was present at the location

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Encounter.languagerequiredAllLanguages
Encounter.statusrequiredPattern: completed
Encounter.classrequiredClaseAtencionVS (a valid code from Códigos para clase de Atención)
Encounter.priorityexampleActPriority
Encounter.typeexampleEncounterType
Encounter.serviceTypeexampleServiceType
Encounter.subjectStatusexampleEncounterSubjectStatus
Encounter.participant.typeextensibleParticipantType
Encounter.reason.useexampleEncounterReasonUse
Encounter.reason.valuepreferredEncounterReasonCodes
Encounter.diagnosis.conditionexampleConditionProblemDiagnosisCodes
Encounter.diagnosis.usepreferredEncounterDiagnosisUse
Encounter.dietPreferenceexampleEncounterDiet
Encounter.specialArrangementpreferredSpecialArrangements
Encounter.specialCourtesypreferredSpecialCourtesy
Encounter.admission.admitSourcepreferredAdmitSource
Encounter.admission.reAdmissionexampleHl7VSReAdmissionIndicator
Encounter.admission.dischargeDispositionexampleDischargeDisposition
Encounter.location.statusrequiredEncounterLocationStatus
Encounter.location.formexampleLocationForm

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
enc-1errorEncounter.participantA type must be provided when no explicit actor is specified
: actor.exists() or type.exists()
enc-2errorEncounter.participantA type cannot be provided for a patient or group participant
: actor.exists(resolve() is Patient or resolve() is Group) implies type.exists().not()
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from Encounter

Summary

Mandatory: 8 elements
Must-Support: 4 elements

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Notas de Implementación


Se describe abajo un resumen de las operaciones de búsqueda sobre este perfil. Se despliegan solo aquellas requeridas para este caso de uso y el formato de la expresión

Search Parameters


Nombre Tipo Descripción Expresión
date-start date Fecha de inicio de un episodio GET [URL_Base]/Encounter?date-start=2018-05-07T16:00:00-03:00
date-start date Episodios desde una fecha en adelante GET [URL_Base]/Encounter?date-start=ge2018-05-07T16:00:00-03:00
date-start date Episodios desde una fecha hacia atrás GET [URL_Base]/Encounter?date-start=le2018-05-07T16:00:00-03:00