catalogEntry[edit | edit source]

Owning committee name[edit | edit source]

Orders & Observations WG

Committee Approval Date:[edit | edit source]

Please enter the date that the committee approved this Resource proposal This proposal was initially approved as EntryDefinition on:

22 Jun 2017

It has then been renamed CatalogEntry in July 2018

Contributing or Reviewing Work Groups[edit | edit source]

  • Pharmacy
  • Devices
  • BR&R
  • II

FHIR Resource Development Project Insight ID[edit | edit source]


Scope of coverage[edit | edit source]

The CatalogEntry resource allows to organize resources representing the definition of {products|services|knowledge artifacts|plans|observations|chemical or biological substances|professionals|roles|organizations|locations|physical objects} within catalogs or compendia assisting practitioners and|or patients in processes of healthcare delivery.

An instance of CatalogEntry contextualizes the inclusion of an item into a Catalog (represented by a Composition resource). For instance CatalogEntry specifies whether this item is orderable or not in the context of this catalog, it provides additional catalog-based context information such as the schedule of the delivery, the billing.

In addition, catalog entries may be related to one another, in order to indicate the replacement of an obsolete entry by a new one, or to include an entry within another.

The catalogEntry does not overlap with the definitional resources.

A catalogEntry will be present in any list of resources that represents or belongs to a structured list of items.

RIM scope[edit | edit source]

Master file concepts were not specifically modelled as a topic area in v3 Messaging.

Resource appropriateness[edit | edit source]

This represents the concept of exchanging Master Files of products, services, (e.g. medications and labs)

Catalogs and Master files have a need for explicit maintenance and exchange.

Expected implementations[edit | edit source]

The recent focus on terminology consistency on products (UDI, IDMP, openMedicine) has shown a good interest from vendors and agencies in providing product information in a standard format. FHIR is a vehicle for such information (Same as specimenDefinition)

Catalogs of laboratory services, which have relied on the exchange of HL7 v2 master files messages, are now looking for a more interactive sharing process, like the one offered by the RESTful API of FHIR.

Content sources[edit | edit source]


Example Scenarios[edit | edit source]

  • Laboratory Directory of Service
  • In-patient Hospital Medication Formulary
  • Human Services Directory
  • Medical Device Catalog

Resource Relationships[edit | edit source]

The CatalogEntry resource references these definitional resources: DeviceDefinition | Organization | Practitioner | PractitionerRole | HealthcareService | ActivityDefinition | PlanDefinition | SpecimenDefinition | ObservationDefinition | MedicationKnowledge | Substance | Location

the CatalogEntry is referenced by the Composition resource under the Catalog profile.

An instance of a CatalogEntry resource may reference other instances of this resource type as related catalog entries. These relationships have a semantic qualification: triggers | is-replaced-by | excludes | includes.

Timelines[edit | edit source]

The timelines for the catalogEntry depend mostly on alignment with other WGs. The resource is aimed at STU4.

gForge Users[edit | edit source]




When Resource Proposal Is Complete[edit | edit source]

When you have completed your proposal, please send an email to