- Household Information: Name, Email, Phone and Address of the household. We currently support 2 household and 4 contacts. These are stored as CiviCRM contacts with a relationship link of type Parent / Child to the student. We created a custom group to store which household a parent belonged to. We did not use CiviCRM's household functionality.
- Emergency Information: Name, Email and Phone for the emergency contacts. These are also stored as CiviCRM contacts with a relationship link of type Emergency Contact to the student. We stored the order in the description field
- Medical Information: Insurance details along with various allergies. The insurance details are stored in a single value custom group. The allergies are stored in a multi-valued custom group so the school can change the list of allergies / medical symptoms easily
- Release Checkboxes: Various release statements, all stored as custom data that extends the student record
- Diversity: Stored as a custom group with multiple checkboxes
Why did you choose not to use 'household' contact records to link contacts in one family? How are you keeping track of which adults are in the same family?
Also, what is the process like for a family that is registering multiple children? ( In my experience, the emergency contacts are typically the same for all kids in one family. )
This looks fantastic!
the current data model in powerschool (the school's SIS) does not really have any family info (its one large flat table for all info) and in our initial import we maintained that structure. We still need to sync with them and hence did not opt to create a household.
Yes parents will need to enter the emergency info twice. we can be smart and load it from their other childrens record, but for now thats left as an exercise to the reader :)
Is there any hope you might be able to set up a demo site of the SF module at some point?
We would love to see the SFS module! Please, please!