Hello, I need the ERD diagram created

ChocAn Group Project Team 2

Project Charter

Executive Summary

7/20/2022

Problem Statement

Our goal is to design a system that can handle all the necessary information coming in and going out from ChocAn’s data center efficiently. The system should have 4 main entities: members ,service providers, Acme and the bank. Each entity needs to include important attributes that the business requires for data validation and information exchange between the entities.

The ChocAn members pay a monthly fee to maintain their memberships to enjoy healthcare services from the providers.The processing of the payments of ChocAn’s membership fees and membership validation has been contracted out to Acme, a third-party organization. The provider side requires functionalities such as, recording services provided to active members, and billing the business.Once the provider bills ChocAn, the fee is audited by the system. A record consisting of EFT data is then written to a disk; baking computers ensure that each provider’s bank account is credited with the appropriate amount.The business needs to be able to manage records of active/inactive members/providers, run accounting procedures, and generate/send out reports. We need to design a system that can carry out all of these functionalities while paying attention to data integrity as well as keeping the design as simplified as possible.

Purpose of the Project:

Current State:

[What is the issue, risk or gap we are trying to address]

  1. To keep an up-to-date lists of members and providers

  2. Keep the privacy of our customer and providers (medical records, payment information and etc)

  3. To minimize human error and improve process accuracy

  4. To restrict possible user input options to protect data integrity

  5. The system should be able to provide the functionality that would allow users to double verify and confirm their inputs

  6. Maintain consistency and enable traceability of past activities of the users



Future State:

[What is the future vision and how does this project address the issue, risk or gap]

  1. Members can delete/pause their accounts voluntarily. In addition, ChocoAn data center’s operators have the admin rights to add new members, delete members who have resigned, or suspend members who have not paid their membership fee for at least a month. The member entity will have an attribute called Previous Membership Payment Date, so each day, the operator can query the database to find out members with a Payment Date more than a month ago and run a batch request to suspend these accounts and send out notification emails, on a daily basis.

  2. Providers can make their profiles private (invisible for others) when they wish to temporarily pause their service contract with ChocAn. When they wish to terminate their service contract with ChocAn, they are required to submit a request form, so the system can be notified, and the business can pay them if there’s any outstanding balance then delete their account.

  3. Available services will be provided as a domain of attributes. The system will not allow user input for the Service Code field. It will be a drop-down box / search bar, so the providers can only choose from available options. Each service has a predetermined fee. The providers cannot charge a different amount of fee other than the predetermined amount. The amount of fee will be automatically displayed on the terminal screen when the provider chooses a service code from the drop-down box.Once the service is selected, the computer will automatically record the day and time .

  4. The predetermined amount of service fee will be displayed on the terminal screen when the provider enters the service code. The providers will also be asked to verify all the services he/she provided and the service fees at the end of each week. The sum is calculated automatically based on the reports the providers submitted.( In Discussion)

  5. The provider has to verify the member’s member card before every session using the terminal. Ideally, after each session, the provider will slide the member card through the card reader on the terminal again to record the provided session. But the provider will also be given the option to key in the Member Number (which can be found in the system when a member books a session with a provider) and record the session info later.A document will then be sent out to both the provider and member to verify a

  6. The members will also receive a weekly report if the system recorded that they had session(s) with provider(s). If the members see unknown sessions on the report, they can either submit a notice through the website or call ChocAn to notify them that they were not the one that received the session.



Complete ERD

Draw ERD for complete organization (i.e. depict all entities and relationships regardless if described in the problem statement/current/future state or not) – remember this describes anything that is a possible data model.

4 entities

(Acme, the bank , the customer and the provider (maybe the database too).

Our goal is to design a system that can handle all the necessary information coming in and going out from ChocAn’s data center efficiently. The system should have 4 main entities: members ,service providers, Acme and the bank. Each entity needs to include important attributes that the business requires for data validation and information exchange between the entities.

The ChocAn members pay a monthly fee to maintain their memberships to enjoy healthcare services from the providers.The processing of the payments of ChocAn’s membership fees has been contracted out to Acme, a third-party organization. The provider side requires functionalities such as, recording services provided to active members, and billing the business.Once the provider bills ChocAn, the fee is audited by the system. A record consisting of EFT data is then written to a disk; baking computers ensure that each provider’s bank account is credited with the appropriate amount.The business needs to be able to manage records of active/inactive members/providers, run accounting procedures, and generate/send out reports. We need to design a system that can carry out all of these functionalities while paying attention to data integrity as well as keeping the design as simplified as possible.


  1. We should find a way to make sure that the service we are providing to the members is actually effective ( this may not be necessary in our project, most likely not )

  2. Keep the privacy of our customer and providers( medical records, payment information and etc)

  3. Update our information everyday to Acme and the bank in case anything changes ( problem could occur when member cancels with us but nothing is sent to Acme and member gets billed )

  4. We need a system to automate the process

  5. Privacy

  6. Processing time