The main (and only) screen.
One of the databases utilized in the project. The SSNs aren't real, no worries!
A snippet of the filtering process that went into registering data. Our goal was to facilitate a common language between hospitals.
funky fresh memes (and an attempt to win best domain)
Note: For domain.com entry, there was a problem that was being worked with support regarding name registration, so our entry to it is posted below.
A current struggle to transfer electronic health data between hospitals with their own databases.
What it does
...it's not really a suite, but we liked the name anyway. Our project allows users to take data and put it into terms understandable by other databases. For example, one database may call first name "first_name", while another may have it as "fname". Usually, when transferring data, these would conflict, and the field would not be filled in at all. The Suite Life provides a way to gap that bridge.
How I built it
Built with HTML/CSS/JS/PHP/SQL.
Challenges I ran into
Idea planning was almost as annoying as Mr. Moseby. We spent the entirety of the first day and half of the following day trying out a project that ended up being unsuccessful. It was our first time working as a team together as well, so finding out each others strengths and weakness was necessary to make a working program in a short amount of time.
Accomplishments that I'm proud of
Making a functional product!
What I learned
When you fix one error, you get ten more.
What's next for The Suite Life of Hack and Code-y
Further parameters for the database, automated file integration.