Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3

2.1.28.6.0 2.1.27.5.0 MetaDatatypes

Maturity Level : 4
Modeling and Methodology Responsible Owner: FHIR Infrastructure icon Work Group Standards Status : Partially Normative

Types Framework Cross Reference: Base Types | Datatypes | Resources | Patterns

This page describes a set of types used for conveying metadata about knowledge resources (mainly for Terminology , Conformance and Clinical Definition resources).

Table of Contents

ContactDetail DataRequirement ParameterDefinition RelatedArtifact
TriggerDefinition Expression UsageContext ExtendedContactDetail
VirtualServiceDetail Availability MonetaryComponent

For an index of all datatypes, see the Datatypes page .

2.1.28.6.0.1 2.1.27.5.0.1 ContactDetail

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Normative

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The ContactDetail structure defines general contact details.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ContactDetail Σ N Element Contact information

Elements defined in Ancestors: id , extension
. . . name Σ 0..1 string Name of an individual to contact
. . . telecom Σ 0..* ContactPoint Contact details for individual or organization


doco Documentation for this format icon

Definition: XML | JSON

XML Template 

<ContactDetail xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <name value="[string]"/><!-- 0..1 Name of an individual to contact -->
 <telecom><!-- 0..* ContactPoint Contact details for individual or organization --></telecom>
</ContactDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:name [ string ] ; # 0..1 Name of an individual to contact
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* Contact details for individual or organization
]

Changes since Release 3

Changes from both R4 and R4B

ContactDetail
  • No Changes

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ContactDetail Σ N Element Contact information

Elements defined in Ancestors: id , extension
. . . name Σ 0..1 string Name of an individual to contact
. . . telecom Σ 0..* ContactPoint Contact details for individual or organization


doco Documentation for this format icon

XML Template 

<ContactDetail xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <name value="[string]"/><!-- 0..1 Name of an individual to contact -->
 <telecom><!-- 0..* ContactPoint Contact details for individual or organization --></telecom>
</ContactDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:name [ string ] ; # 0..1 Name of an individual to contact
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* Contact details for individual or organization
]

Changes since Release 3

Changes from both R4 and R4B

ContactDetail
  • No Changes

See the Full Difference for further information

Constraints

ContactDetail is used in the following places: Contributor , ActivityDefinition , ActorDefinition , CanonicalResource , CapabilityStatement , ChargeItemDefinition , Citation , CodeSystem , CompartmentDefinition , ConceptMap , ConditionDefinition , DeviceDefinition , EventDefinition , Evidence , EvidenceReport , EvidenceVariable , ExampleScenario , GraphDefinition FormularyItem , Group , ImplementationGuide , Library , Measure , MedicationKnowledge , MessageDefinition , MetadataResource , NamingSystem , ObservationDefinition , OperationDefinition , Parameters , PlanDefinition , Questionnaire , Requirements , SearchParameter , SpecimenDefinition , StructureDefinition , StructureMap , SubscriptionTopic , Task , TerminologyCapabilities , TestPlan , TestScript and ValueSet

2.1.28.6.0.2 2.1.27.5.0.2 DataRequirement

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The DataRequirement structure defines a general data requirement for a knowledge asset such as a decision support rule or quality measure.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . DataRequirement Σ TU N Element Describes a required data item

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code The type of the required data
Binding: All FHIR Types ( Required )
. . . profile Σ 0..* canonical ( StructureDefinition ) The profile of the required data

. . . subject[x] Σ 0..1 E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device
Binding: Participant Resource Types ( Extensible )
. . . . subjectCodeableConcept CodeableConcept
. . . . subjectReference Reference ( Group )
. . . codeFilter Σ C 0..* Element What codes are expected
+ Rule: Either a path or a searchParam must be provided, but not both

. . . . path Σ C 0..1 string A code-valued attribute to filter on
. . . . searchParam Σ C 0..1 string A coded (token) parameter to search on
. . . . valueSet Σ 0..1 canonical ( ValueSet ) ValueSet for the filter
. . . . code Σ 0..* Coding What code is expected

. . . dateFilter Σ C 0..* Element What dates/date ranges are expected
+ Rule: Either a path or a searchParam must be provided, but not both

. . . . path Σ C 0..1 string A date-valued attribute to filter on
. . . . searchParam Σ C 0..1 string A date valued parameter to search on
. . . . value[x] Σ 0..1 The value of the filter, as a Period, DateTime, or Duration value
. . . . . valueDateTime dateTime
. . . . . valuePeriod Period
. . . . . valueDuration Duration
. . . valueFilter Σ 0..* Element What values are expected

. . . . path Σ 0..1 string An attribute to filter on
. . . . searchParam Σ 0..1 string A parameter to search on
. . . . comparator Σ 0..1 code eq | gt | lt | ge | le | sa | eb
Binding: Value Filter Comparator ( Required )
. . . . value[x] Σ 0..1 The value of the filter, as a Period, DateTime, or Duration value
. . . . . valueDateTime dateTime
. . . . . valuePeriod Period
. . . . . valueDuration Duration
. . . limit Σ 0..1 positiveInt Number of results
. . . sort Σ 0..* Element Order of the results

. . . . path Σ 1..1 string The name of the attribute to perform the sort
. . . . direction Σ 1..1 code ascending | descending
Binding: SortDirection ( Required )

doco Documentation for this format icon

Definition: XML | JSON

UML Diagram ( Legend )

DataRequirement The type of the required data, specified as the type name of a resource. For profiles, this value is set to the type of the base resource of the profile type : code [1..1] « List of FHIR types (resources, data types). (Strength=Required) FHIRTypes ! » The profile of the required data, specified as the uri of the profile definition profile : canonical [0..*] « StructureDefinition » The intended subjects of the data requirement. If this element is not provided, a Patient subject is assumed subject[x] : DataType [0..1] « CodeableConcept | Reference ( Group ); The possible types of subjects for a data requirement (E.g., Patient, Practitioner, Organization, Location, etc.). (Strength=Extensible) ParticipantResourceTypes + » Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. The value of mustSupport SHALL be a FHIRPath resolvable on the type of the DataRequirement. The path SHALL consist only of identifiers, constant indexers, and .resolve() (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details) mustSupport : string [0..*] Specifies a maximum number of results that are required (uses the _count search parameter) limit : positiveInt [0..1] CodeFilter The code-valued attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type code, Coding, or CodeableConcept path : string [0..1] « This element has or is affected by some invariants C » A token parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type code, Coding, or CodeableConcept searchParam : string [0..1] « This element has or is affected by some invariants C » The valueset for the code filter. The valueSet and code elements are additive. If valueSet is specified, the filter will return only those data items for which the value of the code-valued element specified in the path is a member of the specified valueset valueSet : canonical [0..1] « ValueSet » The codes for the code filter. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified codes. If codes are specified in addition to a value set, the filter returns items matching a code in the value set or one of the specified codes code : Coding [0..*] DateFilter The date-valued attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type date, dateTime, Period, Schedule, or Timing path : string [0..1] « This element has or is affected by some invariants C » A date parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type date, dateTime, Period, Schedule, or Timing searchParam : string [0..1] « This element has or is affected by some invariants C » The value of the filter. If period is specified, the filter will return only those data items that fall within the bounds determined by the Period, inclusive of the period boundaries. If dateTime is specified, the filter will return only those data items that are equal to the specified dateTime. If a Duration is specified, the filter will return only those data items that fall within Duration before now value[x] : DataType [0..1] « dateTime | Period | Duration » ValueFilter The attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of a type that is comparable to the valueFilter.value[x] element for the filter path : string [0..1] A search parameter defined on the specified type of the DataRequirement, and which searches on elements of a type compatible with the type of the valueFilter.value[x] for the filter searchParam : string [0..1] The comparator to be used to determine whether the value is matching comparator : code [0..1] « Possible comparators for the valueFilter element. (Strength=Required) ValueFilterComparator ! » The value of the filter value[x] : DataType [0..1] « dateTime | Period | Duration » Sort The attribute of the sort. The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer constant path : string [1..1] The direction of the sort, ascending or descending direction : code [1..1] « The possible sort directions, ascending or descending. (Strength=Required) SortDirection ! » DataType Code filters specify additional constraints on the data, specifying the value set of interest for a particular element of the data. Each code filter defines an additional constraint on the data, i.e. code filters are AND'ed, not OR'ed codeFilter [0..*] Date filters specify additional constraints on the data in terms of the applicable date range for specific elements. Each date filter specifies an additional constraint on the data, i.e. date filters are AND'ed, not OR'ed dateFilter [0..*] Value filters specify additional constraints on the data for elements other than code-valued or date-valued. Each value filter specifies an additional constraint on the data (i.e. valueFilters are AND'ed, not OR'ed) valueFilter [0..*] Specifies the order of the results to be returned sort [0..*]

XML Template 

<DataRequirement xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <type value="[code]"/><!-- 1..1 The type of the required data -->
 <profile><!-- 0..* canonical(StructureDefinition) The profile of the required data --></profile>
 <subject[x]><!-- 0..1 CodeableConcept|Reference(Group) E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device --></subject[x]>
 <<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


 <mustSupport value="[string]"/><!-- 0..* Indicates specific structure elements that are referenced by the knowledge module -->
 <codeFilter>  <!-- 0..* What codes are expected -->
  <path value="[string]"/><!-- I 0..1 A code-valued attribute to filter on -->
  <searchParam value="[string]"/><!-- I 0..1 A coded (token) parameter to search on -->
  <valueSet><!-- 0..1 canonical(ValueSet) ValueSet for the filter --></valueSet>
  <code><!-- 0..* Coding What code is expected --></code>
 </codeFilter>
 <dateFilter>  <!-- 0..* What dates/date ranges are expected -->
  <path value="[string]"/><!-- I 0..1 A date-valued attribute to filter on -->
  <searchParam value="[string]"/><!-- I 0..1 A date valued parameter to search on -->
  <value[x]><!-- 0..1 dateTime|Period|Duration The value of the filter, as a Period, DateTime, or Duration value --></value[x]>
 </dateFilter>
 <valueFilter>  <!-- 0..* What values are expected -->
  <path value="[string]"/><!-- 0..1 An attribute to filter on -->
  <searchParam value="[string]"/><!-- 0..1 A parameter to search on -->
  <comparator value="[code]"/><!-- 0..1 eq | gt | lt | ge | le | sa | eb -->
  <value[x]><!-- 0..1 dateTime|Period|Duration The value of the filter, as a Period, DateTime, or Duration value --></value[x]>
 </valueFilter>
 <limit value="[positiveInt]"/><!-- 0..1 Number of results -->
 <sort>  <!-- 0..* Order of the results -->
  <path value="[string]"/><!-- 1..1 The name of the attribute to perform the sort -->
  <direction value="[code]"/><!-- 1..1 ascending | descending -->
 </sort>
</DataRequirement>

JSON Template 

{doco
  // from Element: extension
  "type" : "<code>", // R!  The type of the required data
  "profile" : ["<canonical(StructureDefinition)>"], // The profile of the required data
  // subject[x]: E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device. One of these 2:
  "subjectCodeableConcept" : { CodeableConcept },
  "subjectReference" : { Reference(Group) },
  "<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


  "mustSupport" : ["<string>"], // Indicates specific structure elements that are referenced by the knowledge module
  "codeFilter" : [{ // What codes are expected
    "path" : "<string>", // I A code-valued attribute to filter on
    "searchParam" : "<string>", // I A coded (token) parameter to search on
    "valueSet" : "<canonical(ValueSet)>", // ValueSet for the filter
    "code" : [{ Coding }] // What code is expected
  }],
  "dateFilter" : [{ // What dates/date ranges are expected
    "path" : "<string>", // I A date-valued attribute to filter on
    "searchParam" : "<string>", // I A date valued parameter to search on
    // value[x]: The value of the filter, as a Period, DateTime, or Duration value. One of these 3:
    "valueDateTime" : "<dateTime>",
    "valuePeriod" : { Period },
    "valueDuration" : { Duration }
  }],
  "valueFilter" : [{ // What values are expected
    "path" : "<string>", // An attribute to filter on
    "searchParam" : "<string>", // A parameter to search on
    "comparator" : "<code>", // eq | gt | lt | ge | le | sa | eb
    // value[x]: The value of the filter, as a Period, DateTime, or Duration value. One of these 3:
    "valueDateTime" : "<dateTime>",
    "valuePeriod" : { Period },
    "valueDuration" : { Duration }
  }],
  "limit" : "<positiveInt>", // Number of results
  "sort" : [{ // Order of the results
    "path" : "<string>", // R!  The name of the attribute to perform the sort
    "direction" : "<code>" // R!  ascending | descending
  }]
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:type [ code ] ; # 1..1 The type of the required data
  fhir:profile  ( [ canonical(StructureDefinition) ] ... ) ; # 0..* The profile of the required data
  # subject[x] : 0..1 E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device. One of these 2
    fhir:subject [  a fhir:CodeableConcept ; CodeableConcept ]
    fhir:subject [  a fhir:Reference ; Reference(Group) ]
  fhir:<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


  fhir:mustSupport  ( [ string ] ... ) ; # 0..* Indicates specific structure elements that are referenced by the knowledge module
  fhir:codeFilter ( [ # 0..* What codes are expected
    fhir:path [ string ] ; # 0..1 I A code-valued attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 I A coded (token) parameter to search on
    fhir:valueSet [ canonical(ValueSet) ] ; # 0..1 ValueSet for the filter
    fhir:code  ( [ Coding ] ... ) ; # 0..* What code is expected
  ] ... ) ;
  fhir:dateFilter ( [ # 0..* What dates/date ranges are expected
    fhir:path [ string ] ; # 0..1 I A date-valued attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 I A date valued parameter to search on
    # value[x] : 0..1 The value of the filter, as a Period, DateTime, or Duration value. One of these 3
      fhir: ]

      fhir:value [  a fhir:DateTime ; dateTime ]

      fhir:value [  a fhir:Period ; Period ]
      fhir:value [  a fhir:Duration ; Duration ]
  ] ... ) ;
  fhir:valueFilter ( [ # 0..* What values are expected
    fhir:path [ string ] ; # 0..1 An attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 A parameter to search on
    fhir:comparator [ code ] ; # 0..1 eq | gt | lt | ge | le | sa | eb
    # value[x] : 0..1 The value of the filter, as a Period, DateTime, or Duration value. One of these 3
      fhir: ]

      fhir:value [  a fhir:DateTime ; dateTime ]

      fhir:value [  a fhir:Period ; Period ]
      fhir:value [  a fhir:Duration ; Duration ]
  ] ... ) ;
  fhir:limit [ positiveInt ] ; # 0..1 Number of results
  fhir:sort ( [ # 0..* Order of the results
    fhir:path [ string ] ; # 1..1 The name of the attribute to perform the sort
    fhir:direction [ code ] ; # 1..1 ascending | descending
  ] ... ) ;
]

Changes since Release 3

Changes from both R4 and R4B

DataRequirement
DataRequirement.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types|4.0.0 to All FHIR Types
  • Remove codes Address , Age , Annotation , Attachment , BackboneElement , CodeableConcept , Coding , ContactDetail , ContactPoint , Contributor , Count , DataRequirement , Distance , Dosage , Duration , Element , ElementDefinition , Expression , Extension , HumanName , Identifier , MarketingStatus , Meta , Money , MoneyQuantity , Narrative , ParameterDefinition , Period , Population , ProdCharacteristic , ProductShelfLife , Quantity , Range , Ratio , Reference , RelatedArtifact , SampledData , Signature , SimpleQuantity , SubstanceAmount , Timing , TriggerDefinition , UsageContext , base64Binary , boolean , canonical , code , date , dateTime , decimal , id , instant , integer , markdown , oid , positiveInt , string , time , unsignedInt , uri , url , uuid , xhtml , Account , ActivityDefinition , AdverseEvent , AllergyIntolerance , Appointment , AppointmentResponse , AuditEvent , Basic , Binary , BiologicallyDerivedProduct , BodyStructure , Bundle , CapabilityStatement , CarePlan , CareTeam , CatalogEntry , ChargeItem , ChargeItemDefinition , Claim , ClaimResponse , ClinicalImpression , CodeSystem , Communication , CommunicationRequest , CompartmentDefinition , Composition , ConceptMap , Condition , Consent , Contract , Coverage , CoverageEligibilityRequest , CoverageEligibilityResponse , DetectedIssue , Device , DeviceDefinition , DeviceMetric , DeviceRequest , DeviceUseStatement , DiagnosticReport , DocumentManifest , DocumentReference , DomainResource , EffectEvidenceSynthesis , Encounter , Endpoint , EnrollmentRequest , EnrollmentResponse , EpisodeOfCare , EventDefinition , Evidence , EvidenceVariable , ExampleScenario , ExplanationOfBenefit , FamilyMemberHistory , Flag , Goal , GraphDefinition , Group , GuidanceResponse , HealthcareService , ImagingStudy , Immunization , ImmunizationEvaluation , ImmunizationRecommendation , ImplementationGuide , InsurancePlan , Invoice , Library , Linkage , List , Location , Measure , MeasureReport , Media , Medication , MedicationAdministration , MedicationDispense , MedicationKnowledge , MedicationRequest , MedicationStatement , MedicinalProduct , MedicinalProductAuthorization , MedicinalProductContraindication , MedicinalProductIndication , MedicinalProductIngredient , MedicinalProductInteraction , MedicinalProductManufactured , MedicinalProductPackaged , MedicinalProductPharmaceutical , MedicinalProductUndesirableEffect , RequestGroup MessageDefinition , ResearchDefinition MessageHeader , ResearchElementDefinition MolecularSequence , RiskEvidenceSynthesis NamingSystem , SubstanceSpecification NutritionOrder , Type Observation , Any Add codes ObservationDefinition , Base OperationDefinition , DataType OperationOutcome , Availability Organization , BackboneType OrganizationAffiliation , CodeableReference Parameters , ExtendedContactDetail Patient , MonetaryComponent PaymentNotice , PrimitiveType PaymentReconciliation , integer64 Person , RatioRange PlanDefinition , VirtualServiceDetail Practitioner , ActorDefinition PractitionerRole , AdministrableProductDefinition Procedure , ArtifactAssessment Provenance , BiologicallyDerivedProductDispense Questionnaire , CanonicalResource QuestionnaireResponse , Citation RelatedPerson , ClinicalUseDefinition RequestGroup , ConditionDefinition ResearchDefinition , DeviceAssociation ResearchElementDefinition , DeviceDispense ResearchStudy , DeviceUsage ResearchSubject , EncounterHistory Resource , EvidenceReport RiskAssessment , FormularyItem RiskEvidenceSynthesis , GenomicStudy Schedule , ImagingSelection SearchParameter , Ingredient ServiceRequest , InventoryItem Slot , InventoryReport Specimen , ManufacturedItemDefinition SpecimenDefinition , MedicinalProductDefinition StructureDefinition , MetadataResource StructureMap , NutritionIntake Subscription , NutritionProduct Substance , PackagedProductDefinition SubstanceNucleicAcid , Permission SubstancePolymer , RegulatedAuthorization SubstanceProtein , RequestOrchestration SubstanceReferenceInformation , Requirements SubstanceSourceMaterial , SubscriptionStatus SubstanceSpecification , SubscriptionTopic SupplyDelivery , SubstanceDefinition SupplyRequest , TestPlan Task , Transport TerminologyCapabilities , TestReport , TestScript , ValueSet , VerificationResult , VisionPrescription , Type , Any
  • Add code Base
DataRequirement.subject[x]
  • Change value set from http://hl7.org/fhir/ValueSet/subject-type to Participant Resource Types
  • Change code system for extensibly bound codes from "http://hl7.org/fhir/resource-types" to "http://hl7.org/fhir/fhir-types"
DataRequirement.valueFilter
  • Added Element
DataRequirement.valueFilter.path
  • Added Element
DataRequirement.valueFilter.searchParam
  • Added Element
DataRequirement.valueFilter.comparator
  • Added Element
DataRequirement.valueFilter.value[x]
  • Added Element

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . DataRequirement Σ TU N Element Describes a required data item

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code The type of the required data
Binding: All FHIR Types ( Required )
. . . profile Σ 0..* canonical ( StructureDefinition ) The profile of the required data

. . . subject[x] Σ 0..1 E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device
Binding: Participant Resource Types ( Extensible )
. . . . subjectCodeableConcept CodeableConcept
. . . . subjectReference Reference ( Group )
. . . codeFilter Σ C 0..* Element What codes are expected
+ Rule: Either a path or a searchParam must be provided, but not both

. . . . path Σ C 0..1 string A code-valued attribute to filter on
. . . . searchParam Σ C 0..1 string A coded (token) parameter to search on
. . . . valueSet Σ 0..1 canonical ( ValueSet ) ValueSet for the filter
. . . . code Σ 0..* Coding What code is expected

. . . dateFilter Σ C 0..* Element What dates/date ranges are expected
+ Rule: Either a path or a searchParam must be provided, but not both

. . . . path Σ C 0..1 string A date-valued attribute to filter on
. . . . searchParam Σ C 0..1 string A date valued parameter to search on
. . . . value[x] Σ 0..1 The value of the filter, as a Period, DateTime, or Duration value
. . . . . valueDateTime dateTime
. . . . . valuePeriod Period
. . . . . valueDuration Duration
. . . valueFilter Σ 0..* Element What values are expected

. . . . path Σ 0..1 string An attribute to filter on
. . . . searchParam Σ 0..1 string A parameter to search on
. . . . comparator Σ 0..1 code eq | gt | lt | ge | le | sa | eb
Binding: Value Filter Comparator ( Required )
. . . . value[x] Σ 0..1 The value of the filter, as a Period, DateTime, or Duration value
. . . . . valueDateTime dateTime
. . . . . valuePeriod Period
. . . . . valueDuration Duration
. . . limit Σ 0..1 positiveInt Number of results
. . . sort Σ 0..* Element Order of the results

. . . . path Σ 1..1 string The name of the attribute to perform the sort
. . . . direction Σ 1..1 code ascending | descending
Binding: SortDirection ( Required )

doco Documentation for this format icon

UML Diagram ( Legend )

DataRequirement The type of the required data, specified as the type name of a resource. For profiles, this value is set to the type of the base resource of the profile type : code [1..1] « List of FHIR types (resources, data types). (Strength=Required) FHIRTypes ! » The profile of the required data, specified as the uri of the profile definition profile : canonical [0..*] « StructureDefinition » The intended subjects of the data requirement. If this element is not provided, a Patient subject is assumed subject[x] : DataType [0..1] « CodeableConcept | Reference ( Group ); The possible types of subjects for a data requirement (E.g., Patient, Practitioner, Organization, Location, etc.). (Strength=Extensible) ParticipantResourceTypes + » Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. The value of mustSupport SHALL be a FHIRPath resolvable on the type of the DataRequirement. The path SHALL consist only of identifiers, constant indexers, and .resolve() (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details) mustSupport : string [0..*] Specifies a maximum number of results that are required (uses the _count search parameter) limit : positiveInt [0..1] CodeFilter The code-valued attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type code, Coding, or CodeableConcept path : string [0..1] « This element has or is affected by some invariants C » A token parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type code, Coding, or CodeableConcept searchParam : string [0..1] « This element has or is affected by some invariants C » The valueset for the code filter. The valueSet and code elements are additive. If valueSet is specified, the filter will return only those data items for which the value of the code-valued element specified in the path is a member of the specified valueset valueSet : canonical [0..1] « ValueSet » The codes for the code filter. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified codes. If codes are specified in addition to a value set, the filter returns items matching a code in the value set or one of the specified codes code : Coding [0..*] DateFilter The date-valued attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type date, dateTime, Period, Schedule, or Timing path : string [0..1] « This element has or is affected by some invariants C » A date parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type date, dateTime, Period, Schedule, or Timing searchParam : string [0..1] « This element has or is affected by some invariants C » The value of the filter. If period is specified, the filter will return only those data items that fall within the bounds determined by the Period, inclusive of the period boundaries. If dateTime is specified, the filter will return only those data items that are equal to the specified dateTime. If a Duration is specified, the filter will return only those data items that fall within Duration before now value[x] : DataType [0..1] « dateTime | Period | Duration » ValueFilter The attribute of the filter. The specified path SHALL be a FHIRPath resolvable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of a type that is comparable to the valueFilter.value[x] element for the filter path : string [0..1] A search parameter defined on the specified type of the DataRequirement, and which searches on elements of a type compatible with the type of the valueFilter.value[x] for the filter searchParam : string [0..1] The comparator to be used to determine whether the value is matching comparator : code [0..1] « Possible comparators for the valueFilter element. (Strength=Required) ValueFilterComparator ! » The value of the filter value[x] : DataType [0..1] « dateTime | Period | Duration » Sort The attribute of the sort. The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer constant path : string [1..1] The direction of the sort, ascending or descending direction : code [1..1] « The possible sort directions, ascending or descending. (Strength=Required) SortDirection ! » DataType Code filters specify additional constraints on the data, specifying the value set of interest for a particular element of the data. Each code filter defines an additional constraint on the data, i.e. code filters are AND'ed, not OR'ed codeFilter [0..*] Date filters specify additional constraints on the data in terms of the applicable date range for specific elements. Each date filter specifies an additional constraint on the data, i.e. date filters are AND'ed, not OR'ed dateFilter [0..*] Value filters specify additional constraints on the data for elements other than code-valued or date-valued. Each value filter specifies an additional constraint on the data (i.e. valueFilters are AND'ed, not OR'ed) valueFilter [0..*] Specifies the order of the results to be returned sort [0..*]

XML Template 

<DataRequirement xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <type value="[code]"/><!-- 1..1 The type of the required data -->
 <profile><!-- 0..* canonical(StructureDefinition) The profile of the required data --></profile>
 <subject[x]><!-- 0..1 CodeableConcept|Reference(Group) E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device --></subject[x]>
 <<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


 <mustSupport value="[string]"/><!-- 0..* Indicates specific structure elements that are referenced by the knowledge module -->
 <codeFilter>  <!-- 0..* What codes are expected -->
  <path value="[string]"/><!-- I 0..1 A code-valued attribute to filter on -->
  <searchParam value="[string]"/><!-- I 0..1 A coded (token) parameter to search on -->
  <valueSet><!-- 0..1 canonical(ValueSet) ValueSet for the filter --></valueSet>
  <code><!-- 0..* Coding What code is expected --></code>
 </codeFilter>
 <dateFilter>  <!-- 0..* What dates/date ranges are expected -->
  <path value="[string]"/><!-- I 0..1 A date-valued attribute to filter on -->
  <searchParam value="[string]"/><!-- I 0..1 A date valued parameter to search on -->
  <value[x]><!-- 0..1 dateTime|Period|Duration The value of the filter, as a Period, DateTime, or Duration value --></value[x]>
 </dateFilter>
 <valueFilter>  <!-- 0..* What values are expected -->
  <path value="[string]"/><!-- 0..1 An attribute to filter on -->
  <searchParam value="[string]"/><!-- 0..1 A parameter to search on -->
  <comparator value="[code]"/><!-- 0..1 eq | gt | lt | ge | le | sa | eb -->
  <value[x]><!-- 0..1 dateTime|Period|Duration The value of the filter, as a Period, DateTime, or Duration value --></value[x]>
 </valueFilter>
 <limit value="[positiveInt]"/><!-- 0..1 Number of results -->
 <sort>  <!-- 0..* Order of the results -->
  <path value="[string]"/><!-- 1..1 The name of the attribute to perform the sort -->
  <direction value="[code]"/><!-- 1..1 ascending | descending -->
 </sort>
</DataRequirement>

JSON Template 

{doco
  // from Element: extension
  "type" : "<code>", // R!  The type of the required data
  "profile" : ["<canonical(StructureDefinition)>"], // The profile of the required data
  // subject[x]: E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device. One of these 2:
  "subjectCodeableConcept" : { CodeableConcept },
  "subjectReference" : { Reference(Group) },
  "<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


  "mustSupport" : ["<string>"], // Indicates specific structure elements that are referenced by the knowledge module
  "codeFilter" : [{ // What codes are expected
    "path" : "<string>", // I A code-valued attribute to filter on
    "searchParam" : "<string>", // I A coded (token) parameter to search on
    "valueSet" : "<canonical(ValueSet)>", // ValueSet for the filter
    "code" : [{ Coding }] // What code is expected
  }],
  "dateFilter" : [{ // What dates/date ranges are expected
    "path" : "<string>", // I A date-valued attribute to filter on
    "searchParam" : "<string>", // I A date valued parameter to search on
    // value[x]: The value of the filter, as a Period, DateTime, or Duration value. One of these 3:
    "valueDateTime" : "<dateTime>",
    "valuePeriod" : { Period },
    "valueDuration" : { Duration }
  }],
  "valueFilter" : [{ // What values are expected
    "path" : "<string>", // An attribute to filter on
    "searchParam" : "<string>", // A parameter to search on
    "comparator" : "<code>", // eq | gt | lt | ge | le | sa | eb
    // value[x]: The value of the filter, as a Period, DateTime, or Duration value. One of these 3:
    "valueDateTime" : "<dateTime>",
    "valuePeriod" : { Period },
    "valueDuration" : { Duration }
  }],
  "limit" : "<positiveInt>", // Number of results
  "sort" : [{ // Order of the results
    "path" : "<string>", // R!  The name of the attribute to perform the sort
    "direction" : "<code>" // R!  ascending | descending
  }]
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:type [ code ] ; # 1..1 The type of the required data
  fhir:profile  ( [ canonical(StructureDefinition) ] ... ) ; # 0..* The profile of the required data
  # subject[x] : 0..1 E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device. One of these 2
    fhir:subject [  a fhir:CodeableConcept ; CodeableConcept ]
    fhir:subject [  a fhir:Reference ; Reference(Group) ]
  fhir:<a href="metadatatypes-definitions.html#DataRequirement.mustSupport" title="Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. 


  fhir:mustSupport  ( [ string ] ... ) ; # 0..* Indicates specific structure elements that are referenced by the knowledge module
  fhir:codeFilter ( [ # 0..* What codes are expected
    fhir:path [ string ] ; # 0..1 I A code-valued attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 I A coded (token) parameter to search on
    fhir:valueSet [ canonical(ValueSet) ] ; # 0..1 ValueSet for the filter
    fhir:code  ( [ Coding ] ... ) ; # 0..* What code is expected
  ] ... ) ;
  fhir:dateFilter ( [ # 0..* What dates/date ranges are expected
    fhir:path [ string ] ; # 0..1 I A date-valued attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 I A date valued parameter to search on
    # value[x] : 0..1 The value of the filter, as a Period, DateTime, or Duration value. One of these 3
      fhir: ]

      fhir:value [  a fhir:DateTime ; dateTime ]

      fhir:value [  a fhir:Period ; Period ]
      fhir:value [  a fhir:Duration ; Duration ]
  ] ... ) ;
  fhir:valueFilter ( [ # 0..* What values are expected
    fhir:path [ string ] ; # 0..1 An attribute to filter on
    fhir:searchParam [ string ] ; # 0..1 A parameter to search on
    fhir:comparator [ code ] ; # 0..1 eq | gt | lt | ge | le | sa | eb
    # value[x] : 0..1 The value of the filter, as a Period, DateTime, or Duration value. One of these 3
      fhir: ]

      fhir:value [  a fhir:DateTime ; dateTime ]

      fhir:value [  a fhir:Period ; Period ]
      fhir:value [  a fhir:Duration ; Duration ]
  ] ... ) ;
  fhir:limit [ positiveInt ] ; # 0..1 Number of results
  fhir:sort ( [ # 0..* Order of the results
    fhir:path [ string ] ; # 1..1 The name of the attribute to perform the sort
    fhir:direction [ code ] ; # 1..1 ascending | descending
  ] ... ) ;
]

Changes since Release 3

Changes from both R4 and R4B

DataRequirement
DataRequirement.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types|4.0.0 to All FHIR Types
  • Remove codes Address , Age , Annotation , Attachment , BackboneElement , CodeableConcept , Coding , ContactDetail , ContactPoint , Contributor , Count , DataRequirement , Distance , Dosage , Duration , Element , ElementDefinition , Expression , Extension , HumanName , Identifier , MarketingStatus , Meta , Money , MoneyQuantity , Narrative , ParameterDefinition , Period , Population , ProdCharacteristic , ProductShelfLife , Quantity , Range , Ratio , Reference , RelatedArtifact , SampledData , Signature , SimpleQuantity , SubstanceAmount , Timing , TriggerDefinition , UsageContext , base64Binary , boolean , canonical , code , date , dateTime , decimal , id , instant , integer , markdown , oid , positiveInt , string , time , unsignedInt , uri , url , uuid , xhtml , Account , ActivityDefinition , AdverseEvent , AllergyIntolerance , Appointment , AppointmentResponse , AuditEvent , Basic , Binary , BiologicallyDerivedProduct , BodyStructure , Bundle , CapabilityStatement , CarePlan , CareTeam , CatalogEntry , ChargeItem , ChargeItemDefinition , Claim , ClaimResponse , ClinicalImpression , CodeSystem , Communication , CommunicationRequest , CompartmentDefinition , Composition , ConceptMap , Condition , Consent , Contract , Coverage , CoverageEligibilityRequest , CoverageEligibilityResponse , DetectedIssue , Device , DeviceDefinition , DeviceMetric , DeviceRequest , DeviceUseStatement , DiagnosticReport , DocumentManifest , DocumentReference , DomainResource , EffectEvidenceSynthesis , Encounter , Endpoint , EnrollmentRequest , EnrollmentResponse , EpisodeOfCare , EventDefinition , Evidence , EvidenceVariable , ExampleScenario , ExplanationOfBenefit , FamilyMemberHistory , Flag , Goal , GraphDefinition , Group , GuidanceResponse , HealthcareService , ImagingStudy , Immunization , ImmunizationEvaluation , ImmunizationRecommendation , ImplementationGuide , InsurancePlan , Invoice , Library , Linkage , List , Location , Measure , MeasureReport , Media , Medication , MedicationAdministration , MedicationDispense , MedicationKnowledge , MedicationRequest , MedicationStatement , MedicinalProduct , MedicinalProductAuthorization , MedicinalProductContraindication , MedicinalProductIndication , MedicinalProductIngredient , MedicinalProductInteraction , MedicinalProductManufactured , MedicinalProductPackaged , MedicinalProductPharmaceutical , MedicinalProductUndesirableEffect , RequestGroup MessageDefinition , ResearchDefinition MessageHeader , ResearchElementDefinition MolecularSequence , RiskEvidenceSynthesis NamingSystem , SubstanceSpecification NutritionOrder , Type Observation , Any Add codes ObservationDefinition , Base OperationDefinition , DataType OperationOutcome , Availability Organization , BackboneType OrganizationAffiliation , CodeableReference Parameters , ExtendedContactDetail Patient , MonetaryComponent PaymentNotice , PrimitiveType PaymentReconciliation , integer64 Person , RatioRange PlanDefinition , VirtualServiceDetail Practitioner , ActorDefinition PractitionerRole , AdministrableProductDefinition Procedure , ArtifactAssessment Provenance , BiologicallyDerivedProductDispense Questionnaire , CanonicalResource QuestionnaireResponse , Citation RelatedPerson , ClinicalUseDefinition RequestGroup , ConditionDefinition ResearchDefinition , DeviceAssociation ResearchElementDefinition , DeviceDispense ResearchStudy , DeviceUsage ResearchSubject , EncounterHistory Resource , EvidenceReport RiskAssessment , FormularyItem RiskEvidenceSynthesis , GenomicStudy Schedule , ImagingSelection SearchParameter , Ingredient ServiceRequest , InventoryItem Slot , InventoryReport Specimen , ManufacturedItemDefinition SpecimenDefinition , MedicinalProductDefinition StructureDefinition , MetadataResource StructureMap , NutritionIntake Subscription , NutritionProduct Substance , PackagedProductDefinition SubstanceNucleicAcid , Permission SubstancePolymer , RegulatedAuthorization SubstanceProtein , RequestOrchestration SubstanceReferenceInformation , Requirements SubstanceSourceMaterial , SubscriptionStatus SubstanceSpecification , SubscriptionTopic SupplyDelivery , SubstanceDefinition SupplyRequest , TestPlan Task , Transport TerminologyCapabilities , TestReport , TestScript , ValueSet , VerificationResult , VisionPrescription , Type , Any
  • Add code Base
DataRequirement.subject[x]
  • Change value set from http://hl7.org/fhir/ValueSet/subject-type to Participant Resource Types
  • Change code system for extensibly bound codes from "http://hl7.org/fhir/resource-types" to "http://hl7.org/fhir/fhir-types"
DataRequirement.valueFilter
  • Added Element
DataRequirement.valueFilter.path
  • Added Element
DataRequirement.valueFilter.searchParam
  • Added Element
DataRequirement.valueFilter.comparator
  • Added Element
DataRequirement.valueFilter.value[x]
  • Added Element

See the Full Difference for further information

Constraints

id Level Location Description Expression
img  drq-1 Rule DataRequirement.codeFilter Either a path or a searchParam must be provided, but not both path.exists() xor searchParam.exists()
img  drq-2 Rule DataRequirement.dateFilter Either a path or a searchParam must be provided, but not both path.exists() xor searchParam.exists()

Terminology Bindings

Path ValueSet Type Documentation
DataRequirement.type FHIRTypes (a valid code from All FHIR Types ) Required

All FHIR types

DataRequirement.subject[x] ParticipantResourceTypes Extensible

All Resource Types that represent participant resources

DataRequirement.valueFilter.comparator ValueFilterComparator Required

The type of comparator operator to use

DataRequirement.sort.direction SortDirection Required

The possible sort directions, ascending or descending.

A DataRequirement differs from a parameter in that it specifies the data to be provided in terms of the type of data, and specific filters on code-valued and/or date-valued attributes. Data requirements are not named because they are referenced by type within the evaluation context.

DataRequirements are used by knowledge modules to communicate the set of required data to a consumer in a way that is computable (as opposed to a set of named parameters which must be integrated by hand based on the meaning of the parameter as communicated through the documentation).

DataRequirements are typically used to communicate patient-dependent information such as MedicationStatements and Encounters, whereas Parameters are typically used to communicate patient-independent information such as configuration values.

For example, consider the following CQL expression: 

define "Total Colectomy Procedures":
  [Procedure: "Total Colectomy Value Set"] P
    where P.performedPeriod during "Measurement Period"

The criteria is looking for procedures matching the "Total Colectomy Value Set" that were performed during the "Measurement Period". In this case, "Measurement Period" is a parameter, referenced by name, whereas the reference to Procedure uses the name of the resource type, and so constitutes a data requirement of the criteria: 

<dataRequirement>
	<type value="Procedure"/>
	<codeFilter>
		<path value="code"/>
		<valueSetString value="Total Colectomy Value Set"/>
	</codeFilter>
	<dateFilter>
		<path value="performed"/>
		<valuePeriod>
			<start value="2016-01-01"/>
			<end value="2016-12-31"/>
		</valuePeriod>
	</dateFilter>
</dataRequirement>

If a resource type has multiple date attributes, then it may be necessary to include multiple date criteria. For instance, in the example above the Procedure resource is using the performedPeriod date attribute. However, the Procedure resource also provides a performedDateTime (specific date and/or time when procedure was performed) attribute. Therefore, if the date criteria for the Procedure in the example was recorded using the performedDateTime attribute, the date criteria would be incomplete. To account for this additional date attribute, the example could be expanded as follows: 

define "Total Colectomy Procedures":
  [Procedure: "Total Colectomy Value Set"] P
    where exists (P.performedPeriod during "Measurement Period")
	  or exists (P.performedDateTime during "Measurement Period")

The data requirement for the expanded criteria: 

<dataRequirement>
	<type value="Procedure"/>
	<codeFilter>
		<path value="code"/>
		<valueSetString value="Total Colectomy Value Set"/>
	</codeFilter>
	<dateFilter>
		<path value="performed"/>
	</dateFilter>
</dataRequirement>

DataRequirement is used in the following places: TriggerDefinition , GuidanceResponse , Library , Measure , Parameters , PlanDefinition and , RequestOrchestration and Task

 

2.1.28.6.0.3 2.1.27.5.0.3 ParameterDefinition

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The ParameterDefinition structure defines a parameter to a knowledge asset such as a decision support rule or quality measure.

Parameters are typically used to communicate patient-independent information such as configuration values, whereas DataRequirements are typically used to communicate patient-dependent information such as MedicationStatements and Encounters.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ParameterDefinition Σ TU N Element Definition of a parameter to a module

Elements defined in Ancestors: id , extension
. . . name Σ 0..1 code Name used to access the parameter value
. . . use Σ 1..1 code in | out
Binding: Operation Parameter Use ( Required )
. . . min Σ 0..1 integer Minimum cardinality
. . . documentation Σ 0..1 string A brief description of the parameter
. . . type Σ 1..1 code What type of value
Binding: All FHIR Types ( Required )
. . . profile Σ 0..1 canonical ( StructureDefinition ) What profile the value is expected to be

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

<ParameterDefinition xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <name value="[code]"/><!-- 0..1 Name used to access the parameter value -->
 <use value="[code]"/><!-- 1..1 in | out -->
 <min value="[integer]"/><!-- 0..1 Minimum cardinality -->
 <max value="[string]"/><!-- 0..1 Maximum cardinality (a number of *) -->
 <documentation value="[string]"/><!-- 0..1 A brief description of the parameter -->
 <type value="[code]"/><!-- 1..1 What type of value -->
 <profile><!-- 0..1 canonical(StructureDefinition) What profile the value is expected to be --></profile>
</ParameterDefinition>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:name [ code ] ; # 0..1 Name used to access the parameter value
  fhir:use [ code ] ; # 1..1 in | out
  fhir:min [ integer ] ; # 0..1 Minimum cardinality
  fhir:max [ string ] ; # 0..1 Maximum cardinality (a number of *)
  fhir:documentation [ string ] ; # 0..1 A brief description of the parameter
  fhir:type [ code ] ; # 1..1 What type of value
  fhir:profile [ canonical(StructureDefinition) ] ; # 0..1 What profile the value is expected to be
]

Changes since Release 3

Changes from both R4 and R4B

ParameterDefinition
ParameterDefinition.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types|4.0.0 to All FHIR Types
  • Remove codes Address , Age , Annotation , Attachment , BackboneElement , CodeableConcept , Coding , ContactDetail , ContactPoint , Contributor , Count , DataRequirement , Distance , Dosage , Duration , Element , ElementDefinition , Expression , Extension , HumanName , Identifier , MarketingStatus , Meta , Money , MoneyQuantity , Narrative , ParameterDefinition , Period , Population , ProdCharacteristic , ProductShelfLife , Quantity , Range , Ratio , Reference , RelatedArtifact , SampledData , Signature , SimpleQuantity , SubstanceAmount , Timing , TriggerDefinition , UsageContext , base64Binary , boolean , canonical , code , date , dateTime , decimal , id , instant , integer , markdown , oid , positiveInt , string , time , unsignedInt , uri , url , uuid , xhtml , Account , ActivityDefinition , AdverseEvent , AllergyIntolerance , Appointment , AppointmentResponse , AuditEvent , Basic , Binary , BiologicallyDerivedProduct , BodyStructure , Bundle , CapabilityStatement , CarePlan , CareTeam , CatalogEntry , ChargeItem , ChargeItemDefinition , Claim , ClaimResponse , ClinicalImpression , CodeSystem , Communication , CommunicationRequest , CompartmentDefinition , Composition , ConceptMap , Condition , Consent , Contract , Coverage , CoverageEligibilityRequest , CoverageEligibilityResponse , DetectedIssue , Device , DeviceDefinition , DeviceMetric , DeviceRequest , DeviceUseStatement , DiagnosticReport , DocumentManifest , DocumentReference , DomainResource , EffectEvidenceSynthesis , Encounter , Endpoint , EnrollmentRequest , EnrollmentResponse , EpisodeOfCare , EventDefinition , Evidence , EvidenceVariable , ExampleScenario , ExplanationOfBenefit , FamilyMemberHistory , Flag , Goal , GraphDefinition , Group , GuidanceResponse , HealthcareService , ImagingStudy , Immunization , ImmunizationEvaluation , ImmunizationRecommendation , ImplementationGuide , InsurancePlan , Invoice , Library , Linkage , List , Location , Measure , MeasureReport , Media , Medication , MedicationAdministration , MedicationDispense , MedicationKnowledge , MedicationRequest , MedicationStatement , MedicinalProduct , MedicinalProductAuthorization , MedicinalProductContraindication , MedicinalProductIndication , MedicinalProductIngredient , MedicinalProductInteraction , MedicinalProductManufactured , MedicinalProductPackaged , MedicinalProductPharmaceutical , MedicinalProductUndesirableEffect , RequestGroup MessageDefinition , ResearchDefinition MessageHeader , ResearchElementDefinition MolecularSequence , RiskEvidenceSynthesis NamingSystem , SubstanceSpecification NutritionOrder , Type Observation , Any Add codes ObservationDefinition , Base OperationDefinition , DataType OperationOutcome , Availability Organization , BackboneType OrganizationAffiliation , CodeableReference Parameters , ExtendedContactDetail Patient , MonetaryComponent PaymentNotice , PrimitiveType PaymentReconciliation , integer64 Person , RatioRange PlanDefinition , VirtualServiceDetail Practitioner , ActorDefinition PractitionerRole , AdministrableProductDefinition Procedure , ArtifactAssessment Provenance , BiologicallyDerivedProductDispense Questionnaire , CanonicalResource QuestionnaireResponse , Citation RelatedPerson , ClinicalUseDefinition RequestGroup , ConditionDefinition ResearchDefinition , DeviceAssociation ResearchElementDefinition , DeviceDispense ResearchStudy , DeviceUsage ResearchSubject , EncounterHistory Resource , EvidenceReport RiskAssessment , FormularyItem RiskEvidenceSynthesis , GenomicStudy Schedule , ImagingSelection SearchParameter , Ingredient ServiceRequest , InventoryItem Slot , InventoryReport Specimen , ManufacturedItemDefinition SpecimenDefinition , MedicinalProductDefinition StructureDefinition , MetadataResource StructureMap , NutritionIntake Subscription , NutritionProduct Substance , PackagedProductDefinition SubstanceNucleicAcid , Permission SubstancePolymer , RegulatedAuthorization SubstanceProtein , RequestOrchestration SubstanceReferenceInformation , Requirements SubstanceSourceMaterial , SubscriptionStatus SubstanceSpecification , SubscriptionTopic SupplyDelivery , SubstanceDefinition SupplyRequest , TestPlan Task , Transport TerminologyCapabilities , TestReport , TestScript , ValueSet , VerificationResult , VisionPrescription , Type , Any
  • Add code Base

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ParameterDefinition Σ TU N Element Definition of a parameter to a module

Elements defined in Ancestors: id , extension
. . . name Σ 0..1 code Name used to access the parameter value
. . . use Σ 1..1 code in | out
Binding: Operation Parameter Use ( Required )
. . . min Σ 0..1 integer Minimum cardinality
. . . documentation Σ 0..1 string A brief description of the parameter
. . . type Σ 1..1 code What type of value
Binding: All FHIR Types ( Required )
. . . profile Σ 0..1 canonical ( StructureDefinition ) What profile the value is expected to be

doco Documentation for this format icon

XML Template 

<ParameterDefinition xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <name value="[code]"/><!-- 0..1 Name used to access the parameter value -->
 <use value="[code]"/><!-- 1..1 in | out -->
 <min value="[integer]"/><!-- 0..1 Minimum cardinality -->
 <max value="[string]"/><!-- 0..1 Maximum cardinality (a number of *) -->
 <documentation value="[string]"/><!-- 0..1 A brief description of the parameter -->
 <type value="[code]"/><!-- 1..1 What type of value -->
 <profile><!-- 0..1 canonical(StructureDefinition) What profile the value is expected to be --></profile>
</ParameterDefinition>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:name [ code ] ; # 0..1 Name used to access the parameter value
  fhir:use [ code ] ; # 1..1 in | out
  fhir:min [ integer ] ; # 0..1 Minimum cardinality
  fhir:max [ string ] ; # 0..1 Maximum cardinality (a number of *)
  fhir:documentation [ string ] ; # 0..1 A brief description of the parameter
  fhir:type [ code ] ; # 1..1 What type of value
  fhir:profile [ canonical(StructureDefinition) ] ; # 0..1 What profile the value is expected to be
]

Changes since Release 3

Changes from both R4 and R4B

ParameterDefinition
ParameterDefinition.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types|4.0.0 to All FHIR Types
  • Remove codes Address , Age , Annotation , Attachment , BackboneElement , CodeableConcept , Coding , ContactDetail , ContactPoint , Contributor , Count , DataRequirement , Distance , Dosage , Duration , Element , ElementDefinition , Expression , Extension , HumanName , Identifier , MarketingStatus , Meta , Money , MoneyQuantity , Narrative , ParameterDefinition , Period , Population , ProdCharacteristic , ProductShelfLife , Quantity , Range , Ratio , Reference , RelatedArtifact , SampledData , Signature , SimpleQuantity , SubstanceAmount , Timing , TriggerDefinition , UsageContext , base64Binary , boolean , canonical , code , date , dateTime , decimal , id , instant , integer , markdown , oid , positiveInt , string , time , unsignedInt , uri , url , uuid , xhtml , Account , ActivityDefinition , AdverseEvent , AllergyIntolerance , Appointment , AppointmentResponse , AuditEvent , Basic , Binary , BiologicallyDerivedProduct , BodyStructure , Bundle , CapabilityStatement , CarePlan , CareTeam , CatalogEntry , ChargeItem , ChargeItemDefinition , Claim , ClaimResponse , ClinicalImpression , CodeSystem , Communication , CommunicationRequest , CompartmentDefinition , Composition , ConceptMap , Condition , Consent , Contract , Coverage , CoverageEligibilityRequest , CoverageEligibilityResponse , DetectedIssue , Device , DeviceDefinition , DeviceMetric , DeviceRequest , DeviceUseStatement , DiagnosticReport , DocumentManifest , DocumentReference , DomainResource , EffectEvidenceSynthesis , Encounter , Endpoint , EnrollmentRequest , EnrollmentResponse , EpisodeOfCare , EventDefinition , Evidence , EvidenceVariable , ExampleScenario , ExplanationOfBenefit , FamilyMemberHistory , Flag , Goal , GraphDefinition , Group , GuidanceResponse , HealthcareService , ImagingStudy , Immunization , ImmunizationEvaluation , ImmunizationRecommendation , ImplementationGuide , InsurancePlan , Invoice , Library , Linkage , List , Location , Measure , MeasureReport , Media , Medication , MedicationAdministration , MedicationDispense , MedicationKnowledge , MedicationRequest , MedicationStatement , MedicinalProduct , MedicinalProductAuthorization , MedicinalProductContraindication , MedicinalProductIndication , MedicinalProductIngredient , MedicinalProductInteraction , MedicinalProductManufactured , MedicinalProductPackaged , MedicinalProductPharmaceutical , MedicinalProductUndesirableEffect , RequestGroup MessageDefinition , ResearchDefinition MessageHeader , ResearchElementDefinition MolecularSequence , RiskEvidenceSynthesis NamingSystem , SubstanceSpecification NutritionOrder , Type Observation , Any Add codes ObservationDefinition , Base OperationDefinition , DataType OperationOutcome , Availability Organization , BackboneType OrganizationAffiliation , CodeableReference Parameters , ExtendedContactDetail Patient , MonetaryComponent PaymentNotice , PrimitiveType PaymentReconciliation , integer64 Person , RatioRange PlanDefinition , VirtualServiceDetail Practitioner , ActorDefinition PractitionerRole , AdministrableProductDefinition Procedure , ArtifactAssessment Provenance , BiologicallyDerivedProductDispense Questionnaire , CanonicalResource QuestionnaireResponse , Citation RelatedPerson , ClinicalUseDefinition RequestGroup , ConditionDefinition ResearchDefinition , DeviceAssociation ResearchElementDefinition , DeviceDispense ResearchStudy , DeviceUsage ResearchSubject , EncounterHistory Resource , EvidenceReport RiskAssessment , FormularyItem RiskEvidenceSynthesis , GenomicStudy Schedule , ImagingSelection SearchParameter , Ingredient ServiceRequest , InventoryItem Slot , InventoryReport Specimen , ManufacturedItemDefinition SpecimenDefinition , MedicinalProductDefinition StructureDefinition , MetadataResource StructureMap , NutritionIntake Subscription , NutritionProduct Substance , PackagedProductDefinition SubstanceNucleicAcid , Permission SubstancePolymer , RegulatedAuthorization SubstanceProtein , RequestOrchestration SubstanceReferenceInformation , Requirements SubstanceSourceMaterial , SubscriptionStatus SubstanceSpecification , SubscriptionTopic SupplyDelivery , SubstanceDefinition SupplyRequest , TestPlan Task , Transport TerminologyCapabilities , TestReport , TestScript , ValueSet , VerificationResult , VisionPrescription , Type , Any
  • Add code Base

See the Full Difference for further information

Constraints

Terminology Bindings

Path ValueSet Type Documentation
ParameterDefinition.use OperationParameterUse Required

Whether an operation parameter is an input or an output parameter.

ParameterDefinition.type FHIRTypes (a valid code from All FHIR Types ) Required

All FHIR types

 

2.1.28.6.0.4 2.1.27.5.0.4 RelatedArtifact

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The RelatedArtifact structure defines resources related to an artifact such as previous and next versions of documents, documentation, citations, etc. Note that the name artifact here is being used in a general sense; The related artifact may be a FHIR resource, or it may be another type of resource, represented using the Attachment datatype.

Structure

classifier Σ 0..* CodeableConcept Additional classifiers Binding: Citation Artifact Classifier ( Example ) date Date of publication of the artifact being referred to
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . RelatedArtifact Σ TU N Element Related artifacts for a knowledge resource
+ Warning: Citation must be inline or a canonical reference to a Citation
+ Warning: Documentation must be an attachment
+ Warning: Justification must be an attachment or a reference to an ArtifactAssessment

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as
Binding: RelatedArtifactType ( Required )
. . . label Σ 0..1 string Short label
. . . display Σ 0..1 string Brief description of the related artifact
. . . document Σ 0..1 Attachment What document is being referenced
. . . resource Σ 0..1 canonical ( Any ) What artifact is being referenced
. . . resourceReference Σ 0..1 Reference ( Any ) What artifact, if not a conformance resource
. . publicationStatus . artifact[x] Σ 0..1 What document, citation, artifact, or resource is being referenced
code
. . . . artifactMarkdown draft | active | retired | unknown Binding: PublicationStatus ( Required markdown )
. . publicationDate . . artifactAttachment Σ Attachment 0..1
. . . . artifactCanonical canonical ( Any )
. . . . artifactReference Reference ( Any )

doco Documentation for this format icon

Definition: XML | JSON

UML Diagram ( Legend )

RelatedArtifact The type of relationship to the related artifact type : code [1..1] « The type of relationship to the related artifact. (Strength=Required) RelatedArtifactType ! » Provides additional classifiers of the related artifact classifier : CodeableConcept [0..*] « Additional classifiers for the related artifact. (Strength=Example) CitationArtifactClassifier ?? » A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index label : string [0..1] A brief description of the document or knowledge resource being referenced, suitable for display to a consumer display : string [0..1] Deprecated in favor of the new artifact[x] element. A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format citation : markdown [0..1] Deprecated in favor of the new artifact[x] element. The document being referenced, represented as an attachment. This is exclusive with the resource element document : Attachment [0..1] Deprecated in favor of the new artifact[x] element. The related artifact, such as a library, value set, profile, or other knowledge resource resource : canonical [0..1] « Any » Deprecated in favor of the new artifact[x] element. The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource resourceReference : Reference [0..1] « Any » The publication status of the related artifact being referred represented as a canonical or direct reference to a FHIR resource, an Attachment, or directly inline as markdown publicationStatus artifact[x] : code DataType [0..1] « Publication status of an artifact being referred to. (Strength=Required) PublicationStatus ! » markdown | Attachment | canonical ( Any )| The date of publication of the artifact being referred to publicationDate Reference : date ( Any [0..1] ) » DataType

XML Template 

< xmlns="http://hl7.org/fhir">

<RelatedArtifact xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
 <</classifier>

 <type value="[code]"/><!-- 1..1 documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of -->

 <label value="[string]"/><!-- 0..1 Short label -->
 <display value="[string]"/><!-- 0..1 Brief description of the related artifact -->
 <
 <</document>
 <</resource>
 <</resourceReference>
 <
 <

 <citation value="[markdown]"/><!-- 0..1 Bibliographic citation for the artifact -->
 <document><!-- 0..1 Attachment What document is being referenced --></document>
 <resource><!-- 0..1 canonical(Any) What artifact is being referenced --></resource>
 <resourceReference><!-- 0..1 Reference(Any) What artifact, if not a conformance resource --></resourceReference>
 <artifact[x]><!-- 0..1 markdown|Attachment|canonical(Any)|Reference(Any) What document, citation, artifact, or resource is being referenced --></artifact[x]>

</RelatedArtifact>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of

  fhir:label [ string ] ; # 0..1 Short label
  fhir:display [ string ] ; # 0..1 Brief description of the related artifact
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:citation [ markdown ] ; # 0..1 Bibliographic citation for the artifact
  fhir:document [ Attachment ] ; # 0..1 What document is being referenced
  fhir:resource [ canonical(Any) ] ; # 0..1 What artifact is being referenced
  fhir:resourceReference [ Reference(Any) ] ; # 0..1 What artifact, if not a conformance resource
  # artifact[x] : 0..1 What document, citation, artifact, or resource is being referenced. One of these 4
    fhir:artifact [  a fhir:Markdown ; markdown ]
    fhir:artifact [  a fhir:Attachment ; Attachment ]
    fhir:artifact [  a fhir:Canonical ; canonical(Any) ]
    fhir:artifact [  a fhir:Reference ; Reference(Any) ]

]

Changes since Release 3

Changes from both R4 and R4B

RelatedArtifact.classifier Added Element
RelatedArtifact
RelatedArtifact.type
  • Add codes code part-of , amends , amended-with , appends , appended-with , cites , cited-by , comments-on , comment-in , contains , contained-in , corrects , correction-in , replaces , replaced-with , retracts , retracted-by , signs , similar-to , supports , supported-with , transforms , transformed-into , transformed-with , documents , specification-of , created-with , cite-as
RelatedArtifact.resourceReference
  • Added Element
RelatedArtifact.publicationStatus Added Element RelatedArtifact.publicationDate RelatedArtifact.artifact[x]
  • Added Element
RelatedArtifact.url
  • Deleted (-> document)

See the Full Difference for further information

Structure

classifier Σ 0..* CodeableConcept Additional classifiers Binding: Citation Artifact Classifier ( Example ) date Date of publication of the artifact being referred to
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . RelatedArtifact Σ TU N Element Related artifacts for a knowledge resource
+ Warning: Citation must be inline or a canonical reference to a Citation
+ Warning: Documentation must be an attachment
+ Warning: Justification must be an attachment or a reference to an ArtifactAssessment

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | documents | specification-of | created-with | cite-as
Binding: RelatedArtifactType ( Required )
. . . label Σ 0..1 string Short label
. . . display Σ 0..1 string Brief description of the related artifact
. . . document Σ 0..1 Attachment What document is being referenced
. . . resource Σ 0..1 canonical ( Any ) What artifact is being referenced
. . . resourceReference Σ 0..1 Reference ( Any ) What artifact, if not a conformance resource
. . publicationStatus . artifact[x] Σ 0..1 What document, citation, artifact, or resource is being referenced
code
. . . . artifactMarkdown draft | active | retired | unknown Binding: PublicationStatus ( Required markdown )
. . publicationDate . . artifactAttachment Σ Attachment 0..1
. . . . artifactCanonical canonical ( Any )
. . . . artifactReference Reference ( Any )

doco Documentation for this format icon

UML Diagram ( Legend )

RelatedArtifact The type of relationship to the related artifact type : code [1..1] « The type of relationship to the related artifact. (Strength=Required) RelatedArtifactType ! » Provides additional classifiers of the related artifact classifier : CodeableConcept [0..*] « Additional classifiers for the related artifact. (Strength=Example) CitationArtifactClassifier ?? » A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index label : string [0..1] A brief description of the document or knowledge resource being referenced, suitable for display to a consumer display : string [0..1] Deprecated in favor of the new artifact[x] element. A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format citation : markdown [0..1] Deprecated in favor of the new artifact[x] element. The document being referenced, represented as an attachment. This is exclusive with the resource element document : Attachment [0..1] Deprecated in favor of the new artifact[x] element. The related artifact, such as a library, value set, profile, or other knowledge resource resource : canonical [0..1] « Any » Deprecated in favor of the new artifact[x] element. The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource resourceReference : Reference [0..1] « Any » The publication status of the related artifact being referred represented as a canonical or direct reference to a FHIR resource, an Attachment, or directly inline as markdown publicationStatus artifact[x] : code DataType [0..1] « Publication status of an artifact being referred to. (Strength=Required) PublicationStatus ! » markdown | Attachment | canonical ( Any )| The date of publication of the artifact being referred to publicationDate Reference : date ( Any [0..1] ) » DataType

XML Template 

< xmlns="http://hl7.org/fhir">

<RelatedArtifact xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
 <</classifier>

 <type value="[code]"/><!-- 1..1 documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of -->

 <label value="[string]"/><!-- 0..1 Short label -->
 <display value="[string]"/><!-- 0..1 Brief description of the related artifact -->
 <
 <</document>
 <</resource>
 <</resourceReference>
 <
 <

 <citation value="[markdown]"/><!-- 0..1 Bibliographic citation for the artifact -->
 <document><!-- 0..1 Attachment What document is being referenced --></document>
 <resource><!-- 0..1 canonical(Any) What artifact is being referenced --></resource>
 <resourceReference><!-- 0..1 Reference(Any) What artifact, if not a conformance resource --></resourceReference>
 <artifact[x]><!-- 0..1 markdown|Attachment|canonical(Any)|Reference(Any) What document, citation, artifact, or resource is being referenced --></artifact[x]>

</RelatedArtifact>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 documentation | justification | citation | predecessor | successor | derived-from | depends-on | composed-of | part-of

  fhir:label [ string ] ; # 0..1 Short label
  fhir:display [ string ] ; # 0..1 Brief description of the related artifact
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:citation [ markdown ] ; # 0..1 Bibliographic citation for the artifact
  fhir:document [ Attachment ] ; # 0..1 What document is being referenced
  fhir:resource [ canonical(Any) ] ; # 0..1 What artifact is being referenced
  fhir:resourceReference [ Reference(Any) ] ; # 0..1 What artifact, if not a conformance resource
  # artifact[x] : 0..1 What document, citation, artifact, or resource is being referenced. One of these 4
    fhir:artifact [  a fhir:Markdown ; markdown ]
    fhir:artifact [  a fhir:Attachment ; Attachment ]
    fhir:artifact [  a fhir:Canonical ; canonical(Any) ]
    fhir:artifact [  a fhir:Reference ; Reference(Any) ]

]

Changes since Release 3

Changes from both R4 and R4B

RelatedArtifact.classifier Added Element Added Element RelatedArtifact.publicationStatus
RelatedArtifact
RelatedArtifact.type
  • Add codes code part-of , amends , amended-with , appends , appended-with , cites , cited-by , comments-on , comment-in , contains , contained-in , corrects , correction-in , replaces , replaced-with , retracts , retracted-by , signs , similar-to , supports , supported-with , transforms , transformed-into , transformed-with , documents , specification-of , created-with , cite-as
RelatedArtifact.resourceReference
  • Added Element
RelatedArtifact.publicationDate RelatedArtifact.artifact[x]
  • Added Element
RelatedArtifact.url
  • Deleted (-> document)

See the Full Difference for further information

Constraints

Terminology Bindings Path Documentation The type of relationship RelatedArtifact.classifier
ValueSet id Type Level RelatedArtifact.type Location RelatedArtifactType Required Description Expression
img  rla-1 Warning (base) Citation must be inline or a canonical reference to the related artifact. a Citation type = 'citation' implies ((citation.exists() xor resource.exists()) or (artifact is markdown or artifact is canonical))
CitationArtifactClassifier img  rla-2 Warning (base) Documentation must be an attachment type = 'documentation' implies (document.exists() or artifact is Attachment)
Example img  rla-3 Warning (base) Justification must be an attachment or a reference to an ArtifactAssessment type = 'justification' implies ((document.exists() or resourceReference.exists()) or (artifact is Attachment or artifact is Reference))

Citation artifact classifier Terminology Bindings

RelatedArtifact.publicationStatus
Path ValueSet Type Documentation
RelatedArtifact.type PublicationStatus RelatedArtifactType Required

The lifecycle status type of an relationship to the related artifact.

The following examples illustrate the use of relatedArtifact elements to provide citations: 

<relatedArtifact>
    <label value="1"/>
    <type value="citation"/>
    <citation value="Linder, J.A., D.W. Bates, G.M. Lee, J.A. Finkelstein. 2005. _Antibiotic treatment of children with sore throat_ JAMA 294(18):2315-2322. "/>
  </relatedArtifact>
  <relatedArtifact>
    <type value="citation"/>
    <label value="2"/>
    <citation value="Infectious Diseases Society of America. 2012. _Clinical Practice Guideline for the Diagnosis and Management of Group A Streptococcal Pharyngitis: 2012 Update._ "/>
  </relatedArtifact>
  <relatedArtifact>
    <type value="citation"/>
    <label value="3"/>
    <citation value="Roberts, R.R., B. Hota, I. Ahmad, et al. _Hospital and Societal Costs of Antimicrobial-Resistant Infections in a Chicago Teaching Hospital: Implications for Antibiotic Stewardship._ Clin Infect Dis. Oct 2009; 49(8):1175-84."/>
</relatedArtifact>

RelatedArtifact is used in the following places: ActivityDefinition , ArtifactAssessment , ChargeItemDefinition , Citation , CodeSystem , Composition , ConceptMap , DeviceDefinition , DiagnosticReport , EventDefinition , Evidence , EvidenceReport , EvidenceVariable , Library , Measure , MetadataResource , NamingSystem , Parameters , PlanDefinition , RequestOrchestration , ResearchStudy Task and ValueSet

2.1.28.6.0.4.0.1 2.1.27.5.0.4.0.1 Interpretation of RelatedArtifact in different contexts

The RelatedArtifact type is used in a variety of contexts, and supports flexible description of relationships between artifacts. For example, the type can be used to describe both successor and predecessor relationships. This flexibility is needed to support use cases where only one side or other of the relationship is represented in FHIR. In practice, this datatype SHALL NOT be used to create bi-directional linking between FHIR resources.

 

2.1.28.6.0.5 2.1.27.5.0.4.0.2 TriggerDefinition Guidance on RelatedArtifact Usage

For resources that make use of RelatedArtifact, the relevant work group SHALL decide which relationships and target types are 'core' for the resource, which would historically have been handled as extensions, and which are not relevant at all. They SHALL define invariants that prohibit the use of relationships and/or target types for their resource that are never relevant or are redundant with other core elements or long-used extensions. (And if there is overlap with extensions that are not long-used, will ensure that the context for those extensions excludes the resource.) They will also add documentation to the element referencing RelatedArtifact calling out those relationship types that are considered 'core'.

Work groups considering the adoption of the RelatedArtifact data type, may only do so after evaluating what proportion of the incorporated elements are core for their resource and determining that the majority of the relationship types meet those criteria. They would still need to impose invariants around nonsensical or redundant relationship types and targets and provide documentation about which types were considered core. The note will also indicate that addition of new relationship types requires agreement that those relationships are 'core' to the majority of resources using the RelatedArtifactType and approval of the FHIR Infrastructure work group (from a methodology perspective).

 

Work Group

Maturity Level : 5 2.1.27.5.0.5 TriggerDefinition Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The TriggerDefinition structure defines when a knowledge artifact is expected to be evaluated. The structure can represent three main kinds of triggering events, depending on the value of type :

  • Named Event
  • Scheduled Event
  • Data Event

A named event is an event identified by the implementation environment. This allows any event generated within the implementation environment to be used as a trigger, but it requires pre-coordination of the names involved with the consuming environments. HL7 V2 events are assigned the URI http://terminology.hl7.org/CodeSystem/v2-0003#[code] e.g. e.g., http://terminology.hl7.org/CodeSystem/v2-0003/A01, and reference any data change that would trigger the sending of the matching HL7 V2 version, if the application providing the FHIR API supports v2 events internally.

A scheduled event occurs on a fixed or periodic schedule.

And finally, a data event occurs in response to some data-related event in the integrated environment such as a record being added or updated. The data-of-interest for a data event is described using a DataRequirement . This allows for systems to automatically invoke based on data activity occurring within the system. A condition may also be specified to further refine the trigger

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . TriggerDefinition Σ TU N Element Defines an expected trigger for a module
+ Rule: Either timing, or a data requirement, but not both
+ Rule: A condition only if there is a data requirement + Rule: A named event requires a name, name or code, a periodic event requires timing, and a data event requires data data, and a subscription topic requires a reference to a subscription topic

Elements defined in Ancestors: id , extension
. . . type Σ C 1..1 code named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic
Binding: TriggerType ( Required )
. . . name Σ C 0..1 string Name or URI that identifies the event
. . . code Σ C 0..1 CodeableConcept Coded definition of the event
. . . timing[x] Σ C 0..1 Timing of the event
. . . . timingTiming Timing timingReference Reference ( Schedule )
. . . . timingDate date
. . . . timingDateTime dateTime
. . . data Σ C 0..* DataRequirement Triggering data of the event (multiple = 'and')

. . . condition Σ C 0..1 Expression Whether the event triggers (boolean expression)

doco Documentation for this format icon

Definition: XML | JSON

UML Diagram ( Legend )

TriggerDefinition The type of triggering event type : code [1..1] « The type of trigger. (Strength=Required) TriggerType ! » « This element has or is affected by some invariants C » A formal name for the event. This may be an absolute URI that identifies the event formally (e.g. from a trigger registry), or a simple relative URI that identifies the event in a local context name : string [0..1] « This element has or is affected by some invariants C » A code that identifies the event code : CodeableConcept [0..1] « This element has or is affected by some invariants C » A reference to a SubscriptionTopic resource that defines the event. If this element is provided, no other information about the trigger definition may be supplied subscriptionTopic : canonical [0..1] « SubscriptionTopic » « This element has or is affected by some invariants C » The timing of the event (if this is a periodic trigger) timing[x] : DataType [0..1] « Timing | Reference ( Schedule )| date | dateTime » « This element has or is affected by some invariants C » The triggering data of the event (if this is a data trigger). If more than one data is requirement is specified, then all the data requirements must be true data : DataRequirement [0..*] « This element has or is affected by some invariants C » A boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires condition : Expression [0..1] « This element has or is affected by some invariants C » DataType

XML Template 

<TriggerDefinition xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <
 <
 <</code>
 <</subscriptionTopic>
 <</timing[x]>
 <</data>
 <</condition>

 <type value="[code]"/><!-- I 1..1 named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic -->
 <name value="[string]"/><!-- I 0..1 Name or URI that identifies the event -->
 <code><!-- I 0..1 CodeableConcept Coded definition of the event --></code>
 <subscriptionTopic><!-- I 0..1 canonical(SubscriptionTopic) What event --></subscriptionTopic>
 <timing[x]><!-- I 0..1 Timing|date|dateTime Timing of the event --></timing[x]>
 <data><!-- I 0..* DataRequirement Triggering data of the event (multiple = 'and') --></data>
 <condition><!-- 0..1 Expression Whether the event triggers (boolean expression) --></condition>

</TriggerDefinition>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:
  fhir:
  fhir:
  # . One of these 4

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 I named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic
  fhir:name [ string ] ; # 0..1 I Name or URI that identifies the event
  fhir:code [ CodeableConcept ] ; # 0..1 I Coded definition of the event
  fhir:subscriptionTopic [ canonical(SubscriptionTopic) ] ; # 0..1 I What event
  # timing[x] : 0..1 I Timing of the event. One of these 3

    fhir:timing [  a fhir:Timing ; Timing ]
    fhir:) ]
    fhir: ]
    fhir: ]
  fhir:
  fhir:

    fhir:timing [  a fhir:Date ; date ]
    fhir:timing [  a fhir:DateTime ; dateTime ]
  fhir:data  ( [ DataRequirement ] ... ) ; # 0..* I Triggering data of the event (multiple = 'and')
  fhir:condition [ Expression ] ; # 0..1 Whether the event triggers (boolean expression)

]

Changes since Release 3

Changes from both R4 and R4B

TriggerDefinition
TriggerDefinition.type
  • Remove codes data-added , data-modified , data-removed
  • Add code subscription-topic
TriggerDefinition.code
  • Added Element
TriggerDefinition.subscriptionTopic
  • Added Element
TriggerDefinition.timing[x]
  • Remove Type Reference(Schedule)

See the Full Difference for further information

Structure

timingReference Reference ( Schedule )
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . TriggerDefinition Σ TU N Element Defines an expected trigger for a module
+ Rule: Either timing, or a data requirement, but not both
+ Rule: A condition only if there is a data requirement + Rule: A named event requires a name, name or code, a periodic event requires timing, and a data event requires data data, and a subscription topic requires a reference to a subscription topic

Elements defined in Ancestors: id , extension
. . . type Σ C 1..1 code named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic
Binding: TriggerType ( Required )
. . . name Σ C 0..1 string Name or URI that identifies the event
. . . code Σ C 0..1 CodeableConcept Coded definition of the event
. . . timing[x] Σ C 0..1 Timing of the event
. . . . timingTiming Timing
. . . . timingDate date
. . . . timingDateTime dateTime
. . . data Σ C 0..* DataRequirement Triggering data of the event (multiple = 'and')

. . . condition Σ C 0..1 Expression Whether the event triggers (boolean expression)

doco Documentation for this format icon

UML Diagram ( Legend )

TriggerDefinition The type of triggering event type : code [1..1] « The type of trigger. (Strength=Required) TriggerType ! » « This element has or is affected by some invariants C » A formal name for the event. This may be an absolute URI that identifies the event formally (e.g. from a trigger registry), or a simple relative URI that identifies the event in a local context name : string [0..1] « This element has or is affected by some invariants C » A code that identifies the event code : CodeableConcept [0..1] « This element has or is affected by some invariants C » A reference to a SubscriptionTopic resource that defines the event. If this element is provided, no other information about the trigger definition may be supplied subscriptionTopic : canonical [0..1] « SubscriptionTopic » « This element has or is affected by some invariants C » The timing of the event (if this is a periodic trigger) timing[x] : DataType [0..1] « Timing | Reference ( Schedule )| date | dateTime » « This element has or is affected by some invariants C » The triggering data of the event (if this is a data trigger). If more than one data is requirement is specified, then all the data requirements must be true data : DataRequirement [0..*] « This element has or is affected by some invariants C » A boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires condition : Expression [0..1] « This element has or is affected by some invariants C » DataType

XML Template 

<TriggerDefinition xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <
 <
 <</code>
 <</subscriptionTopic>
 <</timing[x]>
 <</data>
 <</condition>

 <type value="[code]"/><!-- I 1..1 named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic -->
 <name value="[string]"/><!-- I 0..1 Name or URI that identifies the event -->
 <code><!-- I 0..1 CodeableConcept Coded definition of the event --></code>
 <subscriptionTopic><!-- I 0..1 canonical(SubscriptionTopic) What event --></subscriptionTopic>
 <timing[x]><!-- I 0..1 Timing|date|dateTime Timing of the event --></timing[x]>
 <data><!-- I 0..* DataRequirement Triggering data of the event (multiple = 'and') --></data>
 <condition><!-- 0..1 Expression Whether the event triggers (boolean expression) --></condition>

</TriggerDefinition>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:
  fhir:
  fhir:
  # . One of these 4

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 I named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic
  fhir:name [ string ] ; # 0..1 I Name or URI that identifies the event
  fhir:code [ CodeableConcept ] ; # 0..1 I Coded definition of the event
  fhir:subscriptionTopic [ canonical(SubscriptionTopic) ] ; # 0..1 I What event
  # timing[x] : 0..1 I Timing of the event. One of these 3

    fhir:timing [  a fhir:Timing ; Timing ]
    fhir:) ]
    fhir: ]
    fhir: ]
  fhir:
  fhir:

    fhir:timing [  a fhir:Date ; date ]
    fhir:timing [  a fhir:DateTime ; dateTime ]
  fhir:data  ( [ DataRequirement ] ... ) ; # 0..* I Triggering data of the event (multiple = 'and')
  fhir:condition [ Expression ] ; # 0..1 Whether the event triggers (boolean expression)

]

Changes since Release 3

Changes from both R4 and R4B

TriggerDefinition
TriggerDefinition.type
  • Remove codes data-added , data-modified , data-removed
  • Add code subscription-topic
TriggerDefinition.code
  • Added Element
TriggerDefinition.subscriptionTopic
  • Added Element
TriggerDefinition.timing[x]
  • Remove Type Reference(Schedule)

See the Full Difference for further information

Constraints

 trd-2 Rule (base) A condition only if there is a data requirement condition.exists() implies data.exists()
id Level Location Description Expression
img  trd-1 Rule (base) Either timing, or a data requirement, but not both data.empty() or timing.empty()
img  trd-3 Rule (base) A named event requires a name, name or code, a periodic event requires timing, and a data event requires data data, and a subscription topic requires a reference to a subscription topic (type = 'named-event' implies name.exists()) (name.exists() or code.exists())) and (type = 'periodic' implies timing.exists()) and (type.startsWith('data-') implies data.exists()) and (type = 'subscription-topic' implies subscriptionTopic.exists())

Terminology Bindings

Path ValueSet Type Documentation
TriggerDefinition.type TriggerType Required

The type of trigger.

TriggerDefinition is used in the following places: EventDefinition and , Parameters , PlanDefinition and Task

 

2.1.28.6.0.6 2.1.27.5.0.6 Expression

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The Expression structure defines an expression that generates a value. The expression is provided in a specifed language (by mime type)

The context of use of the expression must specify the context in which the expression is evaluated, and how the result of the expression is used.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Expression Σ TU N Element An expression that can be used to generate a value
+ Rule: An expression or a reference must be provided
+ Rule: The name must be a valid variable name in most computer languages

Elements defined in Ancestors: id , extension
. . . description Σ 0..1 string Natural language description of the condition
. . . name Σ C 0..1 code Short name assigned to expression for reuse
. . . language Σ 0..1 code text/cql | text/fhirpath | application/x-fhir-query | etc.
Binding: Expression Language ( Extensible )
Additional Bindings Purpose
Mime Types Max Binding

. . . reference Σ C 0..1 uri Where the expression is found

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

<Expression xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <description value="[string]"/><!-- 0..1 Natural language description of the condition -->
 <name value="[code]"/><!-- I 0..1 Short name assigned to expression for reuse -->
 <language value="[code]"/><!-- 0..1 text/cql | text/fhirpath | application/x-fhir-query | etc. -->
 <expression value="[string]"/><!-- I 0..1 Expression in specified language -->
 <reference value="[uri]"/><!-- I 0..1 Where the expression is found -->
</Expression>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:description [ string ] ; # 0..1 Natural language description of the condition
  fhir:name [ code ] ; # 0..1 I Short name assigned to expression for reuse
  fhir:language [ code ] ; # 0..1 text/cql | text/fhirpath | application/x-fhir-query | etc.
  fhir:expression [ string ] ; # 0..1 I Expression in specified language
  fhir:reference [ uri ] ; # 0..1 I Where the expression is found
]

Changes since Release 3

Changes from both R4 and R4B

Expression
Expression.name
  • Type changed from id to code
Expression.language
  • Min Cardinality changed from 1 to 0
  • Change max value set from http://www.rfc-editor.org/bcp/bcp13.txt to none
  • Change code system for extensibly bound codes from "http://hl7.org/fhir/expression-language" to "urn:ietf:bcp:13"

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Expression Σ TU N Element An expression that can be used to generate a value
+ Rule: An expression or a reference must be provided
+ Rule: The name must be a valid variable name in most computer languages

Elements defined in Ancestors: id , extension
. . . description Σ 0..1 string Natural language description of the condition
. . . name Σ C 0..1 code Short name assigned to expression for reuse
. . . language Σ 0..1 code text/cql | text/fhirpath | application/x-fhir-query | etc.
Binding: Expression Language ( Extensible )
Additional Bindings Purpose
Mime Types Max Binding

. . . reference Σ C 0..1 uri Where the expression is found

doco Documentation for this format icon

XML Template 

<Expression xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <description value="[string]"/><!-- 0..1 Natural language description of the condition -->
 <name value="[code]"/><!-- I 0..1 Short name assigned to expression for reuse -->
 <language value="[code]"/><!-- 0..1 text/cql | text/fhirpath | application/x-fhir-query | etc. -->
 <expression value="[string]"/><!-- I 0..1 Expression in specified language -->
 <reference value="[uri]"/><!-- I 0..1 Where the expression is found -->
</Expression>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:description [ string ] ; # 0..1 Natural language description of the condition
  fhir:name [ code ] ; # 0..1 I Short name assigned to expression for reuse
  fhir:language [ code ] ; # 0..1 text/cql | text/fhirpath | application/x-fhir-query | etc.
  fhir:expression [ string ] ; # 0..1 I Expression in specified language
  fhir:reference [ uri ] ; # 0..1 I Where the expression is found
]

Changes since Release 3

Changes from both R4 and R4B

Expression
Expression.name
  • Type changed from id to code
Expression.language
  • Min Cardinality changed from 1 to 0
  • Change max value set from http://www.rfc-editor.org/bcp/bcp13.txt to none
  • Change code system for extensibly bound codes from "http://hl7.org/fhir/expression-language" to "urn:ietf:bcp:13"

See the Full Difference for further information

Constraints

id Level Location Description Expression
img  exp-1 Rule (base) An expression or a reference must be provided expression.exists() or reference.exists()
img  exp-2 Rule (base) The name must be a valid variable name in most computer languages name.hasValue() implies name.matches('[A-Za-z][A-Za-z0-9\\_]{0,63}')

Terminology Bindings

Path ValueSet Type Documentation
Expression.language ExpressionLanguage Extensible

The media type of the expression language.

  http://hl7.org/fhir/ValueSet/mimetypes maximum

Language support

While the expression data type supports any language, a few specific languages defined by HL7 at particularly of interest for the purposes of this specification:

Expression is used in the following places: TriggerDefinition , ActivityDefinition , ChargeItemDefinition , ClinicalUseDefinition , Consent , EvidenceVariable , Group , Measure , Parameters , Permission , PlanDefinition and , RequestOrchestration and Task

 

2.1.28.6.0.7 2.1.27.5.0.7 UsageContext

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The UsageContext structure defines the context of use for a module.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . UsageContext Σ TU N Element Describes the context of use for a conformance or knowledge resource

Elements defined in Ancestors: id , extension
. . . code Σ 1..1 Coding Type of context being specified
Binding: UsageContextType icon ( Extensible )
. . . value[x] Σ 1..1 Value that defines the context
Binding: Context of Use ValueSet ( Example )
. . . . valueCodeableConcept CodeableConcept
. . . . valueQuantity Quantity
. . . . valueRange Range
. . . . valueReference Reference ( PlanDefinition | ResearchStudy | InsurancePlan | HealthcareService | Group | Location | Organization )

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

<UsageContext xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <</code>

 <code><!-- 1..1 Coding Type of context being specified icon --></code>

 <value[x]><!-- 1..1 CodeableConcept|Quantity|Range|Reference(Group|
   HealthcareService|InsurancePlan|Location|Organization|PlanDefinition|
   ResearchStudy) Value that defines the context --></value[x]>
</UsageContext>

JSON Template 

{doco
  // from Element: extension
  "

  "code" : { Coding }, // R!  Type of context being specified icon

  // value[x]: Value that defines the context. One of these 4:
  "valueCodeableConcept" : { CodeableConcept },
  "valueQuantity" : { Quantity },
  "valueRange" : { Range },
  "valueReference" : { Reference(Group|HealthcareService|InsurancePlan|Location|
   Organization|PlanDefinition|ResearchStudy) }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:code [ Coding ] ; # 1..1 Type of context being specified
  # value[x] : 1..1 Value that defines the context. One of these 4
    fhir:value [  a fhir:CodeableConcept ; CodeableConcept ]
    fhir:value [  a fhir:Quantity ; Quantity ]
    fhir:value [  a fhir:Range ; Range ]
    fhir:value [  a fhir:Reference ; Reference(Group|HealthcareService|InsurancePlan|Location|Organization|PlanDefinition|
  ResearchStudy) ]
]

Changes since Release 3

Changes from both R4 and R4B

UsageContext
UsageContext.code
  • Change value set from http://hl7.org/fhir/ValueSet/usage-context-type to UsageContextType icon

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . UsageContext Σ TU N Element Describes the context of use for a conformance or knowledge resource

Elements defined in Ancestors: id , extension
. . . code Σ 1..1 Coding Type of context being specified
Binding: UsageContextType icon ( Extensible )
. . . value[x] Σ 1..1 Value that defines the context
Binding: Context of Use ValueSet ( Example )
. . . . valueCodeableConcept CodeableConcept
. . . . valueQuantity Quantity
. . . . valueRange Range
. . . . valueReference Reference ( PlanDefinition | ResearchStudy | InsurancePlan | HealthcareService | Group | Location | Organization )

doco Documentation for this format icon

XML Template 

<UsageContext xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <</code>

 <code><!-- 1..1 Coding Type of context being specified icon --></code>

 <value[x]><!-- 1..1 CodeableConcept|Quantity|Range|Reference(Group|
   HealthcareService|InsurancePlan|Location|Organization|PlanDefinition|
   ResearchStudy) Value that defines the context --></value[x]>
</UsageContext>

JSON Template 

{doco
  // from Element: extension
  "

  "code" : { Coding }, // R!  Type of context being specified icon

  // value[x]: Value that defines the context. One of these 4:
  "valueCodeableConcept" : { CodeableConcept },
  "valueQuantity" : { Quantity },
  "valueRange" : { Range },
  "valueReference" : { Reference(Group|HealthcareService|InsurancePlan|Location|
   Organization|PlanDefinition|ResearchStudy) }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:code [ Coding ] ; # 1..1 Type of context being specified
  # value[x] : 1..1 Value that defines the context. One of these 4
    fhir:value [  a fhir:CodeableConcept ; CodeableConcept ]
    fhir:value [  a fhir:Quantity ; Quantity ]
    fhir:value [  a fhir:Range ; Range ]
    fhir:value [  a fhir:Reference ; Reference(Group|HealthcareService|InsurancePlan|Location|Organization|PlanDefinition|
  ResearchStudy) ]
]

Changes since Release 3

Changes from both R4 and R4B

UsageContext
UsageContext.code
  • Change value set from http://hl7.org/fhir/ValueSet/usage-context-type to UsageContextType icon

See the Full Difference for further information

Constraints

Terminology Bindings

Path ValueSet Type Documentation
UsageContext.code UsageContextType icon Extensible

A code that specifies a type of context being specified by a usage context.

UsageContext.value[x] ContextOfUseValueSet Example

This value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts.

UsageContext is used in the following places: ElementDefinition , ActivityDefinition , ActorDefinition , CanonicalResource , CapabilityStatement , ChargeItemDefinition , Citation , CodeSystem , CompartmentDefinition , Composition , ConceptMap , ConditionDefinition , DeviceDefinition , EventDefinition , Evidence , EvidenceReport , EvidenceVariable , ExampleScenario , GraphDefinition Group , ImplementationGuide , Library , Measure , MessageDefinition , NamingSystem , ObservationDefinition , OperationDefinition , Parameters , PlanDefinition , Questionnaire , Requirements , SearchParameter , SpecimenDefinition , StructureDefinition , StructureMap , SubscriptionTopic , Task , TerminologyCapabilities , TestPlan , TestScript and ValueSet

2.1.28.6.0.8 2.1.27.5.0.8 ExtendedContactDetail

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The ExtendedContactDetail structure defines extended contact details for a named, or unnamed individual/purpose.

These are extensively used in provider directory resources where contact information is often very rich in nature, and requires additional metadata around their usage.
This datatype permits the context of the contact informations use to be provided, and groups them together with other important metadata.

Not all properties are expected to be present in all instances, and only the ones that apply.
e.g. e.g., A website contact will only have the telecom included, but might also include a purpose and possibly a period if required. Whereas an accounts contact detail could include their name, postal address and telephone number (and possibly Organization if it was an outsourced capability)

The period provides the general start and end of the contact's applicability for usage. This is not intended to store a history of usages over time, but a convenient way to record upcoming relevant changes to the content when it is being published.
This permits a contact to be marked as becoming available from X, or is expected to no longer be available from Y. An extension may be used to mark a contact's general availability times (9am - 5pm) and also exceptions where the contact is not available (e.g. (e.g., Public holidays)

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ExtendedContactDetail Σ TU N Element Contact information

Elements defined in Ancestors: id , extension
. . . purpose Σ 0..1 CodeableConcept The type of contact
Binding: Contact entity type icon ( Preferred )
. . . name Σ 0..* HumanName Name of an individual to contact

. . . telecom Σ 0..* ContactPoint Contact details (e.g.phone/fax/url)

. . . organization Σ 0..1 Reference ( Organization ) This contact detail is handled/monitored by a specific organization
. . . period Σ 0..1 Period Period that this contact was valid for usage

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

<ExtendedContactDetail xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <</purpose>

 <purpose><!-- 0..1 CodeableConcept The type of contact icon --></purpose>

 <name><!-- 0..* HumanName Name of an individual to contact --></name>
 <telecom><!-- 0..* ContactPoint Contact details (e.g.phone/fax/url) --></telecom>
 <address><!-- 0..1 Address Address for the contact --></address>
 <organization><!-- 0..1 Reference(Organization) This contact detail is handled/monitored by a specific organization --></organization>
 <period><!-- 0..1 Period Period that this contact was valid for usage --></period>
</ExtendedContactDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:purpose [ CodeableConcept ] ; # 0..1 The type of contact
  fhir:name  ( [ HumanName ] ... ) ; # 0..* Name of an individual to contact
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* Contact details (e.g.phone/fax/url)
  fhir:address [ Address ] ; # 0..1 Address for the contact
  fhir:organization [ Reference(Organization) ] ; # 0..1 This contact detail is handled/monitored by a specific organization
  fhir:period [ Period ] ; # 0..1 Period that this contact was valid for usage
]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . ExtendedContactDetail Σ TU N Element Contact information

Elements defined in Ancestors: id , extension
. . . purpose Σ 0..1 CodeableConcept The type of contact
Binding: Contact entity type icon ( Preferred )
. . . name Σ 0..* HumanName Name of an individual to contact

. . . telecom Σ 0..* ContactPoint Contact details (e.g.phone/fax/url)

. . . organization Σ 0..1 Reference ( Organization ) This contact detail is handled/monitored by a specific organization
. . . period Σ 0..1 Period Period that this contact was valid for usage

doco Documentation for this format icon

XML Template 

<ExtendedContactDetail xmlns="http://hl7.org/fhir">
 <!-- from Element: extension -->
 <</purpose>

 <purpose><!-- 0..1 CodeableConcept The type of contact icon --></purpose>

 <name><!-- 0..* HumanName Name of an individual to contact --></name>
 <telecom><!-- 0..* ContactPoint Contact details (e.g.phone/fax/url) --></telecom>
 <address><!-- 0..1 Address Address for the contact --></address>
 <organization><!-- 0..1 Reference(Organization) This contact detail is handled/monitored by a specific organization --></organization>
 <period><!-- 0..1 Period Period that this contact was valid for usage --></period>
</ExtendedContactDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:purpose [ CodeableConcept ] ; # 0..1 The type of contact
  fhir:name  ( [ HumanName ] ... ) ; # 0..* Name of an individual to contact
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* Contact details (e.g.phone/fax/url)
  fhir:address [ Address ] ; # 0..1 Address for the contact
  fhir:organization [ Reference(Organization) ] ; # 0..1 This contact detail is handled/monitored by a specific organization
  fhir:period [ Period ] ; # 0..1 Period that this contact was valid for usage
]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Constraints

Terminology Bindings

Path ValueSet Type Documentation
ExtendedContactDetail.purpose ContactEntityType icon Preferred

This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.

ExtendedContactDetail is used in the following places: VirtualServiceDetail , HealthcareService , InsurancePlan InsuranceProduct , Location , Organization , OrganizationAffiliation and PractitionerRole

2.1.28.6.0.9 2.1.27.5.0.9 VirtualServiceDetail

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The VirtualServiceDetail structure defines details of a virtual communication capability, such as a web conference call.

Structure

Address
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . VirtualServiceDetail Σ TU N Element Virtual Service Contact Details

Elements defined in Ancestors: id , extension
. . . channelType Σ 0..1 Coding Channel Type
Binding: Virtual Service Type ( Example )
. . . address[x] Σ 0..1 Contact address/number
. . . . addressUrl url
. . . . addressString string
. . . . addressContactPoint ContactPoint
. . . . addressExtendedContactDetail ExtendedContactDetail
. . . additionalInfo Σ 0..* url Web address to see alternative connection details

. . . sessionKey Σ 0..1 string Session Key required by the virtual service

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

< xmlns="http://hl7.org/fhir">

<VirtualServiceDetail xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <channelType><!-- 0..1 Coding Channel Type --></channelType>
 <address[x]><!-- 0..1 url|string|ContactPoint|ExtendedContactDetail Contact address/number --></address[x]>
 <
 <
 <

 <additionalInfo value="[url]"/><!-- 0..* Web address to see alternative connection details -->
 <maxParticipants value="[positiveInt]"/><!-- 0..1 Maximum number of participants supported by the virtual service -->
 <sessionKey value="[string]"/><!-- 0..1 Session Key required by the virtual service -->

</VirtualServiceDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:channelType [ Coding ] ; # 0..1 Channel Type
  # address[x] : 0..1 Contact address/number. One of these 4
    fhir: ]
    fhir: ]

    fhir:address [  a fhir:Url ; url ]
    fhir:address [  a fhir:String ; string ]

    fhir:address [  a fhir:ContactPoint ; ContactPoint ]
    fhir:address [  a fhir:ExtendedContactDetail ; ExtendedContactDetail ]
  fhir:
  fhir:
  fhir:

  fhir:additionalInfo  ( [ url ] ... ) ; # 0..* Web address to see alternative connection details
  fhir:maxParticipants [ positiveInt ] ; # 0..1 Maximum number of participants supported by the virtual service
  fhir:sessionKey [ string ] ; # 0..1 Session Key required by the virtual service

]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Structure

Address
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . VirtualServiceDetail Σ TU N Element Virtual Service Contact Details

Elements defined in Ancestors: id , extension
. . . channelType Σ 0..1 Coding Channel Type
Binding: Virtual Service Type ( Example )
. . . address[x] Σ 0..1 Contact address/number
. . . . addressUrl url
. . . . addressString string
. . . . addressContactPoint ContactPoint
. . . . addressExtendedContactDetail ExtendedContactDetail
. . . additionalInfo Σ 0..* url Web address to see alternative connection details

. . . sessionKey Σ 0..1 string Session Key required by the virtual service

doco Documentation for this format icon

XML Template 

< xmlns="http://hl7.org/fhir">

<VirtualServiceDetail xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <channelType><!-- 0..1 Coding Channel Type --></channelType>
 <address[x]><!-- 0..1 url|string|ContactPoint|ExtendedContactDetail Contact address/number --></address[x]>
 <
 <
 <

 <additionalInfo value="[url]"/><!-- 0..* Web address to see alternative connection details -->
 <maxParticipants value="[positiveInt]"/><!-- 0..1 Maximum number of participants supported by the virtual service -->
 <sessionKey value="[string]"/><!-- 0..1 Session Key required by the virtual service -->

</VirtualServiceDetail>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 

 # from Element: fhir:extension

  fhir:channelType [ Coding ] ; # 0..1 Channel Type
  # address[x] : 0..1 Contact address/number. One of these 4
    fhir: ]
    fhir: ]

    fhir:address [  a fhir:Url ; url ]
    fhir:address [  a fhir:String ; string ]

    fhir:address [  a fhir:ContactPoint ; ContactPoint ]
    fhir:address [  a fhir:ExtendedContactDetail ; ExtendedContactDetail ]
  fhir:
  fhir:
  fhir:

  fhir:additionalInfo  ( [ url ] ... ) ; # 0..* Web address to see alternative connection details
  fhir:maxParticipants [ positiveInt ] ; # 0..1 Maximum number of participants supported by the virtual service
  fhir:sessionKey [ string ] ; # 0..1 Session Key required by the virtual service

]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Constraints

Terminology Bindings

Path ValueSet Type Documentation
VirtualServiceDetail.channelType VirtualServiceType Example

Example codes for possible virtual service connection types.

VirtualServiceDetail is used in the following places: Appointment , Encounter and Location

2.1.28.6.0.10 2.1.27.5.0.10 Availability

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The Availability structure defines a pattern of availability data typically used in directory resources.

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Availability Σ TU N Element Availability data for an {item}

Elements defined in Ancestors: id , extension
. . . period Σ 0..1 Period When the availability applies
. . . availableTime Σ C 0..* Element Times the {item} is available
+ Rule: Cannot include start/end times when selecting all day availability.

. . . . daysOfWeek Σ 0..* code mon | tue | wed | thu | fri | sat | sun
Binding: Days Of Week ( Required )

. . . . allDay Σ C 0..1 boolean Always available? i.e. 24 hour service
. . . . availableStartTime Σ C 0..1 time Opening time of day (ignored if allDay = true)
. . . . availableEndTime Σ C 0..1 time Closing time of day (ignored if allDay = true)
. . . notAvailableTime Σ 0..* Element Not available during this time due to provided reason

. . . . description Σ 0..1 string Reason presented to the user explaining why time not available
. . . . during Σ 0..1 Period Service not available during this period

doco Documentation for this format icon

Definition: XML | JSON

UML Diagram ( Legend )

Availability The period of time when the availability is applicable. For example, you might use this property to indicate the period during the holiday season when you close an hour early period : Period [0..1] AvailableTime mon | tue | wed | thu | fri | sat | sun Indicates which days of the week are available between the start and end Times daysOfWeek : code [0..*] « The purpose for which an extended contact detail should be used. (Strength=Required) DaysOfWeek ! » Always Is this always available? (hence times are irrelevant) i.e. 24 hour service allDay : boolean [0..1] « This element has or is affected by some invariants C » Opening The opening time of day (ignored if allDay = true) day. Note: If the AllDay flag is set, then this time is ignored availableStartTime : time [0..1] « This element has or is affected by some invariants C » Closing The closing time of day (ignored if allDay = true) day. Note: If the AllDay flag is set, then this time is ignored availableEndTime : time [0..1] « This element has or is affected by some invariants C » NotAvailableTime Reason The reason that can be presented to the user explaining as to why this time is not available description : string [0..1] Service The {item} is not available (seasonally or for a public holiday) during this period during : Period [0..1] DataType Times A collection of times that the {item} is available availableTime [0..*] Not The {item} is not available during this period of time due to the provided reason notAvailableTime [0..*]

XML Template 

< xmlns="http://hl7.org/fhir">

<Availability xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
  <
  <
  <
  <

 <period><!-- 0..1 Period When the availability applies --></period>
 <availableTime>  <!-- 0..* Times the {item} is available -->
  <daysOfWeek value="[code]"/><!-- 0..* mon | tue | wed | thu | fri | sat | sun -->
  <allDay value="[boolean]"/><!-- I 0..1 Always available? i.e. 24 hour service -->
  <availableStartTime value="[time]"/><!-- I 0..1 Opening time of day (ignored if allDay = true) -->
  <availableEndTime value="[time]"/><!-- I 0..1 Closing time of day (ignored if allDay = true) -->

 </availableTime>
 <
  <
  <</during>

 <notAvailableTime>  <!-- 0..* Not available during this time due to provided reason -->
  <description value="[string]"/><!-- 0..1 Reason presented to the user explaining why time not available -->
  <during><!-- 0..1 Period Service not available during this period --></during>

 </notAvailableTime>
</Availability>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
    fhir:
    fhir:
    fhir:
    fhir:

 # from Element: fhir:extension
  fhir:period [ Period ] ; # 0..1 When the availability applies
  fhir:availableTime ( [ # 0..* Times the {item} is available
    fhir:daysOfWeek  ( [ code ] ... ) ; # 0..* mon | tue | wed | thu | fri | sat | sun
    fhir:allDay [ boolean ] ; # 0..1 I Always available? i.e. 24 hour service
    fhir:availableStartTime [ time ] ; # 0..1 I Opening time of day (ignored if allDay = true)
    fhir:availableEndTime [ time ] ; # 0..1 I Closing time of day (ignored if allDay = true)

  ] ... ) ;
  fhir:
    fhir:
    fhir:

  fhir:notAvailableTime ( [ # 0..* Not available during this time due to provided reason
    fhir:description [ string ] ; # 0..1 Reason presented to the user explaining why time not available
    fhir:during [ Period ] ; # 0..1 Service not available during this period

  ] ... ) ;
]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Structure

Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Availability Σ TU N Element Availability data for an {item}

Elements defined in Ancestors: id , extension
. . . period Σ 0..1 Period When the availability applies
. . . availableTime Σ C 0..* Element Times the {item} is available
+ Rule: Cannot include start/end times when selecting all day availability.

. . . . daysOfWeek Σ 0..* code mon | tue | wed | thu | fri | sat | sun
Binding: Days Of Week ( Required )

. . . . allDay Σ C 0..1 boolean Always available? i.e. 24 hour service
. . . . availableStartTime Σ C 0..1 time Opening time of day (ignored if allDay = true)
. . . . availableEndTime Σ C 0..1 time Closing time of day (ignored if allDay = true)
. . . notAvailableTime Σ 0..* Element Not available during this time due to provided reason

. . . . description Σ 0..1 string Reason presented to the user explaining why time not available
. . . . during Σ 0..1 Period Service not available during this period

doco Documentation for this format icon

UML Diagram ( Legend )

Availability The period of time when the availability is applicable. For example, you might use this property to indicate the period during the holiday season when you close an hour early period : Period [0..1] AvailableTime mon | tue | wed | thu | fri | sat | sun Indicates which days of the week are available between the start and end Times daysOfWeek : code [0..*] « The purpose for which an extended contact detail should be used. (Strength=Required) DaysOfWeek ! » Always Is this always available? (hence times are irrelevant) i.e. 24 hour service allDay : boolean [0..1] « This element has or is affected by some invariants C » Opening The opening time of day (ignored if allDay = true) day. Note: If the AllDay flag is set, then this time is ignored availableStartTime : time [0..1] « This element has or is affected by some invariants C » Closing The closing time of day (ignored if allDay = true) day. Note: If the AllDay flag is set, then this time is ignored availableEndTime : time [0..1] « This element has or is affected by some invariants C » NotAvailableTime Reason The reason that can be presented to the user explaining as to why this time is not available description : string [0..1] Service The {item} is not available (seasonally or for a public holiday) during this period during : Period [0..1] DataType Times A collection of times that the {item} is available availableTime [0..*] Not The {item} is not available during this period of time due to the provided reason notAvailableTime [0..*]

XML Template 

< xmlns="http://hl7.org/fhir">

<Availability xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
  <
  <
  <
  <

 <period><!-- 0..1 Period When the availability applies --></period>
 <availableTime>  <!-- 0..* Times the {item} is available -->
  <daysOfWeek value="[code]"/><!-- 0..* mon | tue | wed | thu | fri | sat | sun -->
  <allDay value="[boolean]"/><!-- I 0..1 Always available? i.e. 24 hour service -->
  <availableStartTime value="[time]"/><!-- I 0..1 Opening time of day (ignored if allDay = true) -->
  <availableEndTime value="[time]"/><!-- I 0..1 Closing time of day (ignored if allDay = true) -->

 </availableTime>
 <
  <
  <</during>

 <notAvailableTime>  <!-- 0..* Not available during this time due to provided reason -->
  <description value="[string]"/><!-- 0..1 Reason presented to the user explaining why time not available -->
  <during><!-- 0..1 Period Service not available during this period --></during>

 </notAvailableTime>
</Availability>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
    fhir:
    fhir:
    fhir:
    fhir:

 # from Element: fhir:extension
  fhir:period [ Period ] ; # 0..1 When the availability applies
  fhir:availableTime ( [ # 0..* Times the {item} is available
    fhir:daysOfWeek  ( [ code ] ... ) ; # 0..* mon | tue | wed | thu | fri | sat | sun
    fhir:allDay [ boolean ] ; # 0..1 I Always available? i.e. 24 hour service
    fhir:availableStartTime [ time ] ; # 0..1 I Opening time of day (ignored if allDay = true)
    fhir:availableEndTime [ time ] ; # 0..1 I Closing time of day (ignored if allDay = true)

  ] ... ) ;
  fhir:
    fhir:
    fhir:

  fhir:notAvailableTime ( [ # 0..* Not available during this time due to provided reason
    fhir:description [ string ] ; # 0..1 Reason presented to the user explaining why time not available
    fhir:during [ Period ] ; # 0..1 Service not available during this period

  ] ... ) ;
]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Constraints

id Level Location Description Expression
img  av-1 Rule Availability.availableTime Cannot include start/end times when selecting all day availability. allDay.exists().not() or (allDay implies availableStartTime.exists().not() and availableEndTime.exists().not())

Terminology Bindings

Path ValueSet Type Documentation
Availability.availableTime.daysOfWeek DaysOfWeek Required

The days of the week.

Availability is used in the following places: Endpoint , HealthcareService , Location and PractitionerRole

2.1.28.6.0.11 2.1.27.5.0.11 MonetaryComponent

FHIR Infrastructure Work Group Maturity Level : 5 Standards Status : Trial Use

See also Examples , Detailed Descriptions , Mappings , Profiles , Extensions and R4 Conversions Extensions

The MonetaryComponent structure defines a the set of properties across the financial resources.

This component is typically used in a list where each value provides a different type of value contributing to the final value used in line items on a financial transaction.
For example, a line item for a product might include the net price, the tax amount, and the surcharge amount as separate components.

Structure

Availability data for an {item}
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . MonetaryComponent Σ TU N Element Types and value of financial information that apply to line item(s)

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code base | surcharge | deduction | discount | tax | informational
Binding: Price Component Type ( Required )
. . . code Σ 0..1 CodeableConcept Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.
. . . factor Σ 0..1 decimal Factor used for calculating this component

doco Documentation for this format icon

Definition: XML | JSON

XML Template 

< xmlns="http://hl7.org/fhir">

<MonetaryComponent xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
 <</code>
 <
 <</amount>

 <type value="[code]"/><!-- 1..1 base | surcharge | discount | tax | informational -->
 <code><!-- 0..1 CodeableConcept Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc. --></code>
 <factor value="[decimal]"/><!-- 0..1 Factor used for calculating this component -->
 <amount><!-- 0..1 Money Explicit value amount to be used --></amount>

</MonetaryComponent>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:
  fhir:
  fhir:

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 base | surcharge | discount | tax | informational
  fhir:code [ CodeableConcept ] ; # 0..1 Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.
  fhir:factor [ decimal ] ; # 0..1 Factor used for calculating this component
  fhir:amount [ Money ] ; # 0..1 Explicit value amount to be used

]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Structure

Availability data for an {item}
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . MonetaryComponent Σ TU N Element Types and value of financial information that apply to line item(s)

Elements defined in Ancestors: id , extension
. . . type Σ 1..1 code base | surcharge | deduction | discount | tax | informational
Binding: Price Component Type ( Required )
. . . code Σ 0..1 CodeableConcept Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.
. . . factor Σ 0..1 decimal Factor used for calculating this component

doco Documentation for this format icon

XML Template 

< xmlns="http://hl7.org/fhir">

<MonetaryComponent xmlns="http://hl7.org/fhir">

 <!-- from Element: extension -->
 <
 <</code>
 <
 <</amount>

 <type value="[code]"/><!-- 1..1 base | surcharge | discount | tax | informational -->
 <code><!-- 0..1 CodeableConcept Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc. --></code>
 <factor value="[decimal]"/><!-- 0..1 Factor used for calculating this component -->
 <amount><!-- 0..1 Money Explicit value amount to be used --></amount>

</MonetaryComponent>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

[
 # from Element: 
  fhir:
  fhir:
  fhir:
  fhir:

 # from Element: fhir:extension
  fhir:type [ code ] ; # 1..1 base | surcharge | discount | tax | informational
  fhir:code [ CodeableConcept ] ; # 0..1 Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.
  fhir:factor [ decimal ] ; # 0..1 Factor used for calculating this component
  fhir:amount [ Money ] ; # 0..1 Explicit value amount to be used

]

Changes since Release 3

Changes from both R4 and R4B

This complex-type did not exist in Release R4

See the Full Difference for further information

Constraints

Terminology Bindings

Path ValueSet Type Documentation
MonetaryComponent.type PriceComponentType Required

Codes indicating the kind of the price component.

MonetaryComponent.code Unknown No details provided yet Example Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.

MonetaryComponent is used in the following places: ChargeItem , ChargeItemDefinition and Invoice