From c02775de58ce9d0a2f89a10a6225480c408ba99f Mon Sep 17 00:00:00 2001 From: witash Date: Fri, 13 Dec 2024 13:10:41 +0300 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Andra Blaj --- content/en/building/guides/interoperability/openhim.md | 6 +++--- .../en/building/guides/interoperability/troubleshooting.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/building/guides/interoperability/openhim.md b/content/en/building/guides/interoperability/openhim.md index fc8e2ee87..6f717fd0c 100644 --- a/content/en/building/guides/interoperability/openhim.md +++ b/content/en/building/guides/interoperability/openhim.md @@ -1,7 +1,7 @@ --- title: "OpenHIM Mediators" linkTitle: "OpenHIM Mediators" -weight: +weight: 2 description: > Guide to running OpenHIM and Mediators with Docker Compose keywords: openmrs interoperability @@ -15,7 +15,7 @@ relatedContent: > #### Overview -The components and reference information for interoperability used in this project are: +The components and reference information for interoperability used in CHT Interoperability project are: - [OpenHIE](https://ohie.org/) defines the architecture for an interoperability layer. - [OpenHIM](http://openhim.org/) is a middleware component designed to ease interoperability between systems. @@ -23,7 +23,7 @@ The components and reference information for interoperability used in this proje #### CHT -The structure of documents in the CHT database reflect the configuration of the system, and therefore do not map directly to a FHIR message format. To achieve interoperability Medic used a middleware to convert the CHT data structure into a standardized form so the other systems can read it. Below is the standard data workflow: +The structure of documents in the CHT database reflects the configuration of the system, and therefore, does not map directly to a FHIR message format. To achieve interoperability, the CHT uses a middleware to convert the CHT data structure into a standardized form so the other systems can read it. Below is the standard data workflow: ![](flow.png) diff --git a/content/en/building/guides/interoperability/troubleshooting.md b/content/en/building/guides/interoperability/troubleshooting.md index f94f0746d..2a449266e 100644 --- a/content/en/building/guides/interoperability/troubleshooting.md +++ b/content/en/building/guides/interoperability/troubleshooting.md @@ -1,7 +1,7 @@ --- title: "Troubleshooting Interoperability" -linkTitle: "Troubleshooting Interoperability" -weight: +linkTitle: "Troubleshooting" +weight: 5 description: > Guide to troubleshooting OpenHIM, Mediators, and configurations for interoperability workflows keywords: openmrs interoperability