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

New MetaElement for PriceComponent

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • ChargeItem
      Invoice
    • Hide

      The MonetaryComponent backbone element in ChargeItemDefinition will be created as a new Metadata Type and make this available as a valid Extension value too.

      The following resource types that currently use a common MonetaryComponent structure will be updated to use the new data type:

      • ChargeItem.totalPriceComponent  (new property being added)
      • ChargeItem.unitPriceComponent  (new property being added)
      • ChargeItemDefinition.propertyGroup.priceComponent
      • Invoice.lineItem.priceComponent
      • Invoice.totalPriceComponent

       

      FM will look at whether this data type can be used in Claim and ExplainationOfBenefit.

       

      The use case for including in extensions was that we have some implementers that would like to include pricing information on medications, and devices (which may not have list prices, and only on a specific device) - not requesting standard extensions, just the ability for implementers/profiles to specify it.

       

       

      Show
      The MonetaryComponent backbone element in ChargeItemDefinition will be created as a new Metadata Type and make this available as a valid Extension value too. The following resource types that currently use a common MonetaryComponent structure will be updated to use the new data type: ChargeItem.totalPriceComponent  (new property being added) ChargeItem.unitPriceComponent  (new property being added) ChargeItemDefinition.propertyGroup.priceComponent Invoice.lineItem.priceComponent Invoice.totalPriceComponent   FM will look at whether this data type can be used in Claim and ExplainationOfBenefit.   The use case for including in extensions was that we have some implementers that would like to include pricing information on medications, and devices (which may not have list prices, and only on a specific device) - not requesting standard extensions, just the ability for implementers/profiles to specify it.    
    • Brian Postlethwaite / Paul Knapp : 18-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      We may need to have a MetadataElement for PriceComponent. It is currently a backbone element, but it may be needed in other resources as well.

      E.g.:

      ChargeItem to capture the results of the calculation after applying a ChargeItemDefinition to a ChargeItem

      ChargeItemDefinition to define the PriceComponents that are relevent to a specific billing code and the rules under which they apply.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Simone Heckmann Simone Heckmann
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: