...
The downloadable release is a copy of the demo site made available for use on your local machine. You will need virtualbox to run the images and meet the minimum hardware requirements to run all of the virtual machines at once for full functionality. With this you may make configuration changes suited to your environment and experiment with the software on your local machine.
Lifecycle of Code?
Development Branch
- Code is committed to a community repo.
- Unit tests are run, if available.
- Code is compiled / packaged and made into an artifact on CI.
- Artifact is deployed to our dev environment.
- Manual User Acceptance Testing occurs, testing for functionality and interoperability. Test interoperability against staging (which should mirror prod).
Release Branch
- Code is tagged as release in code repository.
- If it is determined that, it should not break anything deploy it to staging.
- If it will break interoperability, determine dependency and wait.
- Run automated Integration Tests.
- Allow users to perform User Acceptance Testing.
- Note all versions as a Demo Release. (e.g. Demo v0.2.0 = OpenEMPI 3.0, OpenHIM 2.3, etc...)
- Rebuild demo and downloadable demo as new release.
Status
Sandbox/Staging
| OHIE Component | GUI URL |
|---|---|
| Point of Care | http://poc.sandbox.ohie.org:8080/openmrs |
| Client Registry | http://cr.sandbox.ohie.org:8080/openempi-admin/ |
| Interoperability Layer | http://iol.sandbox.ohie.org:8089/auth/login |
| Provider Registry (old version) | http://pr.sandbox.ohie.org/webservices/ |
| Terminology Service | http://ts.sandbox.ohie.org/home.php |
| Facility Registry | http://fr.sandbox.ohie.org/ |
| Shared Health Record | http://shr.sandbox.ohie.org:8080/openmrs |
...