Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Potentially rename English "Fee Centers" to something more standard #5861

Closed
jniles opened this issue Aug 17, 2021 · 2 comments
Closed

Comments

@jniles
Copy link
Collaborator

jniles commented Aug 17, 2021

As discussed in #5860 (comment) and #5860 (comment), the name "Fee Centers" doesn't appear in any of the documentation Larry has provided. Since he is the ultimate client, we should find terminology that he is familiar with and that is standard across the industry, particularly if his goal is to sell the BHIMA product.

@jmcameron
Copy link
Collaborator

I see the (English) terminology "Profit Center". I think we should consider renaming these to "Revenue Center". You don't really know if there is a profit until you do a larger-scale analysis, so "profit" may not be the best term to use in this context.

@jniles
Copy link
Collaborator Author

jniles commented Aug 18, 2021

I agree with renaming profit -> revenue. That is a much more appropriate term.

@jniles jniles self-assigned this Sep 2, 2021
jniles added a commit to jniles/bhima that referenced this issue Sep 2, 2021
This commit renames the fee_center to cost_center wherever it is found
throughout the application.

Closes Third-Culture-Software#5861.
jniles added a commit to jniles/bhima that referenced this issue Sep 2, 2021
This commit renames the fee_center to cost_center wherever it is found
throughout the application.

Closes Third-Culture-Software#5861.
jniles added a commit to jniles/bhima that referenced this issue Sep 2, 2021
This commit renames the fee_center to cost_center wherever it is found
throughout the application.

Closes Third-Culture-Software#5861.
@bors bors bot closed this as completed in 763072a Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants