Skip to Content

Changes for page Home

Last modified by Amicus Wellness FLAGs Admin on 2025/12/17 17:35
From version 4.1
edited by Amicus Wellness FLAGs Admin
on 2025/12/17 05:37
Change comment: There is no comment for this version
To version 2.3
edited by Amicus Wellness FLAGs Admin
on 2025/12/17 05:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,52 +18,20 @@
18 18  * Enable secure collaboration between multiple stakeholders while keeping access controlled
19 19  * Showcase partner organizations through dedicated profile pages (directory + impact pages)
20 20  
21 -== Who this portal is for ==
22 22  
23 -Amicus is built to serve multiple stakeholders, and this portal is organized to support each group:
24 24  
25 -* **Patients & Caregivers:** education, care pathways, program guides, FAQs, and self-service support
26 -* **Clinics & Hospitals:** referral workflows, clinical documentation guides, integration references, and care coordination resources
27 -* **Doctors & Health Practitioners:** triage pathways, clinical decision support resources, patient follow-up workflows
28 -* **CBOs / FBOs / NGOs:** enrollment guides, case management workflows, safeguarding resources, community programs
29 -* **Donors & Supporters:** transparency references, program summaries, how support flows, impact reporting structure
30 -* **Partner Administrators & Staff:** operational runbooks, onboarding steps, user management, support procedures
23 +To make the most out of your wiki, log-in and:
31 31  
32 -== What Amicus enables (high-level) ==
25 +Use the {{displayIcon name="pencil"/}} button above to //edit// this page and start customizing your wiki to your needs.
33 33  
34 -Amicus supports modern, collaborative healthcare and community support through:
27 +Use the {{displayIcon name="add"/}} button above to //add// more pages to your wiki and create the //hierarchy// that best organizes your content.
35 35  
36 -=== 1) Secure, accessible communication ===
29 +Use the {{displayIcon name="home"/}} breadcrumbs located above the title to //navigate// inside your pages. It's easy to get lost in a big wiki without them.
37 37  
38 -Amicus makes support reachable where people already are—while keeping communication structured and auditable for partners.
31 +You can also use the [[Sandbox>>Sandbox.WebHome]] for more demo content and generally a place to experiment with your wiki's features.
39 39  
40 -=== 2) AI-assisted self-service support and knowledge access ===
33 + {{box}}Learn more on how to use XWiki with the [[Getting Started Guide>>https://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/GettingStarted/WebHome]].{{/box}}
41 41  
42 -Partners can maintain their own trusted documents and information resources, and users can receive helpful answers through guided experiences (with clear boundaries and safety rules).
43 -
44 -=== 3) Health journeys, screening, and follow-up ===
45 -
46 -Amicus supports structured care journeys (for example: maternal health monitoring, symptom journaling, follow-up check-ins) so partners can identify risk early and respond faster.
47 -
48 -=== 4) Referrals and coordinated care across levels ===
49 -
50 -Amicus is designed to support referrals and continuity of care across community programs, clinics, and hospitals—so a patient’s pathway is easier to manage and less fragmented.
51 -
52 -=== 5) Partner collaboration and support ecosystems ===
53 -
54 -Amicus strengthens coordination between organizations: shared program resources, structured handoffs, escalation pathways, and partner-to-partner collaboration—without mixing data inappropriately.
55 -
56 -== Privacy, trust, and responsible use ==
57 -
58 -Amicus is built around **privacy, consent, and controlled access**.
59 -
60 -* Information is shared based on **permissions and purpose**, not convenience.
61 -* Partner access is managed through **roles**, **auditability**, and **data minimization** principles.
62 -* Where clinical data exchange is needed, Amicus supports **standards-aligned interoperability approaches** (e.g., structured exchange models) to make collaboration safer and clearer.
63 -* This Wiki contains both public-facing partner materials **and** restricted operational content—access depends on your role.
64 -
65 -
66 -
67 67  (% class="row" %)
68 68  (((
69 69  (% class="col-xs-12 col-sm-6" %)