Vulcan ePI FHIR Implementation Guide
0.1.0 - CI Build

Vulcan ePI FHIR Implementation Guide - Local Development build (v0.1.0). See the Directory of published versions

Resource Profile: List - ePI

Official URL: http://hl7.org/fhir/uv/vulcan-epi/StructureDefinition/List-uv-epi Version: 0.1.0
Active as of 2022-09-02 Computable Name: ListUvEpi

This profile represents the constraints applied to the List resource by the Electronic Product Information (ePI) FHIR Implementation Guide.

An electronic product information (ePI) is authorised, statutory product information for medicines (i.e. summary of product characteristics, package leaflet and labelling) in a semi-structured format created using the common EU electronic standard.

Usage:

  • This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from List

Summary

Mandatory: 1 element
Prohibited: 3 elements

Structures

This structure refers to these other structures:

This structure is derived from List

NameFlagsCard.TypeDescription & Constraintsdoco
.. List 0..*ListElectronic Product Information List
... identifier 1..*IdentifierBusiness identifier
... status 1..1codecurrent | retired | entered-in-error
Example general: current
... mode 1..1codeworking | snapshot | changes
Example general: working
... code 0..1CodeableConceptWhat the purpose of this list is
Required Pattern: At least the following
.... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
..... system1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
..... code1..1codeSymbol in syntax defined by the system
Fixed Value: X-EPI
... subject 0..0
... encounter 0..0
... date 0..1dateTimeWhen the list was prepared.
... orderedBy 0..1CodeableConceptWhat order the list has
Example general: entry-date
... entry
.... flag 0..1CodeableConceptStatus of this ePI
Binding: CompositionStatus (required)
.... date 0..1dateTimeWhen the ePI was added to the list
.... item 1..1Reference(Bundle - ePI)Actual entry
... emptyReason 0..0

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. List I0..*ListElectronic Product Information List
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 1..*IdentifierBusiness identifier
... status ?!Σ1..1codecurrent | retired | entered-in-error
Binding: ListStatus (required): The current state of the list.


Example general: current
... mode ?!Σ1..1codeworking | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this list.


Example general: working
... title Σ0..1stringName of the list
Example General: Dr. Jane's Patients
... code Σ0..1CodeableConceptWhat the purpose of this list is
Binding: ExampleUseCodesForList (example): What the purpose of a list is.


Required Pattern: At least the following
.... id0..1stringUnique id for inter-element referencing
.... extension0..*ExtensionAdditional content defined by implementations
.... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... system1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
..... version0..1stringVersion of the system - if relevant
..... code1..1codeSymbol in syntax defined by the system
Fixed Value: X-EPI
..... display0..1stringRepresentation defined by the system
..... userSelected0..1booleanIf this coding was chosen directly by the user
.... text0..1stringPlain text representation of the concept
... date Σ0..1dateTimeWhen the list was prepared.
... source Σ0..1Reference(Practitioner | PractitionerRole | Patient | Device)Who and/or what defined the list contents (aka Author)
... orderedBy 0..1CodeableConceptWhat order the list has
Binding: ListOrderCodes (preferred): What order applies to the items in a list.


Example general: entry-date
... note 0..*AnnotationComments about the list
... entry I0..*BackboneElementEntries in the list
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... flag 0..1CodeableConceptStatus of this ePI
Binding: CompositionStatus (required)
.... deleted ?!I0..1booleanIf this item is actually marked as deleted
.... date 0..1dateTimeWhen the ePI was added to the list
.... item 1..1Reference(Bundle - ePI)Actual entry

doco Documentation for this format

This structure is derived from List

Summary

Mandatory: 1 element
Prohibited: 3 elements

Structures

This structure refers to these other structures:

Differential View

This structure is derived from List

NameFlagsCard.TypeDescription & Constraintsdoco
.. List 0..*ListElectronic Product Information List
... identifier 1..*IdentifierBusiness identifier
... status 1..1codecurrent | retired | entered-in-error
Example general: current
... mode 1..1codeworking | snapshot | changes
Example general: working
... code 0..1CodeableConceptWhat the purpose of this list is
Required Pattern: At least the following
.... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
..... system1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
..... code1..1codeSymbol in syntax defined by the system
Fixed Value: X-EPI
... subject 0..0
... encounter 0..0
... date 0..1dateTimeWhen the list was prepared.
... orderedBy 0..1CodeableConceptWhat order the list has
Example general: entry-date
... entry
.... flag 0..1CodeableConceptStatus of this ePI
Binding: CompositionStatus (required)
.... date 0..1dateTimeWhen the ePI was added to the list
.... item 1..1Reference(Bundle - ePI)Actual entry
... emptyReason 0..0

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. List I0..*ListElectronic Product Information List
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 1..*IdentifierBusiness identifier
... status ?!Σ1..1codecurrent | retired | entered-in-error
Binding: ListStatus (required): The current state of the list.


Example general: current
... mode ?!Σ1..1codeworking | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this list.


Example general: working
... title Σ0..1stringName of the list
Example General: Dr. Jane's Patients
... code Σ0..1CodeableConceptWhat the purpose of this list is
Binding: ExampleUseCodesForList (example): What the purpose of a list is.


Required Pattern: At least the following
.... id0..1stringUnique id for inter-element referencing
.... extension0..*ExtensionAdditional content defined by implementations
.... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... system1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
..... version0..1stringVersion of the system - if relevant
..... code1..1codeSymbol in syntax defined by the system
Fixed Value: X-EPI
..... display0..1stringRepresentation defined by the system
..... userSelected0..1booleanIf this coding was chosen directly by the user
.... text0..1stringPlain text representation of the concept
... date Σ0..1dateTimeWhen the list was prepared.
... source Σ0..1Reference(Practitioner | PractitionerRole | Patient | Device)Who and/or what defined the list contents (aka Author)
... orderedBy 0..1CodeableConceptWhat order the list has
Binding: ListOrderCodes (preferred): What order applies to the items in a list.


Example general: entry-date
... note 0..*AnnotationComments about the list
... entry I0..*BackboneElementEntries in the list
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... flag 0..1CodeableConceptStatus of this ePI
Binding: CompositionStatus (required)
.... deleted ?!I0..1booleanIf this item is actually marked as deleted
.... date 0..1dateTimeWhen the ePI was added to the list
.... item 1..1Reference(Bundle - ePI)Actual entry

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSet / Code
List.languagepreferredCommonLanguages
Max Binding: AllLanguages
List.statusrequiredListStatus
List.moderequiredListMode
List.codeexamplePattern: LOINC code X-EPI
List.orderedBypreferredListOrderCodes
List.entry.flagrequiredCompositionStatus