|
3 min read

FHIR Profiling: Extensions

Summarize this blog post with:

FHIR Extensions in Profiles

In FHIR, you can define a profile not only for a resource but also for an extension. A profile on an extension allows for restricting the acceptable types of extension values, specifying a binding for a coded value, and describing the validation of the value using FHIRPath.

Example of how to describe your own extension that describes a patient’s place of birth:

POST /fhir/StructureDefinition

resourceType: StructureDefinition
id: my-extension
type: Extension
baseDefinition: http://hl7.org/fhir/StructureDefinition/Extension
url: http://example.org/fhir/StructureDefinition/my-extension
name: MyExtension
kind: complex-type
abstract: false
derivation: constraint
differential:
  element:
   - id: Extension.url
     path: Extension.url
     fixedUri: http://example.org/fhir/StructureDefinition/patient-birthPlace
   - id: Extension.value[x]
     path: Extension.value[x]
     min: 1
     type:
      - code: string

See also: Extending FHIR Resources and FHIR Profiling.

Comments
Comments
Sign in
Loading comments...
Subscribe to our blog

Get the latest articles on FHIR, interoperability, and healthcare IT.