Encounter
Estrutura FHIR para troca de informações de atendimentos do membro da Sami.
OBS: As informações são compartilhadas apenas perante o consentimento prévio do membro.
Snapshot
Encounter | I | Encounter | |
id | Σ | 0..1 | string |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | I | 0..* | Extension |
PatientEncounterAdmission | I | 0..1 | ExtensionBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | Binding | |
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
PatientEncounterDischarge | I | 0..1 | ExtensionBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | Binding | |
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
EncouterSpeciality | I | 0..1 | ExtensionBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | Binding | |
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
EncounterBeneficiary | I | 0..1 | Extension |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Fixed Value | ||
type | |||
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
EncounterPosterior | I | 0..1 | Extension |
id | 0..1 | string | |
extension | I | 0..* | Extension |
url | 1..1 | uriFixed Value | |
value[x] | 0..1 | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | |||
type | |||
valueBase64Binary | base64Binary | ||
valueBoolean | boolean | ||
valueCanonical | canonical() | ||
valueCode | code | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueDecimal | decimal | ||
valueId | id | ||
valueInstant | instant | ||
valueInteger | integer | ||
valueMarkdown | markdown | ||
valueOid | oid | ||
valuePositiveInt | positiveInt | ||
valueString | string | ||
valueTime | time | ||
valueUnsignedInt | unsignedInt | ||
valueUri | uri | ||
valueUrl | url | ||
valueUuid | uuid | ||
valueAddress | Address | ||
valueAge | Age | ||
valueAnnotation | Annotation | ||
valueAttachment | Attachment | ||
valueCodeableConcept | CodeableConcept | ||
valueCoding | Coding | ||
valueContactPoint | ContactPoint | ||
valueCount | Count | ||
valueDistance | Distance | ||
valueDuration | Duration | ||
valueHumanName | HumanName | ||
valueIdentifier | Identifier | ||
valueMoney | Money | ||
valuePeriod | Period | ||
valueQuantity | Quantity | ||
valueRange | Range | ||
valueRatio | Ratio | ||
valueSampledData | SampledData | ||
valueSignature | Signature | ||
valueTiming | Timing | ||
valueContactDetail | ContactDetail | ||
valueContributor | Contributor | ||
valueDataRequirement | DataRequirement | ||
valueExpression | Expression | ||
valueParameterDefinition | ParameterDefinition | ||
valueRelatedArtifact | RelatedArtifact | ||
valueTriggerDefinition | TriggerDefinition | ||
valueUsageContext | UsageContext | ||
valueDosage | Dosage | ||
valueMeta | Meta | ||
valueReference | Reference() | ||
modifierExtension | ?! I | 0..* | Extension |
identifier | Σ | 0..0 | Identifier |
status | Σ ?! | 1..1 | codeBinding |
statusHistory | 0..0 | BackboneElement | |
class | Σ | 1..1 | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uri |
version | Σ | 0..0 | string |
code | Σ | 0..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..0 | boolean |
classHistory | 0..0 | BackboneElement | |
type | Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..1 | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uriBinding |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..0 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
serviceType | Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uriBinding |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..0 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
priority | 0..1 | CodeableConceptBinding | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uriBinding |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..0 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
subject | Σ I | 1..1 | Reference(Patient | Group) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 1..1 | string |
type | Σ | 1..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
episodeOfCare | Σ I | 0..0 | Reference(EpisodeOfCare) |
basedOn | I | 0..0 | Reference(ServiceRequest) |
participant | Σ | 1..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
type | Σ | 0..* | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | Coding |
text | Σ | 0..0 | string |
period | I | 0..0 | Period |
individual | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
appointment | Σ I | 0..0 | Reference(Appointment) |
period | I | 0..1 | Period |
id | 0..1 | string | |
extension | I | 0..* | Extension |
start | Σ I | 0..1 | dateTime |
end | Σ I | 0..1 | dateTime |
length | I | 0..0 | Duration |
reasonCode | Σ | 0..* | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | CodingBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uriBinding |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..0 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
reasonReference | Σ I | 0..* | Reference(Condition | Procedure | Observation | ImmunizationRecommendation) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..0 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
diagnosis | Σ | 0..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
condition | Σ I | 1..1 | Reference(Condition | Procedure) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..0 | string |
type | Σ | 0..0 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
use | 0..0 | CodeableConceptBinding | |
rank | 0..0 | positiveInt | |
account | I | 0..0 | Reference(Account) |
hospitalization | 0..0 | BackboneElement | |
location | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
location | I | 1..1 | Reference(Location)Fixed Value |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | stringBindingFixed Value |
type | Σ | 0..1 | uriBindingFixed Value |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
status | 0..0 | codeBinding | |
physicalType | 0..1 | CodeableConceptBinding | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uriBinding |
version | Σ | 0..0 | string |
code | Σ | 0..1 | codeBinding |
display | Σ | 0..0 | string |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
period | I | 0..0 | Period |
serviceProvider | I | 0..1 | Reference(Organization) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
partOf | I | 0..1 | Reference(Encounter) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..0 | Identifier |
display | Σ | 0..0 | string |
Encounter | .. | |
Encounter.extension | 0.. | |
Encounter.extension | Extension | 0..1 |
Encounter.extension.value[x] | .. | |
Encounter.extension | Extension | 0..1 |
Encounter.extension.value[x] | .. | |
Encounter.extension | Extension | 0..1 |
Encounter.extension.value[x] | .. | |
Encounter.extension | Extension | 0..1 |
Encounter.extension.value[x] | .. | |
Encounter.extension.value[x].reference | .. | |
Encounter.extension.value[x].type | .. | |
Encounter.extension | Extension | 0..1 |
Encounter.extension.value[x] | .. | |
Encounter.extension.value[x].reference | .. | |
Encounter.extension.value[x].type | .. | |
Encounter.identifier | ..0 | |
Encounter.status | .. | |
Encounter.statusHistory | ..0 | |
Encounter.class | .. | |
Encounter.class.system | .. | |
Encounter.class.version | ..0 | |
Encounter.class.code | .. | |
Encounter.class.display | .. | |
Encounter.class.userSelected | ..0 | |
Encounter.classHistory | ..0 | |
Encounter.type | ..1 | |
Encounter.type.coding | ..1 | |
Encounter.type.coding.system | .. | |
Encounter.type.coding.version | ..0 | |
Encounter.type.coding.code | .. | |
Encounter.type.coding.display | ..0 | |
Encounter.type.coding.userSelected | ..0 | |
Encounter.type.text | ..0 | |
Encounter.serviceType | .. | |
Encounter.serviceType.coding | .. | |
Encounter.serviceType.coding.system | .. | |
Encounter.serviceType.coding.version | ..0 | |
Encounter.serviceType.coding.code | .. | |
Encounter.serviceType.coding.display | ..0 | |
Encounter.serviceType.coding.userSelected | ..0 | |
Encounter.serviceType.text | ..0 | |
Encounter.priority | .. | |
Encounter.priority.coding | .. | |
Encounter.priority.coding.system | .. | |
Encounter.priority.coding.version | ..0 | |
Encounter.priority.coding.code | .. | |
Encounter.priority.coding.display | ..0 | |
Encounter.priority.coding.userSelected | ..0 | |
Encounter.priority.text | ..0 | |
Encounter.subject | 1.. | |
Encounter.subject.reference | 1.. | |
Encounter.subject.type | 1.. | |
Encounter.subject.identifier | ..0 | |
Encounter.subject.display | ..0 | |
Encounter.episodeOfCare | ..0 | |
Encounter.basedOn | ..0 | |
Encounter.participant | 1.. | |
Encounter.participant.type | .. | |
Encounter.participant.type.coding | .. | |
Encounter.participant.type.text | ..0 | |
Encounter.participant.period | ..0 | |
Encounter.participant.individual | .. | |
Encounter.participant.individual.reference | .. | |
Encounter.participant.individual.type | .. | |
Encounter.participant.individual.identifier | ..0 | |
Encounter.participant.individual.display | ..0 | |
Encounter.appointment | ..0 | |
Encounter.period | .. | |
Encounter.period.start | .. | |
Encounter.period.end | .. | |
Encounter.length | ..0 | |
Encounter.reasonCode | .. | |
Encounter.reasonCode.coding | .. | |
Encounter.reasonCode.coding.system | .. | |
Encounter.reasonCode.coding.version | ..0 | |
Encounter.reasonCode.coding.code | .. | |
Encounter.reasonCode.coding.display | ..0 | |
Encounter.reasonCode.coding.userSelected | ..0 | |
Encounter.reasonCode.text | ..0 | |
Encounter.reasonReference | .. | |
Encounter.reasonReference.reference | .. | |
Encounter.reasonReference.type | ..0 | |
Encounter.reasonReference.identifier | ..0 | |
Encounter.reasonReference.display | ..0 | |
Encounter.diagnosis | .. | |
Encounter.diagnosis.condition | .. | |
Encounter.diagnosis.condition.reference | ..0 | |
Encounter.diagnosis.condition.type | ..0 | |
Encounter.diagnosis.condition.identifier | ..0 | |
Encounter.diagnosis.condition.display | ..0 | |
Encounter.diagnosis.use | ..0 | |
Encounter.diagnosis.rank | ..0 | |
Encounter.account | ..0 | |
Encounter.hospitalization | ..0 | |
Encounter.location | .. | |
Encounter.location.location | .. | |
Encounter.location.location.reference | .. | |
Encounter.location.location.type | .. | |
Encounter.location.location.identifier | ..0 | |
Encounter.location.location.display | ..0 | |
Encounter.location.status | ..0 | |
Encounter.location.physicalType | .. | |
Encounter.location.physicalType.coding | .. | |
Encounter.location.physicalType.coding.system | .. | |
Encounter.location.physicalType.coding.version | ..0 | |
Encounter.location.physicalType.coding.code | .. | |
Encounter.location.physicalType.coding.display | ..0 | |
Encounter.location.physicalType.coding.userSelected | ..0 | |
Encounter.location.physicalType.text | ..0 | |
Encounter.location.period | ..0 | |
Encounter.serviceProvider | .. | |
Encounter.serviceProvider.reference | .. | |
Encounter.serviceProvider.type | .. | |
Encounter.serviceProvider.identifier | ..0 | |
Encounter.serviceProvider.display | ..0 | |
Encounter.partOf | .. | |
Encounter.partOf.reference | .. | |
Encounter.partOf.type | .. | |
Encounter.partOf.identifier | ..0 | |
Encounter.partOf.display | ..0 |
Encounter | |
Definition | Uma interação entre um paciente e o(s) provedor(es) de saúde com a finalidade de fornecer serviço(s) de saúde ou avaliar o estado de saúde de um paciente. |
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 | string |
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. |
Encounter.meta | |
Definition | 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. |
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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
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. 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. |
Invariants |
|
Mappings |
|
Encounter.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
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 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. |
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 information 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
Mappings |
|
Encounter.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
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.extension:PatientEncounterAdmission | |
Definition | Tipo de admissão do encontro |
Cardinality | 0...1 |
Type | Extension |
Binding | episode-admission (required) |
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. |
Invariants |
|
Mappings |
|
Encounter.extension:PatientEncounterAdmission.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 |
Mappings |
|
Encounter.extension:PatientEncounterAdmission.extension | |
Definition | 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. |
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.extension:PatientEncounterAdmission.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://samisaude.com/fhir/StructureDefinition/PatientEncounterAdmission |
Mappings |
|
Encounter.extension:PatientEncounterAdmission.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 0...1 |
Type | base64Binary |
Binding | episode-admission (required) |
Invariants |
|
Mappings |
|
Encounter.extension:PatientEncounterDischarge | |
Definition | Desfecho do encontro. |
Cardinality | 0...1 |
Type | Extension |
Binding | discharge-nature (required) |
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. |
Invariants |
|
Mappings |
|
Encounter.extension:PatientEncounterDischarge.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 |
Mappings |
|
Encounter.extension:PatientEncounterDischarge.extension | |
Definition | 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. |
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.extension:PatientEncounterDischarge.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://samisaude.com/fhir/StructureDefinition/PatientEncounterDischarge |
Mappings |
|
Encounter.extension:PatientEncounterDischarge.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 0...1 |
Type | base64Binary |
Binding | discharge-nature (required) |
Invariants |
|
Mappings |
|
Encounter.extension:EncouterSpeciality | |
Definition | Especialidade do encontro. |
Cardinality | 0...1 |
Type | Extension |
Binding | cbo (required) |
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. |
Invariants |
|
Mappings |
|
Encounter.extension:EncouterSpeciality.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 |
Mappings |
|
Encounter.extension:EncouterSpeciality.extension | |
Definition | 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. |
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.extension:EncouterSpeciality.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://samisaude.com/fhir/StructureDefinition/EncounterSpecialty |
Mappings |
|
Encounter.extension:EncouterSpeciality.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 0...1 |
Type | base64Binary |
Binding | cbo (required) |
Invariants |
|
Mappings |
|
Encounter.extension:EncounterBeneficiary | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...1 |
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. |
Invariants |
|
Mappings |
|
Encounter.extension:EncounterBeneficiary.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 |
Mappings |
|
Encounter.extension:EncounterBeneficiary.extension | |
Definition | 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. |
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.extension:EncounterBeneficiary.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://samisaude.com/fhir/StructureDefinition/EncounterBeneficiary |
Mappings |
|
Encounter.extension:EncounterBeneficiary.value[x] | |
Definition | Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista). |
Cardinality | 0...1 |
Type | base64Binary |
Invariants |
|
Mappings |
|
Encounter.extension:EncounterBeneficiary.value[x].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 |
Mappings |
|
Encounter.extension:EncounterBeneficiary.value[x].extension | |
Definition | 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. |
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.extension:EncounterBeneficiary.value[x].reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Fixed Value | Coverage |
Encounter.extension:EncounterBeneficiary.value[x].type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Encounter.extension:EncounterPosterior | |
Definition | Encontro posterior |
Cardinality | 0...1 |
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. |
Invariants |
|
Mappings |
|
Encounter.extension:EncounterPosterior.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 |
Mappings |
|
Encounter.extension:EncounterPosterior.extension | |
Definition | 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. |
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.extension:EncounterPosterior.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://samisaude.com/fhir/StructureDefinition/EncounterPosterior |
Mappings |
|
Encounter.extension:EncounterPosterior.value[x] | |
Definition | Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista). |
Cardinality | 0...1 |
Type | base64Binary |
Invariants |
|
Mappings |
|
Encounter.extension:EncounterPosterior.value[x].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 |
Mappings |
|
Encounter.extension:EncounterPosterior.value[x].extension | |
Definition | 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. |
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.extension:EncounterPosterior.value[x].reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Encounter.extension:EncounterPosterior.value[x].type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
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...0 |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Encounter.status | |
Definition | Concluído | Solicitado | Suspenso | Falta do Paciente | Cancelado | Desconhecido |
Cardinality | 1...1 |
Type | code |
Binding | Status atual do encontro. |
Modifier | True |
Summary | True |
Comments | Observe que as regras de negócios internas determinarão as transições apropriadas que podem ocorrer entre os status (e também as classes). |
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...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 |
Mappings |
|
Encounter.statusHistory.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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. |
Comments | Note that FHIR strings SHALL 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 | 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"). Period is not used for a duration (a measure of elapsed time). See Duration. |
Invariants |
|
Mappings |
|
Encounter.class | |
Definition | Conceitos que representam a classificação do encontro do paciente, como ambulatorial (ambulatorial), hospitalar, de emergência, saúde doméstica ou outros devido a variações locais. |
Cardinality | 1...1 |
Type | Coding |
Binding | Classificação do encontro do paciente. |
Summary | True |
Comments | Os códigos podem ser definidos casualmente em enumerações ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. |
Invariants |
|
Mappings |
|
Encounter.class.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 |
Mappings |
|
Encounter.class.extension | |
Definition | 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. |
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.class.system | |
Definition | A identificação do sistema de código que define o significado do símbolo no código. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca. |
Invariants |
|
Mappings |
|
Encounter.class.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...0 |
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 |
|
Encounter.class.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.class.display | |
Definition | Uma representação do significado do código no sistema, seguindo as regras do sistema. |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.class.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
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 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. |
Cardinality | 0...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 |
Mappings |
|
Encounter.classHistory.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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. |
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 | 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"). Period is not used for a duration (a measure of elapsed time). See Duration. |
Invariants |
|
Mappings |
|
Encounter.type | |
Definition | Tipo específico de encontro (por exemplo, consulta por e-mail, creche cirúrgica, enfermagem especializada, reabilitação). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Tipo de encontro. |
Summary | True |
Comments | Como há muitas maneiras de classificar mais os encontros, este elemento é 0 .. *. |
Invariants |
|
Mappings |
|
Encounter.type.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 |
Mappings |
|
Encounter.type.extension | |
Definition | 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. |
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.type.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...1 |
Type | Coding |
Binding | episodes (required) |
Summary | True |
Requirements | Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Encounter.type.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 |
Mappings |
|
Encounter.type.coding.extension | |
Definition | 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. |
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.type.coding.system | |
Definition | A identificação do sistema de código que define o significado do símbolo no código. |
Cardinality | 0...1 |
Type | uri |
Binding | episodes (required) |
Summary | True |
Requirements | Precisa ser inequívoco sobre a origem da definição do símbolo. |
Comments | O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca. |
Invariants |
|
Mappings |
|
Encounter.type.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...0 |
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 |
|
Encounter.type.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | episodes (required) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...0 |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
Encounter.type.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...0 |
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.serviceType | |
Definition | Categorização do serviço a ser prestado. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Ampla categorização do serviço a ser fornecido. |
Summary | True |
Comments | Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação. |
Invariants |
|
Mappings |
|
Encounter.serviceType.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 |
Mappings |
|
Encounter.serviceType.extension | |
Definition | 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. |
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.serviceType.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Binding | episode-type (extensible) |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
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.serviceType.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 |
Mappings |
|
Encounter.serviceType.coding.extension | |
Definition | 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. |
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.serviceType.coding.system | |
Definition | A identificação do sistema de código que define o significado do símbolo no código. |
Cardinality | 0...1 |
Type | uri |
Binding | episode-type (extensible) |
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 reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Encounter.serviceType.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...0 |
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 |
|
Encounter.serviceType.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | episode-type (extensible) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.serviceType.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...0 |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.serviceType.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
Encounter.serviceType.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...0 |
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.priority | |
Definition | Indica a prioridade de admissão. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Indica a prioridade de admissão. |
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.priority.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 |
Mappings |
|
Encounter.priority.extension | |
Definition | 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. |
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.priority.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Binding | admission-priority (extensible) |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Encounter.priority.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 |
Mappings |
|
Encounter.priority.coding.extension | |
Definition | 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. |
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.priority.coding.system | |
Definition | A identificação do sistema de código que define o significado do símbolo no código. |
Cardinality | 0...1 |
Type | uri |
Binding | admission-priority (extensible) |
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 reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Encounter.priority.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...0 |
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 |
|
Encounter.priority.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | admission-priority (extensible) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.priority.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...0 |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.priority.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
Encounter.priority.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...0 |
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.subject | |
Definition | O paciente ou grupo presente no encontro. |
Cardinality | 1...1 |
Type | Reference(Patient | Group) |
Summary | True |
Alias | patient |
Comments | Embora o encontro seja sempre sobre o paciente, o paciente pode não ser realmente conhecido em todos os contextos de uso, e pode haver um grupo de pacientes que podem ser anônimos (como em uma terapia de grupo para Alcoólicos Anônimos - onde a gravação do O encontro pode ser usado para faturamento no número de pessoas / equipe e não é importante para o contexto dos pacientes específicos) ou alternativamente em cuidados veterinários um rebanho de ovelhas recebendo tratamento (onde os animais não são rastreados individualmente). |
Invariants |
|
Mappings |
|
Encounter.subject.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 |
Mappings |
|
Encounter.subject.extension | |
Definition | 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. |
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.subject.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Encounter.subject.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 1...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Encounter.subject.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.subject.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
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...0 |
Type | Reference(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.basedOn | |
Definition | The request this encounter satisfies (e.g. incoming referral or procedure request). |
Cardinality | 0...0 |
Type | Reference(ServiceRequest) |
Alias | incomingReferral |
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 | A lista de pessoas responsáveis pela prestação do serviço. |
Cardinality | 1...* |
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 |
Mappings |
|
Encounter.participant.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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 | Papel do participante no encontro |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Role of participant in encounter. |
Summary | True |
Comments | O tipo de participante indica como um indivíduo participa de um encontro. Inclui participantes não praticantes e, para praticantes, descreve o tipo de ação no contexto deste encontro (por exemplo, Dr. Admitidor, Dr. Assistente, Tradutor, Dr. Consultor). Isso é diferente das funções do profissional, que são funções funcionais, derivadas de termos de emprego, educação, licenciamento, etc. |
Invariants |
|
Mappings |
|
Encounter.participant.type.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 |
Mappings |
|
Encounter.participant.type.extension | |
Definition | 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. |
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.type.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Encounter.participant.type.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...0 |
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.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...0 |
Type | Period |
Comments | 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"). Period is not used for a duration (a measure of elapsed time). See Duration. |
Invariants |
|
Mappings |
|
Encounter.participant.individual | |
Definition | Pessoas envolvidas no encontro que não sejam o paciente |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | RelatedPerson) |
Summary | True |
Comments | As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local. |
Invariants |
|
Mappings |
|
Encounter.participant.individual.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 |
Mappings |
|
Encounter.participant.individual.extension | |
Definition | 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. |
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.individual.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Encounter.participant.individual.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Encounter.participant.individual.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.participant.individual.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Encounter.appointment | |
Definition | The appointment that scheduled this encounter. |
Cardinality | 0...0 |
Type | Reference(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 | O horário de início e término do encontro. |
Cardinality | 0...1 |
Type | Period |
Comments | Caso não seja (ainda) conhecido, o final do Período pode ser omitido. |
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 |
Mappings |
|
Encounter.period.extension | |
Definition | 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. |
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 | O início do período. O limite é inclusivo. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | Se o elemento inferior estiver faltando, o significado é que o limite inferior não é conhecido. |
Invariants |
|
Mappings |
|
Encounter.period.end | |
Definition | O fim do período. Se o final do período estiver faltando, significa que nenhum final era conhecido ou planejado no momento em que a instância foi criada. O início pode estar no passado e a data de término no futuro, o que significa que o período é esperado / planejado para terminar nessa hora. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | O valor alto inclui qualquer data / hora correspondente. ou seja, 2012-02-03T10: 00: 00 está em um período que tem um valor final de 2012-02-03. |
Invariants |
|
Mappings |
|
Encounter.length | |
Definition | Quantity of time the encounter lasted. This excludes the time during leaves of absence. |
Cardinality | 0...0 |
Type | Duration |
Comments | May differ from the time the Encounter.period lasted because of leave of absence. |
Invariants |
|
Mappings |
|
Encounter.reasonCode | |
Definition | A razão pela qual o encontro ocorre, expressa em um código. Para admissões, isso pode ser usado para um diagnóstico de admissão codificado. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Razão pela qual o encontro acontece. |
Summary | True |
Alias | Indication, Admission diagnosis |
Comments | Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal). |
Invariants |
|
Mappings |
|
Encounter.reasonCode.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 |
Mappings |
|
Encounter.reasonCode.extension | |
Definition | 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. |
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.reasonCode.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Binding | reason-of-service (required) |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
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.reasonCode.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 |
Mappings |
|
Encounter.reasonCode.coding.extension | |
Definition | 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. |
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.reasonCode.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Binding | reason-of-service (preferred) |
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 reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
Encounter.reasonCode.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...0 |
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 |
|
Encounter.reasonCode.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 0...1 |
Type | code |
Binding | reason-of-service (preferred) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.reasonCode.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...0 |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.reasonCode.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
Encounter.reasonCode.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...0 |
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.reasonReference | |
Definition | A razão pela qual o encontro ocorre, expressa em um código. Para admissões, isso pode ser usado para um diagnóstico de admissão codificado. |
Cardinality | 0...* |
Type | Reference(Condition | Procedure | Observation | ImmunizationRecommendation) |
Summary | True |
Alias | Indication, Admission diagnosis |
Comments | Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal). |
Invariants |
|
Mappings |
|
Encounter.reasonReference.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 |
Mappings |
|
Encounter.reasonReference.extension | |
Definition | 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. |
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.reasonReference.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Encounter.reasonReference.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...0 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Encounter.reasonReference.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.reasonReference.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Encounter.diagnosis | |
Definition | A lista de diagnósticos relevantes para este encontro |
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 |
Mappings |
|
Encounter.diagnosis.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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 | Motivo pelo qual o encontro ocorre, conforme especificado usando informações de outro recurso. Para admissões, este é o diagnóstico de admissão. A indicação normalmente será uma Condição (com outros recursos referenciados em evidências.detalhes) ou um Procedimento. |
Cardinality | 1...1 |
Type | Reference(Condition | Procedure) |
Summary | True |
Alias | Admission diagnosis, discharge diagnosis, indication |
Comments | Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal). |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition.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 |
Mappings |
|
Encounter.diagnosis.condition.extension | |
Definition | 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. |
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.condition.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...0 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.diagnosis.condition.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Encounter.diagnosis.use | |
Definition | Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | The type of diagnosis this condition represents. |
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...0 |
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...0 |
Type | Reference(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...0 |
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 |
Mappings |
|
Encounter.hospitalization.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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/organization from which the patient came before admission. |
Cardinality | 0...1 |
Type | Reference(Location | 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.hospitalization.admitSource | |
Definition | From where patient was admitted (physician referral, transfer). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | From where the patient was admitted. |
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. |
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. |
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. |
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. |
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/organization to which the patient is discharged. |
Cardinality | 0...1 |
Type | Reference(Location | 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.hospitalization.dischargeDisposition | |
Definition | Category or kind of location after discharge. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Discharge Disposition. |
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 | Lista de locais onde o paciente esteve durante este encontro. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | Encontros virtuais podem ser registrados no Encontro especificando uma referência de local para um local do tipo "tipo", como "casa do cliente" e um encontro.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 |
Mappings |
|
Encounter.location.extension | |
Definition | 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. |
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 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
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 | O local onde ocorre o encontro. |
Cardinality | 1...1 |
Type | Reference(Location) |
Comments | As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local. |
Invariants |
|
Fixed Value | { "reference": "https://www.samisaude.com.br/fhir/r4/CodeSystem/place-of-service", "type": "CodeSystem" } |
Mappings |
|
Encounter.location.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 |
Mappings |
|
Encounter.location.location.extension | |
Definition | 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. |
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.location.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos. |
Cardinality | 0...1 |
Type | string |
Binding | place-of-service (extensible) |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Encounter.location.location.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Um recurso (ou, para modelos lógicos, o URI do modelo lógico). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Encounter.location.location.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.location.location.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Encounter.location.status | |
Definition | 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. |
Cardinality | 0...0 |
Type | code |
Binding | The status of the location. |
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.physicalType | |
Definition | Isso será usado para especificar os níveis necessários (cama / enfermaria / quarto / etc.) Que deseja gravar para simplificar o envio de mensagens ou consulta. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Forma física do local. |
Comments | Essas informações são desnormalizadas a partir do recurso Local para oferecer suporte a uma compreensão mais fácil do recurso de encontro e processamento em mensagens ou consultas. Pode haver muitos níveis na hierarquia, e isso pode representar apenas níveis específicos que são necessários para um cenário de uso específico. |
Invariants |
|
Mappings |
|
Encounter.location.physicalType.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 |
Mappings |
|
Encounter.location.physicalType.extension | |
Definition | 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. |
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.physicalType.coding | |
Definition | Uma referência a um código definido por um sistema de terminologia. |
Cardinality | 0...* |
Type | Coding |
Binding | accomodation-type (example) |
Summary | True |
Requirements | Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código. |
Comments | Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true. |
Invariants |
|
Mappings |
|
Encounter.location.physicalType.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 |
Mappings |
|
Encounter.location.physicalType.coding.extension | |
Definition | 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. |
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.physicalType.coding.system | |
Definition | A identificação do sistema de código que define o significado do símbolo no código. |
Cardinality | 0...1 |
Type | uri |
Binding | accomodation-type (extensible) |
Summary | True |
Requirements | Precisa ser inequívoco sobre a origem da definição do símbolo. |
Comments | O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca. |
Invariants |
|
Mappings |
|
Encounter.location.physicalType.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...0 |
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 |
|
Encounter.location.physicalType.coding.code | |
Definition | Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação). |
Cardinality | 0...1 |
Type | code |
Binding | accomodation-type (extensible) |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.location.physicalType.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...0 |
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 SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.location.physicalType.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
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 |
|
Encounter.location.physicalType.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...0 |
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.location.period | |
Definition | Time period during which the patient was present at the location. |
Cardinality | 0...0 |
Type | Period |
Comments | 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"). Period is not used for a duration (a measure of elapsed time). See Duration. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider | |
Definition | A organização principal responsável pelos serviços deste Encontro. PODE ser o mesmo que a organização no prontuário do paciente, porém pode ser diferente, como se o ator que realiza os serviços fosse de uma organização externa (que pode ser faturada separadamente) para uma consulta externa. Consulte o pacote de exemplo que mostra um conjunto abreviado de Encontros para uma colonoscopia. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Comments | As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider.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 |
Mappings |
|
Encounter.serviceProvider.extension | |
Definition | 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. |
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.serviceProvider.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful.. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Invariants |
|
Mappings |
|
Encounter.serviceProvider.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.serviceProvider.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Encounter.partOf | |
Definition | Outro Encontro do qual este encontro faz parte (administrativamente ou no tempo). |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Comments | Isso também é usado para associar o encontro de uma criança ao encontro da mãe. Consulte a seção Notas no recurso Paciente para obter mais detalhes. |
Invariants |
|
Mappings |
|
Encounter.partOf.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 |
Mappings |
|
Encounter.partOf.extension | |
Definition | 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. |
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.partOf.reference | |
Definition | Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura "/ [type] / [id]", deve-se assumir que a referência é a um servidor FHIR RESTful. |
Invariants |
|
Mappings |
|
Encounter.partOf.type | |
Definition | O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes. O tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo "Paciente" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado. |
Invariants |
|
Mappings |
|
Encounter.partOf.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...0 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Encounter.partOf.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
JSON
{ "resourceType": "StructureDefinition", "url": "https://www.samisaude.com.br/fhir/r4/StructureDefinition/MyEncounter", "name": "Encontro/Evento de saúde", "status": "active", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Encounter", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Encounter", "derivation": "constraint", "differential": { "element": [ { "id": "Encounter", "path": "Encounter", "short": "Uma interação durante a qual os serviços são prestados ao paciente.", "definition": "Uma interação entre um paciente e o(s) provedor(es) de saúde com a finalidade de fornecer serviço(s) de saúde ou avaliar o estado de saúde de um paciente." }, { "id": "Encounter.extension", "path": "Encounter.extension", "slicing": { "discriminator": [ { "type": "value", "path": "url" } ], "rules": "open" }, "min": 0 }, { "id": "Encounter.extension:PatientEncounterAdmission", "path": "Encounter.extension", "sliceName": "PatientEncounterAdmission", "short": "Tipo de admissão do encontro", "definition": "Tipo de admissão do encontro", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://samisaude.com/fhir/StructureDefinition/PatientEncounterAdmission" ] } ], "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-admission" } }, { "id": "Encounter.extension:PatientEncounterAdmission.value[x]", "path": "Encounter.extension.value[x]", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-admission" } }, { "id": "Encounter.extension:PatientEncounterDischarge", "path": "Encounter.extension", "sliceName": "PatientEncounterDischarge", "short": "Desfecho do encontro", "definition": "Desfecho do encontro.", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://samisaude.com/fhir/StructureDefinition/PatientEncounterDischarge" ] } ], "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/discharge-nature" } }, { "id": "Encounter.extension:PatientEncounterDischarge.value[x]", "path": "Encounter.extension.value[x]", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/discharge-nature" } }, { "id": "Encounter.extension:EncouterSpeciality", "path": "Encounter.extension", "sliceName": "EncouterSpeciality", "short": "Especialidade do encontro", "definition": "Especialidade do encontro.", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://samisaude.com/fhir/StructureDefinition/EncounterSpecialty" ] } ], "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/cbo" } }, { "id": "Encounter.extension:EncouterSpeciality.value[x]", "path": "Encounter.extension.value[x]", "short": "Valor da Extensão para Especialidade do Evento.", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/cbo" } }, { "id": "Encounter.extension:EncounterBeneficiary", "path": "Encounter.extension", "sliceName": "EncounterBeneficiary", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://samisaude.com/fhir/StructureDefinition/EncounterBeneficiary" ] } ] }, { "id": "Encounter.extension:EncounterBeneficiary.value[x]", "path": "Encounter.extension.value[x]", "definition": "Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista)." }, { "id": "Encounter.extension:EncounterBeneficiary.value[x].reference", "path": "Encounter.extension.value[x].reference", "short": "Coverage", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful.", "fixedString": "Coverage" }, { "id": "Encounter.extension:EncounterBeneficiary.value[x].type", "path": "Encounter.extension.value[x].type", "short": "Coverage", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Encounter.extension:EncounterPosterior", "path": "Encounter.extension", "sliceName": "EncounterPosterior", "short": "Outros encontros", "definition": "Encontro posterior", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://samisaude.com/fhir/StructureDefinition/EncounterPosterior" ] } ] }, { "id": "Encounter.extension:EncounterPosterior.value[x]", "path": "Encounter.extension.value[x]", "short": "Valor da Extensão", "definition": "Valor da extensão - deve ser um de um conjunto restrito de tipos de dados (consulte [Extensibilidade] (extensibility.html) para obter uma lista)." }, { "id": "Encounter.extension:EncounterPosterior.value[x].reference", "path": "Encounter.extension.value[x].reference", "short": "Encounter", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Encounter.extension:EncounterPosterior.value[x].type", "path": "Encounter.extension.value[x].type", "short": "Encounter", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Encounter.identifier", "path": "Encounter.identifier", "max": "0" }, { "id": "Encounter.status", "path": "Encounter.status", "short": "Concluído | Solicitado | Suspenso | Falta do Paciente | Cancelado | Desconhecido", "definition": "Concluído | Solicitado | Suspenso | Falta do Paciente | Cancelado | Desconhecido", "comment": "Observe que as regras de negócios internas determinarão as transições apropriadas que podem ocorrer entre os status (e também as classes).", "binding": { "strength": "required", "description": "Status atual do encontro.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/procedure-status" } }, { "id": "Encounter.statusHistory", "path": "Encounter.statusHistory", "max": "0" }, { "id": "Encounter.class", "path": "Encounter.class", "short": "Classificação do encontro com o paciente", "definition": "Conceitos que representam a classificação do encontro do paciente, como ambulatorial (ambulatorial), hospitalar, de emergência, saúde doméstica ou outros devido a variações locais.", "comment": "Os códigos podem ser definidos casualmente em enumerações ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações.", "binding": { "strength": "extensible", "description": "Classificação do encontro do paciente." } }, { "id": "Encounter.class.system", "path": "Encounter.class.system", "short": "Identidade do sistema de terminologia: Episode-type", "definition": "A identificação do sistema de código que define o significado do símbolo no código.", "comment": "O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca." }, { "id": "Encounter.class.version", "path": "Encounter.class.version", "max": "0" }, { "id": "Encounter.class.code", "path": "Encounter.class.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação)." }, { "id": "Encounter.class.display", "path": "Encounter.class.display", "short": "Representação definida pelo sistema", "definition": "Uma representação do significado do código no sistema, seguindo as regras do sistema." }, { "id": "Encounter.class.userSelected", "path": "Encounter.class.userSelected", "max": "0" }, { "id": "Encounter.classHistory", "path": "Encounter.classHistory", "max": "0" }, { "id": "Encounter.type", "path": "Encounter.type", "short": "Tipo específico de encontro", "definition": "Tipo específico de encontro (por exemplo, consulta por e-mail, creche cirúrgica, enfermagem especializada, reabilitação).", "comment": "Como há muitas maneiras de classificar mais os encontros, este elemento é 0 .. *.", "max": "1", "binding": { "strength": "required", "description": "Tipo de encontro.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episodes" } }, { "id": "Encounter.type.coding", "path": "Encounter.type.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true.", "requirements": "Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código.", "max": "1", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episodes" } }, { "id": "Encounter.type.coding.system", "path": "Encounter.type.coding.system", "short": "Identidade do sistema de terminologia", "definition": "A identificação do sistema de código que define o significado do símbolo no código.", "comment": "O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca.", "requirements": "Precisa ser inequívoco sobre a origem da definição do símbolo.", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episodes" } }, { "id": "Encounter.type.coding.version", "path": "Encounter.type.coding.version", "max": "0" }, { "id": "Encounter.type.coding.code", "path": "Encounter.type.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episodes" } }, { "id": "Encounter.type.coding.display", "path": "Encounter.type.coding.display", "max": "0" }, { "id": "Encounter.type.coding.userSelected", "path": "Encounter.type.coding.userSelected", "max": "0" }, { "id": "Encounter.type.text", "path": "Encounter.type.text", "max": "0" }, { "id": "Encounter.serviceType", "path": "Encounter.serviceType", "short": "Tipo específico de serviço", "definition": "Categorização do serviço a ser prestado.", "comment": "Nem todos os usos de terminologia se enquadram neste padrão geral. Em alguns casos, os modelos não devem usar CodeableConcept e usar Coding diretamente e fornecer sua própria estrutura para gerenciar texto, codificações, traduções e a relação entre elementos e pré e pós-coordenação.", "binding": { "strength": "extensible", "description": "Ampla categorização do serviço a ser fornecido.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-type" } }, { "id": "Encounter.serviceType.coding", "path": "Encounter.serviceType.coding", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-type" } }, { "id": "Encounter.serviceType.coding.system", "path": "Encounter.serviceType.coding.system", "short": "Identidade do sistema de terminologia", "definition": "A identificação do sistema de código que define o significado do símbolo no código.", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-type" } }, { "id": "Encounter.serviceType.coding.version", "path": "Encounter.serviceType.coding.version", "max": "0" }, { "id": "Encounter.serviceType.coding.code", "path": "Encounter.serviceType.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/episode-type" } }, { "id": "Encounter.serviceType.coding.display", "path": "Encounter.serviceType.coding.display", "max": "0" }, { "id": "Encounter.serviceType.coding.userSelected", "path": "Encounter.serviceType.coding.userSelected", "max": "0" }, { "id": "Encounter.serviceType.text", "path": "Encounter.serviceType.text", "max": "0" }, { "id": "Encounter.priority", "path": "Encounter.priority", "short": "Indica a prioridade de admissão", "definition": "Indica a prioridade de admissão.", "binding": { "strength": "extensible", "description": "Indica a prioridade de admissão.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/admission-priority" } }, { "id": "Encounter.priority.coding", "path": "Encounter.priority.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true.", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/admission-priority" } }, { "id": "Encounter.priority.coding.system", "path": "Encounter.priority.coding.system", "short": "Identidade do sistema de terminologia", "definition": "A identificação do sistema de código que define o significado do símbolo no código.", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/admission-priority" } }, { "id": "Encounter.priority.coding.version", "path": "Encounter.priority.coding.version", "max": "0" }, { "id": "Encounter.priority.coding.code", "path": "Encounter.priority.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/admission-priority" } }, { "id": "Encounter.priority.coding.display", "path": "Encounter.priority.coding.display", "max": "0" }, { "id": "Encounter.priority.coding.userSelected", "path": "Encounter.priority.coding.userSelected", "max": "0" }, { "id": "Encounter.priority.text", "path": "Encounter.priority.text", "max": "0" }, { "id": "Encounter.subject", "path": "Encounter.subject", "short": "O paciente ou grupo presente no encontro", "definition": "O paciente ou grupo presente no encontro.", "comment": "Embora o encontro seja sempre sobre o paciente, o paciente pode não ser realmente conhecido em todos os contextos de uso, e pode haver um grupo de pacientes que podem ser anônimos (como em uma terapia de grupo para Alcoólicos Anônimos - onde a gravação do O encontro pode ser usado para faturamento no número de pessoas / equipe e não é importante para o contexto dos pacientes específicos) ou alternativamente em cuidados veterinários um rebanho de ovelhas recebendo tratamento (onde os animais não são rastreados individualmente).", "min": 1 }, { "id": "Encounter.subject.reference", "path": "Encounter.subject.reference", "short": "Referência literal, URL relativa, interna ou absoluta", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for a um servidor FHIR RESTful, deve ser considerado específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful.", "min": 1 }, { "id": "Encounter.subject.type", "path": "Encounter.subject.type", "short": "Patient | Paciente", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "min": 1 }, { "id": "Encounter.subject.identifier", "path": "Encounter.subject.identifier", "max": "0" }, { "id": "Encounter.subject.display", "path": "Encounter.subject.display", "max": "0" }, { "id": "Encounter.episodeOfCare", "path": "Encounter.episodeOfCare", "max": "0" }, { "id": "Encounter.basedOn", "path": "Encounter.basedOn", "max": "0" }, { "id": "Encounter.participant", "path": "Encounter.participant", "short": "Lista de participantes envolvidos no encontro", "definition": "A lista de pessoas responsáveis pela prestação do serviço.", "min": 1 }, { "id": "Encounter.participant.type", "path": "Encounter.participant.type", "short": "Papel do participante no encontro", "definition": "Papel do participante no encontro", "comment": "O tipo de participante indica como um indivíduo participa de um encontro. Inclui participantes não praticantes e, para praticantes, descreve o tipo de ação no contexto deste encontro (por exemplo, Dr. Admitidor, Dr. Assistente, Tradutor, Dr. Consultor). Isso é diferente das funções do profissional, que são funções funcionais, derivadas de termos de emprego, educação, licenciamento, etc." }, { "id": "Encounter.participant.type.coding", "path": "Encounter.participant.type.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true." }, { "id": "Encounter.participant.type.text", "path": "Encounter.participant.type.text", "max": "0" }, { "id": "Encounter.participant.period", "path": "Encounter.participant.period", "max": "0" }, { "id": "Encounter.participant.individual", "path": "Encounter.participant.individual", "short": "Pessoas envolvidas no encontro que não sejam o paciente", "definition": "Pessoas envolvidas no encontro que não sejam o paciente", "comment": "As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local." }, { "id": "Encounter.participant.individual.reference", "path": "Encounter.participant.individual.reference", "short": "Referência literal, URL relativa, interna ou absoluta", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Encounter.participant.individual.type", "path": "Encounter.participant.individual.type", "short": "Practioner", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos)." }, { "id": "Encounter.participant.individual.identifier", "path": "Encounter.participant.individual.identifier", "max": "0" }, { "id": "Encounter.participant.individual.display", "path": "Encounter.participant.individual.display", "max": "0" }, { "id": "Encounter.appointment", "path": "Encounter.appointment", "max": "0" }, { "id": "Encounter.period", "path": "Encounter.period", "short": "O horário de início e término do encontro", "definition": "O horário de início e término do encontro.", "comment": "Caso não seja (ainda) conhecido, o final do Período pode ser omitido." }, { "id": "Encounter.period.start", "path": "Encounter.period.start", "short": "Hora de início com limite inclusivo", "definition": "O início do período. O limite é inclusivo.", "comment": "Se o elemento inferior estiver faltando, o significado é que o limite inferior não é conhecido." }, { "id": "Encounter.period.end", "path": "Encounter.period.end", "short": "Horário de término com limite inclusivo, se não for contínuo", "definition": "O fim do período. Se o final do período estiver faltando, significa que nenhum final era conhecido ou planejado no momento em que a instância foi criada. O início pode estar no passado e a data de término no futuro, o que significa que o período é esperado / planejado para terminar nessa hora.", "comment": "O valor alto inclui qualquer data / hora correspondente. ou seja, 2012-02-03T10: 00: 00 está em um período que tem um valor final de 2012-02-03." }, { "id": "Encounter.length", "path": "Encounter.length", "max": "0" }, { "id": "Encounter.reasonCode", "path": "Encounter.reasonCode", "short": "Razão codificada pela qual o encontro ocorre", "definition": "A razão pela qual o encontro ocorre, expressa em um código. Para admissões, isso pode ser usado para um diagnóstico de admissão codificado.", "comment": "Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal).", "binding": { "strength": "required", "description": "Razão pela qual o encontro acontece.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/reason-of-service" } }, { "id": "Encounter.reasonCode.coding", "path": "Encounter.reasonCode.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "binding": { "strength": "required", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/reason-of-service" } }, { "id": "Encounter.reasonCode.coding.system", "path": "Encounter.reasonCode.coding.system", "binding": { "strength": "preferred", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/reason-of-service" } }, { "id": "Encounter.reasonCode.coding.version", "path": "Encounter.reasonCode.coding.version", "max": "0" }, { "id": "Encounter.reasonCode.coding.code", "path": "Encounter.reasonCode.coding.code", "binding": { "strength": "preferred", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/reason-of-service" } }, { "id": "Encounter.reasonCode.coding.display", "path": "Encounter.reasonCode.coding.display", "max": "0" }, { "id": "Encounter.reasonCode.coding.userSelected", "path": "Encounter.reasonCode.coding.userSelected", "max": "0" }, { "id": "Encounter.reasonCode.text", "path": "Encounter.reasonCode.text", "max": "0" }, { "id": "Encounter.reasonReference", "path": "Encounter.reasonReference", "short": "Motivo do encontro (referência)", "definition": "A razão pela qual o encontro ocorre, expressa em um código. Para admissões, isso pode ser usado para um diagnóstico de admissão codificado.", "comment": "Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal)." }, { "id": "Encounter.reasonReference.reference", "path": "Encounter.reasonReference.reference", "short": "Referência literal, URL relativa, interna ou absolutaL", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Encounter.reasonReference.type", "path": "Encounter.reasonReference.type", "max": "0" }, { "id": "Encounter.reasonReference.identifier", "path": "Encounter.reasonReference.identifier", "max": "0" }, { "id": "Encounter.reasonReference.display", "path": "Encounter.reasonReference.display", "max": "0" }, { "id": "Encounter.diagnosis", "path": "Encounter.diagnosis", "short": "A lista de diagnósticos relevantes para este encontro", "definition": "A lista de diagnósticos relevantes para este encontro" }, { "id": "Encounter.diagnosis.condition", "path": "Encounter.diagnosis.condition", "short": "O diagnóstico ou procedimento relevante para o encontro", "definition": "Motivo pelo qual o encontro ocorre, conforme especificado usando informações de outro recurso. Para admissões, este é o diagnóstico de admissão. A indicação normalmente será uma Condição (com outros recursos referenciados em evidências.detalhes) ou um Procedimento.", "comment": "Para sistemas que precisam saber qual foi o diagnóstico principal, eles serão marcados com a extensão padrão PrimaryDiagnosis (que é um valor de sequência em vez de um sinalizador, 1 = diagnóstico principal)." }, { "id": "Encounter.diagnosis.condition.reference", "path": "Encounter.diagnosis.condition.reference", "max": "0" }, { "id": "Encounter.diagnosis.condition.type", "path": "Encounter.diagnosis.condition.type", "max": "0" }, { "id": "Encounter.diagnosis.condition.identifier", "path": "Encounter.diagnosis.condition.identifier", "max": "0" }, { "id": "Encounter.diagnosis.condition.display", "path": "Encounter.diagnosis.condition.display", "max": "0" }, { "id": "Encounter.diagnosis.use", "path": "Encounter.diagnosis.use", "max": "0" }, { "id": "Encounter.diagnosis.rank", "path": "Encounter.diagnosis.rank", "max": "0" }, { "id": "Encounter.account", "path": "Encounter.account", "max": "0" }, { "id": "Encounter.hospitalization", "path": "Encounter.hospitalization", "max": "0" }, { "id": "Encounter.location", "path": "Encounter.location", "short": "Lista de locais onde o paciente esteve", "definition": "Lista de locais onde o paciente esteve durante este encontro.", "comment": "Encontros virtuais podem ser registrados no Encontro especificando uma referência de local para um local do tipo \"tipo\", como \"casa do cliente\" e um encontro.class = \"virtual\"." }, { "id": "Encounter.location.location", "path": "Encounter.location.location", "short": "Local onde o encontro acontece", "definition": "O local onde ocorre o encontro.", "comment": "As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local.", "fixedReference": { "reference": "https://www.samisaude.com.br/fhir/r4/CodeSystem/place-of-service", "type": "CodeSystem" } }, { "id": "Encounter.location.location.reference", "path": "Encounter.location.location.reference", "short": "Referência literal, URL relativa, interna ou absoluta", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos.", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful.", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/place-of-service" } }, { "id": "Encounter.location.location.type", "path": "Encounter.location.location.type", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "binding": { "strength": "extensible", "description": "Um recurso (ou, para modelos lógicos, o URI do modelo lógico).", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/place-of-service-type" } }, { "id": "Encounter.location.location.identifier", "path": "Encounter.location.location.identifier", "max": "0" }, { "id": "Encounter.location.location.display", "path": "Encounter.location.location.display", "max": "0" }, { "id": "Encounter.location.status", "path": "Encounter.location.status", "max": "0" }, { "id": "Encounter.location.physicalType", "path": "Encounter.location.physicalType", "short": "O tipo físico da localização (geralmente o nível na hierarquia de localização - enfermaria, quarto, etc.)", "definition": "Isso será usado para especificar os níveis necessários (cama / enfermaria / quarto / etc.) Que deseja gravar para simplificar o envio de mensagens ou consulta.", "comment": "Essas informações são desnormalizadas a partir do recurso Local para oferecer suporte a uma compreensão mais fácil do recurso de encontro e processamento em mensagens ou consultas.\n\nPode haver muitos níveis na hierarquia, e isso pode representar apenas níveis específicos que são necessários para um cenário de uso específico.", "binding": { "strength": "extensible", "description": "Forma física do local.", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/accomodation-type" } }, { "id": "Encounter.location.physicalType.coding", "path": "Encounter.location.physicalType.coding", "short": "Código definido por um sistema de terminologia", "definition": "Uma referência a um código definido por um sistema de terminologia.", "comment": "Os códigos podem ser definidos casualmente em enumerações, ou listas de códigos, até definições muito formais, como SNOMED CT - consulte os Princípios Básicos do HL7 v3 para obter mais informações. A ordem das codificações é indefinida e NÃO DEVE ser usada para inferir significado. Geralmente, no máximo apenas um dos valores de codificação será rotulado como UserSelected = true.", "requirements": "Permite codificações alternativas dentro de um sistema de código e traduções para outros sistemas de código.", "binding": { "strength": "example", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/accomodation-type" } }, { "id": "Encounter.location.physicalType.coding.system", "path": "Encounter.location.physicalType.coding.system", "short": "Identidade do sistema de terminologia", "definition": "A identificação do sistema de código que define o significado do símbolo no código.", "comment": "O URI pode ser um OID (urn: oid: ...) ou um UUID (urn: uuid: ...). OIDs e UUIDs DEVEM ser referências ao registro HL7 OID. Caso contrário, o URI deve vir da lista do HL7 de URIs especiais definidos pelo FHIR ou deve fazer referência a alguma definição que estabeleça o sistema de forma clara e inequívoca.", "requirements": "Precisa ser inequívoco sobre a origem da definição do símbolo.", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/accomodation-type" } }, { "id": "Encounter.location.physicalType.coding.version", "path": "Encounter.location.physicalType.coding.version", "max": "0" }, { "id": "Encounter.location.physicalType.coding.code", "path": "Encounter.location.physicalType.coding.code", "short": "Símbolo na sintaxe definida pelo sistema", "definition": "Um símbolo na sintaxe definida pelo sistema. O símbolo pode ser um código predefinido ou uma expressão em uma sintaxe definida pelo sistema de codificação (por exemplo, pós-coordenação).", "binding": { "strength": "extensible", "valueSet": "https://www.samisaude.com.br/fhir/r4/CodeSystem/accomodation-type" } }, { "id": "Encounter.location.physicalType.coding.display", "path": "Encounter.location.physicalType.coding.display", "max": "0" }, { "id": "Encounter.location.physicalType.coding.userSelected", "path": "Encounter.location.physicalType.coding.userSelected", "max": "0" }, { "id": "Encounter.location.physicalType.text", "path": "Encounter.location.physicalType.text", "max": "0" }, { "id": "Encounter.location.period", "path": "Encounter.location.period", "max": "0" }, { "id": "Encounter.serviceProvider", "path": "Encounter.serviceProvider", "short": "A organização (instalação) responsável por este encontro", "definition": "A organização principal responsável pelos serviços deste Encontro. PODE ser o mesmo que a organização no prontuário do paciente, porém pode ser diferente, como se o ator que realiza os serviços fosse de uma organização externa (que pode ser faturada separadamente) para uma consulta externa. Consulte o pacote de exemplo que mostra um conjunto abreviado de Encontros para uma colonoscopia.", "comment": "As referências DEVEM ser uma referência a um recurso FHIR real e DEVEM ser resolvidas (permitindo o controle de acesso, indisponibilidade temporária, etc.). A resolução pode ser recuperada da URL ou, quando aplicável por tipo de recurso, tratando uma referência absoluta como uma URL canônica e procurando-a em um registro / repositório local." }, { "id": "Encounter.serviceProvider.reference", "path": "Encounter.serviceProvider.reference", "short": "HealthcareService", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos..", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful.." }, { "id": "Encounter.serviceProvider.type", "path": "Encounter.serviceProvider.type", "short": "HealthcareService", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Encounter.serviceProvider.identifier", "path": "Encounter.serviceProvider.identifier", "max": "0" }, { "id": "Encounter.serviceProvider.display", "path": "Encounter.serviceProvider.display", "max": "0" }, { "id": "Encounter.partOf", "path": "Encounter.partOf", "short": "Outro Encontro do qual este encontro faz parte", "definition": "Outro Encontro do qual este encontro faz parte (administrativamente ou no tempo).", "comment": "Isso também é usado para associar o encontro de uma criança ao encontro da mãe.\n\nConsulte a seção Notas no recurso Paciente para obter mais detalhes." }, { "id": "Encounter.partOf.reference", "path": "Encounter.partOf.reference", "short": "Encounter", "definition": "Uma referência a um local onde o outro recurso é encontrado. A referência pode ser uma referência relativa, caso em que é relativa ao URL base do serviço, ou um URL absoluto que resolve para o local onde o recurso é encontrado. A referência pode ser específica da versão ou não. Se a referência não for para um servidor FHIR RESTful, deve-se considerar que é específico da versão. As referências de fragmento interno (começam com '#') referem-se aos recursos contidos..", "comment": "O uso de URLs absolutos fornece uma abordagem escalonável estável adequada para um contexto de nuvem / web, enquanto o uso de referências relativas / lógicas fornece uma abordagem flexível adequada para uso ao negociar através de fronteiras fechadas de ecossistema. Os URLs absolutos não precisam apontar para um servidor FHIR RESTful, embora essa seja a abordagem preferencial. Se a URL estiver de acordo com a estrutura \"/ [type] / [id]\", deve-se assumir que a referência é a um servidor FHIR RESTful." }, { "id": "Encounter.partOf.type", "path": "Encounter.partOf.type", "short": "Encounter", "definition": "O tipo esperado de destino da referência. Se Reference.type e Reference.reference são preenchidos e Reference.reference é um URL FHIR, ambos DEVEM ser consistentes.\n\nO tipo é o URL canônico da definição de recurso, ao qual esta referência se refere. As referências são URLs relativos a http://hl7.org/fhir/StructureDefinition/, por exemplo \"Paciente\" é uma referência a http://hl7.org/fhir/StructureDefinition/Patient. URLs absolutos são permitidos apenas para modelos lógicos (e só podem ser usados em referências em modelos lógicos, não em recursos).", "comment": "Este elemento é usado para indicar o tipo de destino da referência. Isso pode ser usado qualquer um dos outros elementos são preenchidos (ou não). Em alguns casos, o tipo de alvo pode ser determinado pela inspeção da referência (por exemplo, um URL RESTful) ou resolvendo o alvo da referência; se o tipo e uma referência forem fornecidos, a referência DEVERÁ resolver para um recurso do mesmo tipo que o especificado." }, { "id": "Encounter.partOf.identifier", "path": "Encounter.partOf.identifier", "max": "0" }, { "id": "Encounter.partOf.display", "path": "Encounter.partOf.display", "max": "0" } ] } }