Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4B in FHIR STU3 - Downloaded Version null See the Directory of published versions

ConceptMap: R4BAppointmentResponseElementMapToR3

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-AppointmentResponse-element-map-to-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4BAppointmentResponseElementMapToR3

This ConceptMap represents cross-version mappings for elements from a FHIR R4B AppointmentResponse to FHIR STU3.

Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/AppointmentResponse|4.3.0 to http://hl7.org/fhir/StructureDefinition/AppointmentResponse|3.0.2

Source CodeRelationshipTarget CodeComment
AppointmentResponse.meta (meta)maps to wider conceptAppointmentResponse.metaElement `AppointmentResponse.meta` is mapped to FHIR STU3 element `AppointmentResponse.meta` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.meta` do not cover the following types: Meta. The mappings for `AppointmentResponse.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.
AppointmentResponse.implicitRules (implicitRules)is equivalent toAppointmentResponse.implicitRulesElement `AppointmentResponse.implicitRules` is mapped to FHIR STU3 element `AppointmentResponse.implicitRules` as `Equivalent`. 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.
AppointmentResponse.language (language)is equivalent toAppointmentResponse.languageElement `AppointmentResponse.language` is mapped to FHIR STU3 element `AppointmentResponse.language` as `Equivalent`. 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).
AppointmentResponse.text (text)maps to wider conceptAppointmentResponse.textElement `AppointmentResponse.text` is mapped to FHIR STU3 element `AppointmentResponse.text` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.text` do not cover the following types: Narrative. The mappings for `AppointmentResponse.text` do not cover the following types based on type expansion: div, status. 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.
AppointmentResponse.contained (contained)is equivalent toAppointmentResponse.containedElement `AppointmentResponse.contained` is mapped to FHIR STU3 element `AppointmentResponse.contained` as `SourceIsBroaderThanTarget`. 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.
AppointmentResponse.identifier (identifier)maps to wider conceptAppointmentResponse.identifierElement `AppointmentResponse.identifier` is mapped to FHIR STU3 element `AppointmentResponse.identifier` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.identifier` do not cover the following types: Identifier. The mappings for `AppointmentResponse.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
AppointmentResponse.appointment (appointment)maps to wider conceptAppointmentResponse.appointmentElement `AppointmentResponse.appointment` is mapped to FHIR STU3 element `AppointmentResponse.appointment` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.appointment` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `AppointmentResponse.appointment` with unmapped reference targets: Appointment.
AppointmentResponse.start (start)is equivalent toAppointmentResponse.startElement `AppointmentResponse.start` is mapped to FHIR STU3 element `AppointmentResponse.start` as `Equivalent`. This may be either the same as the appointment request to confirm the details of the appointment, or alternately a new time to request a re-negotiation of the start time.
AppointmentResponse.end (end)is equivalent toAppointmentResponse.endElement `AppointmentResponse.end` is mapped to FHIR STU3 element `AppointmentResponse.end` as `Equivalent`.
AppointmentResponse.participantType (participantType)is equivalent toAppointmentResponse.participantTypeElement `AppointmentResponse.participantType` is mapped to FHIR STU3 element `AppointmentResponse.participantType` as `Equivalent`. The role of the participant can be used to declare what the actor will be doing in the scope of the referenced appointment. If the actor is not specified, then it is expected that the actor will be filled in at a later stage of planning. This value SHALL be the same as specified on the referenced Appointment so that they can be matched, and subsequently updated.
AppointmentResponse.actor (actor)maps to wider conceptAppointmentResponse.actorElement `AppointmentResponse.actor` is mapped to FHIR STU3 element `AppointmentResponse.actor` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `AppointmentResponse.actor` with unmapped reference targets: Device, HealthcareService, Location, Patient, Practitioner, PractitionerRole, RelatedPerson.
AppointmentResponse.participantStatus (participantStatus)is equivalent toAppointmentResponse.participantStatusElement `AppointmentResponse.participantStatus` is mapped to FHIR STU3 element `AppointmentResponse.participantStatus` as `Equivalent`. This element is labeled as a modifier because the status contains the code entered-in-error that marks the participant as not currently valid.
AppointmentResponse.comment (comment)is equivalent toAppointmentResponse.commentElement `AppointmentResponse.comment` is mapped to FHIR STU3 element `AppointmentResponse.comment` as `Equivalent`. This comment is particularly important when the responder is declining, tentatively accepting or requesting another time to indicate the reasons why.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/AppointmentResponse|4.3.0 to R4B: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AppointmentResponse.meta (meta)is equivalent toExtension (R4B: meta additional types)Element `AppointmentResponse.meta` is mapped to FHIR STU3 element `AppointmentResponse.meta` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.meta` do not cover the following types: Meta. The mappings for `AppointmentResponse.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/AppointmentResponse|4.3.0 to R4B: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AppointmentResponse.text (text)is equivalent toExtension (R4B: text additional types)Element `AppointmentResponse.text` is mapped to FHIR STU3 element `AppointmentResponse.text` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.text` do not cover the following types: Narrative. The mappings for `AppointmentResponse.text` do not cover the following types based on type expansion: div, status. 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/AppointmentResponse|4.3.0 to R4B: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AppointmentResponse.identifier (identifier)is equivalent toExtension (R4B: identifier additional types)Element `AppointmentResponse.identifier` is mapped to FHIR STU3 element `AppointmentResponse.identifier` as `SourceIsBroaderThanTarget`. The mappings for `AppointmentResponse.identifier` do not cover the following types: Identifier. The mappings for `AppointmentResponse.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.