CFS Water CFSWater is a mobile application that reports scheduled and current water release and power generations for Army Corp of Engineer Tailwaters.Overview A team of consultants on the KeyholeSoftware.Dev team architected and developed CFSWater, a cross-platform mobile application using Flutter. The result was a highly functioning mobile app that reports scheduled and current water release and power generations for …
Deep Dive Into Vue.js Comparing ReactHome→Search ResultsA 45-minute deep dive into the Vue.js framework, including its technical philosophies, how it differs from the React library, and how it should be applied to new applications at an enterprise scale. RecordingThe video was recorded at a Keyhole Software Public Education Event in December 2022. Speaker Zach Gardner is a Senior Consultant and …
A 45-minute discussion diving into the Vue.js framework, including its technical philosophies, how it differs from the React library, and how it should be applied to new applications at an enterprise scale.
Keyhole Software is proud to announce the v3.0 release of MockOla, a web-based design software for software developers. This release provides significant feature and usability updates, including a formal template gallery that simplifies the illustration of complex software design concepts.
In version 3.0, we add a formal template gallery with IT templates for application architecture, cloud, .NET, Java, UML, UI, and other software concepts. Users can quickly modify and customize predesigned templates to minimize design time. MockOla v3.0 also adds an image gallery containing specialized images and logos, allowing users to make effective, communicative diagrams.
Welcome to the fourth and final installment of Creating an FHIR API with GCP. So far, we’ve covered a lot!
We discussed the differences between Google and Azure, landing on GCP as the best option for FHIR in Part 1. We began our implementation in Part 2, creating both the BigQuery resources and your FHIR repository resources. And finally, in Part 3, we tackled authentication methods and populating data in our FHIR repository.
This time, we’ll wrap everything up with a nice little bow. First, we’ll finish our implementation, and then, I’ll share the limitation I found – for the sake of transparency. Let’s dive in.