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

Substantive workflow changes for PA resources

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Very High Very High
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • ChargeItem
    • Hide

      1. rename the context to encounter and remove the EpisodeOfCare from the reference types.

      Short definition: "Encounter associated with this ChargeItem"

      Long description: "This ChargeItem has the details of how the associated Encounter should be billed or otherwise be handled by finance systems".

      Usage Comment : "This ChargeItem may be recorded during planning, execution or after the actual encounter takes place."

      Include the ChargeItem as one of the contexts for the EpisodeOfCare workflow standard extension.

      Search parameter for the EpisodeOfCare should be updated to read the standard extension

      The mappings for the Event pattern should be updated to reflect the above changes.

      Update any examples that have the context property.

      2. Considered. No.

      ChargeItems are fed into invoicing/claim/transaction/statement/other processing which is where non primary records would be end up being captured.

      Shouldn't this concept be covered by the "meta.source" property instead?

       

      Show
      1. rename the context to encounter and remove the EpisodeOfCare from the reference types. Short definition: "Encounter associated with this ChargeItem" Long description: "This ChargeItem has the details of how the associated Encounter should be billed or otherwise be handled by finance systems". Usage Comment : "This ChargeItem may be recorded during planning, execution or after the actual encounter takes place." Include the ChargeItem as one of the contexts for the EpisodeOfCare workflow standard extension. Search parameter for the EpisodeOfCare should be updated to read the standard extension The mappings for the Event pattern should be updated to reflect the above changes. Update any examples that have the context property. 2. Considered. No. ChargeItems are fed into invoicing/claim/transaction/statement/other processing which is where non primary records would be end up being captured. Shouldn't this concept be covered by the "meta.source" property instead?  
    • Lloyd McKenzie/Alex de Leon:8-0-0
    • Enhancement
    • Non-compatible
    • R5

    Description

      1. Per GF#17794, the "context" element should be renamed to Encounter and changed to 0..1 Encounter with a short definition of "Encounter created as part of" and long description of "The Encounter during which this [x] was created or to which the creation of this record is tightly associated.". Usage Comment : "This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter."

      The need to link to episodes of care will be handled with an extension.

      2. Per GF#17169, consider adopting the pattern of reported[x]:

      0..1 boolean|Reference(Patient|RelatedPerson|Practitioner|PractitionerRole|Organization) with a short definition of "Reported rather than primary record" and full definition of: "Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report."

      If this is not core but would be an appropriate extension for your resource, add a comment to GF#17169 and Lloyd will include your resource as part of the context for the common extension when he defines it.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: