The name of this is boring. I suggest we call it the Space Shuttle.
S.P.A.C.E - Scalable Packaged Apps for Containerized EHR
I vote YES to this. It’s out of this world!
Concept of shuttle reprocessing for flight.
Actual of shuttle reprocessing for flight.
Don’t think your links work
Here is the first DRAFT of the SPACE project estimates - I need to identify the resources, so, now is the time to speak up and identify the places you can add value.
S.P.A.C.E. Launch - “Scalable Packaged Apps for Containerized EHR”
LibreEHR Containerization UNF DIAL Grant Plan aka S.P.A.C.E.
This project proposes to rework core structure of the EHR so that it can be deployed as a series of containers using common container management standards, such as Kubernetes.
Containerization Key Areas of Focus
- Modify document storage to use server (file or database) outside of the application container.
- Modify all configuration data to be stored outside of the application container
- Create containers and container deployment models
- Create Kubernetes, Puppet, Chef or similar management tools to allow easy creation,scaling and deployment
- Document the model and deploy the EHR demo and test sites using the new model
- Test in several environments including public and private cloud service providers such as AWS, GCP, ApiFocal as well as local “stand alone”.
- Maintain current installation models for on-premise, VM based and XAMPP packaging
This new model will allow the project to grow by taking advantage of current industry trends in scaling and deployment. Other projects, such as the Educational EHR/NHANES project, that could then adopt the EHR and help spread the use more broadly to more users.
Plan, Estimates and proposed resources
- Project Management - 40h (5h per week for 2 months) - MI-SQUARED, Tony McCormick
- Infrastructure Management and development – Build your own (reference example) - 20h
- External/Service Partnership, Enterprise Level - $200/m estimated
Development and Deployment
- Choose a container Model (Docker) 1-2h
- Choose a registry (Gitlab and/or Docker Hub) 2h
- Choose / design an orchestration model-Kubernetes/OpenShift? Rancher? - 30h
- Choose or design the Discovery model - 4 hrs
- Develop a testing plan and recommendations for deployment models and OS - 4h
- Identify the all the persistent data needs in the EHR - 10h
- Identify the applications that are outside of the EHR that can also be used from containers (PHP, SQL, COUCHDB, etc) - 5h
- Determine the disk storage models that will be supported (NAS/Local/Cloud, etc) - 10h
- Modify the code to allow the persistant data to be external to the EHR application container -30h
- Create a container(s) (tagged tarfile) for the EHR code, configuration, static-data -10h65
- Add the container to the registry (automation strategy, Jenkins?, etc) 10h
- Create Installation tools / instructions (where are the secrets managed?) - 20h
- QA and Testing (All 3 Products) - 60hrs
- Deploy EHR to at least two environments such as LibreHealth infrastructure, Google Cloud, etc
Specific Breakouts (based on Diagram)
- EHR Core Container *minimum code for complete function
- Build and Install Tools
- Build (Docker)
- Install (dependency mapping etc)
- Ansible and/or Kubernetes, etc
- Database Server Container - MySQL or MariaDB - *STANDARD Docker (or cloud) Packages
- Database Service - Cloud SQL via GCP/AWS
- Patient Portal Container *minimum code for complete function of “onsite portal”
- PHP 7.x Container *STANDARD Docker (or cloud) Packages
- Web Service -Apache2 or NginX, *STANDARD Docker (or cloud) Packages
- EHR Module Containers n+1 (placeholder for future stuff)
- File Storage * attached/shared or cloud based for Medical Docs, Images, EDI, form Templates,DB files (raw), Local Backups
This all sounds a-okay. I am in favor of Docker Hub/GitLab container registry together.
Orchastration we could use Kubernetes…
Since no one else in the community (other than @r0bby) appears to be interested in being a contributor, I will select the sub-contractors that I trust to do this work.
At this point they are:
- MI-Squared for overall management of the project and QA
- Robby (volunteer) for Tech, QA and deployment issues in various environments
- APIFocal for container development and consulting (@hzbarcea)
- MI-Squared staff for core EHR changes to support this model
- MI-Squared sub-contractor(s) TBD for various component/module development and spliting… (@pri2si17 is one possible)
I plan on sending the final plan to SFC next week early…
I don’t even know what it is.
Yes, there is a lot of work to do before we get to that point, however.
Just keep me updated and I can help you out – I’ll prioritze it.