Drop account.active - 2018-Jan Core #153

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Account
    • Hide

      The account.period should be renamed to account.servicePeriod and the description clarified from

      "Identifies the period of time the account applies to; e.g. accounts created per fiscal year, quarter, etc."

      to

      "The date range of services associated with this account"

      The comments section will be clarified to:

      "It is possible for transactions to be posted outside the service period, as long as the service was provided within the defined service period."

      The account.active property will be removed, and those the desire to communicate this as a period (over batch jobs that alter the lifecycle status) may use a local extension to handle this.

      Show
      The account.period should be renamed to account.servicePeriod and the description clarified from "Identifies the period of time the account applies to; e.g. accounts created per fiscal year, quarter, etc." to "The date range of services associated with this account" The comments section will be clarified to: "It is possible for transactions to be posted outside the service period, as long as the service was provided within the defined service period." The account.active property will be removed, and those the desire to communicate this as a period (over batch jobs that alter the lifecycle status) may use a local extension to handle this.
    • Andrew Torres/Keith Boone:8-0-1
    • Correction
    • Non-compatible
    • STU3

      Comment:

      Account.active is not required as we already specify the period for which the services that are being charged for must be within this period in Account.period.

      Summary:

      Drop account.active

            Assignee:
            Unassigned
            Reporter:
            rohan_chavan
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: