deploy: medic/cht-docs@5fdc625

medic · Nov 7, 2024 · 6bf59fe · 6bf59fe
1 parent 96f270d
commit 6bf59fe
Show file tree

Hide file tree

Showing 467 changed files with 25,583 additions and 24,803 deletions.
diff --git a/404.html b/404.html
diff --git a/apps/concepts/hierarchy/index.html b/apps/concepts/hierarchy/index.html
@@ -1,2 +1,2 @@
-<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/concepts/hierarchy/</title>
-<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/concepts/hierarchy/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/concepts/hierarchy/"></head></html>
+<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/hierarchy/</title>
+<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/hierarchy/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/hierarchy/"></head></html>
diff --git a/apps/concepts/workflows/index.html b/apps/concepts/workflows/index.html
@@ -1,2 +1,2 @@
-<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/concepts/workflows/</title>
-<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/concepts/workflows/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/concepts/workflows/"></head></html>
+<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/workflows-overview/</title>
+<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/workflows-overview/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/workflows-overview/"></head></html>
diff --git a/apps/features/muting/index.html b/apps/features/muting/index.html
@@ -1,2 +1,2 @@
-<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/features/muting/</title>
-<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/features/muting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/features/muting/"></head></html>
+<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/muting/</title>
+<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/muting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/muting/"></head></html>
diff --git a/apps/tutorials/death-reporting/index.html b/apps/tutorials/death-reporting/index.html
@@ -1,2 +1,2 @@
-<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/tutorials/death-reporting/</title>
-<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/tutorials/death-reporting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/tutorials/death-reporting/"></head></html>
+<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/</title>
+<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/"></head></html>
diff --git a/buidling/tutorials/death-reporting/index.html b/buidling/tutorials/death-reporting/index.html
@@ -0,0 +1,2 @@
+<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/</title>
+<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/"></head></html>
diff --git a/building/concepts/access/index.html b/building/concepts/access/index.html
diff --git a/building/concepts/care-guides/index.html b/building/concepts/care-guides/index.html
diff --git a/building/concepts/forms/index.html b/building/concepts/forms/index.html
diff --git a/building/concepts/hierarchy/index.html b/building/concepts/hierarchy/index.html
diff --git a/building/concepts/index.html b/building/concepts/index.html
diff --git a/building/concepts/index.xml b/building/concepts/index.xml
@@ -3,8 +3,5 @@ Hardware &amp;amp; Software RequirementsHardware procurement, ownership, and man
 Accessing on DesktopOn desktop devices, there is no need to download anything. Simply go to a web browser and type in your unique URL, for example:</description></item><item><title>Navigating CHT Apps</title><link>https://docs.communityhealthtoolkit.org/building/concepts/navigation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/navigation/</guid><description>Summary of Page TabsPage tabs are the primary way to navigate apps built with the Core Framework. The number of tabs is variable depending on the user’s role and place in the hierarchy. For example, non-admin users don’t have Messages. The Reports tab is accessible to CHWs but often located inside the secondary menu drawer.
 Messages: A place for community-based staff to send and exchange messages Tasks: This is a list of upcoming visits, follow-ups, or other required tasks Reports: A detailed history of all forms submitted by CHWs and other staff People: This is where profiles of districts, staff, CHWs and patients live Targets: Displays real-time visualizations of key activity and impact indicators The Menu Drawer Tap the menu icon in the upper right corner of the header to access other pages, edit personal settings, view sync status and more.</description></item><item><title>Forms</title><link>https://docs.communityhealthtoolkit.org/building/concepts/forms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/forms/</guid><description>Forms are a building block of all CHT apps. They are used when creating or editing contacts, and when completing a care guide or survey within the app. Forms are also used to interpret SMS interactions with the CHT.
 When a completed form is submitted, it is treated as a Report in the app. All reports can be viewed in the Reports tab by those with the proper access within the hierarchy.</description></item><item><title>Care Guides</title><link>https://docs.communityhealthtoolkit.org/building/concepts/care-guides/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/care-guides/</guid><description>Care Guides Forms are used to build “Care Guides” that take health workers through care protocols and provide decision support for their interactions with patients. App designers can use the basic form building functionality in a variety of ways.
-Care Guides also allow CHWs to register new families and people, assess a sick child, and enroll a new pregnancy into an antenatal care schedule. Care Guides can be located in many parts of your app, including the Tasks, People, and Reports tabs.</description></item><item><title>Building Workflows</title><link>https://docs.communityhealthtoolkit.org/building/concepts/workflows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/workflows/</guid><description>Workflows can be defined within apps built with the Core Framework to connect actions and data with people. Forms are the main building block of tasks and messaging workflows, and are useful in creating reminders for follow-up visits or referrals.
-TasksTasks within the app can drive a workflow, ensuring that the right actions are taken for people at the right time. Tasks indicate a recommended action to the user. They indicate who the user should perform the action with, and the recommended timeframe of that action.</description></item><item><title>Configurable Hierarchies</title><link>https://docs.communityhealthtoolkit.org/building/concepts/hierarchy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/hierarchy/</guid><description>The Core Framework requires a hierarchy to organize the information in the app. It is often based on the hierarchy of a health system within a particular geographic region.
-Large deployment sites often need three or more levels of place hierarchy, while some small sites need fewer than three levels. For this reason, the Core Framework’s information hierarchies are configurable to meet a users needs.
-A user logging into their app will see a custom set of people, tasks, reports, and analytics based on the hierarchy level that they belong to.</description></item><item><title>Users</title><link>https://docs.communityhealthtoolkit.org/building/concepts/users/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/users/</guid><description>Apps built with the Core Framework use roles and permissions to determine who has access to what data. User roles are general categories you can use to assign a collection of broad permissions to users. There are two classes of roles: online and offline. Generally speaking, CHWs are usually offline users, while managers and nurses are usually online users. SMS users do not use the app, and thus do not have a user role.</description></item><item><title>Interoperability</title><link>https://docs.communityhealthtoolkit.org/building/concepts/interoperability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/interoperability/</guid><description>IntroductionInteroperability refers to the ability of different health information systems and applications to communicate with each other and exchange data seamlessly. With interoperability, patient information can be seen, exchanged, and used across different platforms. The information/data exchanged has to be understood across the different software for these systems to become interoperable. This is different from integration which requires custom development to connect two specific systems together.
+Care Guides also allow CHWs to register new families and people, assess a sick child, and enroll a new pregnancy into an antenatal care schedule. Care Guides can be located in many parts of your app, including the Tasks, People, and Reports tabs.</description></item><item><title>Users</title><link>https://docs.communityhealthtoolkit.org/building/concepts/users/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/users/</guid><description>Apps built with the Core Framework use roles and permissions to determine who has access to what data. User roles are general categories you can use to assign a collection of broad permissions to users. There are two classes of roles: online and offline. Generally speaking, CHWs are usually offline users, while managers and nurses are usually online users. SMS users do not use the app, and thus do not have a user role.</description></item><item><title>Interoperability</title><link>https://docs.communityhealthtoolkit.org/building/concepts/interoperability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.communityhealthtoolkit.org/building/concepts/interoperability/</guid><description>IntroductionInteroperability refers to the ability of different health information systems and applications to communicate with each other and exchange data seamlessly. With interoperability, patient information can be seen, exchanged, and used across different platforms. The information/data exchanged has to be understood across the different software for these systems to become interoperable. This is different from integration which requires custom development to connect two specific systems together.
 Interoperability is the best practice for health systems because it allows information from one system to be shared with one or more other systems with no additional development.</description></item></channel></rss>
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		<!doctype html><html lang=en><head><title>https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/</title>
		<link rel=canonical href=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://docs.communityhealthtoolkit.org/building/workflows/death-reporting/"></head></html>