Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-35874

Advance the Product pattern

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • BiologicallyDerivedProduct
      Device
      DeviceDefinition
      Medication
      NutritionProduct
    • Hide

      Motion to find not persuasive with modification as we created the InventoryItem to address the capabilities of interest while maintaining various specialized product resources to address other unique capabilities.  At the same time we harmonized the search parameters on those resources.  We agreed to update the InventoryItem to clarify when the InventoryItem is to reference the relevant specialized product resource or can be used on its own for inventory specific purposes.

      Show
      Motion to find not persuasive with modification as we created the InventoryItem to address the capabilities of interest while maintaining various specialized product resources to address other unique capabilities.  At the same time we harmonized the search parameters on those resources.  We agreed to update the InventoryItem to clarify when the InventoryItem is to reference the relevant specialized product resource or can be used on its own for inventory specific purposes.
    • Marti Velezis / Jose Costa Teixeira: 12-0-0
    • Clarification
    • Compatible, substantive

    Description

      While implementing global supply and management of products (e.g. vaccines), organizations like WHO expect to support Product-related functionalities on FHIR

      • Product delivery and tracking
      • Product catalogs
        The Product pattern is missing some useful features (e.g. common search parameters) and is adopted differently across resources: NutritionProduct seems a good match with the Product Pattern, but Medication/MedicationKnowledge and Device/DeviceDefinition have different approaches.

      Additionally, both from a Catalog and Supply/Tracking perspective, it would be best to have a Product resource, not only a model. The Product resource could be used instead of the specific resources inside the Supply Chain.

      It is important to define common search parameters for searching (track & trace) as well invariants that are common across products.

      An alignment with GS1 product model is also important.

      To align with GS1 (Transactional)TradeItem product structure, ideally this Product resource would have:

      • A generic Key-value pair for characteristics, like the NutritionProduct
      • A generic key-value pair for related Items, for relations like "requires.." or "contains".

      Attachments

        Activity

          People

            costateixeira Jose Costa-Teixeira
            litlfred Carl Leitner
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: