Catalog FHIR Profile Proposal

From HL7Wiki
Jump to navigation Jump to search



Catalog (Draft)

Profile balloting plans

  • For Comment ballot in January 2018
  • STU ballot May 2018

Profile Details

Profiled Resource(s)

Constraints to be Applied

  • Constraint subject to 0..0; Catalog is non patient specific
  • Define value sets for documentTypeCode and Composition.class (or constrain out Composition.class)

Extensions to be Applied

  • Add an extension for PublishedDate, unless SD wants to consider that for core
  • Add an extension for ValidityPeriod, unless SD wants to consider that for core
  • Provide for inclusion of subCompositions (subCatalogs) as an extension
  • Determine how to address lifecycle stage (Draft, Published, etc)

Example Scenarios

  • Medication Formulary within an institution
  • Orderable Devices Catalog
  • Lab Electronic Directory of Service
  • Catalog of Order Sets
  • Human Services Directories
  • Catalog of Approved Protocols in an Institution

Scope of coverage

Order Service Catalogs vary in the type of entries they contain. For instance, a product catalog such as a medication catalog may list products that are available for selection within a single organization or across a number of organizations; an orderable catalog typically holds collections of orderable items available to an organization or facility, the definition of orderables used to render and constrain order entry forms, and libraries of order set or plan of care definitions for any number of patient populations. Other examples include Electronic Delivery of Service (eDOS) compliant catalogs that enumerate the orderable tests for laboratories or medication product catalogs.

Service catalogs may offer a set of services that can be ordered such as laboratory services and may also contain entries in the catalog for items that are not necessarily orderable but rather which serve a supporting role when ordering a specific service.

Catalogs of knowledge artifacts, another type of order service catalog, enable organizations to ensure that high quality standards are maintained over time. Order sets and plans of care evolve as best practices and evidence change, but without standardized Catalog APIs, it is often not easy or even possible to exchange catalog resources between organizations. For instance, an organization may decide to contract with a CDS Knowledge Provider to obtain evidence-based order sets to help them standardize care. The organization may wish to customize these order sets (e.g., modifying the names of orderable items to reflect the local vocabulary used at a given facility or changing the data models of categories of orderables such as medication orderables), and, with great effort, import these customized order sets into their EMR. Given the lack of standard interfaces to support the import of such order sets, updating local content as evidence-based practices evolve is unnecessarily convoluted and expensive. 

An Order Catalog consists of Catalog Entries — items such as medication products, laboratory tests, procedures, or knowledge artifacts such as order sets—which support the ordering process as well as groups of such entries. Fundamentally, an Order Catalog consists of the collection of Catalog Entries that make up the catalog and any associated metadata that describes the overall collection.  The content of a catalog consist of entries of three types: catalog entry groups which supports the grouping of entries in a catalog, catalog entries representing an individual entry in the catalog, and references to other entries in the catalog to support easier organization of catalog content.

Realm

Realm Neutral

Ownership

Owning committee name

Orders and Observations

Contributing or Reviewing Work Groups

  • Reviewing Work Group:
    • Structured Documents (Approved Sept 11, 2017)
  • Contributing WorkGroups:
    • Pharmacy
    • Clinical Decision Support
    • Imaging Integration
    • Service Oriented Architecture

Expected implementations

  • IHE will require a catalog of medications for profiling and guidance
  • LIVD project (LOINC - IVD Test Code) intends to use this profile
  • FHIR based eDOS implementations

gForge Users

Claude Nanjo, Jose Teixera

FHIR Profile Development Project Insight ID

1010

Plans

Timelines

  • Planning for Design Review in time for January 2018 Connectathon

Balloting Requirements

Choose one:

  • Ballot with next FHIR DSTU or Normative Edition


Desired Ballot Date

  • As scheduled by overall FHIR ballot