Week 13: Building the Backend

-

 Week 13: Building the Backend

    This week, we moved from designing screens to working on the actual backend of the Dietary Inventory System (DIS). This is where all the important functions live like user logins, inventory tracking, and delivery management. It felt like going behind the scenes after working on the frontend last week.

    We set up three types of users: admin, who has access to everything staff related operations, staff, and wards, who receive food deliveries. Creating the login system was tricky at first. Making sure each user only sees what they’re supposed to. The admin can add new users and adjust settings, staff can update food stock levels, and wards can only view delivery schedules. Testing permissions was funny. I kept accidentally locking myself out or seeing pages I shouldn’t.

    For the inventory module, we made sure it could track food quantities. I helped set up simple alerts so the kitchen knows when to reorder or use certain ingredients first. The delivery module was the hardest part. We had to link it so wards could confirm when they receive food, updating the system automatically.

    It wasn’t perfect as sometimes entering data would cause an error, or a user type couldn’t access what they needed. But each fix taught me something new. Ma’am Ynah walked us through debugging, showing how small mistakes can break everything.

    Between coding sessions, I still took helpdesk calls. After working on DIS, I’d answer a ticket and think, “Maybe someday, this system will have its own helpdesk issues too.” It’s cool to build something from scratch, but I’m also realizing how much maintenance comes after.

    Now that the basic backend works, next week we’ll connect it to the frontend. Fingers crossed our test users (us) don’t crash it!

Comments

Post a Comment

Popular posts from this blog

Week 1: A Slow but Steady Start

-
Image
Week 1: A Slow but Steady Start      The first week of my OJT at Bicol Regional Hospital and Medical Center (BRHMC) under IHOMP was a gentle introduction to the world of healthcare IT. No dramatic rescues of crashing systems... yet, but plenty of learning in small, steady steps.      Day one started with an orientation by Ma’am Annie, who walked us through hospital policies and workplace etiquette. It wasn’t the most thrilling part of the week, but at least I now know where not to wander off to! After that, Sir Jims gave us a quick tour of the different departments, and it was interesting seeing how everything connects behind the scenes. By the afternoon, assignments were handed out, and I landed at IHOMP, where my first task was updating case rate data in HOMIS NX. Not exactly an exciting IT work I imagined, but hey, everyone starts somewhere.      The next two days settled into a routine. Mornings and afternoons spent carefully encoding and...
Read more

Week 2: Transitioning to Help Desk Operations

-
Image
Week 2: Transitioning to Help Desk Operations      My second week at BRHMC's IHOMP department started right where I left off, diving deep into the HOMIS system for more case rate updates. The first two days were all about wrapping up that massive data entry task. It felt satisfying to finally complete it, like finishing a long and tedious puzzle.      Just when I thought I’d become a permanent HOMIS data encoder, Ma’am Annie introduced us to the IT Help Desk system, which is a welcomed change of pace! She walked us through how it works, from processing user requests to managing roles and permissions in HOMIS. We even learned how to install the HOMIS application on other PCs, which made me feel like I was actually doing something technical for once.      Then came the real test. I was handling actual IT Help Desk requests. I was nervous at first but most requests were straightforward, like assigning nurses to their wards or updating case rates...
Read more

Week 14: Wrapping Up the Internship

-
Week 14: Wrapping Up the Internship      This final week of development on the Dietary Inventory System felt like racing against the clock to get everything functional before my OJT period ends. We focused on completing the  inventory and delivery modules, along with basic ordering functions for the wards, which turned out to be more involved than I expected. The delivery module required careful planning to ensure it could not only generate accurate delivery confirmations but also handle special cases like reprints and audits. I spent considerable time testing different scenarios, discovering along the way how small details like server time settings could throw off entire reports if not configured properly.      The order module presented its own challenges as we worked to create an intuitive interface that would prevent mistakes during busy kitchen hours. We implemented safeguards like patient count-based quantity calculations, though our initial...
Read more