This
page
is
part
of
the
FHIR
Specification
v6.0.0-ballot3:
Release
6
Ballot
(3rd
Draft)
(see
Ballot
Notes
).
The
current
version
is
5.0.0
.
For
a
full
list
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
Responsible
Owner:
FHIR
Infrastructure
|
|
A pattern to be followed by resources that represent a product used in healthcare, for clinical or operational purposes.
This is NOT a resource. It is not part of the FHIR schema and cannot appear directly in FHIR instances. It is a logical model that defines a pattern adhered to by other resources. This pattern serves two purposes:
A "Healthcare Product" represents any type of product, manufactured or not, regulated or not, that is used in healthcare, for clinical or operational purposes. The Product pattern provides an abstraction with the common characteristics of Healthcare Products.
Note to Implementers: The Product pattern is being developed. The committee is looking for feedback on this pattern as well as its applicability to the different product resources - Medication, Device, BiologicallyDerivedProduct, Substance, etc.
The Product pattern is instantiated in resources like Medication, Device, etc., and it is used in requesting a product (xxxRequest resources), or reporting a delivery or a usage (xxxUsage resources), or in a procedure.
This model represents a pattern. It provides a standard list of data elements with cardinalities, data types, definitions, rationale and usage notes that will ideally be adhered to by resources that fall into the "product" workflow category. However, adherence to this pattern is not mandatory. Not all healthcare domains are the same. Concepts that may be generally applicable (and thus are included in this standard pattern) might still not be relevant everywhere or may be sufficiently uncommon that they are more appropriate to include as extensions than as core properties of the resource. Work groups are encouraged to adjust descriptions, usage notes and rationale to be specific to their resource. As well, design notes in the comments column marked with [square brackets] identifies areas where domain variation is expected and encouraged. Other variation, including differences in names, cardinalities, data types and the decision to omit an element outright are also possible, but should be discussed with the FHIR Infrastructure work group's Workflow project to ensure the rationale for non-alignment is understood, to confirm that the deviation is necessary and to identify whether any adjustments to the pattern are appropriate.
This pattern provides a linkage to the W5 list of standard data elements. Resources that adhere to this pattern should ensure their w5 mappings are consistent, as is their data element ordering.
No references for this Pattern.
Structure
| Name | Flags | Card. | Type |
Description
&
Constraints
Filter:
|
|---|---|---|---|---|
|
I | Logical |
Product
Pattern
|
|
|
?! Σ | 1..1 | code |
active
|
inactive
|
entered-in-error
Binding: ProductStatus ( Required ) |
|
Σ | 0..* | CodeableConcept |
A
category
or
class
of
the
product
|
|
Σ | 0..1 | CodeableConcept |
A
code
designating
a
specific
type
of
product
|
|
Σ | 0..* | Reference ( Organization ) |
Manufacturer,
representative
or
officially
responsible
for
the
product
|
|
0..1 | BackboneElement |
One
or
several
physical
instances
or
occurrences
of
the
product
|
|
|
0..1 | SimpleQuantity |
The
amount
of
items
|
|
|
0..* | Identifier |
The
identifier
for
the
physical
instance,
typically
a
serial
number
|
|
|
0..1 | string |
The
identification
of
the
batch
or
lot
of
the
product
|
|
|
0..1 | dateTime |
The
expiry
date
or
date
and
time
for
the
product
|
|
|
Σ | 0..1 | Reference ( Patient | Group ) |
Individual
the
product
is
associated
with,
or
which
has
used
the
product
|
|
0..* | Annotation |
Comments
made
about
the
product
|
|
Documentation
for
this
format
|
||||
UML Diagram ( Legend )
Structure
| Name | Flags | Card. | Type |
Description
&
Constraints
Filter:
|
|---|---|---|---|---|
|
I | Logical |
Product
Pattern
|
|
|
?! Σ | 1..1 | code |
active
|
inactive
|
entered-in-error
Binding: ProductStatus ( Required ) |
|
Σ | 0..* | CodeableConcept |
A
category
or
class
of
the
product
|
|
Σ | 0..1 | CodeableConcept |
A
code
designating
a
specific
type
of
product
|
|
Σ | 0..* | Reference ( Organization ) |
Manufacturer,
representative
or
officially
responsible
for
the
product
|
|
0..1 | BackboneElement |
One
or
several
physical
instances
or
occurrences
of
the
product
|
|
|
0..1 | SimpleQuantity |
The
amount
of
items
|
|
|
0..* | Identifier |
The
identifier
for
the
physical
instance,
typically
a
serial
number
|
|
|
0..1 | string |
The
identification
of
the
batch
or
lot
of
the
product
|
|
|
0..1 | dateTime |
The
expiry
date
or
date
and
time
for
the
product
|
|
|
Σ | 0..1 | Reference ( Patient | Group ) |
Individual
the
product
is
associated
with,
or
which
has
used
the
product
|
|
0..* | Annotation |
Comments
made
about
the
product
|
|
Documentation
for
this
format
|
||||
Alternate definitions: Master Definition XML + JSON .
| Path | ValueSet | Type | Documentation |
|---|---|---|---|
| Product.status | ProductStatus | Required |
Codes identifying the lifecycle stage of a product. |
Not all resources that follow the 'Product' pattern will necessarily include all of the above elements.
...
| status | category | code | manufacturer | instance | .quantity | .identifier | .lotNumber | .expiry | .subject | note |
Each non-grey cell contains a number, the number of elements and extensions (if > 0) mapped in the resource that are mapped to the pattern element in the column. If there are 0 elements and extensions, the number is not shown. In addition, the cell has a color and some character flags.
Colors:
Flags: