OZ-758: Update Enabling & Disabling HIS Components Section of implementer docs#20
OZ-758: Update Enabling & Disabling HIS Components Section of implementer docs#20enyachoke wants to merge 2 commits intoozone-his:mainfrom
Conversation
rbuisson
left a comment
rbuisson
left a comment
There was a problem hiding this comment.
The top paragraph is already a bit too technical, let's move the part that mentions Ozone Docker Compose as a Maven dependency lower down in the page.
Let's also make sure we add a block as a pre-requisite for this article to remind that at this stage, we we expect the implementer to have created their own distro through using the archetype (+link to the page)
Add a "Prepare for production" page (as draft: italic + grey)
| ### Running Only the EMR | ||
| The core funcionality of Ozone is built around the EMR component so in a barebone setup you are likely going to want to run only the EMR component. At the moment Only OpenMRS 3 is supported | ||
|
|
||
| ### Running Ozone with an ERP | ||
| In deployments where billing and stock management is needed you can run Ozone with an ERP. Ozone has 2 options for the ERP you can run Ozone with Odoo or ERPNext. Take a look at the Matrix below for how to combine Ozone the ERP of choice | ||
|
|
||
| ### Running Ozone with a LIMS | ||
| In deployments where a Lab is available you can run Ozone a LIMS. Ozone supports SENAITE as the LIMS component. See the Matrix below for how to combine with a LIMS |
There was a problem hiding this comment.
Those are useful paragraphs for introducing the concepts of picking/choosing apps.
Let's move them higher up.
| <th>O3</th> | ||
| <th>Odoo</th> |
There was a problem hiding this comment.
This should be 1 column (maybe header could be O3 + Odoo).
docs/enabling-components.md
Outdated
|
|
||
| There will be a default Docker Compose file provided by Ozone for each supported component of the Ozone HIS FOSS ecosystem. | ||
|
|
||
| ## Overriding `docker-compose-files.txt` |
There was a problem hiding this comment.
| ## Overriding `docker-compose-files.txt` | |
| ## Understanding the `docker-compose-files.txt` |
|
|
||
|
|
||
| ### Running Only the EMR | ||
| The core funcionality of Ozone is built around the EMR component so in a barebone setup you are likely going to want to run only the EMR component. At the moment Only OpenMRS 3 is supported |
There was a problem hiding this comment.
| The core funcionality of Ozone is built around the EMR component so in a barebone setup you are likely going to want to run only the EMR component. At the moment Only OpenMRS 3 is supported | |
| The core functionality of Ozone is built around the EMR component so in a barebone setup you are likely going to want to run only the EMR component. At the moment only OpenMRS 3 is supported. |
mks-d
left a comment
mks-d
left a comment
There was a problem hiding this comment.
I like the idea of a page that would run implementers through hands-on use cases, but should this actually be a follow-up page to the current Enabling & Disabling HIS Components page, rather than expanding the existing one with more stuff?
| - Enabling & Disabling HIS Components: 'enabling-components.md' | ||
| - "<span style='color:#b0b0b0;font-style:italic'>Configuring HIS Components</span>": 'configuring-components.md' | ||
| - "<span style='color:#b0b0b0;font-style:italic'>EIP Configuration Points</span>": 'eip-config-points.md' | ||
| - "<span style='color:#b0b0b0;font-style:italic'>Preparing for Prod</span>": 'prepare-for-prod.md' |
There was a problem hiding this comment.
To be removed along with the corresponding, empty, file.
3 participants
This PR updates the Implementer docs inline with the ticket https://mekomsolutions.atlassian.net/browse/OZ-758