Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Create a basic billing module #2496

Open
blestab opened this issue Dec 6, 2020 · 5 comments 路 May be fixed by #2528
Open

Create a basic billing module #2496

blestab opened this issue Dec 6, 2020 · 5 comments 路 May be fixed by #2528
Assignees
Labels
billing 馃殌enhancement an issue/pull request that adds a feature to the application in progress indicates that issue/pull request is currently being worked on LOE - large indicates that the level of effort to complete issue is large
Projects
Milestone

Comments

@blestab
Copy link
Contributor

blestab commented Dec 6, 2020

馃殌 Feature Proposal

This issue is to create a very basic billing module. When this issue is finished, a user would expect to be able to:

  • create a new pricing item
  • view a list of all pricing items
  • view a single pricing item

Technical Notes

Model Name PricingItem defined as:

{
  id: string
  name: string
  price: number
  expenseTo: string
  category: imaging|lab|procedure|ward
  type: string
  notes: string
  createdAt: string
  createdBy: string
}
  • id, createdBy (logged on user), createdAt (datetime string of current date/time) should be auto-generated
  • For categories imaging and lab, if type is not specified then the display should show the category+ "Procedure" appended e.g. "Imaging Procedure" or "Lab Procedure"
  • There should be a text box which allows a user to search for pricing items
  • Add the ability to filter the search by category, including the ability to show all categories
  • The table of matching items should show the following fields:
    category, name, price, expense to
  • There should be a view button which takes us to a view screen
  • The view screen allows user to edit the following fields: name, category, type, price, expenseTo, notes
  • The view screen should have an "Update" button to save changes

Permissions

  • Add new set of permissions for viewing and adding billing items

Menu / Sidebar

  • Add a sidebar link named Billing above the Incidents link
  • Underneath the Billing sidebar menu, add the following options:
    • "Add Pricing Item" => takes use to a form to create a new pricing item
    • "Pricing Items" => takes user to a listing of all pricing items
  • Add "Add Pricing Item" to quick create button in the Navbar as the last item
@blestab blestab transferred this issue from HospitalRun/hospitalrun Dec 6, 2020
@blestab blestab added billing help wanted indicates that an issue is open for contributions LOE - large indicates that the level of effort to complete issue is large 馃殌enhancement an issue/pull request that adds a feature to the application labels Dec 6, 2020
@blestab blestab added this to the v2.0 milestone Dec 6, 2020
@rsousaj
Copy link
Contributor

rsousaj commented Dec 7, 2020

Hi guys, I would love to build this module. May I ?

@blestab
Copy link
Contributor Author

blestab commented Dec 7, 2020

Hi guys, I would love to build this module. May I ?

Sure @rsousaj

@blestab blestab added in progress indicates that issue/pull request is currently being worked on and removed help wanted indicates that an issue is open for contributions labels Dec 7, 2020
@rsousaj
Copy link
Contributor

rsousaj commented Dec 10, 2020

@blestab Hi, createdOn and createdAt (inherited from AbstractDBModel) are any different ?

@jackcmeyer
Copy link
Member

@rsousaj use whichever is inherited from the AbstractDBModel they are intended to be the same.

@rsousaj rsousaj linked a pull request Dec 22, 2020 that will close this issue
@amit-srt
Copy link

amit-srt commented Sep 2, 2022

I would like to work on this issue. Can you please assign this to me

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
billing 馃殌enhancement an issue/pull request that adds a feature to the application in progress indicates that issue/pull request is currently being worked on LOE - large indicates that the level of effort to complete issue is large
Projects
Version 2.0
  
To do
Development

Successfully merging a pull request may close this issue.

4 participants