This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0-ballot: R5 Ballot - Mixed Normative and STU see ballot notes ) in it's permanent home (it will always be available at this URL). ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

Extension-iso21090-adxp-deliverymode.xml

FHIR Infrastructure Work Group

Maturity Level : N/A

Standards Status : Informative

Raw XML ( canonical form + also see XML Format Specification ) ADXP-deliveryMode <?xml version="1.0" encoding="UTF-8"?> Indicates the type of service offered, method of delivery. For example: post office box, rural route, general delivery, etc. Indicates the type of service offered, method of delivery. For example: post office box, rural route, general delivery, etc. Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. 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. Value of extension - must be one of a constrained set of the data types (see [Extensibility](http:// hl7.org/fhir/extensibility.html) for a list). Indicates the type of service offered, method of delivery. For example: post office box, rural route, general delivery, etc.

</ StructureDefinition 2.1.13 > Transforms between R4 and R5

Usage note: every effort Note to Balloters: The R4 / R5 version comparison information is updated prior to publication of the final copy of R5. At this point in time (ballot) it has not been made updated. Ballot comments concerning this information are welcome to ensure identify issues, but will not be counted as negative.

In addition to a list of all differences between R4 and R5 , this specification also provides transforms between R4 and R5 for most resources that the examples were in R5. These transforms are correct expressed using the FHIR Mapping Language , and useful, but both serve as formal documentation of the relationship between the resource structures in R4 and R5, and can also be used to convert between the formats automatically.

The following table summarizes the state of the R5:R5 maps for each resource type.

Note the following:

• Transforms are tested using the following method:
  1. For each example resource in the R4 release of the FHIR specification that has a transform to R5
  2. apply the transform to R5
  3. validate against the R5 specification
  4. apply the reverse transform back to R4
  5. compare the outcome with the original resource - ideally, it should be identical
• All transforms should execute - that is, they should be able to take any R4 resource, represent the content in R5, and then generate an R4 representation for the same content. Note, though, that in a few cases, the differences between R4 and R5 designs are so significant that not all examples can be successfully transformed at all.
• For some resources, the differences in design between R4 and R5 are sufficiently great that the R4 examples cannot reproduce the same output after conversion to R5 and then back to R4. For example, the R5 resource may have a normative part different set of status codes with imperfect maps
• For some resources, the specification. information available in the R4 examples is not enough to generate valid R5 resources, and so the resources generate R5 validation errors. (e.g. R4 resources missing an element that is required in R5)
• The transform scripts are only tested to the degree that R4 provided example data
• For all these reasons, the maps provided in the specification are not authoritative; they are provided to help implementers who need to convert between the R2 and R4 format, but additional revision may be required in an implementation specific context
• The maps are subject to ongoing maintenance using the FHIR NPM Package " fhir.versions.r3r4 " which is maintained on GitHub . See also FHIR Wiki for other ongoing work to support R4/R5 transformations

Resource	# Tests	% Execute OK	% RoundTrip Ok	% R5 Valid	R5 Error Count
Account	2	100	0	100
ActivityDefinition	9	100	77	0
ActorDefinition	No r3:r4 maps available
AdministrableProductDefinition	No r3:r4 maps available
AdverseEvent	1	100	0	0
AllergyIntolerance	3	100	100	100
Appointment	3	100	100	100
AppointmentResponse	2	100	100	100
ArtifactAssessment	No r3:r4 maps available
AuditEvent	8	100	100	100
Basic	3	100	100	100
Binary	2	100	100	100
BiologicallyDerivedProduct	No r3:r4 maps available
BodyStructure	3	100	100	100
Bundle	28	89	88	36
CapabilityStatement	9	100	88	0
CarePlan	11	100	100	9
CareTeam	1	100	100	0
ChargeItem	1	100	100	100
ChargeItemDefinition	No r3:r4 maps available
Citation	No r3:r4 maps available
Claim	16	81	0	76
ClaimResponse	1	100	0	0
ClinicalImpression	1	100	100	100
ClinicalUseDefinition	No r3:r4 maps available
CodeSystem	4	100	100	25
Communication	3	100	100	33
CommunicationRequest	2	100	100	50
CompartmentDefinition	6	100	83	16
Composition	1	100	100	100
ConceptMap	4	100	100	0
Condition	12	100	100	91
ConditionDefinition	No r3:r4 maps available
Consent	12	100	100	0
Contract	7	28	50	-150
Coverage	4	100	75	100
CoverageEligibilityRequest	No r3:r4 maps available
CoverageEligibilityResponse	No r3:r4 maps available
DetectedIssue	4	100	100	100
Device	9	100	100	88
DeviceDefinition	No r3:r4 maps available
DeviceDispense	No r3:r4 maps available
DeviceMetric	1	100	100	100
DeviceRequest	2	100	0	50
DeviceUsage	No r3:r4 maps available
DiagnosticReport	14	100	100	35
DocumentManifest	2	0	0	0
DocumentReference	1	0	0	0
Encounter	10	100	100	70
Endpoint	3	100	100	100
EnrollmentRequest	1	100	0	100
EnrollmentResponse	1	100	100	100
EpisodeOfCare	1	100	100	100
EventDefinition	No r3:r4 maps available
Evidence	No r3:r4 maps available
EvidenceReport	No r3:r4 maps available
EvidenceVariable	No r3:r4 maps available
ExampleScenario	No r3:r4 maps available
ExplanationOfBenefit	1	100	0	0
FamilyMemberHistory	2	100	100	50
Flag	2	100	100	100
FormularyItem	No r3:r4 maps available
GenomicStudy	No r3:r4 maps available
Goal	2	100	100	100
GraphDefinition	1	100	100	0
Group	2	100	100	100
GuidanceResponse	1	100	100	100
HealthcareService	1	100	100	0
ImagingSelection	No r3:r4 maps available
ImagingStudy	2	100	50	0
Immunization	3	100	100	0
ImmunizationEvaluation	No r3:r4 maps available
ImmunizationRecommendation	1	100	100	100
ImplementationGuide	1	100	100	0
Ingredient	No r3:r4 maps available
InsurancePlan	No r3:r4 maps available
InventoryReport	No r3:r4 maps available
Invoice	No r3:r4 maps available
Library	11	100	100	0
Linkage	1	100	100	100
List	9	100	100	44
Location	6	100	100	83
ManufacturedItemDefinition	No r3:r4 maps available
Measure	6	100	100	0
MeasureReport	3	100	100	0
Medication	23	100	4	4
MedicationAdministration	14	100	71	0
MedicationDispense	31	100	80	0
MedicationKnowledge	No r3:r4 maps available
MedicationRequest	36	100	77	0
MedicationUsage	No r3:r4 maps available
MedicinalProductDefinition	No r3:r4 maps available
MessageDefinition	3	100	100	33
MessageHeader	1	100	100	0
MolecularSequence	14	100	100	100
NamingSystem	3	100	66	0
NutritionIntake	No r3:r4 maps available
NutritionOrder	13	100	100	0
NutritionProduct	No r3:r4 maps available
Observation	48	100	100	52
ObservationDefinition	No r3:r4 maps available
OperationDefinition	37	100	100	8
OperationOutcome	6	100	100	100
Organization	11	100	100	90
OrganizationAffiliation	No r3:r4 maps available
PackagedProductDefinition	No r3:r4 maps available
Patient	16	100	100	100
PaymentNotice	1	100	0	0
PaymentReconciliation	1	100	0	0
Permission	No r3:r4 maps available
Person	5	100	100	100
PlanDefinition	11	45	100	0
Practitioner	14	100	100	100
PractitionerRole	1	100	100	100
Procedure	15	100	80	93
Provenance	5	100	100	60
Questionnaire	6	100	100	16
QuestionnaireResponse	5	100	80	0
RegulatedAuthorization	No r3:r4 maps available
RelatedPerson	4	100	100	100
RequestOrchestration	No r3:r4 maps available
Requirements	No r3:r4 maps available
ResearchStudy	1	100	100	100
ResearchSubject	1	100	100	100
RiskAssessment	4	100	100	25
Schedule	3	100	100	100
SearchParameter	3	100	100	0
ServiceRequest	No r3:r4 maps available
Slot	4	100	100	100
Specimen	4	100	100	50
SpecimenDefinition	No r3:r4 maps available
StructureDefinition	206	100	98	0
StructureMap	2	100	100	50
Subscription	2	100	0	100
SubscriptionStatus	No r3:r4 maps available
SubscriptionTopic	No r3:r4 maps available
Substance	6	100	100	83
SubstanceDefinition	No r3:r4 maps available
SubstanceNucleicAcid	No r3:r4 maps available
SubstancePolymer	No r3:r4 maps available
SubstanceProtein	No r3:r4 maps available
SubstanceReferenceInformation	No r3:r4 maps available
SubstanceSourceMaterial	No r3:r4 maps available
SupplyDelivery	2	100	100	100
SupplyRequest	1	100	100	0
Task	6	100	50	83
TerminologyCapabilities	No r3:r4 maps available
TestReport	1	100	100	100
TestScript	7	100	85	0
Transport	No r3:r4 maps available
ValueSet	8	100	100	0
VerificationResult	No r3:r4 maps available
VisionPrescription	2	100	50	0