{"schemaVersion":2,"canonicalOrigin":"https://mansoq.com","languages":["en","ar"],"entity":{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://mansoq.com/#organization","name":"MANSOQ","alternateName":"منسوق","url":"https://mansoq.com/","logo":{"@type":"ImageObject","url":"https://mansoq.com/brand/mansoq-logo.svg"},"description":"MANSOQ connects clinical care, hospital operations and the revenue cycle, with configurable HIMS and RCM workflows for healthcare teams.","founder":{"@id":"https://mansoq.com/#owner"}},{"@type":"WebSite","@id":"https://mansoq.com/#website","url":"https://mansoq.com/","name":"MANSOQ","alternateName":"منسوق","inLanguage":["en","ar"],"publisher":{"@id":"https://mansoq.com/#organization"}},{"@type":"Person","@id":"https://mansoq.com/#owner","name":"Mohamed (AK) Abdel Khalek","alternateName":["Mohamed Abdel Khalek","Mohamed AK Abdel Khalek"],"sameAs":["https://www.linkedin.com/in/mohamedakn/"],"description":"Mohamed (AK) Abdel Khalek is the founder and owner of MANSOQ. Identity supplied by MANSOQ.","jobTitle":"Founder and owner"}]},"ownership":{"name":"Mohamed (AK) Abdel Khalek","role":"Founder and owner","profile":"https://www.linkedin.com/in/mohamedakn/","attribution":"Founder and owner identity supplied by MANSOQ. The LinkedIn profile identifies the person. No CEO role or personal authorship of product documentation is asserted."},"interpretation":"This is the public marketing knowledge catalogue. Planned services are not active subscriptions. Integration adapters do not establish regulatory certification. No customer, clinical, account, draft or private dashboard data is included.","pages":[{"slug":"/about","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/about","title":"About MANSOQ | Connected Care & Revenue","eyebrow":"MANSOQ Platform","summary":"MANSOQ brings clinical, operational and revenue workflows together so teams can work from one connected foundation.","sections":[{"kind":"cards","intro":"","items":[{"text":"Bring care and revenue into one coherent healthcare operating platform with a Saudi-rooted identity.","title":"Our direction"},{"href":"/about/open-source","text":"MANSOQ builds on OHC/CARE-derived components and other open-source projects. Each component retains its own licence and attribution obligations.","title":"Our foundation"},{"text":"Saudi revenue-cycle models and engines, payer rules, financial controls, terminology workflows and a unified MANSOQ brand.","title":"Our additions"}],"title":"Built from a shared foundation. Developed for MANSOQ."},{"kind":"cards","intro":"","items":[{"text":"Role-based access and facility context limit what each team can view and change.","title":"Access by responsibility"},{"text":"Clinical and financial actions carry traceability; revenue controls preserve the evidence behind decisions.","title":"Audit and evidence"},{"text":"Hosting, residency, backups, retention and incident responsibilities are agreed for each implementation.","title":"Deployment review"},{"text":"MANSOQ does not inherit OHC certifications, endorsements or deployment counts. Ask for MANSOQ-specific evidence during evaluation.","title":"Certification evidence"}],"title":"Trust comes from controls you can examine."}],"seoTitle":"About MANSOQ | Connected Care & Revenue","seoDescription":"MANSOQ brings clinical, operational and revenue workflows together so teams can work from one connected foundation.","description":"MANSOQ brings clinical, operational and revenue workflows together so teams can work from one connected foundation.","answers":[]},"ar":{"url":"https://mansoq.com/about?lang=ar","title":"عن منسوق | رعاية وإيراد متصلان","eyebrow":"منصة منسوق","summary":"يجمع منسوق سير العمل السريري والتشغيلي والإيراد لتمكين الفرق من العمل على أساس متصل.","sections":[{"kind":"cards","intro":"","items":[{"text":"جمع الرعاية والإيراد في منصة تشغيل صحية مترابطة بهوية سعودية.","title":"توجهنا"},{"href":"/about/open-source","text":"يستند منسوق إلى مكونات مشتقة من OHC وCARE ومشاريع مفتوحة المصدر أخرى. يحتفظ كل مكون بترخيصه ومتطلبات نسبه.","title":"أساسنا"},{"text":"نماذج ومحركات دورة الإيراد السعودية وقواعد الجهات الدافعة والضوابط المالية ومسارات المصطلحات وهوية منسوق الموحدة.","title":"إضافاتنا"}],"title":"مبني على أساس مشترك ومطور لمنسوق."},{"kind":"cards","intro":"","items":[{"text":"تحدد الصلاحيات بحسب الدور وسياق المنشأة ما يمكن لكل فريق عرضه وتغييره.","title":"صلاحيات بحسب المسؤولية"},{"text":"تتيح الإجراءات السريرية والمالية التتبع، وتحفظ ضوابط الإيراد الأدلة الداعمة للقرارات.","title":"التدقيق والأدلة"},{"text":"تُتفق الاستضافة وإقامة البيانات والنسخ الاحتياطي والاحتفاظ ومسؤوليات الحوادث لكل تطبيق.","title":"مراجعة النشر"},{"text":"لا يرث منسوق اعتمادات OHC أو توصياتها أو أعداد تطبيقاتها. اطلب أدلة خاصة بمنسوق أثناء التقييم.","title":"أدلة الاعتماد"}],"title":"الثقة تأتي من ضوابط يمكن فحصها."}],"seoTitle":"عن منسوق | رعاية وإيراد متصلان","seoDescription":"يجمع منسوق سير العمل السريري والتشغيلي والإيراد لتمكين الفرق من العمل على أساس متصل.","description":"يجمع منسوق سير العمل السريري والتشغيلي والإيراد لتمكين الفرق من العمل على أساس متصل.","answers":[]}},{"slug":"/about/open-source","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/about/open-source","title":"Open-Source Foundation & Attribution | MANSOQ","eyebrow":"MANSOQ Platform","summary":"MANSOQ includes components derived from Open Healthcare Network and other projects. Upstream licences and notices remain applicable.","sections":[{"kind":"cards","intro":"","items":[{"text":"Bring care and revenue into one coherent healthcare operating platform with a Saudi-rooted identity.","title":"Our direction"},{"href":"/about/open-source","text":"MANSOQ builds on OHC/CARE-derived components and other open-source projects. Each component retains its own licence and attribution obligations.","title":"Our foundation"},{"text":"Saudi revenue-cycle models and engines, payer rules, financial controls, terminology workflows and a unified MANSOQ brand.","title":"Our additions"}],"title":"Built from a shared foundation. Developed for MANSOQ."},{"kind":"cards","intro":"","items":[{"href":"https://ohc.network","text":"Visit the upstream project to understand the CARE foundation and its own programs. OHC outcomes and endorsements belong to OHC.","title":"Open Healthcare Network"},{"href":"/contact?interest=Partnership","text":"Request architecture, integration guidance and component-level licence information from the MANSOQ team.","title":"Technical documentation"}],"title":"Source and attribution."}],"seoTitle":"Open-Source Foundation & Attribution | MANSOQ","seoDescription":"MANSOQ includes components derived from Open Healthcare Network and other projects. Upstream licences and notices remain applicable.","description":"MANSOQ includes components derived from Open Healthcare Network and other projects. Upstream licences and notices remain applicable.","answers":[]},"ar":{"url":"https://mansoq.com/about/open-source?lang=ar","title":"أساس المصدر المفتوح والإسناد | منسوق","eyebrow":"منصة منسوق","summary":"يتضمن منسوق مكونات مشتقة من شبكة الرعاية الصحية المفتوحة ومشاريع أخرى. تبقى تراخيص وإشعارات المصادر الأصلية سارية.","sections":[{"kind":"cards","intro":"","items":[{"text":"جمع الرعاية والإيراد في منصة تشغيل صحية مترابطة بهوية سعودية.","title":"توجهنا"},{"href":"/about/open-source","text":"يستند منسوق إلى مكونات مشتقة من OHC وCARE ومشاريع مفتوحة المصدر أخرى. يحتفظ كل مكون بترخيصه ومتطلبات نسبه.","title":"أساسنا"},{"text":"نماذج ومحركات دورة الإيراد السعودية وقواعد الجهات الدافعة والضوابط المالية ومسارات المصطلحات وهوية منسوق الموحدة.","title":"إضافاتنا"}],"title":"مبني على أساس مشترك ومطور لمنسوق."},{"kind":"cards","intro":"","items":[{"href":"https://ohc.network","text":"زر المشروع الأصلي لفهم أساس CARE وبرامجه. تعود نتائج OHC وتوصياتها إلى OHC.","title":"شبكة الرعاية الصحية المفتوحة"},{"href":"/contact?interest=Partnership","text":"اطلب المعمارية وإرشادات التكامل ومعلومات تراخيص المكونات من فريق منسوق.","title":"الوثائق التقنية"}],"title":"المصدر والنسب."}],"seoTitle":"أساس المصدر المفتوح والإسناد | منسوق","seoDescription":"يتضمن منسوق مكونات مشتقة من شبكة الرعاية الصحية المفتوحة ومشاريع أخرى. تبقى تراخيص وإشعارات المصادر الأصلية سارية.","description":"يتضمن منسوق مكونات مشتقة من شبكة الرعاية الصحية المفتوحة ومشاريع أخرى. تبقى تراخيص وإشعارات المصادر الأصلية سارية.","answers":[]}},{"slug":"/about/security-compliance","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/about/security-compliance","title":"Security & Deployment Compliance | MANSOQ","eyebrow":"MANSOQ Platform","summary":"Evaluate access controls, auditability, hosting and integration requirements with evidence for the specific MANSOQ deployment.","sections":[{"kind":"cards","intro":"","items":[{"text":"Role-based access and facility context limit what each team can view and change.","title":"Access by responsibility"},{"text":"Clinical and financial actions carry traceability; revenue controls preserve the evidence behind decisions.","title":"Audit and evidence"},{"text":"Hosting, residency, backups, retention and incident responsibilities are agreed for each implementation.","title":"Deployment review"},{"text":"MANSOQ does not inherit OHC certifications, endorsements or deployment counts. Ask for MANSOQ-specific evidence during evaluation.","title":"Certification evidence"}],"title":"Trust comes from controls you can examine."},{"kind":"cards","intro":"","items":[{"text":"The clinical core uses FHIR-aligned resources and APIs. National exchanges use their own governed profiles.","title":"Clinical interoperability"},{"href":"/integrations/nphies","text":"NPHIES adapters prepare and validate exchange payloads. Production access depends on credentials, testing and regulator approval.","title":"Saudi revenue exchange"},{"text":"Terminology releases, file hashes and licence references are recorded. Licensed coding data is supplied through authorized sources.","title":"Terminology ownership"},{"text":"Clinical, web, remote care, revenue and intelligence components retain clear runtime and release boundaries.","title":"Modular deployment"}],"title":"Open interfaces. Explicit boundaries."}],"seoTitle":"Security & Deployment Compliance | MANSOQ","seoDescription":"Evaluate access controls, auditability, hosting and integration requirements with evidence for the specific MANSOQ deployment.","description":"Evaluate access controls, auditability, hosting and integration requirements with evidence for the specific MANSOQ deployment.","answers":[]},"ar":{"url":"https://mansoq.com/about/security-compliance?lang=ar","title":"الأمن والامتثال عند النشر | منسوق","eyebrow":"منصة منسوق","summary":"قيّم ضوابط الوصول والتدقيق والاستضافة ومتطلبات التكامل بأدلة خاصة بتطبيق منسوق المحدد.","sections":[{"kind":"cards","intro":"","items":[{"text":"تحدد الصلاحيات بحسب الدور وسياق المنشأة ما يمكن لكل فريق عرضه وتغييره.","title":"صلاحيات بحسب المسؤولية"},{"text":"تتيح الإجراءات السريرية والمالية التتبع، وتحفظ ضوابط الإيراد الأدلة الداعمة للقرارات.","title":"التدقيق والأدلة"},{"text":"تُتفق الاستضافة وإقامة البيانات والنسخ الاحتياطي والاحتفاظ ومسؤوليات الحوادث لكل تطبيق.","title":"مراجعة النشر"},{"text":"لا يرث منسوق اعتمادات OHC أو توصياتها أو أعداد تطبيقاتها. اطلب أدلة خاصة بمنسوق أثناء التقييم.","title":"أدلة الاعتماد"}],"title":"الثقة تأتي من ضوابط يمكن فحصها."},{"kind":"cards","intro":"","items":[{"text":"يستخدم الأساس السريري موارد وواجهات متوافقة مع FHIR. وتستخدم التبادلات الوطنية ملفاتها المحكومة.","title":"التشغيل البيني السريري"},{"href":"/integrations/nphies","text":"تجهز موائمات نفيس بيانات التبادل وتتحقق منها. ويتطلب الاستخدام الفعلي بيانات اعتماد واختبارات وموافقة الجهة المنظمة.","title":"تبادل الإيراد السعودي"},{"text":"تسجل إصدارات المصطلحات وبصمات الملفات ومراجع التراخيص. وتُحمّل بيانات الترميز المرخصة من مصادر مخولة.","title":"حوكمة المصطلحات"},{"text":"تحتفظ المكونات السريرية والواجهات والرعاية عن بعد والإيراد والذكاء بحدود تشغيل وإصدار واضحة.","title":"نشر معياري"}],"title":"واجهات مفتوحة وحدود واضحة."}],"seoTitle":"الأمن والامتثال عند النشر | منسوق","seoDescription":"قيّم ضوابط الوصول والتدقيق والاستضافة ومتطلبات التكامل بأدلة خاصة بتطبيق منسوق المحدد.","description":"قيّم ضوابط الوصول والتدقيق والاستضافة ومتطلبات التكامل بأدلة خاصة بتطبيق منسوق المحدد.","answers":[]}},{"slug":"/blog","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/blog","title":"Healthcare Technology & Revenue Cycle Insights | MANSOQ","eyebrow":"Resources","summary":"Product updates and practical explanations for teams connecting care, operations and revenue.","sections":[],"seoTitle":"Healthcare Technology & Revenue Cycle Insights | MANSOQ","seoDescription":"Product updates and practical explanations for teams connecting care, operations and revenue.","description":"Product updates and practical explanations for teams connecting care, operations and revenue.","answers":[]},"ar":{"url":"https://mansoq.com/blog?lang=ar","title":"رؤى التقنية الصحية ودورة الإيراد | منسوق","eyebrow":"الموارد","summary":"تحديثات المنتج وشروح عملية للفرق التي تربط الرعاية والتشغيل والإيراد.","sections":[],"seoTitle":"رؤى التقنية الصحية ودورة الإيراد | منسوق","seoDescription":"تحديثات المنتج وشروح عملية للفرق التي تربط الرعاية والتشغيل والإيراد.","description":"تحديثات المنتج وشروح عملية للفرق التي تربط الرعاية والتشغيل والإيراد.","answers":[]}},{"slug":"/blog/connecting-care-and-revenue","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/blog/connecting-care-and-revenue","title":"Connecting Clinical Care and Revenue Cycle | MANSOQ","eyebrow":"Platform notes · 8 October 2026","summary":"A financial record is most useful when it follows the encounter instead of creating a second clinical workflow.","sections":[{"kind":"steps","intro":"","items":[{"text":"Link the patient and episode to coverage, payer networks, benefit rules, eligibility preparation and authorization requirements.","title":"Before the visit"},{"text":"Resolve effective-dated tariffs, capture charges, evaluate cost sharing and reserve benefit limits against the existing encounter.","title":"As care is delivered"},{"text":"Prepare claim packages, validate exchanges, track remittance exceptions and reconcile financial evidence with the ledger.","title":"From claim to collection"},{"text":"Keep versioned policies, append-only financial records, explicit unknown values and decision gates that block unsupported activation.","title":"Control and traceability"}],"title":"Care and revenue, aligned at every step."}],"seoTitle":"Connecting Clinical Care and Revenue Cycle | MANSOQ","seoDescription":"A financial record is most useful when it follows the encounter instead of creating a second clinical workflow.","description":"A financial record is most useful when it follows the encounter instead of creating a second clinical workflow.","answers":[]},"ar":{"url":"https://mansoq.com/blog/connecting-care-and-revenue?lang=ar","title":"ربط الرعاية السريرية ودورة الإيراد | منسوق","eyebrow":"ملاحظات المنصة · ٨ أكتوبر ٢٠٢٦","summary":"يكون السجل المالي أكثر فائدة عندما يتبع الزيارة بدلًا من إنشاء مسار سريري ثانٍ.","sections":[{"kind":"steps","intro":"","items":[{"text":"ربط المريض والحالة بالتغطية وشبكات الجهات الدافعة وقواعد المنافع وتجهيز الأهلية ومتطلبات الموافقة.","title":"قبل الزيارة"},{"text":"تحديد الأسعار السارية وتسجيل الرسوم وتقييم المشاركة في التكلفة وحجز حدود المنافع ضمن الزيارة الحالية.","title":"أثناء تقديم الرعاية"},{"text":"تجهيز ملفات المطالبات والتحقق من التبادل ومتابعة استثناءات التسويات ومطابقة الأدلة المالية مع دفتر الحسابات.","title":"من المطالبة إلى التحصيل"},{"text":"حفظ السياسات بإصدارات والسجلات المالية غير القابلة للتعديل والقيم غير المعروفة وبوابات القرار التي تمنع التفعيل غير المدعوم.","title":"الرقابة والتتبع"}],"title":"الرعاية والإيراد في نسق واحد في كل خطوة."}],"seoTitle":"ربط الرعاية السريرية ودورة الإيراد | منسوق","seoDescription":"يكون السجل المالي أكثر فائدة عندما يتبع الزيارة بدلًا من إنشاء مسار سريري ثانٍ.","description":"يكون السجل المالي أكثر فائدة عندما يتبع الزيارة بدلًا من إنشاء مسار سريري ثانٍ.","answers":[]}},{"slug":"/blog/implementing-with-your-team","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/blog/implementing-with-your-team","title":"Healthcare Software Implementation with Your Team | MANSOQ","eyebrow":"Platform notes · 8 October 2026","summary":"Shared workflow understanding, rehearsal and training give implementation a practical foundation.","sections":[{"kind":"steps","intro":"","items":[{"text":"Map services, teams, patient journeys, billing responsibilities and the systems you already use.","title":"Understand your facility"},{"text":"Prepare facility structure, staff roles, service catalogues, forms, terminology and approved integrations.","title":"Configure the foundation"},{"text":"Use agreed scenarios to validate clinical, operational and financial handovers before rollout.","title":"Rehearse real workflows"},{"text":"Train teams, begin with a defined scope, review feedback and expand with release and support controls.","title":"Launch in phases"}],"title":"A rollout your people can follow."}],"seoTitle":"Healthcare Software Implementation with Your Team | MANSOQ","seoDescription":"Shared workflow understanding, rehearsal and training give implementation a practical foundation.","description":"Shared workflow understanding, rehearsal and training give implementation a practical foundation.","answers":[]},"ar":{"url":"https://mansoq.com/blog/implementing-with-your-team?lang=ar","title":"تطبيق برمجيات الرعاية الصحية مع فريقك | منسوق","eyebrow":"ملاحظات المنصة · ٨ أكتوبر ٢٠٢٦","summary":"يمنح الفهم المشترك لسير العمل والتجربة والتدريب التطبيق أساسًا عمليًا.","sections":[{"kind":"steps","intro":"","items":[{"text":"تحديد الخدمات والفرق ورحلات المرضى ومسؤوليات الفوترة والأنظمة الحالية.","title":"فهم منشأتك"},{"text":"تجهيز هيكل المنشأة وصلاحيات الموظفين ودليل الخدمات والنماذج والمصطلحات والتكاملات المعتمدة.","title":"تهيئة الأساس"},{"text":"استخدام سيناريوهات متفق عليها للتحقق من انتقال العمل السريري والتشغيلي والمالي قبل الإطلاق.","title":"تجربة سير العمل"},{"text":"تدريب الفرق والبدء بنطاق واضح ومراجعة الملاحظات والتوسع مع ضوابط الإصدارات والدعم.","title":"إطلاق مرحلي"}],"title":"إطلاق يستطيع فريقك متابعته."}],"seoTitle":"تطبيق برمجيات الرعاية الصحية مع فريقك | منسوق","seoDescription":"يمنح الفهم المشترك لسير العمل والتجربة والتدريب التطبيق أساسًا عمليًا.","description":"يمنح الفهم المشترك لسير العمل والتجربة والتدريب التطبيق أساسًا عمليًا.","answers":[]}},{"slug":"/blog/saudi-revenue-controls","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/blog/saudi-revenue-controls","title":"Traceable Saudi Healthcare Revenue Controls | MANSOQ","eyebrow":"Platform notes · 8 October 2026","summary":"Effective dates, explicit unknown values and controlled activation help teams understand why a financial decision was made.","sections":[{"kind":"steps","intro":"","items":[{"text":"Link the patient and episode to coverage, payer networks, benefit rules, eligibility preparation and authorization requirements.","title":"Before the visit"},{"text":"Resolve effective-dated tariffs, capture charges, evaluate cost sharing and reserve benefit limits against the existing encounter.","title":"As care is delivered"},{"text":"Prepare claim packages, validate exchanges, track remittance exceptions and reconcile financial evidence with the ledger.","title":"From claim to collection"},{"text":"Keep versioned policies, append-only financial records, explicit unknown values and decision gates that block unsupported activation.","title":"Control and traceability"}],"title":"Care and revenue, aligned at every step."},{"kind":"cards","intro":"","items":[{"text":"The clinical core uses FHIR-aligned resources and APIs. National exchanges use their own governed profiles.","title":"Clinical interoperability"},{"href":"/integrations/nphies","text":"NPHIES adapters prepare and validate exchange payloads. Production access depends on credentials, testing and regulator approval.","title":"Saudi revenue exchange"},{"text":"Terminology releases, file hashes and licence references are recorded. Licensed coding data is supplied through authorized sources.","title":"Terminology ownership"},{"text":"Clinical, web, remote care, revenue and intelligence components retain clear runtime and release boundaries.","title":"Modular deployment"}],"title":"Open interfaces. Explicit boundaries."}],"seoTitle":"Traceable Saudi Healthcare Revenue Controls | MANSOQ","seoDescription":"Effective dates, explicit unknown values and controlled activation help teams understand why a financial decision was made.","description":"Effective dates, explicit unknown values and controlled activation help teams understand why a financial decision was made.","answers":[]},"ar":{"url":"https://mansoq.com/blog/saudi-revenue-controls?lang=ar","title":"ضوابط قابلة للتتبع للإيراد الصحي السعودي | منسوق","eyebrow":"ملاحظات المنصة · ٨ أكتوبر ٢٠٢٦","summary":"تساعد فترات السريان والقيم غير المعروفة الصريحة والتفعيل المحكوم الفرق على فهم أسباب القرار المالي.","sections":[{"kind":"steps","intro":"","items":[{"text":"ربط المريض والحالة بالتغطية وشبكات الجهات الدافعة وقواعد المنافع وتجهيز الأهلية ومتطلبات الموافقة.","title":"قبل الزيارة"},{"text":"تحديد الأسعار السارية وتسجيل الرسوم وتقييم المشاركة في التكلفة وحجز حدود المنافع ضمن الزيارة الحالية.","title":"أثناء تقديم الرعاية"},{"text":"تجهيز ملفات المطالبات والتحقق من التبادل ومتابعة استثناءات التسويات ومطابقة الأدلة المالية مع دفتر الحسابات.","title":"من المطالبة إلى التحصيل"},{"text":"حفظ السياسات بإصدارات والسجلات المالية غير القابلة للتعديل والقيم غير المعروفة وبوابات القرار التي تمنع التفعيل غير المدعوم.","title":"الرقابة والتتبع"}],"title":"الرعاية والإيراد في نسق واحد في كل خطوة."},{"kind":"cards","intro":"","items":[{"text":"يستخدم الأساس السريري موارد وواجهات متوافقة مع FHIR. وتستخدم التبادلات الوطنية ملفاتها المحكومة.","title":"التشغيل البيني السريري"},{"href":"/integrations/nphies","text":"تجهز موائمات نفيس بيانات التبادل وتتحقق منها. ويتطلب الاستخدام الفعلي بيانات اعتماد واختبارات وموافقة الجهة المنظمة.","title":"تبادل الإيراد السعودي"},{"text":"تسجل إصدارات المصطلحات وبصمات الملفات ومراجع التراخيص. وتُحمّل بيانات الترميز المرخصة من مصادر مخولة.","title":"حوكمة المصطلحات"},{"text":"تحتفظ المكونات السريرية والواجهات والرعاية عن بعد والإيراد والذكاء بحدود تشغيل وإصدار واضحة.","title":"نشر معياري"}],"title":"واجهات مفتوحة وحدود واضحة."}],"seoTitle":"ضوابط قابلة للتتبع للإيراد الصحي السعودي | منسوق","seoDescription":"تساعد فترات السريان والقيم غير المعروفة الصريحة والتفعيل المحكوم الفرق على فهم أسباب القرار المالي.","description":"تساعد فترات السريان والقيم غير المعروفة الصريحة والتفعيل المحكوم الفرق على فهم أسباب القرار المالي.","answers":[]}},{"slug":"/careers","lastModified":"2026-10-11T04:29:37.967Z","en":{"url":"https://mansoq.com/careers","title":"Healthcare Technology Careers | MANSOQ","eyebrow":"MANSOQ Platform","summary":"Introduce your experience through the contact form. Open roles will be published here when confirmed.","sections":[{"kind":"cards","intro":"","items":[{"text":"Bring care and revenue into one coherent healthcare operating platform with a Saudi-rooted identity.","title":"Our direction"},{"href":"/about/open-source","text":"MANSOQ builds on OHC/CARE-derived components and other open-source projects. Each component retains its own licence and attribution obligations.","title":"Our foundation"},{"text":"Saudi revenue-cycle models and engines, payer rules, financial controls, terminology workflows and a unified MANSOQ brand.","title":"Our additions"}],"title":"Built from a shared foundation. Developed for MANSOQ."},{"kind":"cards","intro":"We start with people and their work, state scope precisely and agree responsibilities before anything goes live.","items":[{"text":"Clinicians and informaticists who turn care workflows, documentation and handovers into precise product scope.","title":"Clinical informatics"},{"text":"Specialists in eligibility, preauthorization, coding, claims, denials and reconciliation who understand NPHIES exchange and payer rules.","title":"Revenue cycle operations"},{"text":"Engineers building the shared record, clinical and departmental modules, NPHIES and ZATCA integrations, interfaces, analytics and reviewed AI.","title":"Engineering"},{"href":"/resources/implementation","text":"People who plan migration, interfaces, training and acceptance with customer teams, and stay accountable through go-live and support.","title":"Implementation"}],"title":"The work we hire for."},{"kind":"steps","intro":"We publish open positions only when they are confirmed. You can introduce yourself now.","items":[{"href":"/contact?request=general","text":"Choose General enquiry and tell us which of these areas fits your experience.","title":"Use the contact page"},{"text":"Include your current role, relevant experience and location. Do not send patient information or other people’s personal data.","title":"Share the essentials"},{"text":"Confirmed roles are published here.","title":"Watch this page"}],"title":"Express your interest."}],"seoTitle":"Healthcare Technology Careers | MANSOQ","seoDescription":"Introduce your experience through the contact form. Open roles will be published here when confirmed.","description":"Introduce your experience through the contact form. Open roles will be published here when confirmed.","answers":[]},"ar":{"url":"https://mansoq.com/careers?lang=ar","title":"فرص العمل في التقنية الصحية | منسوق","eyebrow":"منصة منسوق","summary":"قدم خبرتك عبر نموذج التواصل. ستُنشر الوظائف المفتوحة هنا بعد تأكيدها.","sections":[{"kind":"cards","intro":"","items":[{"text":"جمع الرعاية والإيراد في منصة تشغيل صحية مترابطة بهوية سعودية.","title":"توجهنا"},{"href":"/about/open-source","text":"يستند منسوق إلى مكونات مشتقة من OHC وCARE ومشاريع مفتوحة المصدر أخرى. يحتفظ كل مكون بترخيصه ومتطلبات نسبه.","title":"أساسنا"},{"text":"نماذج ومحركات دورة الإيراد السعودية وقواعد الجهات الدافعة والضوابط المالية ومسارات المصطلحات وهوية منسوق الموحدة.","title":"إضافاتنا"}],"title":"مبني على أساس مشترك ومطور لمنسوق."},{"kind":"cards","intro":"نبدأ بالأشخاص وعملهم، ونحدد النطاق بدقة، ونتفق على المسؤوليات قبل إطلاق أي شيء.","items":[{"text":"أطباء ومختصون في المعلوماتية الصحية يحوّلون مسارات الرعاية والتوثيق والتسليم إلى نطاق منتج دقيق.","title":"المعلوماتية السريرية"},{"text":"مختصون في الأهلية والموافقات المسبقة والترميز والمطالبات والرفض والمطابقة، ملمّون بتبادل نفيس وقواعد الجهات الدافعة.","title":"عمليات دورة الإيرادات"},{"text":"مهندسون يبنون السجل المشترك والوحدات السريرية ووحدات الأقسام وتكاملات نفيس وزاتكا والاتصالات والتحليلات والذكاء الاصطناعي الخاضع للمراجعة.","title":"الهندسة"},{"href":"/resources/implementation","text":"مختصون يخططون للترحيل والاتصالات والتدريب والاعتماد مع فرق العملاء، ويبقون مسؤولين حتى الإطلاق والدعم.","title":"التنفيذ"}],"title":"مجالات العمل التي نستقطب لها."},{"kind":"steps","intro":"لا ننشر الوظائف إلا بعد تأكيدها. ويمكنك التعريف بنفسك الآن.","items":[{"href":"/contact?request=general","text":"اختر «استفسار عام» وأخبرنا بالمجال الأقرب إلى خبرتك.","title":"استخدم صفحة التواصل"},{"text":"اذكر دورك الحالي وخبرتك ذات الصلة وموقعك. ولا ترسل معلومات المرضى أو البيانات الشخصية لأشخاص آخرين.","title":"شارك المعلومات الأساسية"},{"text":"تُنشر الوظائف المؤكدة هنا.","title":"تابع هذه الصفحة"}],"title":"عبّر عن اهتمامك."}],"seoTitle":"فرص العمل في التقنية الصحية | منسوق","seoDescription":"قدم خبرتك عبر نموذج التواصل. ستُنشر الوظائف المفتوحة هنا بعد تأكيدها.","description":"قدم خبرتك عبر نموذج التواصل. ستُنشر الوظائف المفتوحة هنا بعد تأكيدها.","answers":[]}},{"slug":"/case-studies","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies","title":"Healthcare workflow case studies & patient journeys | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore clearly labeled workflow demonstrations across six care settings. Substantiated customer stories and measured outcomes are separate.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore clearly labeled workflow demonstrations across six care settings. Substantiated customer stories and measured outcomes are separate.","description":"Explore illustrative hospital, clinic, polyclinic, medical-city, TeleICU and home-care case studies. Follow care, departments and financial workflows end to end.","answers":[]},"ar":{"url":"https://mansoq.com/case-studies?lang=ar","title":"دراسات حالات الرعاية ورحلات المرضى | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف عروضاً لمسارات العمل ذات تسمية واضحة عبر ست بيئات رعاية. وتعرض قصص العملاء المثبتة والنتائج المقاسة بشكل مستقل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف عروضاً لمسارات العمل ذات تسمية واضحة عبر ست بيئات رعاية. وتعرض قصص العملاء المثبتة والنتائج المقاسة بشكل مستقل.","description":"استكشف حالات توضيحية للمستشفيات والعيادات والمجمعات والمدن الطبية والعناية عن بُعد والرعاية المنزلية: رحلة الرعاية والأقسام والإيرادات.","answers":[]}},{"slug":"/case-studies/ai-assisted-documentation","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/ai-assisted-documentation","title":"Documentation assistance. The clinician stays in control. | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Explore named supported assistance, source context and required clinician review; no autonomous clinical decisions.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore named supported assistance, source context and required clinician review; no autonomous clinical decisions.","description":"Illustrative scenario: Explore a verified assistive task with defined source context and mandatory professional review. Confirm the supported task → Establish encounter context…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative clinics workflow, not a named deployment or a measured outcome. A clinic selects an approved documentation assistance task. The clinician reviews its output before any content becomes part of the care record.","href":"/case-studies/ai-assisted-documentation#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The selected task has a defined source and boundary. The clinician owns the accepted documentation. Care decisions remain with the responsible professional. Incorrect or insufficient assistance is rejected by the reviewer. No autonomous diagnosis, treatment selection or universal AI task availability is represented.","href":"/case-studies/ai-assisted-documentation#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Documentation assistance. The clinician stays in control.","scenario":"A clinic selects an approved documentation assistance task. The clinician reviews its output before any content becomes part of the care record.","challenge":"Assistance supports professional documentation; it does not replace clinical judgment.","workflow":[{"title":"Confirm the supported task","action":"Agree the named verified assistance task, data boundary and responsible reviewer.","owner":"Service leadership","record":"Task · Data boundary · Reviewer"},{"title":"Establish encounter context","action":"Confirm the correct patient and the documentation context available to the selected task.","owner":"Treating clinician","record":"Patient · Encounter · Source context"},{"title":"Use the agreed assistance","action":"Use the selected assistive workflow within its accepted operational scope.","owner":"Treating clinician","record":"Assistive output · Task reference"},{"title":"Review and correct professionally","action":"Check the output against the source and correct or reject unsupported content.","owner":"Treating clinician","record":"Source · Review · Corrections"},{"title":"Complete clinician-authored documentation","action":"Record only the clinician-reviewed documentation in the encounter.","owner":"Treating clinician","record":"Reviewed note · Responsible clinician"},{"title":"Continue the care workflow","action":"Document the clinician’s care decisions and subsequent orders through the standard care workflow.","owner":"Treating clinician","record":"Care decision · Orders · Follow-up"}],"exception":"Incorrect or insufficient assistance is rejected by the reviewer. No autonomous diagnosis, treatment selection or universal AI task availability is represented.","completion":["The selected task has a defined source and boundary.","The clinician owns the accepted documentation.","Care decisions remain with the responsible professional."]}},"ar":{"url":"https://mansoq.com/case-studies/ai-assisted-documentation?lang=ar","title":"مساندة التوثيق. والتحكم يبقى للطبيب. | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"استكشف المساعدة المدعومة المحددة والسياق المصدر ومراجعة الطبيب المطلوبة؛ دون قرارات سريرية مستقلة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف المساعدة المدعومة المحددة والسياق المصدر ومراجعة الطبيب المطلوبة؛ دون قرارات سريرية مستقلة.","description":"سيناريو توضيحي: استكشف مهمة مساعدة متحققاً منها بسياق مصدر محدد ومراجعة مهنية لازمة. تأكيد المهمة المدعومة → تأسيس سياق الزيارة → استخدام المساندة المتفق عليها → المراجعة…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. تختار عيادة مهمة معتمدة لمساندة التوثيق. يراجع الطبيب مخرجاتها قبل أن تصبح أي محتويات جزءاً من سجل الرعاية.","href":"/case-studies/ai-assisted-documentation#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"للمهمة المحددة مصدر وحدود واضحان. يتولى الطبيب مسؤولية التوثيق المعتمد. تبقى قرارات الرعاية بيد الممارس المسؤول. يرفض المراجع المساندة غير الصحيحة أو غير الكافية. لا يُعرض تشخيص مستقل أو اختيار علاج أو توافر شامل لمهام الذكاء الاصطناعي.","href":"/case-studies/ai-assisted-documentation#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"مساندة التوثيق. والتحكم يبقى للطبيب.","scenario":"تختار عيادة مهمة معتمدة لمساندة التوثيق. يراجع الطبيب مخرجاتها قبل أن تصبح أي محتويات جزءاً من سجل الرعاية.","challenge":"تدعم المساندة التوثيق المهني ولا تحل محل الحكم السريري.","workflow":[{"title":"تأكيد المهمة المدعومة","action":"الاتفاق على المهمة المساعدة المحددة المتحقق منها وحدود البيانات والمراجع المسؤول.","owner":"قيادة الخدمة","record":"المهمة · حدود البيانات · المراجع"},{"title":"تأسيس سياق الزيارة","action":"تأكيد المريض الصحيح وسياق التوثيق المتاح للمهمة المحددة.","owner":"الطبيب المعالج","record":"المريض · الزيارة · سياق المصدر"},{"title":"استخدام المساندة المتفق عليها","action":"استخدام مسار المساندة المحدد ضمن نطاقه التشغيلي المعتمد.","owner":"الطبيب المعالج","record":"المخرجات المساعدة · مرجع المهمة"},{"title":"المراجعة والتصحيح مهنياً","action":"فحص المخرجات مقابل المصدر وتصحيح المحتوى غير المدعوم أو رفضه.","owner":"الطبيب المعالج","record":"المصدر · المراجعة · التصحيحات"},{"title":"إنجاز التوثيق المعتمد من الطبيب","action":"تسجيل التوثيق الذي راجعه الطبيب فقط في الزيارة.","owner":"الطبيب المعالج","record":"التوثيق المراجع · الطبيب المسؤول"},{"title":"متابعة مسار الرعاية","action":"توثيق قرارات الطبيب وطلباته اللاحقة عبر مسار الرعاية المعتاد.","owner":"الطبيب المعالج","record":"قرار الرعاية · الطلبات · المتابعة"}],"exception":"يرفض المراجع المساندة غير الصحيحة أو غير الكافية. لا يُعرض تشخيص مستقل أو اختيار علاج أو توافر شامل لمهام الذكاء الاصطناعي.","completion":["للمهمة المحددة مصدر وحدود واضحان.","يتولى الطبيب مسؤولية التوثيق المعتمد.","تبقى قرارات الرعاية بيد الممارس المسؤول."]}}},{"slug":"/case-studies/clinic-first-visit","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/clinic-first-visit","title":"The first visit | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Bring reception, the clinician and revenue teams around the outpatient journey.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Bring reception, the clinician and revenue teams around the outpatient journey.","description":"Illustrative scenario: Reception, the clinician and the billing team share one encounter from arrival to payment. Arrange the appointment → Register the arrival → Document the…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative clinics workflow, not a named deployment or a measured outcome. A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps.","href":"/case-studies/clinic-first-visit#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"A complete visit record from arrival to follow-up. Orders remain linked to the consultation that created them. The account reflects the documented visit activity. If the patient already has a record, verify the identity before continuing so the new encounter follows the correct history.","href":"/case-studies/clinic-first-visit#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"The first visit","scenario":"A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps.","challenge":"Reception, consultation and payment should describe the same visit.","workflow":[{"title":"Arrange the appointment","action":"Connect the appointment to the selected service and patient identity.","owner":"Access & coordination","record":"Appointment · Service · Identity"},{"title":"Register the arrival","action":"Confirm the shared patient record and establish the outpatient encounter and financial context.","owner":"Access & coordination","record":"Patient record · Encounter · Payer"},{"title":"Document the consultation","action":"Review the available history and record the assessment and agreed care plan.","owner":"Treating clinician","record":"History · Clinical note · Care plan"},{"title":"Connect requests and medication","action":"Attach the clinician’s orders and prescriptions to the consultation context.","owner":"Treating clinician","record":"Orders · Prescription · Encounter"},{"title":"Complete visit billing","action":"Review recorded services, patient contribution and payment against the encounter.","owner":"Finance team","record":"Services · Invoice · Payment"},{"title":"Arrange the next visit","action":"Record the next appointment or follow-up responsibility with the consultation’s care context.","owner":"Access & coordination","record":"Follow-up · Responsible service"}],"exception":"If the patient already has a record, verify the identity before continuing so the new encounter follows the correct history.","completion":["A complete visit record from arrival to follow-up.","Orders remain linked to the consultation that created them.","The account reflects the documented visit activity."]}},"ar":{"url":"https://mansoq.com/case-studies/clinic-first-visit?lang=ar","title":"الزيارة الأولى | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"اجمع الاستقبال والطبيب وفرق الإيرادات حول مسار العيادة الخارجية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اجمع الاستقبال والطبيب وفرق الإيرادات حول مسار العيادة الخارجية.","description":"سيناريو توضيحي: يتشارك الاستقبال والطبيب وفريق الفوترة زيارة واحدة من الوصول إلى الدفع. تنظيم الموعد → تسجيل الوصول → توثيق الاستشارة → ربط الطلبات والأدوية → إنجاز فوترة…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يحجز مريض جديد استشارة ويصل إلى العيادة ويتلقى خطة رعاية موثقة ويكمل الخطوات المالية للزيارة.","href":"/case-studies/clinic-first-visit#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"سجل زيارة كامل من الوصول إلى المتابعة. تظل الطلبات مرتبطة بالاستشارة التي أنشأتها. يعكس الحساب نشاط الزيارة الموثق. إذا كان للمريض سجل سابق، تُتحقق الهوية قبل المتابعة لتتبع الزيارة الجديدة التاريخ الصحيح.","href":"/case-studies/clinic-first-visit#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"الزيارة الأولى","scenario":"يحجز مريض جديد استشارة ويصل إلى العيادة ويتلقى خطة رعاية موثقة ويكمل الخطوات المالية للزيارة.","challenge":"يجب أن يصف الاستقبال والاستشارة والدفع الزيارة نفسها.","workflow":[{"title":"تنظيم الموعد","action":"ربط الموعد بالخدمة المحددة وهوية المريض.","owner":"الاستقبال والتنسيق","record":"الموعد · الخدمة · الهوية"},{"title":"تسجيل الوصول","action":"تأكيد سجل المريض المشترك وتأسيس زيارة العيادة وسياقها المالي.","owner":"الاستقبال والتنسيق","record":"سجل المريض · الزيارة · الجهة الدافعة"},{"title":"توثيق الاستشارة","action":"مراجعة التاريخ المتاح وتسجيل التقييم وخطة الرعاية المتفق عليها.","owner":"الطبيب المعالج","record":"التاريخ · التوثيق السريري · خطة الرعاية"},{"title":"ربط الطلبات والأدوية","action":"إرفاق طلبات الطبيب ووصفاته بسياق الاستشارة.","owner":"الطبيب المعالج","record":"الطلبات · الوصفة · الزيارة"},{"title":"إنجاز فوترة الزيارة","action":"مراجعة الخدمات المسجلة ومساهمة المريض والدفع مقابل الزيارة.","owner":"الفريق المالي","record":"الخدمات · الفاتورة · الدفع"},{"title":"تنظيم الزيارة التالية","action":"تسجيل الموعد التالي أو مسؤولية المتابعة مع سياق رعاية الاستشارة.","owner":"الاستقبال والتنسيق","record":"المتابعة · الخدمة المسؤولة"}],"exception":"إذا كان للمريض سجل سابق، تُتحقق الهوية قبل المتابعة لتتبع الزيارة الجديدة التاريخ الصحيح.","completion":["سجل زيارة كامل من الوصول إلى المتابعة.","تظل الطلبات مرتبطة بالاستشارة التي أنشأتها.","يعكس الحساب نشاط الزيارة الموثق."]}}},{"slug":"/case-studies/clinics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/clinics","title":"Clinics workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind Clinics.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind Clinics.","description":"Illustrative operational cases: The first visit; A follow-up with context; From order to review; An insured visit, followed through. Roles, data, exceptions and acceptance…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/clinics?lang=ar","title":"حالات العيادات ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف العيادات.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف العيادات.","description":"حالات تشغيل توضيحية: الزيارة الأولى؛ متابعة بسياق واضح؛ من الطلب إلى المراجعة؛ زيارة مؤمّنة بمتابعة كاملة. الأدوار والبيانات والاستثناءات ومعايير القبول.","answers":[]}},{"slug":"/case-studies/connected-integrations","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/connected-integrations","title":"An interface with clear ownership | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Separate native care, exchanged data, interface delivery and external system responsibilities.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Separate native care, exchanged data, interface delivery and external system responsibilities.","description":"Illustrative scenario: The delivery team defines what is exchanged and who operates each side of the connection. Define the service boundary → Specify the interface → Rehearse…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative teleicu workflow, not a named deployment or a measured outcome. A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.","href":"/case-studies/connected-integrations#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The interface has a defined technical and clinical purpose. Review and fallback responsibilities are agreed. The accepted service has a clear activation boundary. A failed test returns to the named interface owner. Activation follows agreed acceptance; connectivity does not grant unrestricted record access.","href":"/case-studies/connected-integrations#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"An interface with clear ownership","scenario":"A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.","challenge":"A usable connection joins technical delivery to a real clinical handover.","workflow":[{"title":"Define the service boundary","action":"Agree the local and remote teams, systems and information needed for the review service.","owner":"Service leadership","record":"Teams · Systems · Information scope"},{"title":"Specify the interface","action":"Document the agreed protocol, identity mapping, licenses and delivery owners.","owner":"Integration & IT team","record":"Protocol · Mapping · Delivery owner"},{"title":"Rehearse a supported case","action":"Prepare an authorized demonstration case and confirm the intended source information.","owner":"Local care team","record":"Demonstration case · Source record"},{"title":"Verify the exchange and access","action":"Review the exchanged context, permitted access and agreed failure handling.","owner":"Integration & IT team","record":"Exchange trace · Access · Fallback"},{"title":"Rehearse the review handover","action":"Document the review and demonstrate its return to the responsible local clinician.","owner":"Remote specialist","record":"Specialist review · Local handover"},{"title":"Accept the operating scope","action":"Agree acceptance, support ownership and the activated service boundary.","owner":"Service leadership","record":"Acceptance · Support · Activation"}],"exception":"A failed test returns to the named interface owner. Activation follows agreed acceptance; connectivity does not grant unrestricted record access.","completion":["The interface has a defined technical and clinical purpose.","Review and fallback responsibilities are agreed.","The accepted service has a clear activation boundary."]}},"ar":{"url":"https://mansoq.com/case-studies/connected-integrations?lang=ar","title":"اتصال بمسؤولية واضحة | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"افصل الرعاية الداخلية والبيانات المتبادلة وتنفيذ الاتصال ومسؤوليات النظام الخارجي.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"افصل الرعاية الداخلية والبيانات المتبادلة وتنفيذ الاتصال ومسؤوليات النظام الخارجي.","description":"سيناريو توضيحي: يحدد فريق التنفيذ ما يتم تبادله ومن يشغّل كل طرف من الاتصال. تحديد حدود الخدمة → تحديد الاتصال → تجربة حالة مدعومة → التحقق من التبادل والصلاحيات → تجربة تسليم…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يضيف مستشفى اتصال عناية مركزة عن بُعد إلى جانب نظامه السريري القائم. تحتاج التقنية والأطباء وقيادة الخدمة إلى مسؤوليات تنفيذ وتشغيل واضحة.","href":"/case-studies/connected-integrations#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"للاتصال غرض تقني وسريري محدد. مسؤوليات المراجعة والبديل متفق عليها. للخدمة المعتمدة حدود تفعيل واضحة. يعود الاختبار غير الناجح إلى مسؤول الاتصال المحدد. يتبع التفعيل الاعتماد المتفق عليه؛ ولا يمنح الاتصال وصولاً غير مقيد للسجلات.","href":"/case-studies/connected-integrations#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"اتصال بمسؤولية واضحة","scenario":"يضيف مستشفى اتصال عناية مركزة عن بُعد إلى جانب نظامه السريري القائم. تحتاج التقنية والأطباء وقيادة الخدمة إلى مسؤوليات تنفيذ وتشغيل واضحة.","challenge":"يربط الاتصال القابل للاستخدام التنفيذ التقني بتسليم رعاية فعلي.","workflow":[{"title":"تحديد حدود الخدمة","action":"الاتفاق على الفرق المحلية والبعيدة والأنظمة والمعلومات اللازمة لخدمة المراجعة.","owner":"قيادة الخدمة","record":"الفرق · الأنظمة · نطاق المعلومات"},{"title":"تحديد الاتصال","action":"توثيق البروتوكول المتفق عليه ومواءمة الهوية والتراخيص ومسؤولي التنفيذ.","owner":"فريق التكامل وتقنية المعلومات","record":"البروتوكول · المواءمة · مسؤول التنفيذ"},{"title":"تجربة حالة مدعومة","action":"تجهيز حالة عرض مصرح بها وتأكيد معلومات المصدر المطلوبة.","owner":"فريق الرعاية المحلي","record":"حالة العرض · سجل المصدر"},{"title":"التحقق من التبادل والصلاحيات","action":"مراجعة السياق المتبادل والصلاحيات المسموح بها ومعالجة الإخفاق المتفق عليها.","owner":"فريق التكامل وتقنية المعلومات","record":"تتبع التبادل · الصلاحيات · البديل"},{"title":"تجربة تسليم المراجعة","action":"توثيق المراجعة وإظهار عودتها إلى الطبيب المحلي المسؤول.","owner":"المختص عن بُعد","record":"مراجعة المختص · التسليم المحلي"},{"title":"اعتماد نطاق التشغيل","action":"الاتفاق على الاعتماد ومسؤولية الدعم وحدود الخدمة المفعّلة.","owner":"قيادة الخدمة","record":"الاعتماد · الدعم · التفعيل"}],"exception":"يعود الاختبار غير الناجح إلى مسؤول الاتصال المحدد. يتبع التفعيل الاعتماد المتفق عليه؛ ولا يمنح الاتصال وصولاً غير مقيد للسجلات.","completion":["للاتصال غرض تقني وسريري محدد.","مسؤوليات المراجعة والبديل متفق عليها.","للخدمة المعتمدة حدود تفعيل واضحة."]}}},{"slug":"/case-studies/finance-follow-up","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/finance-follow-up","title":"Care delivered. Revenue followed. | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Trace charges, patient liability, invoices and payments without confusing national exchange readiness.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Trace charges, patient liability, invoices and payments without confusing national exchange readiness.","description":"Illustrative scenario: Revenue teams follow service activity through billing, payer responses and reconciliation. Establish financial responsibility → Capture delivered…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative hospitals workflow, not a named deployment or a measured outcome. A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.","href":"/case-studies/finance-follow-up#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"Every reviewed charge has a care-activity reference. Payments and outstanding balances have clear allocation. Financial differences have a responsible next action. A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.","href":"/case-studies/finance-follow-up#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Care delivered. Revenue followed.","scenario":"A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.","challenge":"Revenue follow-up starts with the services actually recorded in the encounter.","workflow":[{"title":"Establish financial responsibility","action":"Record the patient, encounter and payer or self-pay context before financial follow-up.","owner":"Access & coordination","record":"Encounter · Payer · Patient account"},{"title":"Capture delivered activity","action":"Link recorded departmental and care services to accountable encounter charges.","owner":"Department team","record":"Service activity · Charge reference"},{"title":"Review prices and contribution","action":"Check the agreed tariffs and patient contribution against the recorded services and coverage.","owner":"Revenue team","record":"Tariff · Coverage · Contribution"},{"title":"Issue the invoice","action":"Review the invoice and use the selected ZATCA exchange scope where configured and activated.","owner":"Finance team","record":"Invoice · E-invoice response"},{"title":"Allocate payments","action":"Match recorded payments or payer financial responses to the relevant account and invoice.","owner":"Finance team","record":"Payment · Allocation · Balance"},{"title":"Resolve the remaining balance","action":"Assign unresolved differences for review and record the reconciliation decision and next action.","owner":"Revenue team","record":"Difference · Owner · Reconciliation"}],"exception":"A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.","completion":["Every reviewed charge has a care-activity reference.","Payments and outstanding balances have clear allocation.","Financial differences have a responsible next action."]}},"ar":{"url":"https://mansoq.com/case-studies/finance-follow-up?lang=ar","title":"رعاية مقدمة. إيرادات متابَعة. | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"تتبع الرسوم والتزام المريض والفواتير والمدفوعات مع توضيح جاهزية التبادل الوطني.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تتبع الرسوم والتزام المريض والفواتير والمدفوعات مع توضيح جاهزية التبادل الوطني.","description":"سيناريو توضيحي: تتابع فرق الإيرادات نشاط الخدمات عبر الفوترة وردود الجهات الدافعة والمطابقة. تحديد المسؤولية المالية → التقاط النشاط المنجز → مراجعة الأسعار والمساهمة → إصدار…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. تشمل زيارة مستشفى رعاية جناح وخدمات أقسام ومدفوعات المريض. تحتاج المالية إلى تفسير كل رسم وكل رصيد متبقٍ.","href":"/case-studies/finance-follow-up#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"لكل رسم تمت مراجعته مرجع نشاط رعاية. للمدفوعات والأرصدة المتبقية تخصيص واضح. للفروقات المالية إجراء تالٍ بمسؤولية محددة. يعود الرسم محل الاعتراض إلى مرجع خدمته للمراجعة؛ ويحتفظ السجل المالي المصحح بتتبع الزيارة الأصلية.","href":"/case-studies/finance-follow-up#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"رعاية مقدمة. إيرادات متابَعة.","scenario":"تشمل زيارة مستشفى رعاية جناح وخدمات أقسام ومدفوعات المريض. تحتاج المالية إلى تفسير كل رسم وكل رصيد متبقٍ.","challenge":"تبدأ متابعة الإيرادات بالخدمات المسجلة فعلياً في الزيارة.","workflow":[{"title":"تحديد المسؤولية المالية","action":"تسجيل المريض والزيارة وسياق الجهة الدافعة أو الدفع الذاتي قبل المتابعة المالية.","owner":"الاستقبال والتنسيق","record":"الزيارة · الجهة الدافعة · حساب المريض"},{"title":"التقاط النشاط المنجز","action":"ربط خدمات الأقسام والرعاية المسجلة برسوم زيارة قابلة للمساءلة.","owner":"فريق القسم","record":"نشاط الخدمة · مرجع الرسم"},{"title":"مراجعة الأسعار والمساهمة","action":"فحص التعريفات المتفق عليها ومساهمة المريض مقابل الخدمات والتغطية المسجلة.","owner":"فريق الإيرادات","record":"التعريفة · التغطية · المساهمة"},{"title":"إصدار الفاتورة","action":"مراجعة الفاتورة واستخدام نطاق تبادل زاتكا المحدد حيث تمت تهيئته وتفعيله.","owner":"الفريق المالي","record":"الفاتورة · رد الفاتورة الإلكترونية"},{"title":"تخصيص المدفوعات","action":"مطابقة المدفوعات المسجلة أو الردود المالية للجهة الدافعة بالحساب والفاتورة المعنيين.","owner":"الفريق المالي","record":"الدفع · التخصيص · الرصيد"},{"title":"معالجة الرصيد المتبقي","action":"إسناد الفروقات غير المحسومة للمراجعة وتسجيل قرار المطابقة والإجراء التالي.","owner":"فريق الإيرادات","record":"الفرق · المسؤول · المطابقة"}],"exception":"يعود الرسم محل الاعتراض إلى مرجع خدمته للمراجعة؛ ويحتفظ السجل المالي المصحح بتتبع الزيارة الأصلية.","completion":["لكل رسم تمت مراجعته مرجع نشاط رعاية.","للمدفوعات والأرصدة المتبقية تخصيص واضح.","للفروقات المالية إجراء تالٍ بمسؤولية محددة."]}}},{"slug":"/case-studies/home-palliative","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/home-palliative","title":"Home & Palliative Care workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind Home & Palliative Care.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind Home & Palliative Care.","description":"Illustrative operational cases: A home visit with continuity; A palliative care-plan review; A multidisciplinary handover; Delivered care to financial follow-up. Roles, data,…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/home-palliative?lang=ar","title":"حالات الرعاية المنزلية والتلطيفية ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف الرعاية المنزلية والتلطيفية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف الرعاية المنزلية والتلطيفية.","description":"حالات تشغيل توضيحية: زيارة منزلية باستمرارية؛ مراجعة خطة رعاية تلطيفية؛ تسليم بين التخصصات؛ من الرعاية المقدمة إلى المتابعة المالية. الأدوار والبيانات والاستثناءات ومعايير…","answers":[]}},{"slug":"/case-studies/home-visit-continuity","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/home-visit-continuity","title":"A home visit with continuity | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Connect visits, observations and care-plan responsibilities without assuming unverified mobile or offline functions.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Connect visits, observations and care-plan responsibilities without assuming unverified mobile or offline functions.","description":"Illustrative scenario: The care professional reviews the record, documents the visit and records the next responsibility. Arrange the visit → Review the current plan → Document…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative home_palliative workflow, not a named deployment or a measured outcome. A home-care team prepares a planned visit, documents the encounter and hands the next care responsibility to the continuing service.","href":"/case-studies/home-visit-continuity#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The home visit adds to the continuing care record. The next visit has a documented purpose and owner. Financial work refers to services actually recorded. If the visit is postponed, record the change and responsible follow-up. Mobile, offline and family messaging are separately agreed scope.","href":"/case-studies/home-visit-continuity#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"A home visit with continuity","scenario":"A home-care team prepares a planned visit, documents the encounter and hands the next care responsibility to the continuing service.","challenge":"Care delivered at home still needs one connected clinical and operational record.","workflow":[{"title":"Arrange the visit","action":"Connect the patient, planned visit and responsible home-care service.","owner":"Access & coordination","record":"Patient · Visit · Service"},{"title":"Review the current plan","action":"Review the documented care plan and earlier visit context before the encounter.","owner":"Home-care professional","record":"Care plan · Previous visits"},{"title":"Document the home encounter","action":"Record observations and the care activity performed within the agreed service.","owner":"Home-care professional","record":"Visit note · Observations · Activity"},{"title":"Connect clinical requests","action":"Document any clinician-reviewed change, medication order or departmental request.","owner":"Treating clinician","record":"Reviewed plan · Orders · Medication"},{"title":"Hand over continuing care","action":"Record the next visit or care-team responsibility with the encounter context.","owner":"Home-care professional","record":"Next visit · Handover · Owner"},{"title":"Review delivered service billing","action":"Connect the documented visit services to the selected billing and revenue follow-up.","owner":"Finance team","record":"Visit service · Account · Follow-up"}],"exception":"If the visit is postponed, record the change and responsible follow-up. Mobile, offline and family messaging are separately agreed scope.","completion":["The home visit adds to the continuing care record.","The next visit has a documented purpose and owner.","Financial work refers to services actually recorded."]}},"ar":{"url":"https://mansoq.com/case-studies/home-visit-continuity?lang=ar","title":"زيارة منزلية باستمرارية | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"اربط الزيارات والملاحظات ومسؤوليات خطة الرعاية دون افتراض وظائف جوال أو عمل دون اتصال غير متحقق منها.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اربط الزيارات والملاحظات ومسؤوليات خطة الرعاية دون افتراض وظائف جوال أو عمل دون اتصال غير متحقق منها.","description":"سيناريو توضيحي: يراجع مختص الرعاية السجل ويوثق الزيارة ويسجل المسؤولية التالية. تنظيم الزيارة → مراجعة الخطة الحالية → توثيق الزيارة المنزلية → ربط الطلبات السريرية → تسليم…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يجهز فريق رعاية منزلية زيارة مخططة ويوثق الزيارة ويسلم مسؤولية الرعاية التالية إلى الخدمة المستمرة.","href":"/case-studies/home-visit-continuity#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"تضيف الزيارة المنزلية إلى سجل الرعاية المستمرة. للزيارة التالية غرض ومسؤول موثقان. يرجع العمل المالي إلى الخدمات المسجلة فعلياً. إذا تأجلت الزيارة، يُسجل التغيير ومسؤول المتابعة. الجوال والعمل دون اتصال ورسائل الأسرة نطاقات متفق عليها بشكل مستقل.","href":"/case-studies/home-visit-continuity#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"زيارة منزلية باستمرارية","scenario":"يجهز فريق رعاية منزلية زيارة مخططة ويوثق الزيارة ويسلم مسؤولية الرعاية التالية إلى الخدمة المستمرة.","challenge":"تحتاج الرعاية المقدمة في المنزل إلى سجل سريري وتشغيلي مترابط واحد.","workflow":[{"title":"تنظيم الزيارة","action":"ربط المريض والزيارة المخططة وخدمة الرعاية المنزلية المسؤولة.","owner":"الاستقبال والتنسيق","record":"المريض · الزيارة · الخدمة"},{"title":"مراجعة الخطة الحالية","action":"مراجعة خطة الرعاية الموثقة وسياق الزيارات السابقة قبل الزيارة.","owner":"ممارس الرعاية المنزلية","record":"خطة الرعاية · الزيارات السابقة"},{"title":"توثيق الزيارة المنزلية","action":"تسجيل الملاحظات ونشاط الرعاية المنفذ ضمن الخدمة المتفق عليها.","owner":"ممارس الرعاية المنزلية","record":"توثيق الزيارة · الملاحظات · النشاط"},{"title":"ربط الطلبات السريرية","action":"توثيق أي تغيير راجعه الطبيب أو طلب دواء أو طلب قسم.","owner":"الطبيب المعالج","record":"الخطة المراجعة · الطلبات · الأدوية"},{"title":"تسليم الرعاية المستمرة","action":"تسجيل الزيارة التالية أو مسؤولية فريق الرعاية مع سياق الزيارة.","owner":"ممارس الرعاية المنزلية","record":"الزيارة التالية · التسليم · المسؤول"},{"title":"مراجعة فوترة الخدمة المنجزة","action":"ربط خدمات الزيارة الموثقة بالفوترة والمتابعة الإيرادية المحددتين.","owner":"الفريق المالي","record":"خدمة الزيارة · الحساب · المتابعة"}],"exception":"إذا تأجلت الزيارة، يُسجل التغيير ومسؤول المتابعة. الجوال والعمل دون اتصال ورسائل الأسرة نطاقات متفق عليها بشكل مستقل.","completion":["تضيف الزيارة المنزلية إلى سجل الرعاية المستمرة.","للزيارة التالية غرض ومسؤول موثقان.","يرجع العمل المالي إلى الخدمات المسجلة فعلياً."]}}},{"slug":"/case-studies/hospital-admission-discharge","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/hospital-admission-discharge","title":"Admission to discharge | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Carry the person’s clinical context across admissions, nursing, departments and discharge.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Carry the person’s clinical context across admissions, nursing, departments and discharge.","description":"Illustrative scenario: A patient moves from admission to the ward, then leaves with a connected discharge record. Establish the encounter → Receive the patient on the ward →…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative hospitals workflow, not a named deployment or a measured outcome. A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge.","href":"/case-studies/hospital-admission-discharge#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"A discharge record carrying the documented care context. A clear follow-up responsibility for the next care team. Financial work traceable to the same admission. If a result or discharge task is outstanding, keep it attached to the encounter with a named owner; the clinical team decides the care action.","href":"/case-studies/hospital-admission-discharge#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Admission to discharge","scenario":"A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge.","challenge":"An admission is one journey, even when responsibility changes between several teams.","workflow":[{"title":"Establish the encounter","action":"Confirm the patient identity, admission details and responsible service against the shared record.","owner":"Access & coordination","record":"Identity · Admission · Service"},{"title":"Receive the patient on the ward","action":"Document the ward handover, observations and care responsibilities for the incoming team.","owner":"Nursing team","record":"Ward · Observations · Responsible team"},{"title":"Document and request","action":"Record the assessment and connect medication and departmental requests to this inpatient encounter.","owner":"Treating clinician","record":"Clinical notes · Orders · Medication"},{"title":"Bring department work back","action":"Complete the selected laboratory or pharmacy work and return its documented result to the care context.","owner":"Department team","record":"Request · Department activity · Result"},{"title":"Prepare the next care step","action":"Record the discharge summary, medication plan and follow-up responsibility for the next team.","owner":"Treating clinician","record":"Discharge summary · Follow-up"},{"title":"Close the financial encounter","action":"Review encounter-linked charges, patient liability and payments; assign any outstanding balance for follow-up.","owner":"Finance team","record":"Charges · Invoice · Balance"}],"exception":"If a result or discharge task is outstanding, keep it attached to the encounter with a named owner; the clinical team decides the care action.","completion":["A discharge record carrying the documented care context.","A clear follow-up responsibility for the next care team.","Financial work traceable to the same admission."]}},"ar":{"url":"https://mansoq.com/case-studies/hospital-admission-discharge?lang=ar","title":"من الدخول إلى الخروج | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"انقل سياق الشخص السريري بين القبول والتمريض والأقسام والخروج.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"انقل سياق الشخص السريري بين القبول والتمريض والأقسام والخروج.","description":"سيناريو توضيحي: ينتقل المريض من القبول إلى الجناح ثم يغادر بسجل خروج مترابط. تأسيس الزيارة → استقبال المريض في الجناح → التوثيق والطلبات → إعادة عمل الأقسام إلى الرعاية → تجهيز…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يصل مريض لإقامة تنويم مخططة. يحتاج الاستقبال والجناح والتشخيص والمالية إلى العمل من سياق الزيارة نفسه حتى الخروج.","href":"/case-studies/hospital-admission-discharge#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"سجل خروج يحمل سياق الرعاية الموثق. مسؤولية متابعة واضحة لفريق الرعاية التالي. عمل مالي قابل للتتبع إلى التنويم نفسه. إذا بقيت نتيجة أو مهمة خروج معلقة، ترتبط بالزيارة وبمسؤول محدد؛ ويقرر الفريق السريري إجراء الرعاية.","href":"/case-studies/hospital-admission-discharge#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"من الدخول إلى الخروج","scenario":"يصل مريض لإقامة تنويم مخططة. يحتاج الاستقبال والجناح والتشخيص والمالية إلى العمل من سياق الزيارة نفسه حتى الخروج.","challenge":"التنويم رحلة واحدة، حتى عندما تنتقل المسؤولية بين فرق متعددة.","workflow":[{"title":"تأسيس الزيارة","action":"تأكيد هوية المريض وبيانات القبول والخدمة المسؤولة مقابل السجل المشترك.","owner":"الاستقبال والتنسيق","record":"الهوية · القبول · الخدمة"},{"title":"استقبال المريض في الجناح","action":"توثيق تسليم الجناح والملاحظات ومسؤوليات الرعاية للفريق المستلم.","owner":"فريق التمريض","record":"الجناح · الملاحظات · الفريق المسؤول"},{"title":"التوثيق والطلبات","action":"تسجيل التقييم وربط الأدوية وطلبات الأقسام بزيارة التنويم هذه.","owner":"الطبيب المعالج","record":"التوثيق السريري · الطلبات · الأدوية"},{"title":"إعادة عمل الأقسام إلى الرعاية","action":"إنجاز عمل المختبر أو الصيدلية المحدد وإعادة نتيجته الموثقة إلى سياق الرعاية.","owner":"فريق القسم","record":"الطلب · نشاط القسم · النتيجة"},{"title":"تجهيز خطوة الرعاية التالية","action":"تسجيل ملخص الخروج وخطة الأدوية ومسؤولية المتابعة للفريق التالي.","owner":"الطبيب المعالج","record":"ملخص الخروج · المتابعة"},{"title":"إقفال الزيارة مالياً","action":"مراجعة الرسوم المرتبطة بالزيارة والتزام المريض والمدفوعات وإسناد الرصيد المتبقي للمتابعة.","owner":"الفريق المالي","record":"الرسوم · الفاتورة · الرصيد"}],"exception":"إذا بقيت نتيجة أو مهمة خروج معلقة، ترتبط بالزيارة وبمسؤول محدد؛ ويقرر الفريق السريري إجراء الرعاية.","completion":["سجل خروج يحمل سياق الرعاية الموثق.","مسؤولية متابعة واضحة لفريق الرعاية التالي.","عمل مالي قابل للتتبع إلى التنويم نفسه."]}}},{"slug":"/case-studies/hospital-day-surgery","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/hospital-day-surgery","title":"Day surgery, end to end | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Explore an agreed day-surgery composition with perioperative responsibilities and charge linkage.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore an agreed day-surgery composition with perioperative responsibilities and charge linkage.","description":"Illustrative scenario: The clinical and operating-room teams work through preparation, procedure and recovery. Book the surgical case → Prepare the case → Coordinate theatre…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative hospitals workflow, not a named deployment or a measured outcome. A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected.","href":"/case-studies/hospital-day-surgery#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"One case history from booking to recovery. A recovery handover with the procedure context. Services and consumables linked to financial review. When a case is rescheduled, update the booking and resource responsibility while retaining the preparation record for review.","href":"/case-studies/hospital-day-surgery#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Day surgery, end to end","scenario":"A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected.","challenge":"Theatre readiness and the recovery handover need more than a booking on a calendar.","workflow":[{"title":"Book the surgical case","action":"Link the scheduled case, patient and responsible surgical service to the encounter.","owner":"Access & coordination","record":"Booking · Encounter · Service"},{"title":"Prepare the case","action":"Document the agreed preoperative assessment and preparation requirements for the surgical team.","owner":"Treating clinician","record":"Assessment · Preparation record"},{"title":"Coordinate theatre resources","action":"Connect the case to selected theatre resources and required consumables within the agreed operating-room scope.","owner":"Department team","record":"Theatre · Resources · Consumables"},{"title":"Document the procedure","action":"Record perioperative activity and the procedure against the patient’s case rather than a separate account.","owner":"Treating clinician","record":"Procedure · Perioperative notes"},{"title":"Hand over to recovery","action":"Carry the procedure record, observations and next responsibilities into recovery and discharge documentation.","owner":"Nursing team","record":"Recovery · Handover · Discharge"},{"title":"Review case-linked charges","action":"Reconcile recorded services and consumables with the case bill and assign financial follow-up.","owner":"Finance team","record":"Services · Consumables · Bill"}],"exception":"When a case is rescheduled, update the booking and resource responsibility while retaining the preparation record for review.","completion":["One case history from booking to recovery.","A recovery handover with the procedure context.","Services and consumables linked to financial review."]}},"ar":{"url":"https://mansoq.com/case-studies/hospital-day-surgery?lang=ar","title":"الجراحة اليومية من البداية للنهاية | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"استكشف تكوين جراحة يومية متفقاً عليه بمسؤوليات الرعاية المحيطة بالجراحة وربط الرسوم.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف تكوين جراحة يومية متفقاً عليه بمسؤوليات الرعاية المحيطة بالجراحة وربط الرسوم.","description":"سيناريو توضيحي: تعمل فرق الرعاية والعمليات عبر التحضير والإجراء والتعافي. حجز الحالة الجراحية → تجهيز الحالة → تنسيق موارد العمليات → توثيق الإجراء → التسليم إلى التعافي →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يحضر مريض لخدمة جراحة يومية مجدولة. يجب أن تظل الحجوزات وتجهيز العمليات والإجراء والتعافي والفوترة مترابطة.","href":"/case-studies/hospital-day-surgery#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"تاريخ حالة واحد من الحجز إلى التعافي. تسليم إلى التعافي يحمل سياق الإجراء. خدمات ومستهلكات مرتبطة بالمراجعة المالية. عند إعادة جدولة الحالة، يُحدّث الحجز ومسؤولية الموارد مع الاحتفاظ بسجل التجهيز للمراجعة.","href":"/case-studies/hospital-day-surgery#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"الجراحة اليومية من البداية للنهاية","scenario":"يحضر مريض لخدمة جراحة يومية مجدولة. يجب أن تظل الحجوزات وتجهيز العمليات والإجراء والتعافي والفوترة مترابطة.","challenge":"جاهزية العمليات وتسليم التعافي يحتاجان إلى أكثر من حجز في التقويم.","workflow":[{"title":"حجز الحالة الجراحية","action":"ربط الحالة المجدولة والمريض والخدمة الجراحية المسؤولة بالزيارة.","owner":"الاستقبال والتنسيق","record":"الحجز · الزيارة · الخدمة"},{"title":"تجهيز الحالة","action":"توثيق التقييم قبل الجراحة ومتطلبات التجهيز المتفق عليها للفريق الجراحي.","owner":"الطبيب المعالج","record":"التقييم · سجل التجهيز"},{"title":"تنسيق موارد العمليات","action":"ربط الحالة بموارد العمليات المحددة والمستهلكات المطلوبة ضمن نطاق غرفة العمليات المتفق عليه.","owner":"فريق القسم","record":"العمليات · الموارد · المستهلكات"},{"title":"توثيق الإجراء","action":"تسجيل النشاط المحيط بالجراحة والإجراء مقابل حالة المريض بدلاً من حساب منفصل.","owner":"الطبيب المعالج","record":"الإجراء · توثيق الرعاية المحيطة بالجراحة"},{"title":"التسليم إلى التعافي","action":"نقل سجل الإجراء والملاحظات والمسؤوليات التالية إلى توثيق التعافي والخروج.","owner":"فريق التمريض","record":"التعافي · التسليم · الخروج"},{"title":"مراجعة رسوم الحالة","action":"مطابقة الخدمات والمستهلكات المسجلة مع فاتورة الحالة وإسناد المتابعة المالية.","owner":"الفريق المالي","record":"الخدمات · المستهلكات · الفاتورة"}],"exception":"عند إعادة جدولة الحالة، يُحدّث الحجز ومسؤولية الموارد مع الاحتفاظ بسجل التجهيز للمراجعة.","completion":["تاريخ حالة واحد من الحجز إلى التعافي.","تسليم إلى التعافي يحمل سياق الإجراء.","خدمات ومستهلكات مرتبطة بالمراجعة المالية."]}}},{"slug":"/case-studies/hospital-emergency-admission","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/hospital-emergency-admission","title":"From emergency arrival to ward care. | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Connect the agreed emergency encounter to inpatient care without losing clinical context.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Connect the agreed emergency encounter to inpatient care without losing clinical context.","description":"Illustrative scenario: Keep the emergency assessment, admitted-care handover and financial encounter connected. Register the emergency encounter → Document the assessment →…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative hospitals workflow, not a named deployment or a measured outcome. Following emergency assessment, the treating team decides a patient needs admission. The ward receives the documented care context and responsibility.","href":"/case-studies/hospital-emergency-admission#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The ward receives the emergency assessment context. Pending clinical work has a receiving owner. Emergency and admitted activity retain financial references. A changed destination or outstanding result remains part of the documented transfer and is assigned to the responsible care team.","href":"/case-studies/hospital-emergency-admission#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"From emergency arrival to ward care.","scenario":"Following emergency assessment, the treating team decides a patient needs admission. The ward receives the documented care context and responsibility.","challenge":"The ward needs the emergency story, not only a new admission record.","workflow":[{"title":"Register the emergency encounter","action":"Confirm identity and establish the emergency encounter.","owner":"Access & coordination","record":"Identity · Emergency encounter"},{"title":"Document the assessment","action":"Record observations, assessment and the treating clinician’s care decisions.","owner":"Treating clinician","record":"Assessment · Observations · Decisions"},{"title":"Connect urgent requests","action":"Link documented medication and department requests to the emergency encounter.","owner":"Treating clinician","record":"Orders · Medication · Results"},{"title":"Record the admission decision","action":"Document the admission decision and receiving service responsibility.","owner":"Treating clinician","record":"Admission decision · Receiving service"},{"title":"Hand over to the ward","action":"Carry the emergency context and pending work into the ward handover.","owner":"Nursing team","record":"Emergency note · Ward handover"},{"title":"Continue care and account review","action":"Review encounter-linked service charges while the ward documents continued care.","owner":"Finance team","record":"Ward record · Encounter charges"}],"exception":"A changed destination or outstanding result remains part of the documented transfer and is assigned to the responsible care team.","completion":["The ward receives the emergency assessment context.","Pending clinical work has a receiving owner.","Emergency and admitted activity retain financial references."]}},"ar":{"url":"https://mansoq.com/case-studies/hospital-emergency-admission?lang=ar","title":"من الوصول إلى الطوارئ إلى رعاية الجناح. | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"اربط زيارة الطوارئ المتفق عليها بالتنويم دون فقد السياق السريري.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اربط زيارة الطوارئ المتفق عليها بالتنويم دون فقد السياق السريري.","description":"سيناريو توضيحي: اربط تقييم الطوارئ وتسليم رعاية التنويم والزيارة المالية. تسجيل زيارة الطوارئ → توثيق التقييم → ربط الطلبات العاجلة → تسجيل قرار التنويم → التسليم إلى الجناح →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. بعد تقييم الطوارئ، يقرر الفريق المعالج حاجة مريض إلى التنويم. يستلم الجناح سياق الرعاية الموثق والمسؤولية.","href":"/case-studies/hospital-emergency-admission#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"يتلقى الجناح سياق تقييم الطوارئ. للعمل السريري المعلق مسؤول مستلم. يحتفظ نشاط الطوارئ والتنويم بمراجع مالية. تبقى الوجهة المتغيرة أو النتيجة المعلقة جزءاً من النقل الموثق وتُسند إلى فريق الرعاية المسؤول.","href":"/case-studies/hospital-emergency-admission#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"من الوصول إلى الطوارئ إلى رعاية الجناح.","scenario":"بعد تقييم الطوارئ، يقرر الفريق المعالج حاجة مريض إلى التنويم. يستلم الجناح سياق الرعاية الموثق والمسؤولية.","challenge":"يحتاج الجناح إلى قصة الطوارئ، لا إلى سجل قبول جديد فقط.","workflow":[{"title":"تسجيل زيارة الطوارئ","action":"تأكيد الهوية وتأسيس زيارة الطوارئ.","owner":"الاستقبال والتنسيق","record":"الهوية · زيارة الطوارئ"},{"title":"توثيق التقييم","action":"تسجيل الملاحظات والتقييم وقرارات الطبيب المعالج.","owner":"الطبيب المعالج","record":"التقييم · الملاحظات · القرارات"},{"title":"ربط الطلبات العاجلة","action":"ربط الأدوية وطلبات الأقسام الموثقة بزيارة الطوارئ.","owner":"الطبيب المعالج","record":"الطلبات · الأدوية · النتائج"},{"title":"تسجيل قرار التنويم","action":"توثيق قرار التنويم ومسؤولية الخدمة المستلمة.","owner":"الطبيب المعالج","record":"قرار التنويم · الخدمة المستلمة"},{"title":"التسليم إلى الجناح","action":"نقل سياق الطوارئ والعمل المعلق إلى تسليم الجناح.","owner":"فريق التمريض","record":"توثيق الطوارئ · تسليم الجناح"},{"title":"استمرار الرعاية ومراجعة الحساب","action":"مراجعة رسوم الخدمات المرتبطة بالزيارة بينما يوثق الجناح الرعاية المستمرة.","owner":"الفريق المالي","record":"سجل الجناح · رسوم الزيارة"}],"exception":"تبقى الوجهة المتغيرة أو النتيجة المعلقة جزءاً من النقل الموثق وتُسند إلى فريق الرعاية المسؤول.","completion":["يتلقى الجناح سياق تقييم الطوارئ.","للعمل السريري المعلق مسؤول مستلم.","يحتفظ نشاط الطوارئ والتنويم بمراجع مالية."]}}},{"slug":"/case-studies/hospital-icu-handover","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/hospital-icu-handover","title":"Critical-care handover | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Review the documented observations, medication and responsibilities the next team needs.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Review the documented observations, medication and responsibilities the next team needs.","description":"Illustrative scenario: The next ICU team reviews the observations, medication and responsibilities it needs. Confirm the care context → Review documented observations → Carry…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative hospitals workflow, not a named deployment or a measured outcome. An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together.","href":"/case-studies/hospital-icu-handover#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The incoming team can review one connected care record. Pending work retains a documented owner. The ICU history accompanies the next care setting. If information is missing, identify its source and responsible team in the handover instead of treating an absent result as a completed task.","href":"/case-studies/hospital-icu-handover#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Critical-care handover","scenario":"An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together.","challenge":"A handover must transfer responsibility as well as information.","workflow":[{"title":"Confirm the care context","action":"Open the correct inpatient encounter and confirm the current ICU team and location.","owner":"Nursing team","record":"Identity · Encounter · ICU location"},{"title":"Review documented observations","action":"Review recorded observations and clinical notes with their encounter context; assess care professionally.","owner":"Treating clinician","record":"Observations · Clinical notes"},{"title":"Carry medication context","action":"Bring the documented medication and order context into the handover for the responsible clinical team.","owner":"Nursing team","record":"Medication · Current orders"},{"title":"Review department follow-up","action":"Link available results and outstanding departmental work to the same encounter.","owner":"Department team","record":"Results · Pending requests"},{"title":"Record the shift handover","action":"Document the care handover and identify who takes responsibility for each next action.","owner":"Nursing team","record":"Handover note · Next owner"},{"title":"Continue or transfer care","action":"Update the next care plan or documented ward transfer while preserving the ICU encounter history.","owner":"Treating clinician","record":"Care plan · Transfer record"}],"exception":"If information is missing, identify its source and responsible team in the handover instead of treating an absent result as a completed task.","completion":["The incoming team can review one connected care record.","Pending work retains a documented owner.","The ICU history accompanies the next care setting."]}},"ar":{"url":"https://mansoq.com/case-studies/hospital-icu-handover?lang=ar","title":"تسليم رعاية حرجة | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"راجع الملاحظات والأدوية والمسؤوليات الموثقة التي يحتاجها الفريق التالي.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"راجع الملاحظات والأدوية والمسؤوليات الموثقة التي يحتاجها الفريق التالي.","description":"سيناريو توضيحي: يراجع فريق العناية التالي الملاحظات والأدوية والمسؤوليات التي يحتاجها. تأكيد سياق الرعاية → مراجعة الملاحظات الموثقة → نقل سياق الأدوية → مراجعة متابعة الأقسام…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. تنتقل رعاية مريض في العناية المركزة من مناوبة إلى التالية. يحتاج الفريق المستلم إلى الملاحظات والأدوية والعمل المعلق الموثق معاً.","href":"/case-studies/hospital-icu-handover#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"يستطيع الفريق المستلم مراجعة سجل رعاية مترابط واحد. يظل للعمل المعلق مسؤول موثق. يرافق تاريخ العناية المركزة بيئة الرعاية التالية. إذا نقصت معلومات، يُحدد مصدرها والفريق المسؤول في التسليم بدلاً من اعتبار النتيجة الغائبة مهمة منجزة.","href":"/case-studies/hospital-icu-handover#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"تسليم رعاية حرجة","scenario":"تنتقل رعاية مريض في العناية المركزة من مناوبة إلى التالية. يحتاج الفريق المستلم إلى الملاحظات والأدوية والعمل المعلق الموثق معاً.","challenge":"يجب أن ينقل تسليم الرعاية المسؤولية إلى جانب المعلومات.","workflow":[{"title":"تأكيد سياق الرعاية","action":"فتح زيارة التنويم الصحيحة وتأكيد فريق العناية المركزة الحالي والموقع.","owner":"فريق التمريض","record":"الهوية · الزيارة · موقع العناية المركزة"},{"title":"مراجعة الملاحظات الموثقة","action":"مراجعة الملاحظات والتوثيق السريري المسجل بسياق الزيارة وتقييم الرعاية مهنياً.","owner":"الطبيب المعالج","record":"الملاحظات · التوثيق السريري"},{"title":"نقل سياق الأدوية","action":"إدراج سياق الأدوية والطلبات الموثق في التسليم للفريق السريري المسؤول.","owner":"فريق التمريض","record":"الأدوية · الطلبات الحالية"},{"title":"مراجعة متابعة الأقسام","action":"ربط النتائج المتاحة وعمل الأقسام المعلق بالزيارة نفسها.","owner":"فريق القسم","record":"النتائج · الطلبات المعلقة"},{"title":"تسجيل تسليم المناوبة","action":"توثيق تسليم الرعاية وتحديد من يتولى مسؤولية كل إجراء تالٍ.","owner":"فريق التمريض","record":"ملاحظة التسليم · المسؤول التالي"},{"title":"استمرار الرعاية أو نقلها","action":"تحديث خطة الرعاية التالية أو النقل الموثق إلى الجناح مع حفظ تاريخ زيارة العناية المركزة.","owner":"الطبيب المعالج","record":"خطة الرعاية · سجل النقل"}],"exception":"إذا نقصت معلومات، يُحدد مصدرها والفريق المسؤول في التسليم بدلاً من اعتبار النتيجة الغائبة مهمة منجزة.","completion":["يستطيع الفريق المستلم مراجعة سجل رعاية مترابط واحد.","يظل للعمل المعلق مسؤول موثق.","يرافق تاريخ العناية المركزة بيئة الرعاية التالية."]}}},{"slug":"/case-studies/hospitals","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/hospitals","title":"Hospitals workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind Hospitals.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind Hospitals.","description":"Illustrative operational cases: Admission to discharge; Day surgery, end to end; Critical-care handover; Care delivered. Revenue followed.. Roles, data, exceptions and…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/hospitals?lang=ar","title":"حالات المستشفيات ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المستشفيات.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المستشفيات.","description":"حالات تشغيل توضيحية: من الدخول إلى الخروج؛ الجراحة اليومية من البداية للنهاية؛ تسليم رعاية حرجة؛ رعاية مقدمة. إيرادات متابَعة.. الأدوار والبيانات والاستثناءات ومعايير القبول.","answers":[]}},{"slug":"/case-studies/medical-cities","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/medical-cities","title":"Medical Cities workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind Medical Cities.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind Medical Cities.","description":"Illustrative operational cases: Continuity across entities; Emergency into inpatient care; Diagnostics and medication across teams; A leadership view grounded in source data.…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/medical-cities?lang=ar","title":"حالات المدن الطبية ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المدن الطبية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المدن الطبية.","description":"حالات تشغيل توضيحية: استمرارية عبر الكيانات؛ من الطوارئ إلى التنويم؛ التشخيص والأدوية بين الفرق؛ رؤية قيادية تستند إلى بيانات المصدر. الأدوار والبيانات والاستثناءات ومعايير…","answers":[]}},{"slug":"/case-studies/medical-city-continuity","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/medical-city-continuity","title":"Continuity across entities | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Explore entity and record boundaries, accountable access and the agreed network composition.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore entity and record boundaries, accountable access and the agreed network composition.","description":"Illustrative scenario: Teams coordinate care within defined entity, patient-record and access boundaries. Define the network boundary → Record the source encounter → Coordinate…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative medical_cities workflow, not a named deployment or a measured outcome. A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries.","href":"/case-studies/medical-city-continuity#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The receiving service has the permitted source context. Source and receiving records retain their entity boundaries. Network visibility follows the agreed governance model. If an identity cannot be matched or access is outside the agreed boundary, the responsible teams resolve it before exchanging additional records.","href":"/case-studies/medical-city-continuity#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Continuity across entities","scenario":"A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries.","challenge":"Continuity across entities requires governed access, not unrestricted record sharing.","workflow":[{"title":"Define the network boundary","action":"Agree the entities, identity scope and permitted record exchange for this composition.","owner":"Integration & IT team","record":"Entities · Identity boundary · Permissions"},{"title":"Record the source encounter","action":"Document the patient’s current encounter and reason for the next service.","owner":"Treating clinician","record":"Source encounter · Referral reason"},{"title":"Coordinate the receiving service","action":"Confirm the destination and responsible team for the referral or transfer.","owner":"Access & coordination","record":"Destination · Team · Transfer"},{"title":"Share the permitted context","action":"Carry the agreed information through the selected connection with source references.","owner":"Integration & IT team","record":"Interface · Source record · Shared context"},{"title":"Document receiving care","action":"Review permitted information and document the receiving entity’s encounter and responsibilities.","owner":"Treating clinician","record":"Receiving encounter · Care plan"},{"title":"Review continuity with governance","action":"Review supported network reporting within the agreed entity and access boundaries.","owner":"Service leadership","record":"Entity view · Access · Reporting"}],"exception":"If an identity cannot be matched or access is outside the agreed boundary, the responsible teams resolve it before exchanging additional records.","completion":["The receiving service has the permitted source context.","Source and receiving records retain their entity boundaries.","Network visibility follows the agreed governance model."]}},"ar":{"url":"https://mansoq.com/case-studies/medical-city-continuity?lang=ar","title":"استمرارية عبر الكيانات | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"استكشف حدود الكيانات والسجلات والصلاحيات ذات المسؤولية وتكوين الشبكة المتفق عليه.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف حدود الكيانات والسجلات والصلاحيات ذات المسؤولية وتكوين الشبكة المتفق عليه.","description":"سيناريو توضيحي: تنسق الفرق الرعاية ضمن حدود محددة للكيانات وسجلات المرضى والوصول. تحديد حدود الشبكة → تسجيل الزيارة المصدر → تنسيق الخدمة المستلمة → مشاركة السياق المسموح →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. ينتقل مريض بين خدمات شبكة مدينة طبية. يحتاج الكيان المستلم إلى سياق الرعاية المسموح مع احتفاظ كل منظمة بحدود بياناتها.","href":"/case-studies/medical-city-continuity#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"تملك الخدمة المستلمة سياق المصدر المسموح. تحتفظ سجلات المصدر والمستلم بحدود كياناتها. تتبع رؤية الشبكة نموذج الحوكمة المتفق عليه. إذا تعذرت مطابقة الهوية أو تجاوز الوصول الحدود المتفق عليها، تعالج الفرق المسؤولة ذلك قبل تبادل سجلات إضافية.","href":"/case-studies/medical-city-continuity#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"استمرارية عبر الكيانات","scenario":"ينتقل مريض بين خدمات شبكة مدينة طبية. يحتاج الكيان المستلم إلى سياق الرعاية المسموح مع احتفاظ كل منظمة بحدود بياناتها.","challenge":"تتطلب الاستمرارية بين الكيانات وصولاً محكوماً، لا مشاركة سجلات بلا حدود.","workflow":[{"title":"تحديد حدود الشبكة","action":"الاتفاق على الكيانات ونطاق الهوية وتبادل السجلات المسموح لهذا التكوين.","owner":"فريق التكامل وتقنية المعلومات","record":"الكيانات · حدود الهوية · الصلاحيات"},{"title":"تسجيل الزيارة المصدر","action":"توثيق زيارة المريض الحالية وسبب الخدمة التالية.","owner":"الطبيب المعالج","record":"الزيارة المصدر · سبب الإحالة"},{"title":"تنسيق الخدمة المستلمة","action":"تأكيد الجهة المستلمة والفريق المسؤول عن الإحالة أو النقل.","owner":"الاستقبال والتنسيق","record":"الوجهة · الفريق · النقل"},{"title":"مشاركة السياق المسموح","action":"نقل المعلومات المتفق عليها عبر الاتصال المحدد مع مراجع المصدر.","owner":"فريق التكامل وتقنية المعلومات","record":"الاتصال · السجل المصدر · السياق المشترك"},{"title":"توثيق الرعاية المستلمة","action":"مراجعة المعلومات المسموح بها وتوثيق زيارة الكيان المستلم ومسؤولياته.","owner":"الطبيب المعالج","record":"الزيارة المستلمة · خطة الرعاية"},{"title":"مراجعة الاستمرارية مع الحوكمة","action":"مراجعة تقارير الشبكة المدعومة ضمن حدود الكيانات والصلاحيات المتفق عليها.","owner":"قيادة الخدمة","record":"عرض الكيان · الصلاحيات · التقارير"}],"exception":"إذا تعذرت مطابقة الهوية أو تجاوز الوصول الحدود المتفق عليها، تعالج الفرق المسؤولة ذلك قبل تبادل سجلات إضافية.","completion":["تملك الخدمة المستلمة سياق المصدر المسموح.","تحتفظ سجلات المصدر والمستلم بحدود كياناتها.","تتبع رؤية الشبكة نموذج الحوكمة المتفق عليه."]}}},{"slug":"/case-studies/operational-insight","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/operational-insight","title":"A leadership view grounded in source data | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Review verified operational and revenue reporting within agreed entity and data boundaries.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Review verified operational and revenue reporting within agreed entity and data boundaries.","description":"Illustrative scenario: Leadership reviews selected operational and revenue reporting within governed boundaries. Agree the reporting view → Identify the source activity →…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative medical_cities workflow, not a named deployment or a measured outcome. Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.","href":"/case-studies/operational-insight#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The reporting audience knows which entities are included. Operational questions retain their source context. Follow-up returns to the accountable team. An incomplete source is identified in the review rather than silently treated as zero activity; the source owner resolves the reporting gap.","href":"/case-studies/operational-insight#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"A leadership view grounded in source data","scenario":"Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.","challenge":"A network report is useful only when the included entities and definitions are clear.","workflow":[{"title":"Agree the reporting view","action":"Define the operational question, selected entities and authorized audience.","owner":"Service leadership","record":"Question · Entities · Access"},{"title":"Identify the source activity","action":"Record the relevant care and departmental activity within its source entity.","owner":"Department team","record":"Activity · Entity · Encounter"},{"title":"Connect revenue context","action":"Review claims, financial responses and outstanding work within the selected reporting scope.","owner":"Revenue team","record":"Claims · Responses · Work items"},{"title":"Review the reporting boundaries","action":"Check included sources, entity permissions and the agreed operational definitions.","owner":"Integration & IT team","record":"Sources · Permissions · Definitions"},{"title":"Review the selected report","action":"Use supported operational and revenue views to identify work requiring attention.","owner":"Service leadership","record":"Report · Review · Work requiring action"},{"title":"Assign accountable follow-up","action":"Record the responsible team and return operational questions to the relevant source.","owner":"Service leadership","record":"Action · Owner · Source reference"}],"exception":"An incomplete source is identified in the review rather than silently treated as zero activity; the source owner resolves the reporting gap.","completion":["The reporting audience knows which entities are included.","Operational questions retain their source context.","Follow-up returns to the accountable team."]}},"ar":{"url":"https://mansoq.com/case-studies/operational-insight?lang=ar","title":"رؤية قيادية تستند إلى بيانات المصدر | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"راجع التقارير التشغيلية والإيرادية المتحقق منها ضمن حدود الكيانات والبيانات المتفق عليها.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"راجع التقارير التشغيلية والإيرادية المتحقق منها ضمن حدود الكيانات والبيانات المتفق عليها.","description":"سيناريو توضيحي: تراجع القيادة التقارير التشغيلية والإيرادية المختارة ضمن حدود محكومة. الاتفاق على عرض التقارير → تحديد نشاط المصدر → ربط سياق الإيرادات → مراجعة حدود التقارير →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يراجع قادة مدينة طبية النشاط التشغيلي والإيرادي عبر كيانات محددة. يحتاجون إلى عروض قابلة للمقارنة بمصدر وحدود تقارير واضحين.","href":"/case-studies/operational-insight#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"يعرف جمهور التقارير الكيانات المشمولة. تحتفظ الأسئلة التشغيلية بسياق مصدرها. تعود المتابعة إلى الفريق المسؤول. يُحدد المصدر غير المكتمل أثناء المراجعة بدلاً من اعتباره نشاطاً صفرياً دون توضيح؛ ويعالج مسؤول المصدر فجوة التقارير.","href":"/case-studies/operational-insight#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"رؤية قيادية تستند إلى بيانات المصدر","scenario":"يراجع قادة مدينة طبية النشاط التشغيلي والإيرادي عبر كيانات محددة. يحتاجون إلى عروض قابلة للمقارنة بمصدر وحدود تقارير واضحين.","challenge":"لا يكون تقرير الشبكة مفيداً إلا عندما تكون الكيانات المشمولة والتعريفات واضحة.","workflow":[{"title":"الاتفاق على عرض التقارير","action":"تحديد السؤال التشغيلي والكيانات المختارة والجمهور المصرح له.","owner":"قيادة الخدمة","record":"السؤال · الكيانات · الصلاحيات"},{"title":"تحديد نشاط المصدر","action":"تسجيل نشاط الرعاية والأقسام المعني داخل الكيان المصدر.","owner":"فريق القسم","record":"النشاط · الكيان · الزيارة"},{"title":"ربط سياق الإيرادات","action":"مراجعة المطالبات والردود المالية والعمل المعلق ضمن نطاق التقارير المحدد.","owner":"فريق الإيرادات","record":"المطالبات · الردود · عناصر العمل"},{"title":"مراجعة حدود التقارير","action":"فحص المصادر المشمولة وصلاحيات الكيانات والتعريفات التشغيلية المتفق عليها.","owner":"فريق التكامل وتقنية المعلومات","record":"المصادر · الصلاحيات · التعريفات"},{"title":"مراجعة التقرير المحدد","action":"استخدام العروض التشغيلية والإيرادية المدعومة لتحديد العمل الذي يتطلب اهتماماً.","owner":"قيادة الخدمة","record":"التقرير · المراجعة · العمل المطلوب"},{"title":"إسناد متابعة بمسؤولية واضحة","action":"تسجيل الفريق المسؤول وإعادة الأسئلة التشغيلية إلى المصدر المعني.","owner":"قيادة الخدمة","record":"الإجراء · المسؤول · مرجع المصدر"}],"exception":"يُحدد المصدر غير المكتمل أثناء المراجعة بدلاً من اعتباره نشاطاً صفرياً دون توضيح؛ ويعالج مسؤول المصدر فجوة التقارير.","completion":["يعرف جمهور التقارير الكيانات المشمولة.","تحتفظ الأسئلة التشغيلية بسياق مصدرها.","تعود المتابعة إلى الفريق المسؤول."]}}},{"slug":"/case-studies/polyclinic-diagnostics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/polyclinic-diagnostics","title":"Diagnostic work in the care journey | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Connect orders, supported specimen/results work and the relevant encounter.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Connect orders, supported specimen/results work and the relevant encounter.","description":"Illustrative scenario: The laboratory handles the order and specimen before the result returns to the clinician. Create the clinical request → Receive the laboratory work →…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative polyclinics workflow, not a named deployment or a measured outcome. A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review.","href":"/case-studies/polyclinic-diagnostics#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The diagnostic request and result remain traceable. The clinician’s review is part of the care record. Laboratory activity connects to the relevant account. A rejected or incomplete specimen stays connected to the original request, with the laboratory’s documented reason and next responsibility.","href":"/case-studies/polyclinic-diagnostics#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Diagnostic work in the care journey","scenario":"A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review.","challenge":"The result must return to the patient and the consultation that requested it.","workflow":[{"title":"Create the clinical request","action":"Record the requested laboratory service in the correct specialty encounter.","owner":"Treating clinician","record":"Order · Encounter · Requested service"},{"title":"Receive the laboratory work","action":"Confirm the patient, request and supported specimen workflow before processing.","owner":"Laboratory team","record":"Patient · Request · Specimen"},{"title":"Process and document","action":"Complete the selected native laboratory work or agreed LIS exchange.","owner":"Laboratory team","record":"Laboratory activity · Source system"},{"title":"Return the available result","action":"Attach the documented result to its request and patient encounter.","owner":"Laboratory team","record":"Result · Request reference"},{"title":"Record clinical review","action":"Review the result professionally and document the next care action.","owner":"Treating clinician","record":"Review note · Care action"},{"title":"Close the service loop","action":"Review the delivered service charge while retaining any remaining clinical follow-up.","owner":"Revenue team","record":"Service charge · Follow-up"}],"exception":"A rejected or incomplete specimen stays connected to the original request, with the laboratory’s documented reason and next responsibility.","completion":["The diagnostic request and result remain traceable.","The clinician’s review is part of the care record.","Laboratory activity connects to the relevant account."]}},"ar":{"url":"https://mansoq.com/case-studies/polyclinic-diagnostics?lang=ar","title":"التشخيص ضمن رحلة الرعاية | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"اربط الطلبات وعمل العينات والنتائج المدعوم بالزيارة المناسبة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اربط الطلبات وعمل العينات والنتائج المدعوم بالزيارة المناسبة.","description":"سيناريو توضيحي: يتعامل المختبر مع الطلب والعينة قبل عودة النتيجة إلى الطبيب. إنشاء الطلب السريري → استلام عمل المختبر → المعالجة والتوثيق → إعادة النتيجة المتاحة → تسجيل…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. تطلب عيادة تخصصية فحصاً مخبرياً. ينفذ المختبر العمل ويعيد النتيجة ويوثق الطبيب مراجعتها.","href":"/case-studies/polyclinic-diagnostics#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"يظل طلب التشخيص ونتيجته قابلين للتتبع. مراجعة الطبيب جزء من سجل الرعاية. يرتبط نشاط المختبر بالحساب المعني. تبقى العينة المرفوضة أو غير المكتملة مرتبطة بالطلب الأصلي، مع سبب المختبر الموثق والمسؤولية التالية.","href":"/case-studies/polyclinic-diagnostics#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"التشخيص ضمن رحلة الرعاية","scenario":"تطلب عيادة تخصصية فحصاً مخبرياً. ينفذ المختبر العمل ويعيد النتيجة ويوثق الطبيب مراجعتها.","challenge":"يجب أن تعود النتيجة إلى المريض والاستشارة التي طلبتها.","workflow":[{"title":"إنشاء الطلب السريري","action":"تسجيل خدمة المختبر المطلوبة في زيارة التخصص الصحيحة.","owner":"الطبيب المعالج","record":"الطلب · الزيارة · الخدمة المطلوبة"},{"title":"استلام عمل المختبر","action":"تأكيد المريض والطلب ومسار العينات المدعوم قبل المعالجة.","owner":"فريق المختبر","record":"المريض · الطلب · العينة"},{"title":"المعالجة والتوثيق","action":"إنجاز عمل المختبر الداخلي المحدد أو تبادل نظام المختبر المتفق عليه.","owner":"فريق المختبر","record":"نشاط المختبر · النظام المصدر"},{"title":"إعادة النتيجة المتاحة","action":"إرفاق النتيجة الموثقة بطلبها وزيارة المريض.","owner":"فريق المختبر","record":"النتيجة · مرجع الطلب"},{"title":"تسجيل المراجعة السريرية","action":"مراجعة النتيجة مهنياً وتوثيق إجراء الرعاية التالي.","owner":"الطبيب المعالج","record":"ملاحظة المراجعة · إجراء الرعاية"},{"title":"إقفال مسار الخدمة","action":"مراجعة رسم الخدمة المنجزة مع الاحتفاظ بأي متابعة سريرية متبقية.","owner":"فريق الإيرادات","record":"رسم الخدمة · المتابعة"}],"exception":"تبقى العينة المرفوضة أو غير المكتملة مرتبطة بالطلب الأصلي، مع سبب المختبر الموثق والمسؤولية التالية.","completion":["يظل طلب التشخيص ونتيجته قابلين للتتبع.","مراجعة الطبيب جزء من سجل الرعاية.","يرتبط نشاط المختبر بالحساب المعني."]}}},{"slug":"/case-studies/polyclinic-pharmacy","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/polyclinic-pharmacy","title":"Medication, from request to dispensing | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Distinguish prescribing, native pharmacy operation and stock responsibilities.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Distinguish prescribing, native pharmacy operation and stock responsibilities.","description":"Illustrative scenario: Clinical prescribing connects to pharmacy operation and stock responsibilities. Document the prescription → Receive the pharmacy work → Review the…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative polyclinics workflow, not a named deployment or a measured outcome. A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work.","href":"/case-studies/polyclinic-pharmacy#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"Dispensing has a prescription and encounter reference. Stock and pharmacy responsibilities remain distinct. Medication activity is visible in financial follow-up. An unavailable item or unclear prescription returns to the responsible pharmacist and prescriber; the software does not choose a substitute treatment.","href":"/case-studies/polyclinic-pharmacy#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Medication, from request to dispensing","scenario":"A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work.","challenge":"Prescribing, dispensing and stock movement need distinct responsibilities in one connected path.","workflow":[{"title":"Document the prescription","action":"Record the clinician’s prescription against the specialty encounter.","owner":"Treating clinician","record":"Prescription · Clinician · Encounter"},{"title":"Receive the pharmacy work","action":"Verify the patient and prescription context within the selected pharmacy scope.","owner":"Pharmacy team","record":"Patient · Prescription reference"},{"title":"Review the medication request","action":"Document the pharmacist’s review and any clarification needed from the prescriber.","owner":"Pharmacy team","record":"Pharmacy review · Clarification"},{"title":"Record the dispensing step","action":"Record the agreed dispensing activity against the prescription and patient.","owner":"Pharmacy team","record":"Dispensing record · Prescription"},{"title":"Connect stock responsibility","action":"Link recorded dispensing to inventory responsibilities where inventory is included.","owner":"Department team","record":"Dispensing · Stock movement"},{"title":"Complete the account and follow-up","action":"Review medication charges and preserve documented follow-up for the care team.","owner":"Finance team","record":"Medication charge · Care follow-up"}],"exception":"An unavailable item or unclear prescription returns to the responsible pharmacist and prescriber; the software does not choose a substitute treatment.","completion":["Dispensing has a prescription and encounter reference.","Stock and pharmacy responsibilities remain distinct.","Medication activity is visible in financial follow-up."]}},"ar":{"url":"https://mansoq.com/case-studies/polyclinic-pharmacy?lang=ar","title":"الدواء من الطلب إلى الصرف | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"ميز بين وصف الدواء وتشغيل الصيدلية الداخلي ومسؤوليات المخزون.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"ميز بين وصف الدواء وتشغيل الصيدلية الداخلي ومسؤوليات المخزون.","description":"سيناريو توضيحي: يرتبط وصف الدواء السريري بتشغيل الصيدلية ومسؤوليات المخزون. توثيق الوصفة → استلام عمل الصيدلية → مراجعة طلب الدواء → تسجيل خطوة الصرف → ربط مسؤولية المخزون →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يغادر مريض استشارة مختص بوصفة. تراجع صيدلية مجمع العيادات عمل الدواء المحدد وتصرفه وتسجله.","href":"/case-studies/polyclinic-pharmacy#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"للصرف مرجع وصفة وزيارة. تظل مسؤوليات المخزون والصيدلية متميزة. يظهر نشاط الدواء في المتابعة المالية. يعود الصنف غير المتاح أو الوصفة غير الواضحة إلى الصيدلي والطبيب المسؤولين؛ ولا تختار البرمجيات علاجاً بديلاً.","href":"/case-studies/polyclinic-pharmacy#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"الدواء من الطلب إلى الصرف","scenario":"يغادر مريض استشارة مختص بوصفة. تراجع صيدلية مجمع العيادات عمل الدواء المحدد وتصرفه وتسجله.","challenge":"تحتاج الوصفة والصرف وحركة المخزون إلى مسؤوليات متميزة ضمن مسار مترابط واحد.","workflow":[{"title":"توثيق الوصفة","action":"تسجيل وصفة الطبيب مقابل زيارة التخصص.","owner":"الطبيب المعالج","record":"الوصفة · الطبيب · الزيارة"},{"title":"استلام عمل الصيدلية","action":"التحقق من المريض وسياق الوصفة ضمن نطاق الصيدلية المحدد.","owner":"فريق الصيدلية","record":"المريض · مرجع الوصفة"},{"title":"مراجعة طلب الدواء","action":"توثيق مراجعة الصيدلي وأي توضيح مطلوب من الطبيب الواصف.","owner":"فريق الصيدلية","record":"مراجعة الصيدلية · التوضيح"},{"title":"تسجيل خطوة الصرف","action":"تسجيل نشاط الصرف المتفق عليه مقابل الوصفة والمريض.","owner":"فريق الصيدلية","record":"سجل الصرف · الوصفة"},{"title":"ربط مسؤولية المخزون","action":"ربط الصرف المسجل بمسؤوليات المخزون حيث يشمل النطاق المخزون.","owner":"فريق القسم","record":"الصرف · حركة المخزون"},{"title":"إنجاز الحساب والمتابعة","action":"مراجعة رسوم الدواء وحفظ المتابعة الموثقة لفريق الرعاية.","owner":"الفريق المالي","record":"رسم الدواء · متابعة الرعاية"}],"exception":"يعود الصنف غير المتاح أو الوصفة غير الواضحة إلى الصيدلي والطبيب المسؤولين؛ ولا تختار البرمجيات علاجاً بديلاً.","completion":["للصرف مرجع وصفة وزيارة.","تظل مسؤوليات المخزون والصيدلية متميزة.","يظهر نشاط الدواء في المتابعة المالية."]}}},{"slug":"/case-studies/polyclinic-referral","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/polyclinic-referral","title":"A specialty referral | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Support the agreed specialist and referral workflow around one shared context.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Support the agreed specialist and referral workflow around one shared context.","description":"Illustrative scenario: The next specialist receives the shared record and the documented referral context. Document the first consultation → Coordinate the referral → Review…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative polyclinics workflow, not a named deployment or a measured outcome. A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.","href":"/case-studies/polyclinic-referral#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"A referral with its clinical reason and receiving service. Specialist work adds to the shared patient record. Separate service accounts retain their encounter references. If the receiving service needs more information, record the missing referral context and return the task to the responsible service.","href":"/case-studies/polyclinic-referral#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"A specialty referral","scenario":"A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.","challenge":"Different specialties should add to one patient story.","workflow":[{"title":"Document the first consultation","action":"Record the assessment and the reason a specialist review is requested.","owner":"Treating clinician","record":"Assessment · Referral reason"},{"title":"Coordinate the referral","action":"Arrange the receiving specialty appointment against the existing patient identity.","owner":"Access & coordination","record":"Referral · Specialty · Appointment"},{"title":"Review the shared context","action":"Review the referring note and relevant available results before documenting the specialist encounter.","owner":"Treating clinician","record":"Referring note · Results · Encounter"},{"title":"Connect specialist requests","action":"Link the specialist’s orders and prescription to the receiving consultation.","owner":"Treating clinician","record":"Specialist note · Orders · Prescription"},{"title":"Return the care plan","action":"Document the specialist assessment and follow-up responsibility for the referring service.","owner":"Treating clinician","record":"Assessment · Plan · Next service"},{"title":"Review each service account","action":"Keep each encounter’s services and billing distinct while retaining the shared patient context.","owner":"Finance team","record":"Encounter charges · Patient account"}],"exception":"If the receiving service needs more information, record the missing referral context and return the task to the responsible service.","completion":["A referral with its clinical reason and receiving service.","Specialist work adds to the shared patient record.","Separate service accounts retain their encounter references."]}},"ar":{"url":"https://mansoq.com/case-studies/polyclinic-referral?lang=ar","title":"إحالة تخصصية | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"ادعم مسار المختص والإحالة المتفق عليه حول سياق مشترك واحد.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"ادعم مسار المختص والإحالة المتفق عليه حول سياق مشترك واحد.","description":"سيناريو توضيحي: يتلقى المختص التالي السجل المشترك وسياق الإحالة الموثق. توثيق الاستشارة الأولى → تنسيق الإحالة → مراجعة السياق المشترك → ربط طلبات المختص → إعادة خطة الرعاية →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يُحال مريض من تخصص إلى آخر داخل مجمع عيادات. يحتاج الطبيب المستلم إلى سبب الإحالة والتوثيق السابق والنتائج المتاحة.","href":"/case-studies/polyclinic-referral#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"إحالة تحمل سببها السريري والخدمة المستلمة. يُضاف عمل المختص إلى سجل المريض المشترك. تحتفظ حسابات الخدمات المنفصلة بمراجع زياراتها. إذا احتاجت الخدمة المستلمة إلى معلومات إضافية، يُسجل سياق الإحالة الناقص وتُعاد المهمة إلى الخدمة المسؤولة.","href":"/case-studies/polyclinic-referral#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"إحالة تخصصية","scenario":"يُحال مريض من تخصص إلى آخر داخل مجمع عيادات. يحتاج الطبيب المستلم إلى سبب الإحالة والتوثيق السابق والنتائج المتاحة.","challenge":"يجب أن تضيف التخصصات المختلفة إلى قصة مريض واحدة.","workflow":[{"title":"توثيق الاستشارة الأولى","action":"تسجيل التقييم وسبب طلب مراجعة المختص.","owner":"الطبيب المعالج","record":"التقييم · سبب الإحالة"},{"title":"تنسيق الإحالة","action":"تنظيم موعد التخصص المستلم مقابل هوية المريض القائمة.","owner":"الاستقبال والتنسيق","record":"الإحالة · التخصص · الموعد"},{"title":"مراجعة السياق المشترك","action":"مراجعة توثيق الطبيب المحيل والنتائج المتاحة ذات الصلة قبل توثيق زيارة المختص.","owner":"الطبيب المعالج","record":"توثيق الإحالة · النتائج · الزيارة"},{"title":"ربط طلبات المختص","action":"ربط طلبات المختص ووصفته بالاستشارة المستلمة.","owner":"الطبيب المعالج","record":"توثيق المختص · الطلبات · الوصفة"},{"title":"إعادة خطة الرعاية","action":"توثيق تقييم المختص ومسؤولية المتابعة للخدمة المحيلة.","owner":"الطبيب المعالج","record":"التقييم · الخطة · الخدمة التالية"},{"title":"مراجعة حساب كل خدمة","action":"إبقاء خدمات كل زيارة وفوترتها متميزة مع الاحتفاظ بسياق المريض المشترك.","owner":"الفريق المالي","record":"رسوم الزيارة · حساب المريض"}],"exception":"إذا احتاجت الخدمة المستلمة إلى معلومات إضافية، يُسجل سياق الإحالة الناقص وتُعاد المهمة إلى الخدمة المسؤولة.","completion":["إحالة تحمل سببها السريري والخدمة المستلمة.","يُضاف عمل المختص إلى سجل المريض المشترك.","تحتفظ حسابات الخدمات المنفصلة بمراجع زياراتها."]}}},{"slug":"/case-studies/polyclinics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/polyclinics","title":"Polyclinics workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind Polyclinics.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind Polyclinics.","description":"Illustrative operational cases: A specialty referral; Diagnostic work in the care journey; Medication, from request to dispensing; Eligibility to reconciliation. Roles, data,…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/polyclinics?lang=ar","title":"حالات المجمعات الطبية ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المجمعات الطبية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف المجمعات الطبية.","description":"حالات تشغيل توضيحية: إحالة تخصصية؛ التشخيص ضمن رحلة الرعاية؛ الدواء من الطلب إلى الصرف؛ من الأهلية إلى المطابقة. الأدوار والبيانات والاستثناءات ومعايير القبول.","answers":[]}},{"slug":"/case-studies/revenue-eligibility-reconciliation","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/revenue-eligibility-reconciliation","title":"Eligibility to reconciliation | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Follow coverage, authorization, charges, claims, payer responses and accountable reconciliation.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Follow coverage, authorization, charges, claims, payer responses and accountable reconciliation.","description":"Illustrative scenario: Revenue teams follow the visit’s insurance and financial work through the payer response. Verify coverage → Follow service approvals → Capture delivered…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative polyclinics workflow, not a named deployment or a measured outcome. An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.","href":"/case-studies/revenue-eligibility-reconciliation#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"Every claim line retains its service context. Corrections and resubmissions have a review history. Paid and unresolved amounts have clear ownership. A partially paid claim keeps the paid allocation and unresolved lines separate, with a documented reason and follow-up owner.","href":"/case-studies/revenue-eligibility-reconciliation#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"Eligibility to reconciliation","scenario":"An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.","challenge":"Several departments can contribute to one claim without losing the origin of each service.","workflow":[{"title":"Verify coverage","action":"Record eligibility and the relevant coverage context for the visit.","owner":"Access & coordination","record":"Eligibility · Coverage · Encounter"},{"title":"Follow service approvals","action":"Connect required preauthorization requests and payer decisions to the requested services.","owner":"Revenue team","record":"Service · Authorization · Response"},{"title":"Capture delivered services","action":"Record consultation, diagnostic and pharmacy activity with its encounter reference.","owner":"Department team","record":"Department activity · Charge reference"},{"title":"Review and submit the claim","action":"Review the claim work items and use the agreed, activated exchange channel.","owner":"Revenue team","record":"Claim · Submission · Exchange trace"},{"title":"Resolve payer responses","action":"Assign rejection reasons for correction, review and documented resubmission where needed.","owner":"Revenue team","record":"Response · Reason · Resubmission"},{"title":"Reconcile the remittance","action":"Match payer remittance to claim records and assign remaining financial differences.","owner":"Finance team","record":"Remittance · Claim · Difference"}],"exception":"A partially paid claim keeps the paid allocation and unresolved lines separate, with a documented reason and follow-up owner.","completion":["Every claim line retains its service context.","Corrections and resubmissions have a review history.","Paid and unresolved amounts have clear ownership."]}},"ar":{"url":"https://mansoq.com/case-studies/revenue-eligibility-reconciliation?lang=ar","title":"من الأهلية إلى المطابقة | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"تابع التغطية والموافقات والرسوم والمطالبات وردود الجهات الدافعة والمطابقة ذات المسؤولية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تابع التغطية والموافقات والرسوم والمطالبات وردود الجهات الدافعة والمطابقة ذات المسؤولية.","description":"سيناريو توضيحي: تتابع فرق الإيرادات العمل التأميني والمالي للزيارة حتى رد الجهة الدافعة. التحقق من التغطية → متابعة موافقات الخدمات → التقاط الخدمات المنجزة → مراجعة المطالبة…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. تشمل زيارة تخصصية مؤمّنة فحوصاً وأدوية. يتابع فريق الإيرادات التغطية والموافقات والمطالبات وتخصيص السداد عبر تلك الخدمات.","href":"/case-studies/revenue-eligibility-reconciliation#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"يحتفظ كل بند مطالبة بسياق خدمته. للتصحيحات وإعادة الإرسال تاريخ مراجعة. للمبالغ المسددة وغير المحسومة مسؤولية واضحة. تُميز المطالبة المسددة جزئياً تخصيص المبلغ المسدد عن البنود غير المحسومة، مع سبب موثق ومسؤول متابعة.","href":"/case-studies/revenue-eligibility-reconciliation#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"من الأهلية إلى المطابقة","scenario":"تشمل زيارة تخصصية مؤمّنة فحوصاً وأدوية. يتابع فريق الإيرادات التغطية والموافقات والمطالبات وتخصيص السداد عبر تلك الخدمات.","challenge":"يمكن لعدة أقسام المساهمة في مطالبة واحدة دون فقد مصدر كل خدمة.","workflow":[{"title":"التحقق من التغطية","action":"تسجيل الأهلية وسياق التغطية المعني للزيارة.","owner":"الاستقبال والتنسيق","record":"الأهلية · التغطية · الزيارة"},{"title":"متابعة موافقات الخدمات","action":"ربط طلبات الموافقة المسبقة المطلوبة وقرارات الجهة الدافعة بالخدمات المطلوبة.","owner":"فريق الإيرادات","record":"الخدمة · الموافقة · الرد"},{"title":"التقاط الخدمات المنجزة","action":"تسجيل نشاط الاستشارة والتشخيص والصيدلية مع مرجع الزيارة.","owner":"فريق القسم","record":"نشاط القسم · مرجع الرسم"},{"title":"مراجعة المطالبة وإرسالها","action":"مراجعة عناصر عمل المطالبة واستخدام قناة التبادل المتفق عليها والمفعّلة.","owner":"فريق الإيرادات","record":"المطالبة · الإرسال · تتبع التبادل"},{"title":"معالجة ردود الجهة الدافعة","action":"إسناد أسباب الرفض للتصحيح والمراجعة وإعادة الإرسال الموثقة عند الحاجة.","owner":"فريق الإيرادات","record":"الرد · السبب · إعادة الإرسال"},{"title":"مطابقة إشعار السداد","action":"مطابقة إشعار سداد الجهة الدافعة بسجلات المطالبة وإسناد الفروقات المالية المتبقية.","owner":"الفريق المالي","record":"إشعار السداد · المطالبة · الفرق"}],"exception":"تُميز المطالبة المسددة جزئياً تخصيص المبلغ المسدد عن البنود غير المحسومة، مع سبب موثق ومسؤول متابعة.","completion":["يحتفظ كل بند مطالبة بسياق خدمته.","للتصحيحات وإعادة الإرسال تاريخ مراجعة.","للمبالغ المسددة وغير المحسومة مسؤولية واضحة."]}}},{"slug":"/case-studies/sbs-service-mapping","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/sbs-service-mapping","title":"From a service record to a traceable coding decision. | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Review supported SBS release, service mapping, validation and separate payer tariffs.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Review supported SBS release, service mapping, validation and separate payer tariffs.","description":"Illustrative scenario: Connect supported SBS mapping, provider services and separate payer tariff responsibilities. Identify the provider service → Confirm the catalogue scope…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative polyclinics workflow, not a named deployment or a measured outcome. A polyclinic introduces a service into its billing catalogue. Coding and revenue teams must agree the supported code mapping and its payer price rules.","href":"/case-studies/sbs-service-mapping#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"Service-to-code mapping has a recorded review decision. Payer prices remain distinct from service classification. Later changes have a catalogue and tariff reference. An uncertain mapping is held for responsible coding review. Catalogue tooling does not grant licensing rights or define payer reimbursement automatically.","href":"/case-studies/sbs-service-mapping#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"From a service record to a traceable coding decision.","scenario":"A polyclinic introduces a service into its billing catalogue. Coding and revenue teams must agree the supported code mapping and its payer price rules.","challenge":"A service code and a payer tariff answer different questions.","workflow":[{"title":"Identify the provider service","action":"Document the service description and operational department.","owner":"Department team","record":"Service · Description · Department"},{"title":"Confirm the catalogue scope","action":"Confirm the supported SBS release and permitted catalogue usage.","owner":"Revenue team","record":"Release · Catalogue scope · Rights"},{"title":"Review the service mapping","action":"Review the proposed provider-to-code mapping and record the responsible decision.","owner":"Revenue team","record":"Provider service · Code · Review"},{"title":"Define payer tariff context","action":"Record the separate contract price and tariff rules for the service.","owner":"Finance team","record":"Contract · Tariff · Price"},{"title":"Validate an encounter example","action":"Review a selected service charge against its mapping and agreed tariff.","owner":"Revenue team","record":"Charge · Mapping · Tariff version"},{"title":"Record approved use and changes","action":"Retain the reviewed mapping and assign responsibility for later catalogue changes.","owner":"Revenue team","record":"Approved mapping · Change responsibility"}],"exception":"An uncertain mapping is held for responsible coding review. Catalogue tooling does not grant licensing rights or define payer reimbursement automatically.","completion":["Service-to-code mapping has a recorded review decision.","Payer prices remain distinct from service classification.","Later changes have a catalogue and tariff reference."]}},"ar":{"url":"https://mansoq.com/case-studies/sbs-service-mapping?lang=ar","title":"من سجل خدمة إلى قرار ترميز قابل للتتبع. | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"راجع إصدار SBS المدعوم ومواءمة الخدمات والتحقق وتعريفات الجهات الدافعة المنفصلة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"راجع إصدار SBS المدعوم ومواءمة الخدمات والتحقق وتعريفات الجهات الدافعة المنفصلة.","description":"سيناريو توضيحي: اربط مواءمة SBS المدعومة وخدمات مقدم الرعاية ومسؤوليات تعريفة الجهة الدافعة المنفصلة. تحديد خدمة مقدم الرعاية → تأكيد نطاق الكتالوج → مراجعة مواءمة الخدمة →…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يضيف مجمع عيادات خدمة إلى كتالوج الفوترة. يجب أن تتفق فرق الترميز والإيرادات على مواءمة الرمز المدعومة وقواعد سعر الجهة الدافعة.","href":"/case-studies/sbs-service-mapping#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"لمواءمة الخدمة إلى الرمز قرار مراجعة مسجل. تظل أسعار الجهات الدافعة متميزة عن تصنيف الخدمات. للتغييرات اللاحقة مرجع كتالوج وتعريفة. تُحال المواءمة غير المؤكدة إلى مراجعة الترميز المسؤولة. لا تمنح أدوات الكتالوج حقوق ترخيص ولا تحدد تعويض الجهة الدافعة تلقائياً.","href":"/case-studies/sbs-service-mapping#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"من سجل خدمة إلى قرار ترميز قابل للتتبع.","scenario":"يضيف مجمع عيادات خدمة إلى كتالوج الفوترة. يجب أن تتفق فرق الترميز والإيرادات على مواءمة الرمز المدعومة وقواعد سعر الجهة الدافعة.","challenge":"يجيب رمز الخدمة وتعريفة الجهة الدافعة عن سؤالين مختلفين.","workflow":[{"title":"تحديد خدمة مقدم الرعاية","action":"توثيق وصف الخدمة والقسم التشغيلي.","owner":"فريق القسم","record":"الخدمة · الوصف · القسم"},{"title":"تأكيد نطاق الكتالوج","action":"تأكيد إصدار SBS المدعوم والاستخدام المسموح للكتالوج.","owner":"فريق الإيرادات","record":"الإصدار · نطاق الكتالوج · الحقوق"},{"title":"مراجعة مواءمة الخدمة","action":"مراجعة مواءمة الخدمة إلى الرمز وتسجيل القرار المسؤول.","owner":"فريق الإيرادات","record":"خدمة مقدم الرعاية · الرمز · المراجعة"},{"title":"تحديد سياق تعريفة الجهة الدافعة","action":"تسجيل سعر العقد وقواعد التعريفة المنفصلة للخدمة.","owner":"الفريق المالي","record":"العقد · التعريفة · السعر"},{"title":"التحقق من مثال زيارة","action":"مراجعة رسم خدمة محدد مقابل مواءمته وتعريفته المتفق عليها.","owner":"فريق الإيرادات","record":"الرسم · المواءمة · إصدار التعريفة"},{"title":"تسجيل الاستخدام المعتمد والتغييرات","action":"حفظ المواءمة المراجعة وإسناد مسؤولية تغييرات الكتالوج اللاحقة.","owner":"فريق الإيرادات","record":"المواءمة المعتمدة · مسؤولية التغيير"}],"exception":"تُحال المواءمة غير المؤكدة إلى مراجعة الترميز المسؤولة. لا تمنح أدوات الكتالوج حقوق ترخيص ولا تحدد تعويض الجهة الدافعة تلقائياً.","completion":["لمواءمة الخدمة إلى الرمز قرار مراجعة مسجل.","تظل أسعار الجهات الدافعة متميزة عن تصنيف الخدمات.","للتغييرات اللاحقة مرجع كتالوج وتعريفة."]}}},{"slug":"/case-studies/teleicu","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/teleicu","title":"TeleICU workflow case studies | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore the people, workflow and product scope behind TeleICU.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore the people, workflow and product scope behind TeleICU.","description":"Illustrative operational cases: A remote critical-care review; A handover between care teams; Orders and results in the review; An interface with clear ownership. Roles, data,…","answers":[]},"ar":{"url":"https://mansoq.com/case-studies/teleicu?lang=ar","title":"حالات العناية المركزة عن بُعد ومسارات الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف العناية المركزة عن بُعد.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف الأشخاص ومسار العمل ونطاق المنتجات خلف العناية المركزة عن بُعد.","description":"حالات تشغيل توضيحية: مراجعة عناية حرجة عن بُعد؛ تسليم بين فرق الرعاية؛ الطلبات والنتائج ضمن المراجعة؛ اتصال بمسؤولية واضحة. الأدوار والبيانات والاستثناءات ومعايير القبول.","answers":[]}},{"slug":"/case-studies/teleicu-review","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/case-studies/teleicu-review","title":"A remote critical-care review | MANSOQ case study","eyebrow":"Workflow demonstration","summary":"Bring the supported clinical context and collaboration scope into an accountable review.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Bring the supported clinical context and collaboration scope into an accountable review.","description":"Illustrative scenario: The local team prepares the case so a remote specialist can review the supported context. Prepare the local case → Bring the supported context → Perform…","answers":[{"question":"Is this a customer result or an operational illustration?","answer":"This is an illustrative teleicu workflow, not a named deployment or a measured outcome. A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team.","href":"/case-studies/teleicu-review#case-content"},{"question":"What must be complete before this journey is accepted?","answer":"The remote review has a documented source and question. Recommendations return to an accountable local clinician. Bedside decisions and subsequent follow-up stay traceable. Missing source information is referred back to the local team. Video, device data and live monitoring are separate connections, not assumed features of this scenario.","href":"/case-studies/teleicu-review#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"A remote critical-care review","scenario":"A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team.","challenge":"Remote expertise needs clinical context and a clear return path to the bedside.","workflow":[{"title":"Prepare the local case","action":"Confirm the patient encounter and document the question for specialist review.","owner":"Local care team","record":"Encounter · Review question"},{"title":"Bring the supported context","action":"Make the agreed notes and observations available through the selected source-system connection.","owner":"Integration & IT team","record":"Source · Notes · Observations"},{"title":"Perform the remote review","action":"Review the available information and record the specialist’s assessment within the agreed service.","owner":"Remote specialist","record":"Review · Specialist note"},{"title":"Return documented recommendations","action":"Document recommendations and the points requiring local clinical review.","owner":"Remote specialist","record":"Recommendations · Local review"},{"title":"Record the bedside decision","action":"Review the specialist note and record the local clinician’s care decision and responsibilities.","owner":"Local care team","record":"Local decision · Care responsibility"},{"title":"Complete the review handover","action":"Document completed review work and any further specialist or bedside follow-up.","owner":"Local care team","record":"Review record · Follow-up owner"}],"exception":"Missing source information is referred back to the local team. Video, device data and live monitoring are separate connections, not assumed features of this scenario.","completion":["The remote review has a documented source and question.","Recommendations return to an accountable local clinician.","Bedside decisions and subsequent follow-up stay traceable."]}},"ar":{"url":"https://mansoq.com/case-studies/teleicu-review?lang=ar","title":"مراجعة عناية حرجة عن بُعد | حالة منسوق","eyebrow":"عرض لمسار العمل","summary":"أدخل السياق السريري ونطاق التعاون المدعومين إلى مراجعة واضحة المسؤولية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"أدخل السياق السريري ونطاق التعاون المدعومين إلى مراجعة واضحة المسؤولية.","description":"سيناريو توضيحي: يجهز الفريق المحلي الحالة ليتمكن المختص عن بُعد من مراجعة السياق المدعوم. تجهيز الحالة المحلية → إحضار السياق المدعوم → تنفيذ المراجعة عن بُعد → إعادة التوصيات…","answers":[{"question":"هل هذه نتائج عميل أم حالة تشغيل توضيحية؟","answer":"هذه حالة تشغيل توضيحية، وليست تنفيذاً لعميل محدد أو نتيجة مقاسة. يطلب فريق عناية مركزة محلي مراجعة مختص عن بُعد. يحتاج المختص إلى السجل السريري المتفق عليه، بينما تبقى رعاية المريض بيد الفريق المحلي.","href":"/case-studies/teleicu-review#case-content"},{"question":"ما الذي يجب إكماله لقبول هذه الرحلة؟","answer":"للمراجعة عن بُعد مصدر وسؤال موثقان. تعود التوصيات إلى طبيب محلي مسؤول. تظل قرارات الفريق المحلي والمتابعة اللاحقة قابلتين للتتبع. تُعاد معلومات المصدر الناقصة إلى الفريق المحلي. الفيديو وبيانات الأجهزة والمراقبة الحية اتصالات مستقلة وليست وظائف مفترضة في هذا المسار.","href":"/case-studies/teleicu-review#case-content"}],"caseStudy":{"type":"Illustrative operational scenario","title":"مراجعة عناية حرجة عن بُعد","scenario":"يطلب فريق عناية مركزة محلي مراجعة مختص عن بُعد. يحتاج المختص إلى السجل السريري المتفق عليه، بينما تبقى رعاية المريض بيد الفريق المحلي.","challenge":"تحتاج الخبرة عن بُعد إلى سياق سريري ومسار عودة واضح إلى سرير المريض.","workflow":[{"title":"تجهيز الحالة المحلية","action":"تأكيد زيارة المريض وتوثيق السؤال المطلوب لمراجعة المختص.","owner":"فريق الرعاية المحلي","record":"الزيارة · سؤال المراجعة"},{"title":"إحضار السياق المدعوم","action":"إتاحة التوثيق والملاحظات المتفق عليها عبر اتصال النظام المصدر المحدد.","owner":"فريق التكامل وتقنية المعلومات","record":"المصدر · التوثيق · الملاحظات"},{"title":"تنفيذ المراجعة عن بُعد","action":"مراجعة المعلومات المتاحة وتسجيل تقييم المختص ضمن الخدمة المتفق عليها.","owner":"المختص عن بُعد","record":"المراجعة · توثيق المختص"},{"title":"إعادة التوصيات الموثقة","action":"توثيق التوصيات والنقاط التي تتطلب مراجعة سريرية محلية.","owner":"المختص عن بُعد","record":"التوصيات · المراجعة المحلية"},{"title":"تسجيل قرار الفريق المحلي","action":"مراجعة توثيق المختص وتسجيل قرار الطبيب المحلي ومسؤوليات الرعاية.","owner":"فريق الرعاية المحلي","record":"القرار المحلي · مسؤولية الرعاية"},{"title":"إنجاز تسليم المراجعة","action":"توثيق عمل المراجعة المنجز وأي متابعة إضافية للمختص أو الفريق المحلي.","owner":"فريق الرعاية المحلي","record":"سجل المراجعة · مسؤول المتابعة"}],"exception":"تُعاد معلومات المصدر الناقصة إلى الفريق المحلي. الفيديو وبيانات الأجهزة والمراقبة الحية اتصالات مستقلة وليست وظائف مفترضة في هذا المسار.","completion":["للمراجعة عن بُعد مصدر وسؤال موثقان.","تعود التوصيات إلى طبيب محلي مسؤول.","تظل قرارات الفريق المحلي والمتابعة اللاحقة قابلتين للتتبع."]}}},{"slug":"/company/about","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/company/about","title":"Built around people, in Saudi Arabia.","eyebrow":"Human-centered experiences. Connected across care.","summary":"MANSOQ connects care and revenue around a shared foundation, with Saudi healthcare and human-centered experiences guiding the product.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Human-centered experiences guide the platform and the way we introduce it.","items":[{"text":"Support continuity and a clear next step across the people delivering care.","title":"Patients and families"},{"text":"Bring relevant clinical context into the workflow and clarify responsibilities.","title":"Clinicians and nurses"},{"text":"Connect the task, the care context and accountable financial follow-up.","title":"Reception, departments and revenue teams"}],"title":"Make every handover matter"},{"kind":"cards","intro":"Useful context and a clear next conversation.","items":[{"href":"/about","text":"MANSOQ connects care and revenue around a shared foundation, with Saudi healthcare and human-centered experiences guiding the product.","title":"Built around people, in Saudi Arabia."}],"title":"Learn more"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"MANSOQ connects care and revenue around a shared foundation, with Saudi healthcare and human-centered experiences guiding the product.","description":"MANSOQ connects care and revenue around a shared foundation, with Saudi healthcare and human-centered experiences guiding the product.","answers":[],"overview":{"title":"Built around people, in Saudi Arabia.","summary":"MANSOQ connects care and revenue around a shared foundation, with Saudi healthcare and human-centered experiences guiding the product.","areas":[]}},"ar":{"url":"https://mansoq.com/company/about?lang=ar","title":"بُني حول الإنسان في السعودية.","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"يربط منسوق الرعاية بالإيراد حول أساس مشترك، وتوجه الرعاية السعودية والتجارب المتمحورة حول الإنسان المنتج.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"تقود التجارب المتمحورة حول الإنسان المنصة وطريقة تقديمها.","items":[{"text":"ادعم الاستمرارية وخطوة تالية واضحة بين مقدمي الرعاية.","title":"المرضى والأسر"},{"text":"أدخل السياق السريري المناسب إلى مسار العمل ووضح المسؤوليات.","title":"الأطباء والتمريض"},{"text":"اربط المهمة وسياق الرعاية والمتابعة المالية ذات المسؤوليات الواضحة.","title":"الاستقبال والأقسام وفرق الإيرادات"}],"title":"اجعل كل تسليم للرعاية ذا معنى"},{"kind":"cards","intro":"سياق مفيد ومحادثة تالية واضحة.","items":[{"href":"/about","text":"يربط منسوق الرعاية بالإيراد حول أساس مشترك، وتوجه الرعاية السعودية والتجارب المتمحورة حول الإنسان المنتج.","title":"بُني حول الإنسان في السعودية."}],"title":"تعرف على المزيد"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"يربط منسوق الرعاية بالإيراد حول أساس مشترك، وتوجه الرعاية السعودية والتجارب المتمحورة حول الإنسان المنتج.","description":"يربط منسوق الرعاية بالإيراد حول أساس مشترك، وتوجه الرعاية السعودية والتجارب المتمحورة حول الإنسان المنتج.","answers":[],"overview":{"title":"بُني حول الإنسان في السعودية.","summary":"يربط منسوق الرعاية بالإيراد حول أساس مشترك، وتوجه الرعاية السعودية والتجارب المتمحورة حول الإنسان المنتج.","areas":[]}}},{"slug":"/company/careers","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/company/careers","title":"Build meaningful healthcare experiences.","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore current opportunities and contribute to the people, workflows and systems supporting care.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Human-centered experiences guide the platform and the way we introduce it.","items":[{"text":"Support continuity and a clear next step across the people delivering care.","title":"Patients and families"},{"text":"Bring relevant clinical context into the workflow and clarify responsibilities.","title":"Clinicians and nurses"},{"text":"Connect the task, the care context and accountable financial follow-up.","title":"Reception, departments and revenue teams"}],"title":"Make every handover matter"},{"kind":"cards","intro":"Useful context and a clear next conversation.","items":[{"href":"/careers","text":"Explore current opportunities and contribute to the people, workflows and systems supporting care.","title":"Build meaningful healthcare experiences."}],"title":"Learn more"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"Explore current opportunities and contribute to the people, workflows and systems supporting care.","description":"Explore current opportunities and contribute to the people, workflows and systems supporting care.","answers":[],"overview":{"title":"Build meaningful healthcare experiences.","summary":"Explore current opportunities and contribute to the people, workflows and systems supporting care.","areas":[]}},"ar":{"url":"https://mansoq.com/company/careers?lang=ar","title":"ابنِ تجارب صحية ذات معنى.","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف الفرص الحالية وساهم في الأشخاص ومسارات العمل والأنظمة الداعمة للرعاية.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"تقود التجارب المتمحورة حول الإنسان المنصة وطريقة تقديمها.","items":[{"text":"ادعم الاستمرارية وخطوة تالية واضحة بين مقدمي الرعاية.","title":"المرضى والأسر"},{"text":"أدخل السياق السريري المناسب إلى مسار العمل ووضح المسؤوليات.","title":"الأطباء والتمريض"},{"text":"اربط المهمة وسياق الرعاية والمتابعة المالية ذات المسؤوليات الواضحة.","title":"الاستقبال والأقسام وفرق الإيرادات"}],"title":"اجعل كل تسليم للرعاية ذا معنى"},{"kind":"cards","intro":"سياق مفيد ومحادثة تالية واضحة.","items":[{"href":"/careers","text":"استكشف الفرص الحالية وساهم في الأشخاص ومسارات العمل والأنظمة الداعمة للرعاية.","title":"ابنِ تجارب صحية ذات معنى."}],"title":"تعرف على المزيد"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"استكشف الفرص الحالية وساهم في الأشخاص ومسارات العمل والأنظمة الداعمة للرعاية.","description":"استكشف الفرص الحالية وساهم في الأشخاص ومسارات العمل والأنظمة الداعمة للرعاية.","answers":[],"overview":{"title":"ابنِ تجارب صحية ذات معنى.","summary":"استكشف الفرص الحالية وساهم في الأشخاص ومسارات العمل والأنظمة الداعمة للرعاية.","areas":[]}}},{"slug":"/company/partners","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/company/partners","title":"Deliver connected care together.","eyebrow":"Human-centered experiences. Connected across care.","summary":"Discuss implementation, system interfaces and accountable delivery with MANSOQ. Partner relationships and credentials are named only when documented.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Human-centered experiences guide the platform and the way we introduce it.","items":[{"text":"Support continuity and a clear next step across the people delivering care.","title":"Patients and families"},{"text":"Bring relevant clinical context into the workflow and clarify responsibilities.","title":"Clinicians and nurses"},{"text":"Connect the task, the care context and accountable financial follow-up.","title":"Reception, departments and revenue teams"}],"title":"Make every handover matter"},{"kind":"cards","intro":"Useful context and a clear next conversation.","items":[{"href":"/network","text":"Discuss implementation, system interfaces and accountable delivery with MANSOQ. Partner relationships and credentials are named only when documented.","title":"Deliver connected care together."}],"title":"Learn more"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"Discuss implementation, system interfaces and accountable delivery with MANSOQ. Partner relationships and credentials are named only when documented.","description":"Discuss implementation, system interfaces and accountable delivery with MANSOQ. Partner relationships and credentials are named only when documented.","answers":[],"overview":{"title":"Deliver connected care together.","summary":"Discuss implementation, system interfaces and accountable delivery with MANSOQ. Partner relationships and credentials are named only when documented.","areas":[]}},"ar":{"url":"https://mansoq.com/company/partners?lang=ar","title":"قدموا الرعاية المترابطة معاً.","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"ناقش التنفيذ واتصالات الأنظمة والتنفيذ المسؤول مع منسوق. ولا تسمى علاقات الشركاء واعتماداتهم إلا عند توثيقها.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"تقود التجارب المتمحورة حول الإنسان المنصة وطريقة تقديمها.","items":[{"text":"ادعم الاستمرارية وخطوة تالية واضحة بين مقدمي الرعاية.","title":"المرضى والأسر"},{"text":"أدخل السياق السريري المناسب إلى مسار العمل ووضح المسؤوليات.","title":"الأطباء والتمريض"},{"text":"اربط المهمة وسياق الرعاية والمتابعة المالية ذات المسؤوليات الواضحة.","title":"الاستقبال والأقسام وفرق الإيرادات"}],"title":"اجعل كل تسليم للرعاية ذا معنى"},{"kind":"cards","intro":"سياق مفيد ومحادثة تالية واضحة.","items":[{"href":"/network","text":"ناقش التنفيذ واتصالات الأنظمة والتنفيذ المسؤول مع منسوق. ولا تسمى علاقات الشركاء واعتماداتهم إلا عند توثيقها.","title":"قدموا الرعاية المترابطة معاً."}],"title":"تعرف على المزيد"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"ناقش التنفيذ واتصالات الأنظمة والتنفيذ المسؤول مع منسوق. ولا تسمى علاقات الشركاء واعتماداتهم إلا عند توثيقها.","description":"ناقش التنفيذ واتصالات الأنظمة والتنفيذ المسؤول مع منسوق. ولا تسمى علاقات الشركاء واعتماداتهم إلا عند توثيقها.","answers":[],"overview":{"title":"قدموا الرعاية المترابطة معاً.","summary":"ناقش التنفيذ واتصالات الأنظمة والتنفيذ المسؤول مع منسوق. ولا تسمى علاقات الشركاء واعتماداتهم إلا عند توثيقها.","areas":[]}}},{"slug":"/company/trust","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/company/trust","title":"Trust starts with clear boundaries.","eyebrow":"Human-centered experiences. Connected across care.","summary":"Review supported access, audit, data, operating and service responsibilities. Certification, SLAs and measured capacity require their own evidence.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Review supported access, audit, data, operating and service responsibilities. Certification, SLAs and measured capacity require their own evidence.","description":"Review supported access, audit, data, operating and service responsibilities. Certification, SLAs and measured capacity require their own evidence.","answers":[],"overview":{"title":"Trust, built into the way you work.","summary":"Clear controls for people, records and responsibilities.","areas":[{"name":"Access","purpose":"Define who can use each part of the agreed scope.","functions":["Named roles","Governed access"]},{"name":"Audit","purpose":"Keep access and actions traceable to responsible teams.","functions":["Actions","Responsibility"]},{"name":"Data boundaries","purpose":"Agree entities, environments and record-sharing boundaries.","functions":["Entities","Shared records"]},{"name":"Service responsibilities","purpose":"Define support coverage and continuity commitments for your deployment.","functions":["Support coverage","Continuity scope"]}]}},"ar":{"url":"https://mansoq.com/company/trust?lang=ar","title":"تبدأ الثقة بحدود واضحة.","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"راجع مسؤوليات الصلاحيات والتدقيق والبيانات والتشغيل والخدمة المدعومة. وتتطلب الاعتمادات ومستويات الخدمة والسعة المقاسة أدلتها المستقلة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"راجع مسؤوليات الصلاحيات والتدقيق والبيانات والتشغيل والخدمة المدعومة. وتتطلب الاعتمادات ومستويات الخدمة والسعة المقاسة أدلتها المستقلة.","description":"راجع مسؤوليات الصلاحيات والتدقيق والبيانات والتشغيل والخدمة المدعومة. وتتطلب الاعتمادات ومستويات الخدمة والسعة المقاسة أدلتها المستقلة.","answers":[],"overview":{"title":"ثقة في صميم عملك.","summary":"ضوابط واضحة للأشخاص والسجلات والمسؤوليات.","areas":[{"name":"الصلاحيات","purpose":"حدد من يمكنه استخدام كل جزء من النطاق المتفق عليه.","functions":["أدوار محددة","وصول محكوم"]},{"name":"التدقيق","purpose":"اجعل الوصول والإجراءات قابلة للتتبع إلى الفرق المسؤولة.","functions":["الإجراءات","المسؤولية"]},{"name":"حدود البيانات","purpose":"اتفق على الكيانات والبيئات وحدود مشاركة السجلات.","functions":["الكيانات","السجلات المشتركة"]},{"name":"مسؤوليات الخدمة","purpose":"حدد تغطية الدعم والتزامات الاستمرارية لتشغيلك.","functions":["تغطية الدعم","نطاق الاستمرارية"]}]}}},{"slug":"/compare","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare","title":"Compare healthcare software scope & implementation | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Use exact scope, local requirements, delivery obligations and documented sources to compare approaches. No unsupported superiority scores.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Use exact scope, local requirements, delivery obligations and documented sources to compare approaches. No unsupported superiority scores.","description":"Compare healthcare software using documented clinical, departmental and financial scope, deployment models, interfaces, migration and acceptance requirements.","answers":[],"overview":{"title":"Compare what your team will actually use.","summary":"Start with the care setting. Review scope, delivery and evidence.","areas":[{"name":"Hospital and network platforms","purpose":"Review the documented approach against your care and delivery needs.","functions":["Workflow and module scope","Native operation versus connections","Saudi standards and terminology","Arabic experience","Deployment and shared-data boundaries","Implementation and support","Commercial basis and obligations","Evaluation boundaries","Data export and exit"],"details":"/compare/unified-his"},{"name":"Clinic and ambulatory suites","purpose":"Review the documented approach against your care and delivery needs.","functions":["Workflow and module scope","Native operation versus connections","Saudi standards and terminology","Arabic experience","Deployment and shared-data boundaries","Implementation and support","Commercial basis and obligations","Evaluation boundaries","Data export and exit"],"details":"/compare/ambulatory"},{"name":"Saudi revenue approaches","purpose":"Review the documented approach against your care and delivery needs.","functions":["Workflow and module scope","Native operation versus connections","Saudi standards and terminology","Arabic experience","Deployment and shared-data boundaries","Implementation and support","Commercial basis and obligations","Evaluation boundaries","Data export and exit"],"details":"/compare/saudi-rcm"},{"name":"Remote critical-care delivery","purpose":"Review the documented approach against your care and delivery needs.","functions":["Workflow and module scope","Native operation versus connections","Saudi standards and terminology","Arabic experience","Deployment and shared-data boundaries","Implementation and support","Commercial basis and obligations","Evaluation boundaries","Data export and exit"],"details":"/compare/remote-critical-care"},{"name":"Home and palliative platforms","purpose":"Review the documented approach against your care and delivery needs.","functions":["Workflow and module scope","Native operation versus connections","Saudi standards and terminology","Arabic experience","Deployment and shared-data boundaries","Implementation and support","Commercial basis and obligations","Evaluation boundaries","Data export and exit"],"details":"/compare/home-palliative"}]}},"ar":{"url":"https://mansoq.com/compare?lang=ar","title":"مقارنة أنظمة الرعاية ونطاقها وتنفيذها | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استخدم النطاق الدقيق والمتطلبات المحلية والتزامات التنفيذ والمصادر الموثقة لمقارنة الأساليب، دون درجات تفوق غير مثبتة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استخدم النطاق الدقيق والمتطلبات المحلية والتزامات التنفيذ والمصادر الموثقة لمقارنة الأساليب، دون درجات تفوق غير مثبتة.","description":"قارن أنظمة الرعاية حسب النطاق السريري والتشغيلي والمالي الموثق ونماذج التشغيل والاتصالات والترحيل ومتطلبات القبول.","answers":[],"overview":{"title":"قارن ما سيستخدمه فريقك فعلاً.","summary":"ابدأ ببيئة الرعاية. راجع النطاق والتنفيذ والأدلة.","areas":[{"name":"منصات المستشفيات والشبكات","purpose":"راجع الأسلوب الموثق وفق احتياجات الرعاية والتنفيذ.","functions":["نطاق المسارات والوحدات","التشغيل الداخلي مقابل الربط","المعايير والمصطلحات السعودية","التجربة العربية","النشر وحدود البيانات المشتركة","التنفيذ والدعم","الأساس التجاري والالتزامات","حدود التقييم","تصدير البيانات والخروج"],"details":"/compare/unified-his"},{"name":"منظومات العيادات والرعاية الخارجية","purpose":"راجع الأسلوب الموثق وفق احتياجات الرعاية والتنفيذ.","functions":["نطاق المسارات والوحدات","التشغيل الداخلي مقابل الربط","المعايير والمصطلحات السعودية","التجربة العربية","النشر وحدود البيانات المشتركة","التنفيذ والدعم","الأساس التجاري والالتزامات","حدود التقييم","تصدير البيانات والخروج"],"details":"/compare/ambulatory"},{"name":"أساليب الإيرادات السعودية","purpose":"راجع الأسلوب الموثق وفق احتياجات الرعاية والتنفيذ.","functions":["نطاق المسارات والوحدات","التشغيل الداخلي مقابل الربط","المعايير والمصطلحات السعودية","التجربة العربية","النشر وحدود البيانات المشتركة","التنفيذ والدعم","الأساس التجاري والالتزامات","حدود التقييم","تصدير البيانات والخروج"],"details":"/compare/saudi-rcm"},{"name":"تنفيذ العناية الحرجة عن بعد","purpose":"راجع الأسلوب الموثق وفق احتياجات الرعاية والتنفيذ.","functions":["نطاق المسارات والوحدات","التشغيل الداخلي مقابل الربط","المعايير والمصطلحات السعودية","التجربة العربية","النشر وحدود البيانات المشتركة","التنفيذ والدعم","الأساس التجاري والالتزامات","حدود التقييم","تصدير البيانات والخروج"],"details":"/compare/remote-critical-care"},{"name":"منصات الرعاية المنزلية والتلطيفية","purpose":"راجع الأسلوب الموثق وفق احتياجات الرعاية والتنفيذ.","functions":["نطاق المسارات والوحدات","التشغيل الداخلي مقابل الربط","المعايير والمصطلحات السعودية","التجربة العربية","النشر وحدود البيانات المشتركة","التنفيذ والدعم","الأساس التجاري والالتزامات","حدود التقييم","تصدير البيانات والخروج"],"details":"/compare/home-palliative"}]}}},{"slug":"/compare/ambulatory","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare/ambulatory","title":"Clinic and ambulatory software","eyebrow":"Human-centered experiences. Connected across care.","summary":"Cliniko, CharmHealth and eClinicalWorks illustrate different practitioner, encounter and software/service pricing bases. Compare workflow coverage before transferring a price metric.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Use your actual care composition; a vendor label does not establish identical functionality.","items":[{"text":"Review role/task coverage and complete clinical or service journeys.","title":"People and workflow"},{"text":"Separate included modules, prerequisites, external-system access and integration delivery.","title":"Products and interfaces"},{"text":"Compare recurring software, implementation, services, third-party licensing, variable costs and tax.","title":"Commercial obligations"},{"text":"Verify language, standards versions, credentials/onboarding and operational acceptance for your exact scope.","title":"Saudi fit and evidence"}],"title":"What to compare"},{"kind":"cards","intro":"Reviewed 8 October 2026. A dated marketing source is not a current contractual inclusion or a MANSOQ equivalence claim.","items":[{"href":"https://www.cliniko.com/pricing/","text":"Cliniko, CharmHealth and eClinicalWorks illustrate different practitioner, encounter and software/service pricing bases. Compare workflow coverage before transferring a price metric.","title":"Vendor reference"},{"href":"https://www.charmhealth.com/ehr/ehr-pricing-us.html","text":"Review the original scope and confirm current terms directly.","title":"Additional reference"}],"title":"Primary-source reference"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"Cliniko, CharmHealth and eClinicalWorks illustrate different practitioner, encounter and software/service pricing bases. Compare workflow coverage before transferring a price metric.","description":"Cliniko, CharmHealth and eClinicalWorks illustrate different practitioner, encounter and software/service pricing bases. Compare workflow coverage before transferring a price metric.","answers":[],"overview":{"title":"Clinic and ambulatory software","summary":"Cliniko, CharmHealth and eClinicalWorks illustrate different practitioner, encounter and software/service pricing bases. Compare workflow coverage before transferring a price metric.","areas":[]}},"ar":{"url":"https://mansoq.com/compare/ambulatory?lang=ar","title":"برمجيات العيادات والرعاية الخارجية","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"توضح كلينيكو وتشارم هيلث وإي كلينيكال ووركس أسساً مختلفة للتسعير بالممارس أو الزيارة أو البرمجيات والخدمات. قارن تغطية المسار قبل نقل مقياس سعر.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"استخدم تكوين رعايتك الفعلي؛ فتسمية المورد لا تثبت تماثل الوظائف.","items":[{"text":"راجع تغطية الأدوار والمهام ومسارات الرعاية أو الخدمة المتكاملة.","title":"الأشخاص ومسار العمل"},{"text":"افصل الوحدات المشمولة والمتطلبات والوصول للأنظمة الخارجية وتنفيذ التكامل.","title":"المنتجات والاتصالات"},{"text":"قارن البرمجيات المتكررة والتنفيذ والخدمات وتراخيص الأطراف الأخرى والتكاليف المتغيرة والضريبة.","title":"الالتزامات التجارية"},{"text":"تحقق من اللغة وإصدارات المعايير والتسجيل وبيانات الاتصال والقبول التشغيلي لنطاقك الدقيق.","title":"الملاءمة السعودية والأدلة"}],"title":"ما الذي تقارنه"},{"kind":"cards","intro":"روجع في 8 أكتوبر 2026. لا يمثل المصدر التسويقي المؤرخ مكوناً تعاقدياً حالياً أو ادعاء بتماثل منسوق.","items":[{"href":"https://www.cliniko.com/pricing/","text":"توضح كلينيكو وتشارم هيلث وإي كلينيكال ووركس أسساً مختلفة للتسعير بالممارس أو الزيارة أو البرمجيات والخدمات. قارن تغطية المسار قبل نقل مقياس سعر.","title":"مرجع المورد"},{"href":"https://www.charmhealth.com/ehr/ehr-pricing-us.html","text":"راجع النطاق الأصلي وأكد الشروط الحالية مباشرة.","title":"مرجع إضافي"}],"title":"مرجع المصدر الأولي"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"توضح كلينيكو وتشارم هيلث وإي كلينيكال ووركس أسساً مختلفة للتسعير بالممارس أو الزيارة أو البرمجيات والخدمات. قارن تغطية المسار قبل نقل مقياس سعر.","description":"توضح كلينيكو وتشارم هيلث وإي كلينيكال ووركس أسساً مختلفة للتسعير بالممارس أو الزيارة أو البرمجيات والخدمات. قارن تغطية المسار قبل نقل مقياس سعر.","answers":[],"overview":{"title":"برمجيات العيادات والرعاية الخارجية","summary":"توضح كلينيكو وتشارم هيلث وإي كلينيكال ووركس أسساً مختلفة للتسعير بالممارس أو الزيارة أو البرمجيات والخدمات. قارن تغطية المسار قبل نقل مقياس سعر.","areas":[]}}},{"slug":"/compare/home-palliative","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare/home-palliative","title":"Home and palliative care software","eyebrow":"Human-centered experiences. Connected across care.","summary":"AlayaCare uses tailored scope and Axxess presents palliative workflows. Compare visit/care-plan depth, country requirements, implementation and verified mobile/offline scope.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Use your actual care composition; a vendor label does not establish identical functionality.","items":[{"text":"Review role/task coverage and complete clinical or service journeys.","title":"People and workflow"},{"text":"Separate included modules, prerequisites, external-system access and integration delivery.","title":"Products and interfaces"},{"text":"Compare recurring software, implementation, services, third-party licensing, variable costs and tax.","title":"Commercial obligations"},{"text":"Verify language, standards versions, credentials/onboarding and operational acceptance for your exact scope.","title":"Saudi fit and evidence"}],"title":"What to compare"},{"kind":"cards","intro":"Reviewed 8 October 2026. A dated marketing source is not a current contractual inclusion or a MANSOQ equivalence claim.","items":[{"href":"https://alayacare.com/pricing/","text":"AlayaCare uses tailored scope and Axxess presents palliative workflows. Compare visit/care-plan depth, country requirements, implementation and verified mobile/offline scope.","title":"Vendor reference"},{"href":"https://www.axxess.com/palliative-care-software/","text":"Review the original scope and confirm current terms directly.","title":"Additional reference"}],"title":"Primary-source reference"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"AlayaCare uses tailored scope and Axxess presents palliative workflows. Compare visit/care-plan depth, country requirements, implementation and verified mobile/offline scope.","description":"AlayaCare uses tailored scope and Axxess presents palliative workflows. Compare visit/care-plan depth, country requirements, implementation and verified mobile/offline scope.","answers":[],"overview":{"title":"Home and palliative care software","summary":"AlayaCare uses tailored scope and Axxess presents palliative workflows. Compare visit/care-plan depth, country requirements, implementation and verified mobile/offline scope.","areas":[]}},"ar":{"url":"https://mansoq.com/compare/home-palliative?lang=ar","title":"برمجيات الرعاية المنزلية والتلطيفية","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تستخدم ألايا كير نطاقاً مخصصاً، ويعرض أكسس مسارات الرعاية التلطيفية. قارن عمق الزيارات وخطط الرعاية والمتطلبات المحلية والتنفيذ ونطاق الجوال والعمل دون اتصال المتحقق منه.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"استخدم تكوين رعايتك الفعلي؛ فتسمية المورد لا تثبت تماثل الوظائف.","items":[{"text":"راجع تغطية الأدوار والمهام ومسارات الرعاية أو الخدمة المتكاملة.","title":"الأشخاص ومسار العمل"},{"text":"افصل الوحدات المشمولة والمتطلبات والوصول للأنظمة الخارجية وتنفيذ التكامل.","title":"المنتجات والاتصالات"},{"text":"قارن البرمجيات المتكررة والتنفيذ والخدمات وتراخيص الأطراف الأخرى والتكاليف المتغيرة والضريبة.","title":"الالتزامات التجارية"},{"text":"تحقق من اللغة وإصدارات المعايير والتسجيل وبيانات الاتصال والقبول التشغيلي لنطاقك الدقيق.","title":"الملاءمة السعودية والأدلة"}],"title":"ما الذي تقارنه"},{"kind":"cards","intro":"روجع في 8 أكتوبر 2026. لا يمثل المصدر التسويقي المؤرخ مكوناً تعاقدياً حالياً أو ادعاء بتماثل منسوق.","items":[{"href":"https://alayacare.com/pricing/","text":"تستخدم ألايا كير نطاقاً مخصصاً، ويعرض أكسس مسارات الرعاية التلطيفية. قارن عمق الزيارات وخطط الرعاية والمتطلبات المحلية والتنفيذ ونطاق الجوال والعمل دون اتصال المتحقق منه.","title":"مرجع المورد"},{"href":"https://www.axxess.com/palliative-care-software/","text":"راجع النطاق الأصلي وأكد الشروط الحالية مباشرة.","title":"مرجع إضافي"}],"title":"مرجع المصدر الأولي"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"تستخدم ألايا كير نطاقاً مخصصاً، ويعرض أكسس مسارات الرعاية التلطيفية. قارن عمق الزيارات وخطط الرعاية والمتطلبات المحلية والتنفيذ ونطاق الجوال والعمل دون اتصال المتحقق منه.","description":"تستخدم ألايا كير نطاقاً مخصصاً، ويعرض أكسس مسارات الرعاية التلطيفية. قارن عمق الزيارات وخطط الرعاية والمتطلبات المحلية والتنفيذ ونطاق الجوال والعمل دون اتصال المتحقق منه.","answers":[],"overview":{"title":"برمجيات الرعاية المنزلية والتلطيفية","summary":"تستخدم ألايا كير نطاقاً مخصصاً، ويعرض أكسس مسارات الرعاية التلطيفية. قارن عمق الزيارات وخطط الرعاية والمتطلبات المحلية والتنفيذ ونطاق الجوال والعمل دون اتصال المتحقق منه.","areas":[]}}},{"slug":"/compare/remote-critical-care","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare/remote-critical-care","title":"Remote critical-care delivery","eyebrow":"Human-centered experiences. Connected across care.","summary":"Hicuity Health combines people, processes and technology; Philips describes bedside and remote connectivity. Software, equipment, interfaces and staffed care are distinct obligations.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Use your actual care composition; a vendor label does not establish identical functionality.","items":[{"text":"Review role/task coverage and complete clinical or service journeys.","title":"People and workflow"},{"text":"Separate included modules, prerequisites, external-system access and integration delivery.","title":"Products and interfaces"},{"text":"Compare recurring software, implementation, services, third-party licensing, variable costs and tax.","title":"Commercial obligations"},{"text":"Verify language, standards versions, credentials/onboarding and operational acceptance for your exact scope.","title":"Saudi fit and evidence"}],"title":"What to compare"},{"kind":"cards","intro":"Reviewed 8 October 2026. A dated marketing source is not a current contractual inclusion or a MANSOQ equivalence claim.","items":[{"href":"https://hicuityhealth.com/teleicu/","text":"Hicuity Health combines people, processes and technology; Philips describes bedside and remote connectivity. Software, equipment, interfaces and staffed care are distinct obligations.","title":"Vendor reference"},{"href":"https://www.usa.philips.com/healthcare/article/what-is-tele-icu-telehealth-critical-care","text":"Review the original scope and confirm current terms directly.","title":"Additional reference"}],"title":"Primary-source reference"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"Hicuity Health combines people, processes and technology; Philips describes bedside and remote connectivity. Software, equipment, interfaces and staffed care are distinct obligations.","description":"Hicuity Health combines people, processes and technology; Philips describes bedside and remote connectivity. Software, equipment, interfaces and staffed care are distinct obligations.","answers":[],"overview":{"title":"Remote critical-care delivery","summary":"Hicuity Health combines people, processes and technology; Philips describes bedside and remote connectivity. Software, equipment, interfaces and staffed care are distinct obligations.","areas":[]}},"ar":{"url":"https://mansoq.com/compare/remote-critical-care?lang=ar","title":"تنفيذ العناية الحرجة عن بُعد","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تجمع هيكيوتي هيلث الأفراد والعمليات والتقنية، وتصف فيليبس الاتصال المحلي وعن بُعد. البرمجيات والمعدات والاتصالات والرعاية البشرية التزامات مستقلة.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"استخدم تكوين رعايتك الفعلي؛ فتسمية المورد لا تثبت تماثل الوظائف.","items":[{"text":"راجع تغطية الأدوار والمهام ومسارات الرعاية أو الخدمة المتكاملة.","title":"الأشخاص ومسار العمل"},{"text":"افصل الوحدات المشمولة والمتطلبات والوصول للأنظمة الخارجية وتنفيذ التكامل.","title":"المنتجات والاتصالات"},{"text":"قارن البرمجيات المتكررة والتنفيذ والخدمات وتراخيص الأطراف الأخرى والتكاليف المتغيرة والضريبة.","title":"الالتزامات التجارية"},{"text":"تحقق من اللغة وإصدارات المعايير والتسجيل وبيانات الاتصال والقبول التشغيلي لنطاقك الدقيق.","title":"الملاءمة السعودية والأدلة"}],"title":"ما الذي تقارنه"},{"kind":"cards","intro":"روجع في 8 أكتوبر 2026. لا يمثل المصدر التسويقي المؤرخ مكوناً تعاقدياً حالياً أو ادعاء بتماثل منسوق.","items":[{"href":"https://hicuityhealth.com/teleicu/","text":"تجمع هيكيوتي هيلث الأفراد والعمليات والتقنية، وتصف فيليبس الاتصال المحلي وعن بُعد. البرمجيات والمعدات والاتصالات والرعاية البشرية التزامات مستقلة.","title":"مرجع المورد"},{"href":"https://www.usa.philips.com/healthcare/article/what-is-tele-icu-telehealth-critical-care","text":"راجع النطاق الأصلي وأكد الشروط الحالية مباشرة.","title":"مرجع إضافي"}],"title":"مرجع المصدر الأولي"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"تجمع هيكيوتي هيلث الأفراد والعمليات والتقنية، وتصف فيليبس الاتصال المحلي وعن بُعد. البرمجيات والمعدات والاتصالات والرعاية البشرية التزامات مستقلة.","description":"تجمع هيكيوتي هيلث الأفراد والعمليات والتقنية، وتصف فيليبس الاتصال المحلي وعن بُعد. البرمجيات والمعدات والاتصالات والرعاية البشرية التزامات مستقلة.","answers":[],"overview":{"title":"تنفيذ العناية الحرجة عن بُعد","summary":"تجمع هيكيوتي هيلث الأفراد والعمليات والتقنية، وتصف فيليبس الاتصال المحلي وعن بُعد. البرمجيات والمعدات والاتصالات والرعاية البشرية التزامات مستقلة.","areas":[]}}},{"slug":"/compare/saudi-rcm","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare/saudi-rcm","title":"Saudi HIMS and revenue approaches","eyebrow":"Human-centered experiences. Connected across care.","summary":"Saudi offers from Andro and Waseel illustrate complete products and transaction-scoped revenue services. Review period, tax, activation, inclusions and actual workflow depth.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Use your actual care composition; a vendor label does not establish identical functionality.","items":[{"text":"Review role/task coverage and complete clinical or service journeys.","title":"People and workflow"},{"text":"Separate included modules, prerequisites, external-system access and integration delivery.","title":"Products and interfaces"},{"text":"Compare recurring software, implementation, services, third-party licensing, variable costs and tax.","title":"Commercial obligations"},{"text":"Verify language, standards versions, credentials/onboarding and operational acceptance for your exact scope.","title":"Saudi fit and evidence"}],"title":"What to compare"},{"kind":"cards","intro":"Reviewed 8 October 2026. A dated marketing source is not a current contractual inclusion or a MANSOQ equivalence claim.","items":[{"href":"https://ahhis.com/en/pricing","text":"Saudi offers from Andro and Waseel illustrate complete products and transaction-scoped revenue services. Review period, tax, activation, inclusions and actual workflow depth.","title":"Vendor reference"},{"href":"https://waseel.com/wrcm/","text":"Review the original scope and confirm current terms directly.","title":"Additional reference"}],"title":"Primary-source reference"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"Saudi offers from Andro and Waseel illustrate complete products and transaction-scoped revenue services. Review period, tax, activation, inclusions and actual workflow depth.","description":"Saudi offers from Andro and Waseel illustrate complete products and transaction-scoped revenue services. Review period, tax, activation, inclusions and actual workflow depth.","answers":[],"overview":{"title":"Saudi HIMS and revenue approaches","summary":"Saudi offers from Andro and Waseel illustrate complete products and transaction-scoped revenue services. Review period, tax, activation, inclusions and actual workflow depth.","areas":[]}},"ar":{"url":"https://mansoq.com/compare/saudi-rcm?lang=ar","title":"أساليب إدارة المستشفيات والإيرادات السعودية","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"توضح عروض أندرو ووصيل السعودية منتجات متكاملة وخدمات إيرادات محددة بالمعاملات. راجع الفترة والضريبة والتفعيل والمكونات وعمق المسار الفعلي.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"استخدم تكوين رعايتك الفعلي؛ فتسمية المورد لا تثبت تماثل الوظائف.","items":[{"text":"راجع تغطية الأدوار والمهام ومسارات الرعاية أو الخدمة المتكاملة.","title":"الأشخاص ومسار العمل"},{"text":"افصل الوحدات المشمولة والمتطلبات والوصول للأنظمة الخارجية وتنفيذ التكامل.","title":"المنتجات والاتصالات"},{"text":"قارن البرمجيات المتكررة والتنفيذ والخدمات وتراخيص الأطراف الأخرى والتكاليف المتغيرة والضريبة.","title":"الالتزامات التجارية"},{"text":"تحقق من اللغة وإصدارات المعايير والتسجيل وبيانات الاتصال والقبول التشغيلي لنطاقك الدقيق.","title":"الملاءمة السعودية والأدلة"}],"title":"ما الذي تقارنه"},{"kind":"cards","intro":"روجع في 8 أكتوبر 2026. لا يمثل المصدر التسويقي المؤرخ مكوناً تعاقدياً حالياً أو ادعاء بتماثل منسوق.","items":[{"href":"https://ahhis.com/en/pricing","text":"توضح عروض أندرو ووصيل السعودية منتجات متكاملة وخدمات إيرادات محددة بالمعاملات. راجع الفترة والضريبة والتفعيل والمكونات وعمق المسار الفعلي.","title":"مرجع المورد"},{"href":"https://waseel.com/wrcm/","text":"راجع النطاق الأصلي وأكد الشروط الحالية مباشرة.","title":"مرجع إضافي"}],"title":"مرجع المصدر الأولي"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"توضح عروض أندرو ووصيل السعودية منتجات متكاملة وخدمات إيرادات محددة بالمعاملات. راجع الفترة والضريبة والتفعيل والمكونات وعمق المسار الفعلي.","description":"توضح عروض أندرو ووصيل السعودية منتجات متكاملة وخدمات إيرادات محددة بالمعاملات. راجع الفترة والضريبة والتفعيل والمكونات وعمق المسار الفعلي.","answers":[],"overview":{"title":"أساليب إدارة المستشفيات والإيرادات السعودية","summary":"توضح عروض أندرو ووصيل السعودية منتجات متكاملة وخدمات إيرادات محددة بالمعاملات. راجع الفترة والضريبة والتفعيل والمكونات وعمق المسار الفعلي.","areas":[]}}},{"slug":"/compare/unified-his","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/compare/unified-his","title":"Unified healthcare platforms","eyebrow":"Human-centered experiences. Connected across care.","summary":"TrakCare organizes shared foundations and modular care/department extensions. MEDITECH MaaS presents a complete subscription delivery scope. Compare exact inclusions, interfaces and local readiness.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"Use your actual care composition; a vendor label does not establish identical functionality.","items":[{"text":"Review role/task coverage and complete clinical or service journeys.","title":"People and workflow"},{"text":"Separate included modules, prerequisites, external-system access and integration delivery.","title":"Products and interfaces"},{"text":"Compare recurring software, implementation, services, third-party licensing, variable costs and tax.","title":"Commercial obligations"},{"text":"Verify language, standards versions, credentials/onboarding and operational acceptance for your exact scope.","title":"Saudi fit and evidence"}],"title":"What to compare"},{"kind":"cards","intro":"Reviewed 8 October 2026. A dated marketing source is not a current contractual inclusion or a MANSOQ equivalence claim.","items":[{"href":"https://www.intersystems.com/products/trakcare/departments-documentation-extensions/","text":"TrakCare organizes shared foundations and modular care/department extensions. MEDITECH MaaS presents a complete subscription delivery scope. Compare exact inclusions, interfaces and local readiness.","title":"Vendor reference"},{"href":"https://ehr.meditech.com/ehr-solutions/meditech-as-a-service-maas","text":"Review the original scope and confirm current terms directly.","title":"Additional reference"}],"title":"Primary-source reference"},{"kind":"cards","intro":"Start with people and their work. Agree the product scope and delivery together.","items":[{"href":"/pricing/custom","text":"Use a care-setting recommendation, then refine the actual departments and extensions.","title":"Explore a complete workflow"},{"href":"/demo","text":"See the care context, handovers and responsibilities relevant to your organization.","title":"Walk through your scenario"},{"href":"/resources/implementation","text":"Define migration, interfaces, training and agreed acceptance before activation.","title":"Plan implementation"}],"title":"A clear way forward"}],"seoDescription":"TrakCare organizes shared foundations and modular care/department extensions. MEDITECH MaaS presents a complete subscription delivery scope. Compare exact inclusions, interfaces and local readiness.","description":"TrakCare organizes shared foundations and modular care/department extensions. MEDITECH MaaS presents a complete subscription delivery scope. Compare exact inclusions, interfaces and local readiness.","answers":[],"overview":{"title":"Unified healthcare platforms","summary":"TrakCare organizes shared foundations and modular care/department extensions. MEDITECH MaaS presents a complete subscription delivery scope. Compare exact inclusions, interfaces and local readiness.","areas":[]}},"ar":{"url":"https://mansoq.com/compare/unified-his?lang=ar","title":"منصات الرعاية الصحية الموحدة","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"ينظم تراك كير أساساً مشتركاً وإضافات معيارية للرعاية والأقسام، ويقدم MEDITECH MaaS نطاق تنفيذ اشتراك متكاملاً. قارن المكونات الدقيقة والاتصالات والجاهزية المحلية.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"استخدم تكوين رعايتك الفعلي؛ فتسمية المورد لا تثبت تماثل الوظائف.","items":[{"text":"راجع تغطية الأدوار والمهام ومسارات الرعاية أو الخدمة المتكاملة.","title":"الأشخاص ومسار العمل"},{"text":"افصل الوحدات المشمولة والمتطلبات والوصول للأنظمة الخارجية وتنفيذ التكامل.","title":"المنتجات والاتصالات"},{"text":"قارن البرمجيات المتكررة والتنفيذ والخدمات وتراخيص الأطراف الأخرى والتكاليف المتغيرة والضريبة.","title":"الالتزامات التجارية"},{"text":"تحقق من اللغة وإصدارات المعايير والتسجيل وبيانات الاتصال والقبول التشغيلي لنطاقك الدقيق.","title":"الملاءمة السعودية والأدلة"}],"title":"ما الذي تقارنه"},{"kind":"cards","intro":"روجع في 8 أكتوبر 2026. لا يمثل المصدر التسويقي المؤرخ مكوناً تعاقدياً حالياً أو ادعاء بتماثل منسوق.","items":[{"href":"https://www.intersystems.com/products/trakcare/departments-documentation-extensions/","text":"ينظم تراك كير أساساً مشتركاً وإضافات معيارية للرعاية والأقسام، ويقدم MEDITECH MaaS نطاق تنفيذ اشتراك متكاملاً. قارن المكونات الدقيقة والاتصالات والجاهزية المحلية.","title":"مرجع المورد"},{"href":"https://ehr.meditech.com/ehr-solutions/meditech-as-a-service-maas","text":"راجع النطاق الأصلي وأكد الشروط الحالية مباشرة.","title":"مرجع إضافي"}],"title":"مرجع المصدر الأولي"},{"kind":"cards","intro":"ابدأ بالأشخاص وعملهم. اتفق على نطاق المنتجات والتنفيذ معاً.","items":[{"href":"/pricing/custom","text":"استخدم توصية لبيئة الرعاية ثم حدد الأقسام والإضافات الفعلية.","title":"استكشف مساراً متكاملاً"},{"href":"/demo","text":"اطلع على سياق الرعاية والتسليم والمسؤوليات ذات الصلة بمنشأتك.","title":"راجع سيناريو فريقك"},{"href":"/resources/implementation","text":"حدد الترحيل والاتصالات والتدريب والاعتماد المتفق عليه قبل التفعيل.","title":"خطط للتنفيذ"}],"title":"مسار واضح للخطوة التالية"}],"seoDescription":"ينظم تراك كير أساساً مشتركاً وإضافات معيارية للرعاية والأقسام، ويقدم MEDITECH MaaS نطاق تنفيذ اشتراك متكاملاً. قارن المكونات الدقيقة والاتصالات والجاهزية المحلية.","description":"ينظم تراك كير أساساً مشتركاً وإضافات معيارية للرعاية والأقسام، ويقدم MEDITECH MaaS نطاق تنفيذ اشتراك متكاملاً. قارن المكونات الدقيقة والاتصالات والجاهزية المحلية.","answers":[],"overview":{"title":"منصات الرعاية الصحية الموحدة","summary":"ينظم تراك كير أساساً مشتركاً وإضافات معيارية للرعاية والأقسام، ويقدم MEDITECH MaaS نطاق تنفيذ اشتراك متكاملاً. قارن المكونات الدقيقة والاتصالات والجاهزية المحلية.","areas":[]}}},{"slug":"/contact","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/contact","title":"Request a healthcare software consultation | MANSOQ","eyebrow":"Talk to MANSOQ","summary":"Tell us what your team needs. Your enquiry goes directly to the MANSOQ relationship workspace for follow-up.","sections":[],"seoTitle":"Contact MANSOQ | Healthcare Software & Services","seoDescription":"Tell us what your team needs. Your enquiry goes directly to the MANSOQ relationship workspace for follow-up.","description":"Request a MANSOQ consultation, product demonstration, proposal or support. Choose the healthcare product and scenario your team needs.","answers":[]},"ar":{"url":"https://mansoq.com/contact?lang=ar","title":"طلب استشارة لأنظمة الرعاية | منسوق","eyebrow":"تواصل مع منسوق","summary":"أخبرنا باحتياجات فريقك. يصل استفسارك مباشرة إلى مساحة إدارة العلاقات في منسوق للمتابعة.","sections":[],"seoTitle":"تواصل مع منسوق | برمجيات الرعاية الصحية والخدمات","seoDescription":"أخبرنا باحتياجات فريقك. يصل استفسارك مباشرة إلى مساحة إدارة العلاقات في منسوق للمتابعة.","description":"اطلب استشارة منسوق أو عرضاً توضيحياً أو عرضاً مالياً أو دعماً، واختر منتج الرعاية والسيناريو المناسب لفريقك.","answers":[]}},{"slug":"/demo","lastModified":"2026-10-11T04:29:37.967Z","en":{"url":"https://mansoq.com/demo","title":"See MANSOQ with your team.","eyebrow":"Human-centered experiences. Connected across care.","summary":"Walk through the people, workflows and products relevant to your organization. Tell us your care setting and the scenario you want to explore.","ctaLabel":"Explore your scope","sections":[{"kind":"cards","intro":"A guided walkthrough of the workflows that matter to your organization, shown with synthetic data rather than real patient records.","items":[{"href":"/solutions","text":"The journey for your clinic, polyclinic, hospital, medical city, TeleICU or home-care team, from registration to follow-up.","title":"Your care setting"},{"href":"/platform/revenue-cycle","text":"How care activity becomes eligibility checks, claims, denial follow-up and reconciliation, with NPHIES and ZATCA scope explained.","title":"Revenue cycle"},{"href":"/resources/implementation","text":"Required components, interfaces, migration and the implementation approach.","title":"Scope and delivery"}],"title":"What a demonstration covers."},{"kind":"steps","intro":"Use the form below. The demonstration itself does not activate a service or create a contract.","items":[{"text":"Name the scenario you want to see, the roles who will attend and any existing systems we should discuss.","title":"Prepare"},{"text":"We reply to confirm availability, timing and attendees. The length depends on the scope you want to cover.","title":"Confirm the session"},{"href":"/pricing","text":"Refine your configuration, request an itemised proposal or discuss a separately accepted evaluation using synthetic data.","title":"Decide the next step"}],"title":"Prepare, confirm and follow up."}],"seoDescription":"Walk through the people, workflows and products relevant to your organization. Tell us your care setting and the scenario you want to explore.","description":"Walk through the people, workflows and products relevant to your organization. Tell us your care setting and the scenario you want to explore.","answers":[]},"ar":{"url":"https://mansoq.com/demo?lang=ar","title":"اطلع على منسوق مع فريقك.","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"راجع الأشخاص ومسارات العمل والمنتجات المناسبة لمنشأتك. أخبرنا ببيئة الرعاية والسيناريو الذي تريد استكشافه.","ctaLabel":"استكشف نطاقك","sections":[{"kind":"cards","intro":"جولة موجهة في مسارات العمل المهمة لمنشأتك، تُعرض ببيانات اصطناعية لا بسجلات مرضى حقيقية.","items":[{"href":"/solutions","text":"رحلة الرعاية في عيادتك أو مجمعك الطبي أو مستشفاك أو مدينتك الطبية أو فريق العناية عن بُعد أو الرعاية المنزلية، من التسجيل إلى المتابعة.","title":"بيئة رعايتك"},{"href":"/platform/revenue-cycle","text":"كيف يتحول نشاط الرعاية إلى تحقق من الأهلية ومطالبات ومتابعة للرفض ومطابقة، مع توضيح نطاق نفيس وزاتكا.","title":"دورة الإيرادات"},{"href":"/resources/implementation","text":"المكونات المطلوبة والاتصالات والترحيل وأسلوب التنفيذ.","title":"النطاق والتنفيذ"}],"title":"ما يشمله العرض التوضيحي."},{"kind":"steps","intro":"استخدم النموذج أدناه. ولا يؤدي العرض التوضيحي بحد ذاته إلى تفعيل خدمة أو إنشاء عقد.","items":[{"text":"حدد السيناريو الذي تريد رؤيته والأدوار التي ستحضر وأي أنظمة حالية ينبغي مناقشتها.","title":"استعد"},{"text":"نرد عليك لتأكيد التوفر والتوقيت والحضور. وتعتمد مدة الجلسة على النطاق الذي تريد تغطيته.","title":"أكّد موعد الجلسة"},{"href":"/pricing","text":"حسّن تكوينك أو اطلب عرضاً مفصلاً أو ناقش تقييماً مقبولاً بشكل مستقل باستخدام بيانات اصطناعية.","title":"حدد الخطوة التالية"}],"title":"استعد وأكّد وتابع."}],"seoDescription":"راجع الأشخاص ومسارات العمل والمنتجات المناسبة لمنشأتك. أخبرنا ببيئة الرعاية والسيناريو الذي تريد استكشافه.","description":"راجع الأشخاص ومسارات العمل والمنتجات المناسبة لمنشأتك. أخبرنا ببيئة الرعاية والسيناريو الذي تريد استكشافه.","answers":[]}},{"slug":"/developers","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/developers","title":"Healthcare APIs & Developer Resources | MANSOQ","eyebrow":"MANSOQ Platform","summary":"Discuss component boundaries, FHIR resources and deployment requirements with the MANSOQ team.","sections":[{"kind":"cards","intro":"","items":[{"text":"The clinical core uses FHIR-aligned resources and APIs. National exchanges use their own governed profiles.","title":"Clinical interoperability"},{"href":"/integrations/nphies","text":"NPHIES adapters prepare and validate exchange payloads. Production access depends on credentials, testing and regulator approval.","title":"Saudi revenue exchange"},{"text":"Terminology releases, file hashes and licence references are recorded. Licensed coding data is supplied through authorized sources.","title":"Terminology ownership"},{"text":"Clinical, web, remote care, revenue and intelligence components retain clear runtime and release boundaries.","title":"Modular deployment"}],"title":"Open interfaces. Explicit boundaries."},{"kind":"cards","intro":"","items":[{"href":"/contact?interest=Partnership","text":"Request architecture, integration guidance and component-level licence information from the MANSOQ team.","title":"Technical documentation"},{"href":"/contact","text":"Describe your systems, data boundaries and workflow needs before building an adapter.","title":"Integration planning"}],"title":"Start with the source."}],"seoTitle":"Healthcare APIs & Developer Resources | MANSOQ","seoDescription":"Discuss component boundaries, FHIR resources and deployment requirements with the MANSOQ team.","description":"Discuss component boundaries, FHIR resources and deployment requirements with the MANSOQ team.","answers":[]},"ar":{"url":"https://mansoq.com/developers?lang=ar","title":"واجهات الرعاية الصحية وموارد المطورين | منسوق","eyebrow":"منصة منسوق","summary":"ناقش حدود المكونات وموارد FHIR ومتطلبات النشر مع فريق منسوق.","sections":[{"kind":"cards","intro":"","items":[{"text":"يستخدم الأساس السريري موارد وواجهات متوافقة مع FHIR. وتستخدم التبادلات الوطنية ملفاتها المحكومة.","title":"التشغيل البيني السريري"},{"href":"/integrations/nphies","text":"تجهز موائمات نفيس بيانات التبادل وتتحقق منها. ويتطلب الاستخدام الفعلي بيانات اعتماد واختبارات وموافقة الجهة المنظمة.","title":"تبادل الإيراد السعودي"},{"text":"تسجل إصدارات المصطلحات وبصمات الملفات ومراجع التراخيص. وتُحمّل بيانات الترميز المرخصة من مصادر مخولة.","title":"حوكمة المصطلحات"},{"text":"تحتفظ المكونات السريرية والواجهات والرعاية عن بعد والإيراد والذكاء بحدود تشغيل وإصدار واضحة.","title":"نشر معياري"}],"title":"واجهات مفتوحة وحدود واضحة."},{"kind":"cards","intro":"","items":[{"href":"/contact?interest=Partnership","text":"اطلب المعمارية وإرشادات التكامل ومعلومات تراخيص المكونات من فريق منسوق.","title":"الوثائق التقنية"},{"href":"/contact","text":"صف أنظمتك وحدود البيانات واحتياجات سير العمل قبل بناء موائم.","title":"تخطيط التكامل"}],"title":"ابدأ بالمصدر."}],"seoTitle":"واجهات الرعاية الصحية وموارد المطورين | منسوق","seoDescription":"ناقش حدود المكونات وموارد FHIR ومتطلبات النشر مع فريق منسوق.","description":"ناقش حدود المكونات وموارد FHIR ومتطلبات النشر مع فريق منسوق.","answers":[]}},{"slug":"/integrations/nphies","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/integrations/nphies","title":"NPHIES software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly.","description":"Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly. Supported eligibility, authorization and…","answers":[{"question":"What does MANSOQ NPHIES cover?","answer":"Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly. Prepare provider identity: Confirm provider and payer identifiers, the supported exchange package and the responsible organization. Record onboarding evidence and agreed sandbox and production endpoints before connection testing. Check eligibility & authorization: Prepare member, policy and service context for supported eligibility and authorization exchanges. Validate the request and preserve payer responses, validity and unresolved coverage information. Exchange claims: Assemble supported claims and attachments, apply package validation and keep message and claim identities traceable. Transmission is permitted only after the production activation gates and required evidence are accepted. Follow responses & reconcile: Track supported responses, polling and payment advice. Distinguish platform errors from payer decisions and reconcile returned business references under the accepted retry and correction rules.","href":"/integrations/nphies#module-workflow"},{"question":"What setup data does NPHIES need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include nphies configurations (rcm_nphies_configurations.csv); production endpoints (rcm_production_endpoints.csv); production routing rules (rcm_production_routing_rules.csv); Interface specification (interfaces.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/integrations/nphies#module-setup"},{"question":"How does NPHIES handle exceptions?","answer":"Transport failure Retain the original exchange identity and payload; use the accepted retry rules and verify whether the target received the transaction. Unsupported package or incomplete onboarding Keep production submission disabled, resolve the package and provider evidence and repeat the affected acceptance tests.","href":"/integrations/nphies#module-exceptions"},{"question":"How does NPHIES connect with other systems?","answer":"NPHIES capability is subject to package support, onboarding, credentials and certification evidence. Built exchange code and sample reference data do not establish certified production readiness.","href":"/integrations/nphies#module-connections"}],"module":{"name":"NPHIES","functions":["Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly."],"workflow":[{"title":"Prepare provider identity","action":"Confirm provider and payer identifiers, the supported exchange package and the responsible organization. Record onboarding evidence and agreed sandbox and production endpoints before connection testing.","owner":"Provider and integration owner","record":"Provider identity, package version and onboarding evidence"},{"title":"Check eligibility & authorization","action":"Prepare member, policy and service context for supported eligibility and authorization exchanges. Validate the request and preserve payer responses, validity and unresolved coverage information.","owner":"Eligibility and authorization team","record":"Request identity, validation, response and authorization reference"},{"title":"Exchange claims","action":"Assemble supported claims and attachments, apply package validation and keep message and claim identities traceable. Transmission is permitted only after the production activation gates and required evidence are accepted.","owner":"Claims and integration team","record":"Validated bundle, message identity and payer response"},{"title":"Follow responses & reconcile","action":"Track supported responses, polling and payment advice. Distinguish platform errors from payer decisions and reconcile returned business references under the accepted retry and correction rules.","owner":"Revenue operations and finance","record":"Response status, error classification and payment references"}],"exceptions":[{"situation":"Transport failure","response":"Retain the original exchange identity and payload; use the accepted retry rules and verify whether the target received the transaction."},{"situation":"Unsupported package or incomplete onboarding","response":"Keep production submission disabled, resolve the package and provider evidence and repeat the affected acceptance tests."}],"connection":"NPHIES capability is subject to package support, onboarding, credentials and certification evidence. Built exchange code and sample reference data do not establish certified production readiness.","scenarios":[{"title":"Accepted eligibility-to-claim pathway","situation":"A provider uses a specifically accepted NPHIES package for supported insurance transactions.","preparation":"Provider identity, payer route, package, evidence, approved credentials and production activation.","steps":["Complete supported eligibility and required authorization exchange with traceable identities.","Prepare performed and coded activity with the required references and attachments.","Run package validation and check activation gates before claim transmission.","Follow supported payer responses and reconcile returned advice with revenue operations."],"acceptance":"The exact package, provider, request identities and response references are recorded for review."},{"title":"Sandbox passes, but production evidence is incomplete","situation":"A sandbox transaction succeeds while required provider onboarding or package evidence remains unresolved.","preparation":"Outstanding evidence register, activation owner, sandbox results and supported-package inventory.","steps":["Retain successful sandbox evidence with the tested package and provider context.","Identify the missing production facts and assign their responsible owners.","Keep live transmission disabled until the required gates are accepted.","Repeat affected tests and record explicit production acceptance before enabling the route."],"acceptance":"Sandbox success is not mistaken for certified production readiness."}],"setupFiles":[{"template":"/implementation/templates/rcm_nphies_configurations.csv","example":"/implementation/examples/rcm_nphies_configurations.csv"},{"template":"/implementation/templates/rcm_production_endpoints.csv","example":"/implementation/examples/rcm_production_endpoints.csv"},{"template":"/implementation/templates/rcm_production_routing_rules.csv","example":"/implementation/examples/rcm_production_routing_rules.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/integrations/nphies?lang=ar","title":"نفيس | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل.","description":"تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل. تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل…","answers":[{"question":"ما نطاق نفيس في منسوق؟","answer":"تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل. تحضير هوية المزود: أكد معرّفات المزود والدافع وحزمة التبادل المدعومة والجهة المسؤولة. سجّل أدلة التسجيل ووجهات الاختبار والإنتاج قبل الاختبار. فحص الأهلية والموافقة: جهز العضو والوثيقة والخدمة لتبادل الأهلية والموافقة المدعوم. تحقق من الطلب واحفظ ردود الدافع والصلاحية والمعلومات غير المحسومة. تبادل المطالبات: اجمع المطالبات والمرفقات المدعومة وطبّق تحقق الحزمة وتتبع معرّفات الرسالة والمطالبة. يسمح بالإرسال بعد اعتماد شروط الإنتاج والأدلة المطلوبة. متابعة الردود والمطابقة: تابع الردود والاستعلامات وإشعارات السداد المدعومة. ميّز أخطاء المنصة من قرارات الدافع وطابق المراجع وفق قواعد الإعادة والتصحيح المعتمدة.","href":"/integrations/nphies#module-workflow"},{"question":"ما بيانات إعداد نفيس؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة دورة الإيرادات · إعدادات NPHIES (rcm_nphies_configurations.csv)؛ تهيئة دورة الإيرادات · نقاط الاتصال الإنتاجية (rcm_production_endpoints.csv)؛ تهيئة دورة الإيرادات · قواعد التوجيه الإنتاجي (rcm_production_routing_rules.csv)؛ مواصفات الربط (interfaces.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/integrations/nphies#module-setup"},{"question":"كيف يتعامل نفيس مع الاستثناءات؟","answer":"فشل النقل احتفظ بهوية التبادل والبيانات الأصلية واستخدم قواعد الإعادة المعتمدة وتحقق من استلام العملية. حزمة غير مدعومة أو تسجيل غير مكتمل أبقِ إرسال الإنتاج معطلاً وأكمل الحزمة والأدلة وأعد اختبارات القبول المتأثرة.","href":"/integrations/nphies#module-exceptions"},{"question":"كيف يتصل نفيس بالأنظمة الأخرى؟","answer":"تخضع قدرة نفيس لدعم الحزمة والتسجيل وبيانات الاتصال وأدلة الاعتماد. لا يثبت الكود أو البيانات المرجعية جاهزية إنتاج معتمدة.","href":"/integrations/nphies#module-connections"}],"module":{"name":"نفيس","functions":["تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل."],"workflow":[{"title":"تحضير هوية المزود","action":"أكد معرّفات المزود والدافع وحزمة التبادل المدعومة والجهة المسؤولة. سجّل أدلة التسجيل ووجهات الاختبار والإنتاج قبل الاختبار.","owner":"المزود ومسؤول الربط","record":"هوية المزود وإصدار الحزمة وأدلة التسجيل"},{"title":"فحص الأهلية والموافقة","action":"جهز العضو والوثيقة والخدمة لتبادل الأهلية والموافقة المدعوم. تحقق من الطلب واحفظ ردود الدافع والصلاحية والمعلومات غير المحسومة.","owner":"فريق الأهلية والموافقات","record":"هوية الطلب والتحقق والرد ومرجع الموافقة"},{"title":"تبادل المطالبات","action":"اجمع المطالبات والمرفقات المدعومة وطبّق تحقق الحزمة وتتبع معرّفات الرسالة والمطالبة. يسمح بالإرسال بعد اعتماد شروط الإنتاج والأدلة المطلوبة.","owner":"فريق المطالبات والربط","record":"الحزمة المتحقق منها وهوية الرسالة ورد الدافع"},{"title":"متابعة الردود والمطابقة","action":"تابع الردود والاستعلامات وإشعارات السداد المدعومة. ميّز أخطاء المنصة من قرارات الدافع وطابق المراجع وفق قواعد الإعادة والتصحيح المعتمدة.","owner":"تشغيل الإيرادات والمالية","record":"حالة الرد وتصنيف الخطأ ومراجع السداد"}],"exceptions":[{"situation":"فشل النقل","response":"احتفظ بهوية التبادل والبيانات الأصلية واستخدم قواعد الإعادة المعتمدة وتحقق من استلام العملية."},{"situation":"حزمة غير مدعومة أو تسجيل غير مكتمل","response":"أبقِ إرسال الإنتاج معطلاً وأكمل الحزمة والأدلة وأعد اختبارات القبول المتأثرة."}],"connection":"تخضع قدرة نفيس لدعم الحزمة والتسجيل وبيانات الاتصال وأدلة الاعتماد. لا يثبت الكود أو البيانات المرجعية جاهزية إنتاج معتمدة.","scenarios":[{"title":"مسار معتمد من الأهلية للمطالبة","situation":"يستخدم مزود حزمة نفيس معتمدة لمعاملات التأمين المدعومة.","preparation":"هوية مزود ومسار دافع وحزمة وأدلة وبيانات اتصال وتفعيل إنتاج معتمدة.","steps":["أكمل الأهلية والموافقة المطلوبة بهويات قابلة للتتبع.","جهز النشاط المنفذ والمرمز بالمراجع والمرفقات.","تحقق من الحزمة وشروط التفعيل قبل الإرسال.","تابع ردود الدافع المدعومة وطابق إشعاراته مع الإيرادات."],"acceptance":"تسجل الحزمة والمزود وهويات الطلبات ومراجع الرد للمراجعة."},{"title":"نجاح الاختبار مع نقص أدلة الإنتاج","situation":"تنجح معاملة اختبار مع بقاء أدلة تسجيل أو حزمة غير مكتملة.","preparation":"سجل أدلة معلقة ومسؤول تفعيل ونتائج اختبار وقائمة حزم.","steps":["احفظ نجاح الاختبار بالحزمة وسياق المزود.","حدد الحقائق الناقصة ومسؤوليها.","أبقِ الإرسال الفعلي معطلاً حتى قبول الشروط.","أعد الاختبارات المتأثرة وسجّل قبول الإنتاج قبل التفعيل."],"acceptance":"لا يُخلط نجاح الاختبار بجاهزية إنتاج معتمدة."}],"setupFiles":[{"template":"/implementation/templates/rcm_nphies_configurations.csv","example":"/implementation/examples/rcm_nphies_configurations.csv"},{"template":"/implementation/templates/rcm_production_endpoints.csv","example":"/implementation/examples/rcm_production_endpoints.csv"},{"template":"/implementation/templates/rcm_production_routing_rules.csv","example":"/implementation/examples/rcm_production_routing_rules.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/integrations/zatca","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/integrations/zatca","title":"ZATCA E-invoicing software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated.","description":"Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated. Supported e-invoice integration and onboarding,…","answers":[{"question":"What does MANSOQ ZATCA E-invoicing cover?","answer":"Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated. Define taxpayer & phase: Confirm the legal taxpayer, VAT identifier, applicable invoicing phase and invoice type. Assign the invoicing owner and record the approved tax and document identity rules. Onboard the connection: Prepare the selected invoice unit, endpoint and securely managed credential references. Complete required onboarding and testing evidence; sample credentials or sandbox success do not authorize live submission. Prepare & validate invoice: Link the supported invoice to billing activity, document identity and tax treatment. Verify required invoice data and the selected reporting or clearance route before transmission. Submit & retain evidence: Keep the supported response and trace with the invoice. Follow approved rejection, retry, credit-note and credential-renewal procedures and reconcile submitted documents to the billing ledger.","href":"/integrations/zatca#module-workflow"},{"question":"What setup data does ZATCA E-invoicing need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include zatca onboardings (rcm_zatca_onboardings.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); Interface specification (interfaces.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/integrations/zatca#module-setup"},{"question":"How does ZATCA E-invoicing handle exceptions?","answer":"Invoice rejected or required field missing Retain the response and original document identity, assign correction to the tax owner and use the accepted correction procedure. Credential expired or endpoint unavailable Invoke the accepted continuity and renewal procedure and reconcile pending documents after recovery.","href":"/integrations/zatca#module-exceptions"},{"question":"How does ZATCA E-invoicing connect with other systems?","answer":"E-invoice scope, phase, document types and production onboarding are explicitly agreed. This module description is not a certification or compliance claim.","href":"/integrations/zatca#module-connections"}],"module":{"name":"ZATCA E-invoicing","functions":["Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated."],"workflow":[{"title":"Define taxpayer & phase","action":"Confirm the legal taxpayer, VAT identifier, applicable invoicing phase and invoice type. Assign the invoicing owner and record the approved tax and document identity rules.","owner":"Tax and finance owner","record":"Taxpayer identity, invoice types and applicable phase"},{"title":"Onboard the connection","action":"Prepare the selected invoice unit, endpoint and securely managed credential references. Complete required onboarding and testing evidence; sample credentials or sandbox success do not authorize live submission.","owner":"E-invoicing integration owner","record":"Onboarding evidence, credential reference and endpoint"},{"title":"Prepare & validate invoice","action":"Link the supported invoice to billing activity, document identity and tax treatment. Verify required invoice data and the selected reporting or clearance route before transmission.","owner":"Billing and tax reviewer","record":"Invoice reference, tax data and validation result"},{"title":"Submit & retain evidence","action":"Keep the supported response and trace with the invoice. Follow approved rejection, retry, credit-note and credential-renewal procedures and reconcile submitted documents to the billing ledger.","owner":"Finance and integration operations","record":"Submission response, trace and reconciliation"}],"exceptions":[{"situation":"Invoice rejected or required field missing","response":"Retain the response and original document identity, assign correction to the tax owner and use the accepted correction procedure."},{"situation":"Credential expired or endpoint unavailable","response":"Invoke the accepted continuity and renewal procedure and reconcile pending documents after recovery."}],"connection":"E-invoice scope, phase, document types and production onboarding are explicitly agreed. This module description is not a certification or compliance claim.","scenarios":[{"title":"Supported invoice with retained submission evidence","situation":"An onboarded taxpayer submits a supported invoice through the agreed e-invoicing route.","preparation":"Taxpayer, VAT identity, applicable phase, invoice type, accepted unit and credential references.","steps":["Review billing activity, document identity and applicable tax data.","Validate the invoice against the accepted release and submission scope.","Transmit only through the approved reporting or clearance route.","Retain response and trace and reconcile the document to the billing ledger."],"acceptance":"Invoice, submission response and billing records reconcile under the agreed phase."},{"title":"Rejected invoice during credential renewal","situation":"Submission is interrupted and an invoice needs correction under the accepted document rules.","preparation":"Original invoice and response, renewal owner, continuity procedure and correction authority.","steps":["Retain the rejected response and identify whether data or connectivity caused the problem.","Have the tax owner approve the required correction and document identity treatment.","Renew credentials through the approved secure process and re-test the affected route.","Follow accepted retry or correction rules and reconcile pending documents after recovery."],"acceptance":"The correction and renewal have evidence and no pending document is silently lost or assumed accepted."}],"setupFiles":[{"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/integrations/zatca?lang=ar","title":"الفوترة الإلكترونية مع زاتكا | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية.","description":"تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية. تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة…","answers":[{"question":"ما نطاق الفوترة الإلكترونية مع زاتكا في منسوق؟","answer":"تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية. تعريف المكلف والمرحلة: أكد المكلف القانوني ومعرّف الضريبة ومرحلة الفوترة ونوع الفاتورة. حدد المسؤول وسجّل قواعد الضريبة وهوية المستند المعتمدة. تسجيل الاتصال: جهز وحدة الفوترة والوجهة ومراجع بيانات الاتصال الآمنة. أكمل التسجيل وأدلة الاختبار؛ لا تخوّل البيانات التجريبية أو نجاح الاختبار الإرسال الفعلي. إعداد الفاتورة والتحقق: اربط الفاتورة المدعومة بنشاط الفوترة وهوية المستند والضريبة. تحقق من البيانات المطلوبة ومسار الإبلاغ أو التخليص المختار قبل الإرسال. الإرسال وحفظ الأدلة: احفظ الرد والتتبع مع الفاتورة. اتبع إجراءات الرفض والإعادة والإشعار الدائن وتجديد بيانات الاتصال وطابق المستندات مع دفتر الفوترة.","href":"/integrations/zatca#module-workflow"},{"question":"ما بيانات إعداد الفوترة الإلكترونية مع زاتكا؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة دورة الإيرادات · التسجيل لدى ZATCA (rcm_zatca_onboardings.csv)؛ ضوابط الإيرادات والمطابقة (rcm_financial_controls.csv)؛ مواصفات الربط (interfaces.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/integrations/zatca#module-setup"},{"question":"كيف يتعامل الفوترة الإلكترونية مع زاتكا مع الاستثناءات؟","answer":"فاتورة مرفوضة أو حقل ناقص احفظ الرد وهوية المستند وأحل التصحيح لمسؤول الضريبة واستخدم الإجراء المعتمد. بيانات اتصال منتهية أو وجهة متعطلة فعّل إجراء الاستمرارية والتجديد المعتمد وطابق المستندات المعلقة بعد التعافي.","href":"/integrations/zatca#module-exceptions"},{"question":"كيف يتصل الفوترة الإلكترونية مع زاتكا بالأنظمة الأخرى؟","answer":"يُتفق صراحة على نطاق الفاتورة والمرحلة وأنواع المستندات وتسجيل الإنتاج. لا يُعد وصف الوحدة ادعاء اعتماد أو امتثال.","href":"/integrations/zatca#module-connections"}],"module":{"name":"الفوترة الإلكترونية مع زاتكا","functions":["تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية."],"workflow":[{"title":"تعريف المكلف والمرحلة","action":"أكد المكلف القانوني ومعرّف الضريبة ومرحلة الفوترة ونوع الفاتورة. حدد المسؤول وسجّل قواعد الضريبة وهوية المستند المعتمدة.","owner":"مسؤول الضريبة والمالية","record":"هوية المكلف وأنواع الفواتير والمرحلة"},{"title":"تسجيل الاتصال","action":"جهز وحدة الفوترة والوجهة ومراجع بيانات الاتصال الآمنة. أكمل التسجيل وأدلة الاختبار؛ لا تخوّل البيانات التجريبية أو نجاح الاختبار الإرسال الفعلي.","owner":"مسؤول ربط الفوترة الإلكترونية","record":"أدلة التسجيل ومرجع بيانات الاتصال والوجهة"},{"title":"إعداد الفاتورة والتحقق","action":"اربط الفاتورة المدعومة بنشاط الفوترة وهوية المستند والضريبة. تحقق من البيانات المطلوبة ومسار الإبلاغ أو التخليص المختار قبل الإرسال.","owner":"مراجع الفوترة والضريبة","record":"مرجع الفاتورة والضريبة ونتيجة التحقق"},{"title":"الإرسال وحفظ الأدلة","action":"احفظ الرد والتتبع مع الفاتورة. اتبع إجراءات الرفض والإعادة والإشعار الدائن وتجديد بيانات الاتصال وطابق المستندات مع دفتر الفوترة.","owner":"المالية وتشغيل الربط","record":"رد الإرسال والتتبع والمطابقة"}],"exceptions":[{"situation":"فاتورة مرفوضة أو حقل ناقص","response":"احفظ الرد وهوية المستند وأحل التصحيح لمسؤول الضريبة واستخدم الإجراء المعتمد."},{"situation":"بيانات اتصال منتهية أو وجهة متعطلة","response":"فعّل إجراء الاستمرارية والتجديد المعتمد وطابق المستندات المعلقة بعد التعافي."}],"connection":"يُتفق صراحة على نطاق الفاتورة والمرحلة وأنواع المستندات وتسجيل الإنتاج. لا يُعد وصف الوحدة ادعاء اعتماد أو امتثال.","scenarios":[{"title":"فاتورة مدعومة وأدلة إرسال محفوظة","situation":"يرسل مكلف مسجل فاتورة مدعومة عبر المسار المتفق عليه.","preparation":"مكلف ومعرّف ضريبة ومرحلة ونوع فاتورة ووحدة ومراجع اتصال معتمدة.","steps":["راجع النشاط وهوية المستند والضريبة.","تحقق من الفاتورة وفق الإصدار والنطاق المعتمدين.","أرسل عبر الإبلاغ أو التخليص المعتمد فقط.","احفظ الرد والتتبع وطابق المستند بدفتر الفوترة."],"acceptance":"تتطابق الفاتورة ورد الإرسال والفوترة وفق المرحلة المتفق عليها."},{"title":"فاتورة مرفوضة أثناء تجديد الاتصال","situation":"يتعطل الإرسال وتحتاج فاتورة تصحيحاً وفق قواعد المستند المعتمدة.","preparation":"فاتورة ورد أصليان ومسؤول تجديد وإجراء استمرارية وصلاحية تصحيح.","steps":["احفظ الرد وحدد سبب البيانات أو الاتصال.","يعتمد مسؤول الضريبة التصحيح ومعالجة هوية المستند.","جدد الاتصال بالطريقة الآمنة وأعد اختبار المسار.","اتبع قواعد الإعادة أو التصحيح وطابق المستندات بعد التعافي."],"acceptance":"توثق المعالجة والتجديد ولا يفقد مستند معلق أو يفترض قبوله ضمنياً."}],"setupFiles":[{"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/network","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/network","title":"Healthcare Partner Ecosystem | MANSOQ","eyebrow":"MANSOQ Platform","summary":"Clinicians, implementation teams and developers help shape how MANSOQ fits local workflows.","sections":[{"kind":"steps","intro":"","items":[{"text":"Map services, teams, patient journeys, billing responsibilities and the systems you already use.","title":"Understand your facility"},{"text":"Prepare facility structure, staff roles, service catalogues, forms, terminology and approved integrations.","title":"Configure the foundation"},{"text":"Use agreed scenarios to validate clinical, operational and financial handovers before rollout.","title":"Rehearse real workflows"},{"text":"Train teams, begin with a defined scope, review feedback and expand with release and support controls.","title":"Launch in phases"}],"title":"A rollout your people can follow."},{"kind":"cards","intro":"","items":[{"href":"/integrations/nphies","text":"Saudi eligibility, authorization, claim and payment-reconciliation exchange adapters.","title":"NPHIES"},{"href":"/integrations/zatca","text":"Invoice lifecycle and tax controls with an explicit external exchange boundary.","title":"Electronic invoicing"},{"href":"/solutions/teleicu","text":"Critical-care clients, device gateways and remote-care services.","title":"TeleICU and devices"},{"text":"Notifications, messaging components and token-display experiences.","title":"Communication and queues"},{"text":"Connectors, reconciliation services, accounting modules and cash operations.","title":"Accounting and payments"},{"href":"/developers","text":"Documented component boundaries and FHIR implementation resources for integration teams.","title":"APIs and extensions"}],"title":"Capabilities that connect to the core."}],"seoTitle":"Healthcare Partner Ecosystem | MANSOQ","seoDescription":"Clinicians, implementation teams and developers help shape how MANSOQ fits local workflows.","description":"Clinicians, implementation teams and developers help shape how MANSOQ fits local workflows.","answers":[]},"ar":{"url":"https://mansoq.com/network?lang=ar","title":"منظومة شركاء الرعاية الصحية | منسوق","eyebrow":"منصة منسوق","summary":"يساهم الأطباء وفرق التطبيق والمطورون في مواءمة منسوق مع سير العمل المحلي.","sections":[{"kind":"steps","intro":"","items":[{"text":"تحديد الخدمات والفرق ورحلات المرضى ومسؤوليات الفوترة والأنظمة الحالية.","title":"فهم منشأتك"},{"text":"تجهيز هيكل المنشأة وصلاحيات الموظفين ودليل الخدمات والنماذج والمصطلحات والتكاملات المعتمدة.","title":"تهيئة الأساس"},{"text":"استخدام سيناريوهات متفق عليها للتحقق من انتقال العمل السريري والتشغيلي والمالي قبل الإطلاق.","title":"تجربة سير العمل"},{"text":"تدريب الفرق والبدء بنطاق واضح ومراجعة الملاحظات والتوسع مع ضوابط الإصدارات والدعم.","title":"إطلاق مرحلي"}],"title":"إطلاق يستطيع فريقك متابعته."},{"kind":"cards","intro":"","items":[{"href":"/integrations/nphies","text":"موائمات تبادل الأهلية والموافقات والمطالبات ومطابقة المدفوعات السعودية.","title":"نفيس"},{"href":"/integrations/zatca","text":"ضوابط دورة المستندات والضرائب مع حدود واضحة للتبادل الخارجي.","title":"الفوترة الإلكترونية"},{"href":"/solutions/teleicu","text":"واجهات الرعاية الحرجة وبوابات الأجهزة وخدمات الرعاية عن بعد.","title":"العناية المركزة عن بعد والأجهزة"},{"text":"مكونات الإشعارات والمراسلة وتجارب عرض أرقام الانتظار.","title":"التواصل والانتظار"},{"text":"الموصلات وخدمات المطابقة ووحدات المحاسبة والعمليات النقدية.","title":"المحاسبة والمدفوعات"},{"href":"/developers","text":"حدود موثقة للمكونات وموارد تطبيق FHIR لفرق التكامل.","title":"واجهات البرمجة والإضافات"}],"title":"قدرات تتصل بالأساس."}],"seoTitle":"منظومة شركاء الرعاية الصحية | منسوق","seoDescription":"يساهم الأطباء وفرق التطبيق والمطورون في مواءمة منسوق مع سير العمل المحلي.","description":"يساهم الأطباء وفرق التطبيق والمطورون في مواءمة منسوق مع سير العمل المحلي.","answers":[]}},{"slug":"/platform","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform","title":"Healthcare platform, EMR & hospital software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"MANSOQ Core connects identity and record. Care workflows, departments and extensions build the complete scope your teams need.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"MANSOQ Core connects identity and record. Care workflows, departments and extensions build the complete scope your teams need.","description":"Explore MANSOQ Core, EMR, outpatient, inpatient, emergency, specialist departments and RCM. Compare functions, dependencies and operating scope.","answers":[],"overview":{"title":"One foundation. Your whole platform.","summary":"Connect care, departments and revenue around one shared record.","areas":[{"name":"Core","purpose":"Identity, record, access and audit.","functions":[],"details":"/platform/core"},{"name":"Care workflows","purpose":"The workflow for the way you deliver care.","functions":[],"details":"/platform/care-settings"},{"name":"Departments","purpose":"Specialist work connected to the care encounter.","functions":[],"details":"/platform/departments"},{"name":"Extensions","purpose":"Revenue, intelligence and connected systems.","functions":[],"details":"/platform/extensions"}]}},"ar":{"url":"https://mansoq.com/platform?lang=ar","title":"منصة الرعاية ونظام المستشفيات والسجل الطبي | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"يربط منسوق كور الهوية بالسجل. وتبني مسارات الرعاية والأقسام والإضافات النطاق المتكامل الذي تحتاجه فرقك.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"يربط منسوق كور الهوية بالسجل. وتبني مسارات الرعاية والأقسام والإضافات النطاق المتكامل الذي تحتاجه فرقك.","description":"استكشف منسوق كور والسجل الطبي والعيادات والتنويم والطوارئ والأقسام ودورة الإيرادات. راجع الوظائف والمتطلبات والنطاق التشغيلي.","answers":[],"overview":{"title":"أساس واحد. منصتك المتكاملة.","summary":"اربط الرعاية والأقسام والإيرادات حول سجل مشترك واحد.","areas":[{"name":"كور","purpose":"الهوية والسجل والصلاحيات والتدقيق.","functions":[],"details":"/platform/core"},{"name":"مسارات الرعاية","purpose":"مسار العمل المناسب لطريقتك في تقديم الرعاية.","functions":[],"details":"/platform/care-settings"},{"name":"الأقسام","purpose":"عمل تخصصي متصل بزيارة الرعاية.","functions":[],"details":"/platform/departments"},{"name":"الإضافات","purpose":"الإيرادات والتحليلات والأنظمة المترابطة.","functions":[],"details":"/platform/extensions"}]}}},{"slug":"/platform/ai","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/ai","title":"Reviewed AI Assistance software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made.","description":"Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made. Only verified assistive tasks, defined…","answers":[{"question":"What does MANSOQ Reviewed AI Assistance cover?","answer":"Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made. Approve the task: Define the text or image assistance use case, permitted data, model provider and responsible reviewer. Agree consent, data handling, evaluation criteria and a manual fallback before activation. Provide context: Supply only the approved record context and inputs. Configure allowed models and usage limits; confirm image size, input boundaries and access for the selected feature. Generate assistance: Use the configured provider to produce assistance for the approved task. Treat the output as proposed content with possible omissions or errors; the model does not replace professional judgment. Review & retain: Have the responsible professional verify and edit the proposed content before saving or acting on it. Monitor approved evaluation results, access and provider failures under the agreed governance procedure.","href":"/platform/ai#module-workflow"},{"question":"What setup data does Reviewed AI Assistance need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Access & approvals (access_matrix.csv); Interface specification (interfaces.csv); Assumptions & decisions (assumptions_decisions.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/ai#module-setup"},{"question":"How does Reviewed AI Assistance handle exceptions?","answer":"Unsupported or inaccurate suggestion Reject or correct the output, retain the review decision where required and use the normal documentation route. Provider unavailable or limit reached Continue through the approved manual workflow; review provider connectivity and usage limits without bypassing access controls.","href":"/platform/ai#module-exceptions"},{"question":"How does Reviewed AI Assistance connect with other systems?","answer":"The plugin supports configured text and image assistance. Autonomous diagnosis, prescribing or clinical action is not implied; each deployed use case and provider must be approved and evaluated.","href":"/platform/ai#module-connections"}],"module":{"name":"Reviewed AI Assistance","functions":["Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made."],"workflow":[{"title":"Approve the task","action":"Define the text or image assistance use case, permitted data, model provider and responsible reviewer. Agree consent, data handling, evaluation criteria and a manual fallback before activation.","owner":"Clinical and data governance owner","record":"Approved use case, provider, model and review policy"},{"title":"Provide context","action":"Supply only the approved record context and inputs. Configure allowed models and usage limits; confirm image size, input boundaries and access for the selected feature.","owner":"Authorized user and administrator","record":"Text or image input, permitted context and usage limit"},{"title":"Generate assistance","action":"Use the configured provider to produce assistance for the approved task. Treat the output as proposed content with possible omissions or errors; the model does not replace professional judgment.","owner":"Authorized clinician or operator","record":"Generated output, request context and selected model"},{"title":"Review & retain","action":"Have the responsible professional verify and edit the proposed content before saving or acting on it. Monitor approved evaluation results, access and provider failures under the agreed governance procedure.","owner":"Responsible professional","record":"Reviewed content, reviewer and evaluation evidence"}],"exceptions":[{"situation":"Unsupported or inaccurate suggestion","response":"Reject or correct the output, retain the review decision where required and use the normal documentation route."},{"situation":"Provider unavailable or limit reached","response":"Continue through the approved manual workflow; review provider connectivity and usage limits without bypassing access controls."}],"connection":"The plugin supports configured text and image assistance. Autonomous diagnosis, prescribing or clinical action is not implied; each deployed use case and provider must be approved and evaluated.","scenarios":[{"title":"Reviewed text assistance for documentation","situation":"An authorized clinician uses an approved assistance task while preparing encounter documentation.","preparation":"Approved provider and model, permitted context, input limits and responsible professional reviewer.","steps":["Confirm the approved task and allowed patient context.","Submit only permitted input to the configured assistance feature.","The clinician checks the proposed output for accuracy and omissions and edits it.","Save only professionally reviewed content through the normal documentation workflow."],"acceptance":"The professional owns the final content; generated output is not treated as an autonomous clinical decision."},{"title":"Image assistance with an unsupported response","situation":"The selected approved image task produces an inaccurate suggestion or the provider becomes unavailable.","preparation":"Permitted image type and size, model configuration, rejection and manual fallback procedure.","steps":["Verify that the input is within approved data and size limits.","Review the output and reject unsupported content rather than accepting it into the record.","If the provider fails or the limit is reached, continue normal documentation manually.","Record evaluation and operational follow-up according to the agreed governance process."],"acceptance":"Rejected output does not drive treatment or record completion, and the manual workflow remains available."}],"setupFiles":[{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/ai?lang=ar","title":"مساندة الذكاء الاصطناعي الخاضعة للمراجعة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل.","description":"تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل. تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات…","answers":[{"question":"ما نطاق مساندة الذكاء الاصطناعي الخاضعة للمراجعة في منسوق؟","answer":"تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل. اعتماد المهمة: حدد مهمة المساعدة النصية أو الصورية والبيانات المسموحة والمزود والمراجع. اتفق على الموافقة والتعامل مع البيانات والتقييم والبديل اليدوي قبل التفعيل. توفير السياق: قدم السياق والمدخلات المعتمدة فقط. هيئ النماذج المسموحة وحدود الاستخدام وأكد حجم الصور وحدود المدخلات والوصول للميزة. توليد المساعدة: استخدم المزود المهيأ للمهمة المعتمدة. تعامل مع الناتج كمحتوى مقترح قد يتضمن نقصاً أو أخطاء؛ لا يستبدل النموذج الحكم المهني. المراجعة والاحتفاظ: يتحقق المهني المسؤول من المحتوى ويعدله قبل الحفظ أو التصرف. تابع نتائج التقييم والوصول وأعطال المزود وفق الحوكمة المعتمدة.","href":"/platform/ai#module-workflow"},{"question":"ما بيانات إعداد مساندة الذكاء الاصطناعي الخاضعة للمراجعة؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الصلاحيات والموافقات (access_matrix.csv)؛ مواصفات الربط (interfaces.csv)؛ الافتراضات والقرارات (assumptions_decisions.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/ai#module-setup"},{"question":"كيف يتعامل مساندة الذكاء الاصطناعي الخاضعة للمراجعة مع الاستثناءات؟","answer":"اقتراح غير مدعوم أو غير دقيق ارفض الناتج أو صححه واحفظ قرار المراجعة عند الحاجة واستخدم مسار التوثيق المعتاد. تعطل المزود أو بلوغ الحد استمر بالمسار اليدوي المعتمد وراجع الاتصال وحدود الاستخدام دون تجاوز الصلاحيات.","href":"/platform/ai#module-exceptions"},{"question":"كيف يتصل مساندة الذكاء الاصطناعي الخاضعة للمراجعة بالأنظمة الأخرى؟","answer":"يدعم الملحق المساعدة النصية والصورية المهيأة. لا يفترض التشخيص أو الوصف أو التصرف السريري المستقل؛ يجب اعتماد وتقييم كل مهمة ومزود.","href":"/platform/ai#module-connections"}],"module":{"name":"مساندة الذكاء الاصطناعي الخاضعة للمراجعة","functions":["تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل."],"workflow":[{"title":"اعتماد المهمة","action":"حدد مهمة المساعدة النصية أو الصورية والبيانات المسموحة والمزود والمراجع. اتفق على الموافقة والتعامل مع البيانات والتقييم والبديل اليدوي قبل التفعيل.","owner":"مسؤول الحوكمة السريرية والبيانات","record":"المهمة المعتمدة والمزود والنموذج وسياسة المراجعة"},{"title":"توفير السياق","action":"قدم السياق والمدخلات المعتمدة فقط. هيئ النماذج المسموحة وحدود الاستخدام وأكد حجم الصور وحدود المدخلات والوصول للميزة.","owner":"المستخدم المخوّل والمدير","record":"المدخل النصي أو الصوري والسياق المسموح وحد الاستخدام"},{"title":"توليد المساعدة","action":"استخدم المزود المهيأ للمهمة المعتمدة. تعامل مع الناتج كمحتوى مقترح قد يتضمن نقصاً أو أخطاء؛ لا يستبدل النموذج الحكم المهني.","owner":"الطبيب أو المشغّل المخوّل","record":"الناتج وسياق الطلب والنموذج المختار"},{"title":"المراجعة والاحتفاظ","action":"يتحقق المهني المسؤول من المحتوى ويعدله قبل الحفظ أو التصرف. تابع نتائج التقييم والوصول وأعطال المزود وفق الحوكمة المعتمدة.","owner":"المهني المسؤول","record":"المحتوى المراجع والمراجع وأدلة التقييم"}],"exceptions":[{"situation":"اقتراح غير مدعوم أو غير دقيق","response":"ارفض الناتج أو صححه واحفظ قرار المراجعة عند الحاجة واستخدم مسار التوثيق المعتاد."},{"situation":"تعطل المزود أو بلوغ الحد","response":"استمر بالمسار اليدوي المعتمد وراجع الاتصال وحدود الاستخدام دون تجاوز الصلاحيات."}],"connection":"يدعم الملحق المساعدة النصية والصورية المهيأة. لا يفترض التشخيص أو الوصف أو التصرف السريري المستقل؛ يجب اعتماد وتقييم كل مهمة ومزود.","scenarios":[{"title":"مساعدة نصية مراجعة للتوثيق","situation":"يستخدم طبيب مخوّل مهمة مساعدة معتمدة أثناء إعداد توثيق الزيارة.","preparation":"مزود ونموذج معتمدان وسياق مسموح وحدود مدخلات ومراجع مهني.","steps":["أكد المهمة والسياق المسموح.","قدم المدخل المسموح فقط لميزة المساعدة المهيأة.","يتحقق الطبيب من الدقة والنقص ويعدل المقترح.","احفظ المحتوى المراجع مهنياً عبر التوثيق المعتاد."],"acceptance":"يتحمل المهني مسؤولية المحتوى النهائي ولا يعد الناتج قراراً سريرياً مستقلاً."},{"title":"مساعدة صورية برد غير مدعوم","situation":"تنتج المهمة الصورية المعتمدة اقتراحاً غير دقيق أو يتعطل المزود.","preparation":"نوع صورة وحجم مسموحان وتهيئة نموذج وإجراء رفض وبديل يدوي.","steps":["تحقق من حدود البيانات والحجم المعتمدين.","راجع الناتج وارفض غير المدعوم دون قبوله بالسجل.","عند تعطل المزود أو بلوغ الحد استمر بالتوثيق يدوياً.","سجّل التقييم والمتابعة وفق الحوكمة."],"acceptance":"لا يقود الناتج المرفوض العلاج أو إكمال السجل ويبقى المسار اليدوي متاحاً."}],"setupFiles":[{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/analytics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/analytics","title":"Advanced Analytics software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Selected operational, departmental and revenue reports, separate from standard Core reporting.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Selected operational, departmental and revenue reports, separate from standard Core reporting.","description":"Selected operational, departmental and revenue reports, separate from standard Core reporting. Selected operational, departmental and revenue reports, separate from standard…","answers":[{"question":"What does MANSOQ Advanced Analytics cover?","answer":"Selected operational, departmental and revenue reports, separate from standard Core reporting. Choose sources: Identify the operational source, owner and reporting boundary. Agree which facilities, encounters and financial records can contribute to each view and how data completeness will be checked. Define measures: Specify the unit of analysis, numerator, denominator, exclusions and reporting period. Reconcile financial and activity totals before treating a dashboard as an accepted measure. Publish a view: Configure the selected dashboard provider and view for its facility context. Verify role access, refresh behaviour, filters and the meaning of each displayed value with the intended users. Monitor & maintain: Review source freshness and changes to definitions or mappings. Agree export controls and retain acceptance evidence when a view is used for operational or financial decisions.","href":"/platform/analytics#module-workflow"},{"question":"What setup data does Advanced Analytics need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Interface specification (interfaces.csv); Access & approvals (access_matrix.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/analytics#module-setup"},{"question":"How does Advanced Analytics handle exceptions?","answer":"Stale source or failed refresh Display the last accepted refresh, investigate the provider and source and avoid interpreting missing data as zero activity. Two reports disagree Compare their grain, time window, filters and exclusions, then reconcile to the named source before changing the definition.","href":"/platform/analytics#module-exceptions"},{"question":"How does Advanced Analytics connect with other systems?","answer":"The analytics connector supplies provider-based dashboard access. Specific dashboards, metrics, warehouse design and external finance feeds require a defined reporting scope and acceptance.","href":"/platform/analytics#module-connections"}],"module":{"name":"Advanced Analytics","functions":["Selected operational, departmental and revenue reports, separate from standard Core reporting."],"workflow":[{"title":"Choose sources","action":"Identify the operational source, owner and reporting boundary. Agree which facilities, encounters and financial records can contribute to each view and how data completeness will be checked.","owner":"Data owner","record":"Source system, entity scope and data ownership"},{"title":"Define measures","action":"Specify the unit of analysis, numerator, denominator, exclusions and reporting period. Reconcile financial and activity totals before treating a dashboard as an accepted measure.","owner":"Operations and finance analysts","record":"Metric definition, period, filters and control totals"},{"title":"Publish a view","action":"Configure the selected dashboard provider and view for its facility context. Verify role access, refresh behaviour, filters and the meaning of each displayed value with the intended users.","owner":"Reporting administrator","record":"Dashboard configuration, context and access permissions"},{"title":"Monitor & maintain","action":"Review source freshness and changes to definitions or mappings. Agree export controls and retain acceptance evidence when a view is used for operational or financial decisions.","owner":"Dashboard and source owners","record":"Freshness, reconciliation and definition change record"}],"exceptions":[{"situation":"Stale source or failed refresh","response":"Display the last accepted refresh, investigate the provider and source and avoid interpreting missing data as zero activity."},{"situation":"Two reports disagree","response":"Compare their grain, time window, filters and exclusions, then reconcile to the named source before changing the definition."}],"connection":"The analytics connector supplies provider-based dashboard access. Specific dashboards, metrics, warehouse design and external finance feeds require a defined reporting scope and acceptance.","scenarios":[{"title":"Facility activity dashboard","situation":"Operations needs a view of accepted service activity for one facility and reporting period.","preparation":"Source owner, encounter grain, period, exclusions, dashboard provider and permitted audience.","steps":["Agree the definition of counted activity and its source.","Reconcile a representative period to accepted control totals.","Configure the provider view, facility context and user access.","Validate filters and refresh behaviour with operational users before accepting the view."],"acceptance":"Users know the measure, period, exclusions and source freshness behind each displayed value."},{"title":"Revenue view with stale source data","situation":"Finance notices a report differs from another view after a failed refresh.","preparation":"Last accepted refresh, financial source, metric definitions and reconciliation owner.","steps":["Identify the stale refresh and affected period rather than showing missing data as zero.","Compare grain, filters, currency and excluded states between views.","Restore the accepted source or provider refresh and reconcile control totals.","Record the issue and any definition change before republishing the view."],"acceptance":"Freshness and definition differences are visible, and financial totals reconcile after recovery."}],"setupFiles":[{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/analytics?lang=ar","title":"التحليلات المتقدمة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور.","description":"تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور. تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور..","answers":[{"question":"ما نطاق التحليلات المتقدمة في منسوق؟","answer":"تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور. اختيار المصادر: حدد المصدر التشغيلي والمسؤول وحدود التقارير. اتفق على المنشآت والزيارات والسجلات المالية المشاركة وكيفية التحقق من اكتمال البيانات. تعريف المقاييس: حدد مستوى التحليل والبسط والمقام والاستثناءات والفترة. طابق الإجماليات المالية والنشاط قبل اعتماد لوحة المعلومات مقياساً. نشر الرؤية: هيئ مزود اللوحات المختار والرؤية لسياق المنشأة. تحقق من الصلاحيات والتحديث والمرشحات ومعنى القيم مع المستخدمين. المراقبة والصيانة: راجع حداثة المصدر وتغييرات التعريفات والمواءمة. حدد ضوابط التصدير واحفظ أدلة القبول للرؤى المستخدمة في قرارات التشغيل أو المال.","href":"/platform/analytics#module-workflow"},{"question":"ما بيانات إعداد التحليلات المتقدمة؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: مواصفات الربط (interfaces.csv)؛ الصلاحيات والموافقات (access_matrix.csv)؛ ضوابط الإيرادات والمطابقة (rcm_financial_controls.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/analytics#module-setup"},{"question":"كيف يتعامل التحليلات المتقدمة مع الاستثناءات؟","answer":"مصدر قديم أو فشل التحديث أظهر آخر تحديث معتمد وحقق في المزود والمصدر ولا تفسر غياب البيانات كنشاط صفري. اختلاف تقريرين قارن مستوى التحليل والفترة والمرشحات والاستثناءات وطابق مع المصدر قبل تغيير التعريف.","href":"/platform/analytics#module-exceptions"},{"question":"كيف يتصل التحليلات المتقدمة بالأنظمة الأخرى؟","answer":"يوفر موصل التحليلات وصولاً للوحات حسب المزود. تتطلب اللوحات والمقاييس وتصميم مستودع البيانات والتغذية المالية نطاق تقارير واعتماداً محددين.","href":"/platform/analytics#module-connections"}],"module":{"name":"التحليلات المتقدمة","functions":["تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور."],"workflow":[{"title":"اختيار المصادر","action":"حدد المصدر التشغيلي والمسؤول وحدود التقارير. اتفق على المنشآت والزيارات والسجلات المالية المشاركة وكيفية التحقق من اكتمال البيانات.","owner":"مسؤول البيانات","record":"نظام المصدر ونطاق الكيانات ومسؤولية البيانات"},{"title":"تعريف المقاييس","action":"حدد مستوى التحليل والبسط والمقام والاستثناءات والفترة. طابق الإجماليات المالية والنشاط قبل اعتماد لوحة المعلومات مقياساً.","owner":"محللو التشغيل والمالية","record":"تعريف المقياس والفترة والمرشحات والإجماليات"},{"title":"نشر الرؤية","action":"هيئ مزود اللوحات المختار والرؤية لسياق المنشأة. تحقق من الصلاحيات والتحديث والمرشحات ومعنى القيم مع المستخدمين.","owner":"مدير التقارير","record":"تهيئة اللوحة والسياق والصلاحيات"},{"title":"المراقبة والصيانة","action":"راجع حداثة المصدر وتغييرات التعريفات والمواءمة. حدد ضوابط التصدير واحفظ أدلة القبول للرؤى المستخدمة في قرارات التشغيل أو المال.","owner":"مسؤولو اللوحة والمصدر","record":"الحداثة والمطابقة وسجل تغيير التعريف"}],"exceptions":[{"situation":"مصدر قديم أو فشل التحديث","response":"أظهر آخر تحديث معتمد وحقق في المزود والمصدر ولا تفسر غياب البيانات كنشاط صفري."},{"situation":"اختلاف تقريرين","response":"قارن مستوى التحليل والفترة والمرشحات والاستثناءات وطابق مع المصدر قبل تغيير التعريف."}],"connection":"يوفر موصل التحليلات وصولاً للوحات حسب المزود. تتطلب اللوحات والمقاييس وتصميم مستودع البيانات والتغذية المالية نطاق تقارير واعتماداً محددين.","scenarios":[{"title":"لوحة نشاط منشأة","situation":"تحتاج العمليات رؤية نشاط خدمات معتمدة لمنشأة وفترة.","preparation":"مالك مصدر ومستوى زيارة وفترة واستثناءات ومزود لوحة وجمهور مخوّل.","steps":["اتفق على تعريف النشاط المعدود ومصدره.","طابق فترة نموذجية بإجماليات معتمدة.","هيئ رؤية المزود وسياق المنشأة والوصول.","اختبر المرشحات والتحديث مع المستخدمين قبل الاعتماد."],"acceptance":"يعرف المستخدمون المقياس والفترة والاستثناءات وحداثة المصدر لكل قيمة."},{"title":"رؤية إيرادات بمصدر قديم","situation":"تلاحظ المالية اختلاف تقرير عن رؤية أخرى بعد فشل تحديث.","preparation":"آخر تحديث معتمد ومصدر مالي وتعريفات ومسؤول مطابقة.","steps":["حدد التحديث القديم والفترة دون إظهار البيانات المفقودة صفراً.","قارن مستوى التحليل والمرشحات والعملة والحالات المستثناة.","استعد تحديث المصدر أو المزود وطابق الإجماليات.","سجّل المشكلة وتغيير التعريف قبل إعادة النشر."],"acceptance":"تظهر فروق الحداثة والتعريف وتتطابق الإجماليات بعد التعافي."}],"setupFiles":[{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/billing-finance","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/billing-finance","title":"Billing & Finance software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Invoices, payments and financial records linked to care activity, with accounting connections defined separately.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Invoices, payments and financial records linked to care activity, with accounting connections defined separately.","description":"Invoices, payments and financial records linked to care activity, with accounting connections defined separately. Invoices, payments and financial records linked to care…","answers":[{"question":"What does MANSOQ Billing & Finance cover?","answer":"Invoices, payments and financial records linked to care activity, with accounting connections defined separately. Define charges: Configure service charge definitions, currency and the applicable tax treatment. Confirm account ownership, gross prices and authorized billing roles; contracted payer prices belong to the selected revenue-cycle configuration. Capture activity: Link charges to the encounter and performed service with quantity and supporting context. Review unbilled medication and departmental services, and resolve missing or duplicate items before invoice preparation. Invoice & collect: Review account charges, invoice ownership and the permitted patient or payer liability. Record payments against their reference and invoice; insurance estimates and submission approval remain separate decisions. Reconcile & correct: Reconcile invoices and payments to accepted control totals. Handle refunds, reversals and adjustments with reasons and approval; agree accounting exports when required. ZATCA e-invoicing is included and transmits live after your ZATCA credentials and external acceptance.","href":"/platform/billing-finance#module-workflow"},{"question":"What setup data does Billing & Finance need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Services & department catalogue (services.csv); Service prices & SBS mapping (service_billing.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); zatca onboardings (rcm_zatca_onboardings.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/billing-finance#module-setup"},{"question":"How does Billing & Finance handle exceptions?","answer":"Duplicate or incorrect charge Trace the service event, review the correction authority and preserve the original and reversal references. Payment does not match the invoice Keep the payment reference, investigate allocation and amount differences and route unresolved cash to finance review.","href":"/platform/billing-finance#module-exceptions"},{"question":"How does Billing & Finance connect with other systems?","answer":"Billing records service activity and money movements. Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. External accounting integration is agreed separately.","href":"/platform/billing-finance#module-connections"}],"module":{"name":"Billing & Finance","functions":["Invoices, payments and financial records linked to care activity, with accounting connections defined separately."],"workflow":[{"title":"Define charges","action":"Configure service charge definitions, currency and the applicable tax treatment. Confirm account ownership, gross prices and authorized billing roles; contracted payer prices belong to the selected revenue-cycle configuration.","owner":"Billing administrator","record":"Charge definitions, currency, tax and account rules"},{"title":"Capture activity","action":"Link charges to the encounter and performed service with quantity and supporting context. Review unbilled medication and departmental services, and resolve missing or duplicate items before invoice preparation.","owner":"Department and billing team","record":"Charge item, encounter, quantity and service reference"},{"title":"Invoice & collect","action":"Review account charges, invoice ownership and the permitted patient or payer liability. Record payments against their reference and invoice; insurance estimates and submission approval remain separate decisions.","owner":"Cashier and billing reviewer","record":"Account, invoice, payment reference and allocation"},{"title":"Reconcile & correct","action":"Reconcile invoices and payments to accepted control totals. Handle refunds, reversals and adjustments with reasons and approval; agree accounting exports when required. ZATCA e-invoicing is included and transmits live after your ZATCA credentials and external acceptance.","owner":"Finance and reconciliation owner","record":"Reconciliation, adjustment and export evidence"}],"exceptions":[{"situation":"Duplicate or incorrect charge","response":"Trace the service event, review the correction authority and preserve the original and reversal references."},{"situation":"Payment does not match the invoice","response":"Keep the payment reference, investigate allocation and amount differences and route unresolved cash to finance review."}],"connection":"Billing records service activity and money movements. Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. External accounting integration is agreed separately.","scenarios":[{"title":"Self-pay visit with reconciled payment","situation":"A patient pays for documented consultation and departmental services.","preparation":"Charge definitions, currency, applicable tax, account and cashier permissions.","steps":["Review the performed services and quantities against their encounter.","Prepare the invoice under the accepted price and tax rules.","Record the payment reference and its invoice allocation.","Reconcile invoice, receipt and account totals with finance."],"acceptance":"Service, invoice and payment references agree, and accepted totals reconcile."},{"title":"Charge correction and partial refund","situation":"An invoice contains an incorrect service and a received payment needs an authorized correction.","preparation":"Original charge and payment references, correction reason and refund approval.","steps":["Trace the incorrect charge to the recorded service event.","Approve the correction through the supported reversal or adjustment route.","Record the approved refund or revised allocation with its payment reference.","Reconcile the before-and-after invoice and payment totals without deleting history."],"acceptance":"The correction has approval, linked financial references and reconciled totals."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/billing-finance?lang=ar","title":"الفوترة والمالية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل.","description":"الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل. الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط…","answers":[{"question":"ما نطاق الفوترة والمالية في منسوق؟","answer":"الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل. تعريف الرسوم: هيئ تعريفات رسوم الخدمات والعملة والمعالجة الضريبية المنطبقة. أكد مسؤولية الحساب والأسعار والصلاحيات؛ تتبع أسعار الدافعين التعاقدية تهيئة الإيرادات المختارة. التقاط النشاط: اربط الرسوم بالزيارة والخدمة المنفذة والكمية والسياق الداعم. راجع الأدوية وخدمات الأقسام غير المفوترة وعالج البنود المفقودة أو المكررة قبل إعداد الفاتورة. الفوترة والتحصيل: راجع رسوم الحساب ومالك الفاتورة ومسؤولية المريض أو الدافع المسموحة. سجّل الدفعات بمراجعها وفواتيرها؛ تبقى تقديرات التأمين واعتماد الإرسال قرارات مستقلة. المطابقة والتصحيح: طابق الفواتير والدفعات مع الإجماليات المعتمدة. عالج الاسترداد والعكس والتسويات بأسباب وموافقات واتفق على التصدير المحاسبي عند الحاجة. الفوترة الإلكترونية لزاتكا مشمولة ويبدأ إرسالها المباشر بعد اعتمادات زاتكا والقبول الخارجي.","href":"/platform/billing-finance#module-workflow"},{"question":"ما بيانات إعداد الفوترة والمالية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الخدمات ودليل الأقسام (services.csv)؛ أسعار الخدمات ومواءمة SBS (service_billing.csv)؛ ضوابط الإيرادات والمطابقة (rcm_financial_controls.csv)؛ تهيئة دورة الإيرادات · التسجيل لدى ZATCA (rcm_zatca_onboardings.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/billing-finance#module-setup"},{"question":"كيف يتعامل الفوترة والمالية مع الاستثناءات؟","answer":"رسوم مكررة أو خاطئة تتبع حدث الخدمة وراجع صلاحية التصحيح واحتفظ بمراجع الأصل والعكس. دفعة لا تطابق الفاتورة احتفظ بمرجع الدفع وحقق في فرق التخصيص والمبلغ وأحل النقد غير المطابق للمراجعة المالية.","href":"/platform/billing-finance#module-exceptions"},{"question":"كيف يتصل الفوترة والمالية بالأنظمة الأخرى؟","answer":"تسجل الفوترة نشاط الخدمات والحركات المالية. مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. يُتفق على الربط المحاسبي الخارجي بشكل مستقل.","href":"/platform/billing-finance#module-connections"}],"module":{"name":"الفوترة والمالية","functions":["الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل."],"workflow":[{"title":"تعريف الرسوم","action":"هيئ تعريفات رسوم الخدمات والعملة والمعالجة الضريبية المنطبقة. أكد مسؤولية الحساب والأسعار والصلاحيات؛ تتبع أسعار الدافعين التعاقدية تهيئة الإيرادات المختارة.","owner":"مدير الفوترة","record":"تعريفات الرسوم والعملة والضريبة وقواعد الحساب"},{"title":"التقاط النشاط","action":"اربط الرسوم بالزيارة والخدمة المنفذة والكمية والسياق الداعم. راجع الأدوية وخدمات الأقسام غير المفوترة وعالج البنود المفقودة أو المكررة قبل إعداد الفاتورة.","owner":"القسم وفريق الفوترة","record":"بند الرسوم والزيارة والكمية ومرجع الخدمة"},{"title":"الفوترة والتحصيل","action":"راجع رسوم الحساب ومالك الفاتورة ومسؤولية المريض أو الدافع المسموحة. سجّل الدفعات بمراجعها وفواتيرها؛ تبقى تقديرات التأمين واعتماد الإرسال قرارات مستقلة.","owner":"أمين الصندوق ومراجع الفوترة","record":"الحساب والفاتورة ومرجع الدفع والتخصيص"},{"title":"المطابقة والتصحيح","action":"طابق الفواتير والدفعات مع الإجماليات المعتمدة. عالج الاسترداد والعكس والتسويات بأسباب وموافقات واتفق على التصدير المحاسبي عند الحاجة. الفوترة الإلكترونية لزاتكا مشمولة ويبدأ إرسالها المباشر بعد اعتمادات زاتكا والقبول الخارجي.","owner":"المالية ومسؤول المطابقة","record":"المطابقة والتسويات وأدلة التصدير"}],"exceptions":[{"situation":"رسوم مكررة أو خاطئة","response":"تتبع حدث الخدمة وراجع صلاحية التصحيح واحتفظ بمراجع الأصل والعكس."},{"situation":"دفعة لا تطابق الفاتورة","response":"احتفظ بمرجع الدفع وحقق في فرق التخصيص والمبلغ وأحل النقد غير المطابق للمراجعة المالية."}],"connection":"تسجل الفوترة نشاط الخدمات والحركات المالية. مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. يُتفق على الربط المحاسبي الخارجي بشكل مستقل.","scenarios":[{"title":"زيارة دفع ذاتي ودفعة مطابقة","situation":"يدفع مريض مقابل استشارة وخدمات أقسام موثقة.","preparation":"تعريفات رسوم وعملة وضريبة منطبقة وحساب وصلاحيات تحصيل.","steps":["راجع الخدمات والكمية مقابل الزيارة.","جهز الفاتورة وفق الأسعار والضريبة المعتمدتين.","سجّل مرجع الدفع وتخصيصه للفاتورة.","طابق الفاتورة والإيصال وإجماليات الحساب مع المالية."],"acceptance":"تتطابق مراجع الخدمة والفاتورة والدفع والإجماليات المعتمدة."},{"title":"تصحيح رسوم واسترداد جزئي","situation":"تحتوي فاتورة خدمة غير صحيحة وتحتاج دفعة مستلمة تصحيحاً مخولاً.","preparation":"مراجع الرسوم والدفع الأصلية وسبب التصحيح وموافقة الاسترداد.","steps":["تتبع الرسوم الخاطئة لحدث الخدمة.","اعتمد التصحيح عبر العكس أو التسوية المدعومين.","سجّل الاسترداد أو التخصيص المعدل بمرجع الدفع.","طابق إجماليات الفاتورة والدفع قبل التغيير وبعده دون حذف التاريخ."],"acceptance":"للتصحيح موافقة ومراجع مالية مرتبطة وإجماليات مطابقة."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/care-settings","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/care-settings","title":"Outpatient, inpatient & emergency care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Products for outpatient, inpatient and verified specialist journeys.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Products for outpatient, inpatient and verified specialist journeys.","description":"Explore outpatient, inpatient, emergency, TeleICU and home-care workflows. Connect patient identity, clinical documentation, orders, departments and revenue.","answers":[],"overview":{"title":"Care changes. Context stays.","summary":"Explore the right workflow for the way you deliver care.","areas":[{"name":"Outpatient Care","purpose":"Connect reception and the clinician around the person’s visit.","functions":["Appointments","Registration","Consultation","Orders & medication","Billing & follow-up"],"details":"/platform/outpatient"},{"name":"Inpatient Care","purpose":"Carry the care context through every ward and departmental handover.","functions":["Admission","Wards & beds","Nursing","Orders & medication","Discharge"],"details":"/platform/inpatient"},{"name":"Emergency Care","purpose":"Make urgent care context visible to the responsible team.","functions":["Urgent encounter","Observations","Clinical work","Care handover"],"details":"/platform/emergency"},{"name":"TeleICU","purpose":"Connect the remote specialist with the local care team and agreed clinical context.","functions":["Local care context","Remote review","Defined interfaces"],"details":"/platform/teleicu"},{"name":"Home & Palliative Care","purpose":"Support continuity across visits and the people providing care.","functions":["Visits","Care plans","Team documentation"],"details":"/platform/home-palliative"}]}},"ar":{"url":"https://mansoq.com/platform/care-settings?lang=ar","title":"أنظمة العيادات والتنويم والطوارئ | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"منتجات لمسارات العيادات الخارجية والتنويم والرعاية التخصصية المتحقق منها.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"منتجات لمسارات العيادات الخارجية والتنويم والرعاية التخصصية المتحقق منها.","description":"استكشف مسارات العيادات والتنويم والطوارئ والعناية عن بُعد والرعاية المنزلية. اربط الهوية والتوثيق والطلبات والأقسام والإيرادات.","answers":[],"overview":{"title":"تتغير الرعاية. ويبقى السياق.","summary":"استكشف المسار المناسب لطريقتك في تقديم الرعاية.","areas":[{"name":"رعاية العيادات الخارجية","purpose":"اربط الاستقبال والطبيب حول زيارة الشخص.","functions":["المواعيد","التسجيل","الاستشارة","الطلبات والأدوية","الفوترة والمتابعة"],"details":"/platform/outpatient"},{"name":"رعاية التنويم","purpose":"حافظ على سياق الرعاية عبر كل تسليم بين الأجنحة والأقسام.","functions":["الدخول","الأجنحة والأسرة","التمريض","الطلبات والأدوية","الخروج"],"details":"/platform/inpatient"},{"name":"رعاية الطوارئ","purpose":"أظهر سياق الرعاية العاجلة للفريق المسؤول.","functions":["زيارة الطوارئ","الملاحظات","العمل السريري","تسليم الرعاية"],"details":"/platform/emergency"},{"name":"العناية المركزة عن بُعد","purpose":"اربط المختص عن بُعد بفريق الرعاية المحلي والسياق السريري المتفق عليه.","functions":["سياق الرعاية المحلي","المراجعة عن بُعد","اتصالات محددة"],"details":"/platform/teleicu"},{"name":"الرعاية المنزلية والتلطيفية","purpose":"ادعم استمرارية الرعاية عبر الزيارات وبين مقدميها.","functions":["الزيارات","خطط الرعاية","توثيق الفريق"],"details":"/platform/home-palliative"}]}}},{"slug":"/platform/clinical-documentation","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/clinical-documentation","title":"Clinical Documentation & Care Planning software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow.","description":"Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow. Required clinician and nursing…","answers":[{"question":"What does MANSOQ Clinical Documentation & Care Planning cover?","answer":"Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow. Prepare forms: Configure approved questionnaires, clinical forms and author permissions for the care setting. Define required fields, terminology and review responsibility before use. Document the encounter: Capture the assessment, observations, conditions and clinical narrative against the correct encounter. Keep structured responses and attachments linked to the patient and responsible author. Review & complete: Review required information and the care plan. Apply the approved completion and signature process for the selected release, then make the relevant record available to authorized receiving teams. Amend & retain: Handle corrections with an identified author and reason. Agree retention and record access, and preserve relevant versions and audit evidence when documentation is used for coding or external exchange.","href":"/platform/clinical-documentation#module-workflow"},{"question":"What setup data does Clinical Documentation & Care Planning need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Clinical workflow configuration (clinical_workflows.csv); Roles & permissions (roles.csv); Users & department access (user_access.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/clinical-documentation#module-setup"},{"question":"How does Clinical Documentation & Care Planning handle exceptions?","answer":"Incorrect encounter or author Route the correction to an authorized reviewer, preserve the original context and verify downstream coding and report references. Required field is missing Identify the responsible author and complete the missing information; do not substitute an assumed clinical finding.","href":"/platform/clinical-documentation#module-exceptions"},{"question":"How does Clinical Documentation & Care Planning connect with other systems?","answer":"Documentation supplies clinical context to orders, handovers and coding. External document exchange, signatures and retention policies must match the accepted release and organization rules.","href":"/platform/clinical-documentation#module-connections"}],"module":{"name":"Clinical Documentation & Care Planning","functions":["Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow."],"workflow":[{"title":"Prepare forms","action":"Configure approved questionnaires, clinical forms and author permissions for the care setting. Define required fields, terminology and review responsibility before use.","owner":"Clinical documentation owner","record":"Questionnaire, form version and author roles"},{"title":"Document the encounter","action":"Capture the assessment, observations, conditions and clinical narrative against the correct encounter. Keep structured responses and attachments linked to the patient and responsible author.","owner":"Clinician and nurse","record":"Notes, questionnaire responses, observations and attachments"},{"title":"Review & complete","action":"Review required information and the care plan. Apply the approved completion and signature process for the selected release, then make the relevant record available to authorized receiving teams.","owner":"Author and clinical reviewer","record":"Completion status, reviewer and care-plan record"},{"title":"Amend & retain","action":"Handle corrections with an identified author and reason. Agree retention and record access, and preserve relevant versions and audit evidence when documentation is used for coding or external exchange.","owner":"Records and governance team","record":"Amendment reason, audit evidence and retention decision"}],"exceptions":[{"situation":"Incorrect encounter or author","response":"Route the correction to an authorized reviewer, preserve the original context and verify downstream coding and report references."},{"situation":"Required field is missing","response":"Identify the responsible author and complete the missing information; do not substitute an assumed clinical finding."}],"connection":"Documentation supplies clinical context to orders, handovers and coding. External document exchange, signatures and retention policies must match the accepted release and organization rules.","scenarios":[{"title":"Structured consultation and completed care plan","situation":"A clinician uses an approved form to document a visit for downstream care and coding.","preparation":"Form version, required fields, clinical terminology, author and reviewer permissions.","steps":["Open the correct patient and encounter and choose the approved form.","Capture structured findings, clinical narrative, observations and attachments.","Review completeness and apply the release-specific completion process.","Make the accepted documentation available to the authorized care and coding teams."],"acceptance":"The form version, author, encounter and required information can be identified without inferred findings."},{"title":"Correction after documentation is completed","situation":"An author discovers a missing or incorrect item in a previously completed record.","preparation":"Authorized amendment route, reason recording, retention and affected downstream references.","steps":["Identify the original note, encounter and information requiring correction.","Have the authorized author or reviewer record the correction and reason.","Preserve the original context and the supported amendment evidence.","Review whether orders, coding or communicated reports need follow-up."],"acceptance":"The correction has an owner and reason and does not silently erase the original documentation context."}],"setupFiles":[{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/clinical-documentation?lang=ar","title":"التوثيق السريري وتخطيط الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار.","description":"التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار. التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق…","answers":[{"question":"ما نطاق التوثيق السريري وتخطيط الرعاية في منسوق؟","answer":"التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار. تحضير النماذج: هيئ الاستبيانات والنماذج السريرية وصلاحيات المؤلفين لبيئة الرعاية. حدد الحقول المطلوبة والمصطلحات ومسؤولية المراجعة قبل الاستخدام. توثيق الزيارة: سجّل التقييم والقياسات والتشخيصات والسرد السريري للزيارة الصحيحة. اربط الإجابات المنظمة والمرفقات بالمريض والمؤلف المسؤول. المراجعة والإكمال: راجع المعلومات المطلوبة وخطة الرعاية. طبّق إجراء الإكمال والتوقيع المعتمد للإصدار المختار وأتح السجل المناسب للفرق المخوّلة المستلمة. التعديل والاحتفاظ: عالج التصحيحات بمؤلف وسبب محددين. اتفق على الاحتفاظ والوصول واحفظ الإصدارات وأدلة التدقيق عند استخدام التوثيق للترميز أو التبادل الخارجي.","href":"/platform/clinical-documentation#module-workflow"},{"question":"ما بيانات إعداد التوثيق السريري وتخطيط الرعاية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة المسارات السريرية (clinical_workflows.csv)؛ الأدوار والصلاحيات (roles.csv)؛ المستخدمون وصلاحيات الأقسام (user_access.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/clinical-documentation#module-setup"},{"question":"كيف يتعامل التوثيق السريري وتخطيط الرعاية مع الاستثناءات؟","answer":"زيارة أو مؤلف غير صحيح أحل التصحيح لمراجع مخوّل واحتفظ بالسياق الأصلي وتحقق من مراجع الترميز والتقارير. حقل مطلوب ناقص حدد المؤلف المسؤول وأكمل المعلومة المفقودة دون افتراض نتيجة سريرية.","href":"/platform/clinical-documentation#module-exceptions"},{"question":"كيف يتصل التوثيق السريري وتخطيط الرعاية بالأنظمة الأخرى؟","answer":"يوفر التوثيق السياق للطلبات والتسليم والترميز. يجب أن تتوافق وثائق التبادل والتوقيعات والاحتفاظ مع الإصدار المعتمد وقواعد المؤسسة.","href":"/platform/clinical-documentation#module-connections"}],"module":{"name":"التوثيق السريري وتخطيط الرعاية","functions":["التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار."],"workflow":[{"title":"تحضير النماذج","action":"هيئ الاستبيانات والنماذج السريرية وصلاحيات المؤلفين لبيئة الرعاية. حدد الحقول المطلوبة والمصطلحات ومسؤولية المراجعة قبل الاستخدام.","owner":"مسؤول التوثيق السريري","record":"الاستبيان وإصدار النموذج وأدوار المؤلفين"},{"title":"توثيق الزيارة","action":"سجّل التقييم والقياسات والتشخيصات والسرد السريري للزيارة الصحيحة. اربط الإجابات المنظمة والمرفقات بالمريض والمؤلف المسؤول.","owner":"الطبيب والممرض","record":"الملاحظات وإجابات الاستبيان والقياسات والمرفقات"},{"title":"المراجعة والإكمال","action":"راجع المعلومات المطلوبة وخطة الرعاية. طبّق إجراء الإكمال والتوقيع المعتمد للإصدار المختار وأتح السجل المناسب للفرق المخوّلة المستلمة.","owner":"المؤلف والمراجع السريري","record":"حالة الإكمال والمراجع وسجل خطة الرعاية"},{"title":"التعديل والاحتفاظ","action":"عالج التصحيحات بمؤلف وسبب محددين. اتفق على الاحتفاظ والوصول واحفظ الإصدارات وأدلة التدقيق عند استخدام التوثيق للترميز أو التبادل الخارجي.","owner":"فريق السجلات والحوكمة","record":"سبب التعديل وأدلة التدقيق وقرار الاحتفاظ"}],"exceptions":[{"situation":"زيارة أو مؤلف غير صحيح","response":"أحل التصحيح لمراجع مخوّل واحتفظ بالسياق الأصلي وتحقق من مراجع الترميز والتقارير."},{"situation":"حقل مطلوب ناقص","response":"حدد المؤلف المسؤول وأكمل المعلومة المفقودة دون افتراض نتيجة سريرية."}],"connection":"يوفر التوثيق السياق للطلبات والتسليم والترميز. يجب أن تتوافق وثائق التبادل والتوقيعات والاحتفاظ مع الإصدار المعتمد وقواعد المؤسسة.","scenarios":[{"title":"استشارة منظمة وخطة رعاية مكتملة","situation":"يستخدم طبيب نموذجاً معتمداً لتوثيق زيارة للرعاية والترميز.","preparation":"إصدار نموذج وحقول مطلوبة ومصطلحات وصلاحيات المؤلف والمراجع.","steps":["افتح المريض والزيارة الصحيحين واختر النموذج المعتمد.","سجّل النتائج المنظمة والسرد والقياسات والمرفقات.","راجع الاكتمال وطبّق إجراء إكمال الإصدار.","أتح التوثيق المعتمد لفرق الرعاية والترميز المخولة."],"acceptance":"يمكن تحديد إصدار النموذج والمؤلف والزيارة والمعلومات دون نتائج مفترضة."},{"title":"تصحيح بعد إكمال التوثيق","situation":"يكتشف مؤلف بنداً ناقصاً أو خاطئاً بسجل مكتمل سابقاً.","preparation":"مسار تعديل مخوّل وتسجيل سبب واحتفاظ ومراجع تابعة متأثرة.","steps":["حدد الملاحظة والزيارة والمعلومة المراد تصحيحها.","يسجل المؤلف أو المراجع المخوّل التصحيح وسببه.","احفظ السياق الأصلي وأدلة التعديل المدعومة.","راجع حاجة الطلبات والترميز والتقارير المبلغة للمتابعة."],"acceptance":"للتصحيح مسؤول وسبب ولا يمحو سياق التوثيق الأصلي ضمنياً."}],"setupFiles":[{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/configurations","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/configurations","title":"Healthcare platform configuration & operating models | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Care profiles compose shared products. Optional Essentials, Premium and Diamond presets can be configured without multiplying offers across all settings.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Care profiles compose shared products. Optional Essentials, Premium and Diamond presets can be configured without multiplying offers across all settings.","description":"Configure MANSOQ around your care setting: shared Core, clinical modules, departments and extensions. Review native operations, external connections and dependencies.","answers":[]},"ar":{"url":"https://mansoq.com/platform/configurations?lang=ar","title":"تهيئة منصة الرعاية ونماذج التشغيل | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تكون ملفات الرعاية منتجات مشتركة. ويمكن تهيئة القوالب الاختيارية الأساسية وبريميوم ودايموند دون مضاعفة العروض بين البيئات.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تكون ملفات الرعاية منتجات مشتركة. ويمكن تهيئة القوالب الاختيارية الأساسية وبريميوم ودايموند دون مضاعفة العروض بين البيئات.","description":"هيّئ منسوق وفق بيئة الرعاية: كور والوحدات السريرية والأقسام والإضافات. راجع التشغيل الفعلي والاتصالات الخارجية والمتطلبات.","answers":[]}},{"slug":"/platform/core","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/core","title":"MANSOQ Core software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary.","description":"Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary. Patient identity and shared…","answers":[{"question":"What does MANSOQ MANSOQ Core cover?","answer":"Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary. Identify: Register the person with the identifiers your organization uses. Review a possible duplicate before creating another patient; preserve the original identifiers when a source system is retained. Organize: Define legal organizations, facilities, departments and locations. Assign each operational record to its facility and keep cross-site sharing within the approved boundary. Authorize: Assign named users to roles and facilities, then verify their read, create and update permissions. Test a restricted user as well as an administrator before accepting the setup. Connect context: Link encounters, notes, observations, requests and attachments to the correct person. Departmental and revenue modules use this context through their selected capabilities and permissions. Review & maintain: Review record changes and responsible users, maintain shared configuration and confirm release-specific retention, backup and support arrangements. Re-test affected permissions when adding a site or module.","href":"/platform/core#module-workflow"},{"question":"What setup data does MANSOQ Core need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Your organization (organization.csv); Facilities (facilities.csv); Departments (departments.csv); Rooms, wards and beds (locations.csv); Planned team (staff.csv); Roles & permissions (roles.csv); Users & department access (user_access.csv); Operating preferences (operations.csv); Your app address (domain.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/core#module-setup"},{"question":"How does MANSOQ Core handle exceptions?","answer":"Possible duplicate patient Compare source identifiers and demographics; route the match to an authorized reviewer. Approve any correction or merge through the supported workflow. User moves to another facility Review the old and new assignments, remove obsolete access and test both allowed and denied actions.","href":"/platform/core#module-exceptions"},{"question":"How does MANSOQ Core connect with other systems?","answer":"Core supplies shared identity and context. Cross-tenant data exchange, external patient matching and enterprise sharing require a separately accepted interface and governance scope.","href":"/platform/core#module-connections"}],"module":{"name":"MANSOQ Core","functions":["Patient identity and shared record","Administrative and clinical perspectives","Baseline access and audit","Shared configuration and supported base services"],"workflow":[{"title":"Identify","action":"Register the person with the identifiers your organization uses. Review a possible duplicate before creating another patient; preserve the original identifiers when a source system is retained.","owner":"Registration team","record":"Patient identifiers, demographics and contact details"},{"title":"Organize","action":"Define legal organizations, facilities, departments and locations. Assign each operational record to its facility and keep cross-site sharing within the approved boundary.","owner":"Organization administrator","record":"Facility hierarchy, department and location references"},{"title":"Authorize","action":"Assign named users to roles and facilities, then verify their read, create and update permissions. Test a restricted user as well as an administrator before accepting the setup.","owner":"Access administrator","record":"Users, role assignments and access decisions"},{"title":"Connect context","action":"Link encounters, notes, observations, requests and attachments to the correct person. Departmental and revenue modules use this context through their selected capabilities and permissions.","owner":"Care and operational teams","record":"Patient, encounter and linked clinical records"},{"title":"Review & maintain","action":"Review record changes and responsible users, maintain shared configuration and confirm release-specific retention, backup and support arrangements. Re-test affected permissions when adding a site or module.","owner":"Governance and support owners","record":"Audit evidence, configuration version and acceptance record"}],"exceptions":[{"situation":"Possible duplicate patient","response":"Compare source identifiers and demographics; route the match to an authorized reviewer. Approve any correction or merge through the supported workflow."},{"situation":"User moves to another facility","response":"Review the old and new assignments, remove obsolete access and test both allowed and denied actions."}],"connection":"Core supplies shared identity and context. Cross-tenant data exchange, external patient matching and enterprise sharing require a separately accepted interface and governance scope.","scenarios":[{"title":"One person, two departments","situation":"A registered patient visits a clinic and then needs laboratory work at the same facility.","preparation":"One facility, a clinic and a laboratory; reception, clinician and laboratory roles.","steps":["Reception matches the existing patient rather than opening a second identity.","The clinician opens the visit and creates the laboratory request against that encounter.","Authorized laboratory staff use the same patient and request references for specimen and report records.","The clinician reviews the returned report; a restricted user is tested against the same record."],"acceptance":"The patient and encounter references remain consistent across the request, specimen and report; role-access checks pass."},{"title":"Open a second facility","situation":"An organization adds another site while keeping local administration and approved sharing boundaries.","preparation":"New facility, departments, locations, users and a written sharing decision.","steps":["Import the new facility before its departments and locations.","Assign local users and explicitly approved cross-site roles.","Rehearse a referral and patient matching within the agreed boundary.","Test denied access to unshared records and review the change evidence before launch."],"acceptance":"Both allowed and denied access are evidenced, and each record retains its owning facility."}],"setupFiles":[{"template":"/implementation/templates/organization.csv","example":"/implementation/examples/organization.csv"},{"template":"/implementation/templates/facilities.csv","example":"/implementation/examples/facilities.csv"},{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/staff.csv","example":"/implementation/examples/staff.csv"},{"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/operations.csv","example":"/implementation/examples/operations.csv"},{"template":"/implementation/templates/domain.csv","example":"/implementation/examples/domain.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/core?lang=ar","title":"منسوق كور | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"هوية المريض وسجله المشترك وسياق الرعاية والإدارة والصلاحيات والتدقيق والتهيئة ضمن حدود بيانات متفق عليها.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"هوية المريض وسجله المشترك وسياق الرعاية والإدارة والصلاحيات والتدقيق والتهيئة ضمن حدود بيانات متفق عليها.","description":"هوية المريض وسجله المشترك وسياق الرعاية والإدارة والصلاحيات والتدقيق والتهيئة ضمن حدود بيانات متفق عليها. هوية المريض والسجل المشترك، السياق الإداري والسريري، الصلاحيات والتدقيق…","answers":[{"question":"ما نطاق منسوق كور في منسوق؟","answer":"هوية المريض وسجله المشترك وسياق الرعاية والإدارة والصلاحيات والتدقيق والتهيئة ضمن حدود بيانات متفق عليها. التعريف: سجّل الشخص بمعرّفات مؤسستك. راجع احتمال التكرار قبل إنشاء مريض آخر واحتفظ بمعرّفات المصدر عند استمرار استخدام نظام سابق. التنظيم: عرّف المؤسسات القانونية والمنشآت والأقسام والمواقع. اربط كل سجل تشغيلي بمنشأته واجعل المشاركة بين المواقع ضمن الحدود المعتمدة. الصلاحيات: اربط المستخدمين بأدوارهم ومنشآتهم وتحقق من صلاحيات القراءة والإنشاء والتعديل. اختبر مستخدماً محدود الصلاحيات ومديراً قبل اعتماد الإعداد. ربط السياق: اربط الزيارات والملاحظات والقياسات والطلبات والمرفقات بالشخص الصحيح. تستخدم الأقسام والإيرادات هذا السياق وفق القدرات والصلاحيات المختارة. المراجعة والصيانة: راجع تغييرات السجلات والمستخدم المسؤول وحدّث التهيئة المشتركة وأكد ترتيبات الاحتفاظ والنسخ الاحتياطي والدعم للإصدار المختار. أعد اختبار الصلاحيات عند إضافة موقع أو وحدة.","href":"/platform/core#module-workflow"},{"question":"ما بيانات إعداد منسوق كور؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: منشأتك (organization.csv)؛ المنشآت (facilities.csv)؛ الأقسام (departments.csv)؛ الغرف والأجنحة والأسرة (locations.csv)؛ الفريق المخطط (staff.csv)؛ الأدوار والصلاحيات (roles.csv)؛ المستخدمون وصلاحيات الأقسام (user_access.csv)؛ تفضيلات التشغيل (operations.csv)؛ عنوان تطبيقك (domain.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/core#module-setup"},{"question":"كيف يتعامل منسوق كور مع الاستثناءات؟","answer":"احتمال تكرار المريض قارن معرّفات المصدر والبيانات وأحل التطابق لمراجع مخوّل. اعتمد التصحيح أو الدمج عبر المسار المدعوم. انتقال المستخدم لمنشأة أخرى راجع التعيين القديم والجديد وأزل الصلاحيات غير اللازمة واختبر الإجراءات المسموحة والمرفوضة.","href":"/platform/core#module-exceptions"},{"question":"كيف يتصل منسوق كور بالأنظمة الأخرى؟","answer":"يوفر كور الهوية والسياق المشتركين. يتطلب التبادل بين الحسابات ومطابقة المرضى خارجياً والمشاركة المؤسسية نطاق ربط وحوكمة معتمداً.","href":"/platform/core#module-connections"}],"module":{"name":"منسوق كور","functions":["هوية المريض والسجل المشترك","السياق الإداري والسريري","الصلاحيات والتدقيق الأساسيان","التهيئة المشتركة والخدمات الأساسية المدعومة"],"workflow":[{"title":"التعريف","action":"سجّل الشخص بمعرّفات مؤسستك. راجع احتمال التكرار قبل إنشاء مريض آخر واحتفظ بمعرّفات المصدر عند استمرار استخدام نظام سابق.","owner":"فريق التسجيل","record":"معرّفات المريض وبياناته ووسائل التواصل"},{"title":"التنظيم","action":"عرّف المؤسسات القانونية والمنشآت والأقسام والمواقع. اربط كل سجل تشغيلي بمنشأته واجعل المشاركة بين المواقع ضمن الحدود المعتمدة.","owner":"مدير المؤسسة","record":"تسلسل المنشآت ومراجع الأقسام والمواقع"},{"title":"الصلاحيات","action":"اربط المستخدمين بأدوارهم ومنشآتهم وتحقق من صلاحيات القراءة والإنشاء والتعديل. اختبر مستخدماً محدود الصلاحيات ومديراً قبل اعتماد الإعداد.","owner":"مدير الصلاحيات","record":"المستخدمون وتعيينات الأدوار وقرارات الوصول"},{"title":"ربط السياق","action":"اربط الزيارات والملاحظات والقياسات والطلبات والمرفقات بالشخص الصحيح. تستخدم الأقسام والإيرادات هذا السياق وفق القدرات والصلاحيات المختارة.","owner":"فرق الرعاية والتشغيل","record":"المريض والزيارة والسجلات السريرية المرتبطة"},{"title":"المراجعة والصيانة","action":"راجع تغييرات السجلات والمستخدم المسؤول وحدّث التهيئة المشتركة وأكد ترتيبات الاحتفاظ والنسخ الاحتياطي والدعم للإصدار المختار. أعد اختبار الصلاحيات عند إضافة موقع أو وحدة.","owner":"مسؤولو الحوكمة والدعم","record":"أدلة التدقيق وإصدار التهيئة وسجل القبول"}],"exceptions":[{"situation":"احتمال تكرار المريض","response":"قارن معرّفات المصدر والبيانات وأحل التطابق لمراجع مخوّل. اعتمد التصحيح أو الدمج عبر المسار المدعوم."},{"situation":"انتقال المستخدم لمنشأة أخرى","response":"راجع التعيين القديم والجديد وأزل الصلاحيات غير اللازمة واختبر الإجراءات المسموحة والمرفوضة."}],"connection":"يوفر كور الهوية والسياق المشتركين. يتطلب التبادل بين الحسابات ومطابقة المرضى خارجياً والمشاركة المؤسسية نطاق ربط وحوكمة معتمداً.","scenarios":[{"title":"شخص واحد وقسمان","situation":"يزور مريض مسجل عيادة ثم يحتاج فحوص مختبر في المنشأة نفسها.","preparation":"منشأة وعيادة ومختبر وأدوار الاستقبال والطبيب والمختبر.","steps":["يطابق الاستقبال المريض الموجود دون إنشاء هوية ثانية.","يفتح الطبيب الزيارة وينشئ طلب المختبر مرتبطاً بها.","يستخدم فريق المختبر المخوّل مراجع المريض والطلب للعينة والتقرير.","يراجع الطبيب التقرير ويُختبر وصول مستخدم مقيد للسجل."],"acceptance":"تتطابق مراجع المريض والزيارة عبر الطلب والعينة والتقرير وتجتاز الصلاحيات الاختبار."},{"title":"افتتاح منشأة ثانية","situation":"تضيف مؤسسة موقعاً آخر مع إدارة محلية وحدود مشاركة معتمدة.","preparation":"منشأة وأقسام ومواقع ومستخدمون جدد وقرار مشاركة مكتوب.","steps":["استورد المنشأة قبل الأقسام والمواقع التابعة.","عين المستخدمين المحليين والأدوار المشتركة المعتمدة صراحة.","جرّب إحالة ومطابقة مريض ضمن الحدود المتفق عليها.","اختبر منع الوصول للسجلات غير المشتركة وراجع دليل التغيير قبل التشغيل."],"acceptance":"توثق حالات السماح والمنع ويحتفظ كل سجل بمنشأته المالكة."}],"setupFiles":[{"template":"/implementation/templates/organization.csv","example":"/implementation/examples/organization.csv"},{"template":"/implementation/templates/facilities.csv","example":"/implementation/examples/facilities.csv"},{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/staff.csv","example":"/implementation/examples/staff.csv"},{"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/operations.csv","example":"/implementation/examples/operations.csv"},{"template":"/implementation/templates/domain.csv","example":"/implementation/examples/domain.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/departments","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/departments","title":"Connected hospital departments & patient journeys | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Depth for each departmental team, with a shared care context.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Depth for each departmental team, with a shared care context.","description":"Follow four complete care and financial journeys across operating room, ICU, laboratory, radiology, pharmacy and inventory. Roles, handovers and exceptions.","answers":[{"question":"How do clinical care and financial records stay connected across departments?","answer":"A shared patient and encounter link requests, specimens, reports, medication, procedures and stock activity. Authorized service evidence supports charge capture and the financial follow-up. The four hospital journeys show separate owners and records for care, charges, invoices, claims, payer advice and cash; a claim acceptance is not a payment.","href":"/platform/departments#department-journeys"}],"overview":{"title":"Every department, connected.","summary":"Specialist work, connected to the person and the next team.","areas":[{"name":"Operating Room","purpose":"Connect preparation, intervention and recovery around the person.","functions":["Case booking","Preparation","Procedure","Consumables","Recovery handover"],"details":"/platform/operating-room"},{"name":"Intensive Care","purpose":"Connect critical-care responsibilities and clinical context.","functions":["Critical-care record","Observations","Medication"],"details":"/platform/icu"},{"name":"Pharmacy","purpose":"Connect the prescription, departmental work and the patient’s next step.","functions":["Medication request","Dispensing","Stock operation"],"details":"/platform/pharmacy"},{"name":"Laboratory","purpose":"Bring diagnostic work back into the relevant care context.","functions":["Orders","Specimens","Results"],"details":"/platform/laboratory"},{"name":"Radiology","purpose":"Connect imaging requests and reports to the person’s care.","functions":["Requests","Departmental operation","Reporting"],"details":"/platform/radiology"},{"name":"Inventory","purpose":"Keep required supplies connected to departmental responsibilities.","functions":["Stock","Stores","Department supply"],"details":"/platform/inventory"}]},"patientAndFinancialJourneys":[{"title":"One urgent admission. Every handover connected.","summary":"An emergency admission moves through investigations, an indicated procedure, critical care and recovery. The same encounter connects departmental evidence to financial follow-up.","stages":[{"title":"Receive & identify","patient":"The patient or family receives a named contact while urgent assessment starts.","care":{"action":"Open the emergency encounter, review identity and record the clinical team. Follow the accepted temporary-identity procedure when demographics are incomplete.","owner":"Patient access team","record":"Patient identifier · encounter · location · responsible team"},"finance":{"action":"Check coverage and record what is known, missing and time-stamped. Route unresolved eligibility to a reviewer alongside clinical assessment.","owner":"Revenue cycle team","record":"Coverage evidence · eligibility response or review task"},"handover":"The next team receives the encounter identity and unresolved responsibilities; financial uncertainty remains visible."},{"title":"Investigate in parallel","patient":"The patient is told which investigations are requested and who will review them.","care":{"action":"Link laboratory requests to collected specimens and imaging requests to accession and study identifiers. Return reviewed reports to the ordering encounter.","owner":"Clinician & nurse","record":"Request → specimen or study → report → reviewer"},"finance":{"action":"Map completed activity to configured services and applicable coding. Keep requested, cancelled and performed work distinct; review authorization requirements.","owner":"Billing & coding team","record":"Performed-service evidence · charge candidate · approval status"},"handover":"Clinical review owns the next care decision. A report and a charge review remain separate states."},{"title":"Prepare & perform the procedure","patient":"The patient receives the team’s explanation and the required consent process.","care":{"action":"Record the team, theatre, preparation, consent references and safety checks. Document the performed procedure, medication and actual consumables for recovery.","owner":"Surgical, anesthesia & recovery teams","record":"Procedure record · checklist · medication · supply usage"},"finance":{"action":"Review procedure and consumable evidence against tariff and contract rules. Remove unused planned items from charge consideration and track changes in authorized scope.","owner":"Billing & coding team","record":"Service and quantity evidence · charge review · authorization amendment"},"handover":"Recovery receives the current treatment, procedure record and outstanding actions with named owners."},{"title":"Receive into ICU","patient":"The family knows the receiving unit and how updates will be communicated.","care":{"action":"Record the receiving bed, assessments, observations and investigation responsibilities. Confirm device-to-encounter mapping where a tested feed is included.","owner":"ICU & receiving ward teams","record":"ICU location · observations · current plan · pending reports"},"finance":{"action":"Review location and service dates against the accepted contract and coverage. Escalate missing or exceeded authorization rather than assuming approval.","owner":"Revenue cycle team","record":"Service dates · coverage review · payer follow-up task"},"handover":"A transfer or shift handover names the next team and the owner of every pending report and order."},{"title":"Deliver medication & supplies","patient":"The patient receives medication under the treating team’s plan; changes are explained.","care":{"action":"Verify prescriptions, select usable lots and record quantities actually handed over. Nursing documents administration separately; inventory records departmental issues and returns.","owner":"Pharmacist & nursing team","record":"Request · dispense · administration · lot movement"},"finance":{"action":"Apply approved unit and charge rules to actual dispensing or usage evidence. Reconcile returns and partial quantities without billing the same activity twice.","owner":"Billing & coding team","record":"Actual quantities · unit conversion · charge or correction reference"},"handover":"The ward receives current medication, remaining supply responsibility and traceable stock records."},{"title":"Recover, transfer & leave","patient":"The patient leaves with instructions, medication information and a named follow-up contact.","care":{"action":"Document ward transfer and discharge decisions, reconcile medication and assign outstanding reports to a follow-up owner. Clinical staff decide readiness for discharge.","owner":"Clinician & nurse","record":"Discharge summary · medication list · follow-up · pending-result owner"},"finance":{"action":"Reconcile departmental evidence, coding, charges and patient-liability assumptions. Explain the financial statement and leave unresolved items with a responsible team.","owner":"Billing & coding team","record":"Reviewed charge set · invoice evidence · open financial items"},"handover":"Clinical discharge and financial follow-up are tracked separately, with neither silently marked complete."},{"title":"Submit & follow the claim","patient":"The patient can ask the responsible team about documented liability and unresolved payer decisions.","care":{"action":"Keep clinical evidence and authorship available to authorized reviewers. Respond to a documentation query through a traceable amendment.","owner":"Clinician & nurse","record":"Clinical evidence · coding query · amendment history"},"finance":{"action":"Validate the claim and submit through the activated payer route. Distinguish transport failure, business rejection and adjudicated denial; assign the appropriate correction or appeal.","owner":"Revenue cycle team","record":"Claim identity · submission · response · denial or appeal task"},"handover":"The team tracks a payer response against the original claim and evidence, rather than treating transmission as payment."},{"title":"Reconcile & close responsibly","patient":"The patient receives an updated balance or approved refund explanation when applicable.","care":{"action":"Keep the follow-up owner and unresolved clinical actions visible after the encounter ends. Preserve departmental and stock corrections in the audit trail.","owner":"Clinician & nurse","record":"Follow-up status · corrected records · stock reconciliation"},"finance":{"action":"Match advice, actual cash and claim lines. Investigate unmatched or partial payments, approve adjustments and retain patient balances until reconciled.","owner":"Finance & reconciliation team","record":"Advice · payment · allocation · approved adjustment · remaining balance"},"handover":"Close only the reconciled financial items; outstanding clinical and financial work retains an owner."}]},{"title":"From the clinic decision to recovery and reconciliation.","summary":"A planned procedure connects pre-operative investigation, theatre preparation, stock usage, recovery and follow-up. Estimates and approvals are reviewed again when the actual scope changes.","stages":[{"title":"Agree the procedure plan","patient":"The patient understands the proposed procedure, preparation and next appointment.","care":{"action":"Record the assessment and procedure request, then coordinate the intended theatre session, team and care setting.","owner":"Clinician & nurse","record":"Clinic encounter · request · planned session · responsible clinician"},"finance":{"action":"Review eligibility, network, benefits and tariff. Share an estimate with assumptions, verification time and unresolved amounts clearly identified.","owner":"Revenue cycle team","record":"Estimate version · coverage evidence · authorization request"},"handover":"Confirm the next appointment and responsibility for outstanding preparation or approval."},{"title":"Complete requested investigations","patient":"The patient completes the investigations requested by the treating team and receives preparation instructions.","care":{"action":"Track specimens and imaging studies to their requests. Review reports, record outstanding findings and document any change to the plan.","owner":"Clinician & nurse","record":"Specimen or study · report · clinical review · revised plan"},"finance":{"action":"Review performed investigation services and their authorization status. Recalculate the estimate when additional accepted scope changes the expected cost.","owner":"Billing & coding team","record":"Investigation evidence · service mapping · revised estimate"},"handover":"The procedure team receives reviewed results or a named owner for any unresolved preparation item."},{"title":"Confirm people, theatre & supplies","patient":"The patient completes the approved identity, consent and preparation checks with the team.","care":{"action":"Confirm the theatre slot, staffing, equipment, consent references and safety checks. Inventory issues appropriate lots; pharmacy verifies procedure medication.","owner":"Surgical, anesthesia & recovery teams","record":"Session · checklist · supply issue · medication preparation"},"finance":{"action":"Confirm the approval scope and expiry or the agreed self-pay deposit. A booking or stock reservation alone is not evidence that a billable service occurred.","owner":"Revenue cycle team","record":"Authorization decision or deposit · planned versus performed status"},"handover":"Release to the procedure follows the team’s approved checks; unresolved financial facts stay assigned for review."},{"title":"Document what actually happened","patient":"The procedure and immediate recovery are documented by the responsible clinical team.","care":{"action":"Document the procedure, observations, medication and actual consumable usage. Retain the request, encounter and author links for recovery and later review.","owner":"Surgical, anesthesia & recovery teams","record":"Procedure notes · medication · consumed lots · author"},"finance":{"action":"Review performed procedure codes and quantities against the applicable tariff. Reconcile supply issues with usage and returns before finalizing charge candidates.","owner":"Billing & coding team","record":"Procedure evidence · coding review · quantities · return references"},"handover":"Recovery receives the documented procedure, current treatment and outstanding actions."},{"title":"Recover or transfer when indicated","patient":"The patient and family know whether the next step is discharge, ward care or critical care.","care":{"action":"Record recovery and the receiving team. If ICU is needed, carry observations, medication, procedure context and pending investigations into the handover.","owner":"Surgical, anesthesia & recovery teams","record":"Recovery note · destination · receiving team · pending actions"},"finance":{"action":"Review any change from day case to admission or critical care, update estimated scope and pursue the applicable authorization amendment.","owner":"Revenue cycle team","record":"Care-setting change · estimate revision · approval amendment"},"handover":"ICU is a conditional branch, not a routine stage of every planned procedure."},{"title":"Prepare discharge & follow-up","patient":"The patient receives discharge instructions, prescribed medication and a follow-up appointment or contact.","care":{"action":"Reconcile medication, record instructions and assign pending reports, including procedure specimens where applicable, to a follow-up owner.","owner":"Clinician & nurse","record":"Discharge record · actual dispense · follow-up · report responsibility"},"finance":{"action":"Review the final service set against the estimate, authorizations and actual dispensing. Explain approved liability and unresolved items to the patient.","owner":"Billing & coding team","record":"Reviewed service set · invoice · liability explanation"},"handover":"Discharge instructions and financial explanations each have a named contact."},{"title":"Invoice or claim the accepted activity","patient":"The patient has a clear statement of the agreed payment route and any outstanding balance.","care":{"action":"Keep the procedure, investigation and medication evidence available for an authorized billing or clinical documentation query.","owner":"Clinician & nurse","record":"Supporting notes · reports · service evidence"},"finance":{"action":"For insurance, validate and follow the claim response. For self-pay, review invoice and deposit allocation. Use national exchanges only within their activated scope.","owner":"Billing & coding team","record":"Claim and response or invoice · deposit allocation · submission evidence"},"handover":"A transmitted claim or issued invoice is distinct from receipt of money."},{"title":"Resolve changes, returns & balances","patient":"The patient can trace an approved adjustment or refund and the final balance.","care":{"action":"Reconcile unused supplies and corrected departmental records. Keep post-procedure follow-up and outstanding results assigned after the episode.","owner":"Inventory & department owners","record":"Returns · corrected records · follow-up evidence"},"finance":{"action":"Match cash, deposits and payer advice to the reviewed items. Investigate variances and authorize refunds, credits or adjustments through the accepted finance process.","owner":"Finance & reconciliation team","record":"Payment allocation · variance · approved refund or adjustment"},"handover":"Closure records what is settled and what remains open, with no loss of the original history."}]},{"title":"Investigations, treatment and follow-up stay together.","summary":"A ward admission brings diagnostic reports, medication and supplies into daily care. The financial journey handles repeated services, partial quantities and payer review without losing the clinical context.","stages":[{"title":"Admit with shared context","patient":"The patient knows the ward, responsible team and expected administrative steps.","care":{"action":"Link admission, identity, location and responsible clinician; receive the referral, current medication and relevant history.","owner":"Patient access team","record":"Admission encounter · bed · referral · medication context"},"finance":{"action":"Review policy, contract, admission approval and estimate assumptions. Mark missing benefits or remaining authorization as unresolved.","owner":"Revenue cycle team","record":"Policy evidence · approval · estimate · review responsibility"},"handover":"The ward receives both the clinical referral and the named administrative contact."},{"title":"Assess & request investigations","patient":"The patient understands the tests and imaging requested by the care team.","care":{"action":"Document assessment, observations and requests. Link each laboratory specimen and imaging accession to the ordering encounter and priority.","owner":"Clinician & nurse","record":"Assessment · observations · requests · specimen and study identifiers"},"finance":{"action":"Check whether requested services are covered or require additional authorization; assign unresolved decisions and communicate estimate changes.","owner":"Revenue cycle team","record":"Service-scope review · approval request · estimate amendment"},"handover":"Request status, authorization status and clinical priority remain separate."},{"title":"Review reports & update the plan","patient":"The treating team explains reviewed findings and the next care step.","care":{"action":"Review released laboratory and imaging reports, record the plan and name owners for outstanding or amended results.","owner":"Clinician & nurse","record":"Released reports · review note · care plan · follow-up owner"},"finance":{"action":"Review completed service evidence against mapped codes and tariffs. A corrected report does not by itself justify a second charge.","owner":"Billing & coding team","record":"Performed services · coding review · duplicate-charge check"},"handover":"The current plan and report version travel into the next shift with their authors and times."},{"title":"Supply & administer medication","patient":"Medication changes and any remaining dispensing responsibility are explained to the patient.","care":{"action":"Verify the current prescription, lot and quantity; record actual dispensing. Nursing records administrations and missed or changed doses in the clinical workflow.","owner":"Pharmacist & nursing team","record":"Prescription · actual dispense · administration · remaining quantity"},"finance":{"action":"Apply the accepted charge basis and unit conversions; reconcile partial dispensing, returns and corrections with the source records.","owner":"Billing & coding team","record":"Actual quantity · charge basis · return or correction reference"},"handover":"A dispense record is not proof that the medication was administered; both remain traceable."},{"title":"Continue care & control supplies","patient":"Each shift knows the current plan, outstanding tests and the person responsible for follow-up.","care":{"action":"Review observations, repeat requests and outstanding actions at handover. Record departmental supply issues, returns and unit transfers with actual quantities.","owner":"Clinician & nurse","record":"Handover · new requests · supply movements · open actions"},"finance":{"action":"Review new service dates and repeat-service evidence against coverage and approvals. Separate legitimate repeat work from duplicate records or interface replay.","owner":"Revenue cycle team","record":"Service dates · repeat-work evidence · approval review · reconciliation"},"handover":"If escalation to ICU is needed, a documented transfer carries the current treatment and pending responsibilities."},{"title":"Discharge with outstanding work assigned","patient":"The patient receives a medication list, instructions, follow-up plan and contact for pending reports.","care":{"action":"Document the discharge decision and summary, reconcile medication and allocate follow-up for incomplete reports or requested appointments.","owner":"Clinician & nurse","record":"Summary · medication reconciliation · pending-results list · follow-up"},"finance":{"action":"Reconcile ward, pharmacy and diagnostic service evidence; review coding and patient-liability facts before explaining the financial statement.","owner":"Billing & coding team","record":"Reviewed charges · coding evidence · liability review · statement"},"handover":"An outstanding result or payer response remains assigned after discharge rather than disappearing with the encounter."},{"title":"Resolve the payer response","patient":"The patient is referred to the responsible team for questions about the reviewed balance.","care":{"action":"Answer an authorized clinical query with encounter-linked evidence; preserve the original note and any approved amendment.","owner":"Clinician & nurse","record":"Evidence request · author response · approved amendment"},"finance":{"action":"Submit through the activated route and classify responses. Resolve missing data, coverage disputes or clinical appeals through their distinct workflows.","owner":"Revenue cycle team","record":"Claim · response class · remedy · resubmission or appeal reference"},"handover":"A payer denial is a review responsibility; contractual adjustments and patient liability require separate decisions."},{"title":"Match payment & retain follow-up","patient":"The patient sees explained balance changes while the clinical follow-up remains available.","care":{"action":"Keep follow-up responsibility active and reconcile corrected diagnostic, medication or inventory records with their original references.","owner":"Clinician & nurse","record":"Follow-up record · correction history · reconciled stock"},"finance":{"action":"Allocate actual payment against reviewed claim or invoice lines, investigate partial settlements and retain approved adjustments and remaining balances.","owner":"Finance & reconciliation team","record":"Payment allocation · unmatched items · adjustment approval · open balance"},"handover":"Clinical completion and financial reconciliation each have their own evidence and owner."}]},{"title":"A specialist visit connects the hospital around the person.","summary":"A specialist consultation leads to requested diagnostics and, when indicated, a day procedure. The patient sees the next step and a clear self-pay estimate while services, stock and payments stay connected.","stages":[{"title":"Book the specialist visit","patient":"The patient chooses an available appointment and receives preparation and contact information.","care":{"action":"Link the person, clinic, practitioner and visit type; record referral details and communication needs in the encounter.","owner":"Patient access team","record":"Patient · booking · referral · encounter"},"finance":{"action":"Confirm the payment route and consultation tariff; explain what the initial estimate includes and what still requires a clinical decision.","owner":"Billing & coding team","record":"Consultation estimate · payment route · stated assumptions"},"handover":"The patient arrives with an appointment, named team and clear initial administrative scope."},{"title":"Consult & agree the next step","patient":"The specialist explains requested investigations and how results will be discussed.","care":{"action":"Document assessment and requested laboratory or imaging work with the clinical question, priority and result-review responsibility.","owner":"Clinician & nurse","record":"Consultation note · requests · result-review owner"},"finance":{"action":"Update the estimate for the requested scope using configured services. If insurance is selected, begin eligibility and approval review instead of assuming self-pay.","owner":"Billing & coding team","record":"Updated estimate · selected payment route · coverage review if needed"},"handover":"The patient can distinguish a proposed investigation from a performed service and final charge."},{"title":"Complete diagnostic department visits","patient":"The patient visits the requested departments with linked requests and preparation information.","care":{"action":"Collect and identify specimens, link imaging accessions and return reviewed reports. Record supplies used and responsibility for delayed or corrected reports.","owner":"Clinician & nurse","record":"Specimen · study · report · supply usage · communication"},"finance":{"action":"Review actual diagnostic activity against the estimate and charge rules. Cancelled requests and repeat interface messages do not become additional performed services.","owner":"Billing & coding team","record":"Performed services · charge review · cancelled-request references"},"handover":"The specialist receives results linked to the original clinical question and reviewed version."},{"title":"Add a day procedure only if indicated","patient":"The patient receives an explanation of the additional procedure, preparation and revised financial scope.","care":{"action":"If indicated, schedule resources, complete the accepted consent and checks, document the procedure and recovery, and track actual medication and supplies.","owner":"Surgical, anesthesia & recovery teams","record":"Procedure request · session · consent · procedure and recovery record"},"finance":{"action":"Issue a revised estimate and record agreed terms or the applicable approval. After the procedure, review performed scope and unused supply returns.","owner":"Billing & coding team","record":"Revised estimate · agreement or approval · procedure charge evidence"},"handover":"If no procedure is indicated, this branch is skipped and the visit continues to the agreed care plan."},{"title":"Review & dispense the prescription","patient":"The patient receives the actual supplied quantity, usage instructions and a contact for any remainder.","care":{"action":"Verify medication and select the appropriate lot; record actual dispensing and authorized substitution with the prescribing request and encounter.","owner":"Pharmacist & nursing team","record":"Prescription · lot · quantity · handover time · substitution if approved"},"finance":{"action":"Review supplied quantities and unit conversions; explain medication charges or the separately agreed external-dispensing route.","owner":"Billing & coding team","record":"Dispense evidence · applicable charge · payment-route allocation"},"handover":"The remaining prescription, stock movement and charge review have separate responsible owners."},{"title":"Close the visit with a follow-up plan","patient":"The patient knows when and with whom results, treatment or a pending procedure report will be reviewed.","care":{"action":"Record the reviewed results and plan; name the contact for pending reports and book the follow-up where appropriate.","owner":"Clinician & nurse","record":"Visit summary · reviewed reports · pending items · follow-up booking"},"finance":{"action":"Compare the final reviewed activity with the estimate and explain differences, cancellations and applicable patient-liability facts.","owner":"Billing & coding team","record":"Estimate comparison · reviewed charges · financial explanation"},"handover":"The patient has a clinical follow-up contact and a financial contact for the statement."},{"title":"Invoice, allocate & explain payment","patient":"The patient receives an explained invoice, payment reference and any outstanding balance.","care":{"action":"Retain the consultation, diagnostic, procedure and dispensing evidence behind the accepted service set.","owner":"Clinician & nurse","record":"Encounter-linked notes · reports · procedure and dispense evidence"},"finance":{"action":"Allocate actual cash and deposits to invoice items. For insured or mixed payment, split responsibility under accepted rules and track the claim independently.","owner":"Finance & reconciliation team","record":"Invoice · payment allocation · payer or patient responsibility · claim if selected"},"handover":"National e-invoice and payer exchanges use only the accepted, activated interface scope."},{"title":"Handle returns, refunds & open work","patient":"The patient can ask about a pending report, remaining medication or approved refund using the same visit reference.","care":{"action":"Keep pending-result responsibility and medication follow-up active; inventory and pharmacy reconcile approved returns without deleting the original history.","owner":"Clinician & nurse","record":"Open clinical work · supply return · original dispense reference"},"finance":{"action":"Review the financial effect of returns, unused deposits or corrected services; authorize credits or refunds and match them to actual transactions.","owner":"Finance & reconciliation team","record":"Adjustment reason · approval · refund or credit · reconciled balance"},"handover":"The visit may be clinically complete while an identified report, claim or refund remains in follow-up."}]}]},"ar":{"url":"https://mansoq.com/platform/departments?lang=ar","title":"أقسام المستشفى ورحلة المريض والإيرادات | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"عمق لكل فريق قسمي مع سياق رعاية مشترك.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"عمق لكل فريق قسمي مع سياق رعاية مشترك.","description":"تابع أربع رحلات للرعاية والإيراد عبر العمليات والعناية المركزة والمختبر والتصوير والصيدلية والمخزون، مع الأدوار والتسليم والاستثناءات.","answers":[{"question":"كيف ترتبط الرعاية والسجلات المالية عبر الأقسام؟","answer":"تربط هوية المريض والزيارة الطلبات والعينات والتقارير والأدوية والإجراءات وحركة المخزون. تدعم أدلة الخدمات المعتمدة تسجيل الرسوم والمتابعة المالية. توضح الرحلات الأربع مسؤولين وسجلات مستقلة للرعاية والرسوم والفواتير والمطالبات وردود التأمين والنقد؛ قبول المطالبة ليس دفعاً.","href":"/platform/departments#department-journeys"}],"overview":{"title":"كل قسم، مترابط.","summary":"عمل تخصصي متصل بالشخص والفريق التالي.","areas":[{"name":"غرفة العمليات","purpose":"اربط التحضير والتدخل والتعافي حول الشخص.","functions":["حجز الحالة","التحضير","الإجراء","المستهلكات","تسليم التعافي"],"details":"/platform/operating-room"},{"name":"العناية المركزة","purpose":"اربط مسؤوليات العناية الحرجة بالسياق السريري.","functions":["سجل العناية الحرجة","الملاحظات","الأدوية"],"details":"/platform/icu"},{"name":"الصيدلية","purpose":"اربط الوصفة وعمل القسم والخطوة التالية للمريض.","functions":["طلب الدواء","الصرف","تشغيل المخزون"],"details":"/platform/pharmacy"},{"name":"المختبر","purpose":"أعد ربط العمل التشخيصي بسياق الرعاية ذي الصلة.","functions":["الطلبات","العينات","النتائج"],"details":"/platform/laboratory"},{"name":"الأشعة","purpose":"اربط طلبات التصوير وتقاريره برعاية الشخص.","functions":["الطلبات","تشغيل القسم","التقارير"],"details":"/platform/radiology"},{"name":"المخزون","purpose":"اربط الإمدادات المطلوبة بمسؤوليات الأقسام.","functions":["المخزون","المستودعات","تزويد الأقسام"],"details":"/platform/inventory"}]},"patientAndFinancialJourneys":[{"title":"دخول عاجل. وكل تسليم مترابط.","summary":"ينتقل دخول من الطوارئ عبر الفحوص وإجراء يقرره الفريق والعناية المركزة والتعافي. تربط الزيارة نفسها أدلة الأقسام بالمتابعة المالية.","stages":[{"title":"الاستقبال والتعريف","patient":"يحصل المريض أو الأسرة على جهة تواصل محددة بينما يبدأ التقييم العاجل.","care":{"action":"افتح زيارة الطوارئ وراجع الهوية وسجّل الفريق السريري. اتبع إجراء الهوية المؤقتة المعتمد عند نقص البيانات.","owner":"فريق وصول المريض","record":"معرّف المريض · الزيارة · الموقع · الفريق المسؤول"},"finance":{"action":"تحقق من التغطية وسجّل المعروف والناقص ووقت التحقق. أحل الأهلية غير المحسومة لمراجع بالتوازي مع التقييم السريري.","owner":"فريق دورة الإيرادات","record":"دليل التغطية · رد الأهلية أو مهمة المراجعة"},"handover":"يتلقى الفريق التالي هوية الزيارة والمسؤوليات المعلقة؛ ويبقى عدم اليقين المالي ظاهراً."},{"title":"الفحوص بالتوازي","patient":"يُشرح للمريض ما طُلب من فحوص ومن سيراجعها.","care":{"action":"اربط طلبات المختبر بالعينات وطلبات التصوير بمعرّفات التسجيل والدراسة. أعد التقارير المراجعة إلى الزيارة الطالبة.","owner":"الطبيب والممرض","record":"الطلب ← العينة أو الدراسة ← التقرير ← المراجع"},"finance":{"action":"واءم النشاط المكتمل مع الخدمات والترميز المهيأ. ميّز المطلوب والملغى والمنفذ وراجع متطلبات الموافقة.","owner":"فريق الفوترة والترميز","record":"دليل الخدمة المنفذة · بند قيد المراجعة · حالة الموافقة"},"handover":"تتولى المراجعة السريرية قرار الرعاية التالي. تبقى حالة التقرير ومراجعة الرسوم مستقلتين."},{"title":"تحضير الإجراء وتنفيذه","patient":"يحصل المريض على شرح الفريق وإجراءات الموافقة المطلوبة.","care":{"action":"سجّل الفريق والغرفة والتحضير ومراجع الموافقة وفحوص السلامة. وثق الإجراء المنفذ والأدوية والمستهلكات الفعلية للإفاقة.","owner":"فرق الجراحة والتخدير والإفاقة","record":"سجل الإجراء · القائمة · الأدوية · استخدام المستلزمات"},"finance":{"action":"راجع أدلة الإجراء والمستهلكات وفق التعريفة والعقد. استبعد الأصناف المخططة غير المستخدمة من مراجعة الرسوم وتابع تغير نطاق الموافقة.","owner":"فريق الفوترة والترميز","record":"دليل الخدمة والكمية · مراجعة الرسوم · تعديل الموافقة"},"handover":"تستلم الإفاقة العلاج الحالي وسجل الإجراء والإجراءات المعلقة ومسؤوليها."},{"title":"الاستقبال في العناية","patient":"تعرف الأسرة الوحدة المستلمة وطريقة تلقي المستجدات.","care":{"action":"سجّل السرير المستلم والتقييمات والقياسات ومسؤوليات الفحوص. أكد مواءمة الجهاز والزيارة عند شمول تغذية مختبرة.","owner":"العناية المركزة والجناح المستلم","record":"موقع العناية · القياسات · الخطة الحالية · التقارير المعلقة"},"finance":{"action":"راجع الموقع وتواريخ الخدمات وفق العقد والتغطية المعتمدين. صعّد الموافقة الناقصة أو المتجاوزة بدلاً من افتراض اعتمادها.","owner":"فريق دورة الإيرادات","record":"تواريخ الخدمات · مراجعة التغطية · مهمة متابعة الدافع"},"handover":"يحدد تسليم النقل أو المناوبة الفريق التالي ومسؤول كل تقرير وطلب معلق."},{"title":"توفير الأدوية والمستلزمات","patient":"يتلقى المريض الأدوية وفق خطة الفريق المعالج مع شرح التغييرات.","care":{"action":"تحقق من الوصفات واختر التشغيلات الصالحة وسجّل الكميات المسلمة فعلياً. يوثق التمريض الإعطاء مستقلاً ويسجّل المخزون صرف الأقسام والمرتجعات.","owner":"الصيدلي وفريق التمريض","record":"الطلب · الصرف · الإعطاء · حركة التشغيلة"},"finance":{"action":"طبّق قواعد الوحدات والرسوم المعتمدة على أدلة الصرف أو الاستخدام الفعلي. طابق المرتجعات والكميات الجزئية دون تكرار احتساب النشاط.","owner":"فريق الفوترة والترميز","record":"الكميات الفعلية · تحويل الوحدات · مرجع الرسوم أو التصحيح"},"handover":"يتلقى الجناح الأدوية الحالية ومسؤولية التوريد المتبقي وسجلات المخزون القابلة للتتبع."},{"title":"التعافي والنقل والخروج","patient":"يغادر المريض بتعليمات ومعلومات الأدوية وجهة متابعة محددة.","care":{"action":"وثق قرار النقل والخروج وطابق الأدوية وعيّن مسؤول متابعة للتقارير المعلقة. يقرر الفريق السريري الاستعداد للخروج.","owner":"الطبيب والممرض","record":"ملخص الخروج · قائمة الأدوية · المتابعة · مسؤول النتائج المعلقة"},"finance":{"action":"طابق أدلة الأقسام والترميز والرسوم وافتراضات التزام المريض. اشرح البيان المالي واترك البنود غير المحسومة لفريق مسؤول.","owner":"فريق الفوترة والترميز","record":"بنود رسوم مراجعة · أدلة الفاتورة · البنود المالية المفتوحة"},"handover":"تُتابع حالة الخروج السريري والمتابعة المالية مستقلاً دون اعتبار أي منهما مكتملة ضمنياً."},{"title":"تقديم المطالبة ومتابعتها","patient":"يمكن للمريض سؤال الفريق المسؤول عن الالتزام الموثق وقرارات الدافع غير المحسومة.","care":{"action":"أتح الأدلة السريرية والمؤلفين للمراجعين المخولين. استجب لاستفسار التوثيق بتعديل قابل للتتبع.","owner":"الطبيب والممرض","record":"الأدلة السريرية · استفسار الترميز · تاريخ التعديل"},"finance":{"action":"تحقق من المطالبة وقدّمها عبر مسار الدافع المفعّل. ميّز فشل النقل والرفض التجاري والرفض بعد البت وعيّن التصحيح أو الاعتراض المناسب.","owner":"فريق دورة الإيرادات","record":"هوية المطالبة · الإرسال · الرد · مهمة الرفض أو الاعتراض"},"handover":"يتابع الفريق رد الدافع مقابل المطالبة الأصلية والأدلة دون اعتبار الإرسال سداداً."},{"title":"المطابقة والإقفال المسؤول","patient":"يتلقى المريض رصيداً محدثاً أو شرحاً للاسترداد المعتمد عند انطباقه.","care":{"action":"أبقِ مسؤول المتابعة والإجراءات السريرية المعلقة ظاهرة بعد انتهاء الزيارة واحتفظ بتصحيحات الأقسام والمخزون في سجل التدقيق.","owner":"الطبيب والممرض","record":"حالة المتابعة · السجلات المصححة · مطابقة المخزون"},"finance":{"action":"طابق الإشعارات والنقد الفعلي وبنود المطالبة. حقق في المدفوعات الجزئية أو غير المطابقة واعتمد التسويات وأبقِ أرصدة المريض حتى مطابقتها.","owner":"فريق المالية والمطابقة","record":"الإشعار · الدفع · التخصيص · التسوية المعتمدة · الرصيد المتبقي"},"handover":"أقفل البنود المالية المطابقة فقط؛ وتبقى للأعمال السريرية والمالية المعلقة مسؤولية محددة."}]},{"title":"من قرار العيادة إلى التعافي والمطابقة.","summary":"يربط الإجراء المخطط فحوص ما قبل العملية وتحضير الغرفة واستخدام المخزون والإفاقة والمتابعة. تُراجع التقديرات والموافقات مجدداً عند تغير النطاق الفعلي.","stages":[{"title":"الاتفاق على خطة الإجراء","patient":"يفهم المريض الإجراء المقترح والتحضير والموعد التالي.","care":{"action":"سجّل التقييم وطلب الإجراء ثم نسّق جلسة العمليات والفريق وبيئة الرعاية المطلوبة.","owner":"الطبيب والممرض","record":"زيارة العيادة · الطلب · الجلسة المخططة · الطبيب المسؤول"},"finance":{"action":"راجع الأهلية والشبكة والمنافع والتعريفة. قدّم تقديراً يوضح الافتراضات ووقت التحقق والمبالغ غير المحسومة.","owner":"فريق دورة الإيرادات","record":"إصدار التقدير · دليل التغطية · طلب الموافقة"},"handover":"أكد الموعد التالي والمسؤولية عن التحضير أو الموافقة المعلقة."},{"title":"إكمال الفحوص المطلوبة","patient":"يكمل المريض فحوص الفريق المعالج ويتلقى تعليمات التحضير.","care":{"action":"تتبع العينات والدراسات إلى طلباتها. راجع التقارير وسجّل النتائج المعلقة ووثق أي تغيير للخطة.","owner":"الطبيب والممرض","record":"العينة أو الدراسة · التقرير · المراجعة السريرية · الخطة المعدلة"},"finance":{"action":"راجع خدمات الفحوص المنفذة وحالة الموافقة. أعد حساب التقدير عند تغير التكلفة المتوقعة بسبب نطاق إضافي معتمد.","owner":"فريق الفوترة والترميز","record":"أدلة الفحوص · مواءمة الخدمات · التقدير المعدل"},"handover":"يتلقى فريق الإجراء النتائج المراجعة أو مسؤولاً محدداً لأي تحضير غير محسوم."},{"title":"تأكيد الفريق والغرفة والمستلزمات","patient":"يكمل المريض إجراءات الهوية والموافقة والتحضير المعتمدة مع الفريق.","care":{"action":"أكد موعد الغرفة والكوادر والأجهزة ومراجع الموافقة وفحوص السلامة. يصرف المخزون التشغيلات المناسبة وتتحقق الصيدلية من أدوية الإجراء.","owner":"فرق الجراحة والتخدير والإفاقة","record":"الجلسة · القائمة · صرف المستلزمات · تحضير الأدوية"},"finance":{"action":"أكد نطاق الموافقة وصلاحيتها أو وديعة الدفع المباشر المتفق عليها. الحجز أو حجز المخزون وحده ليس دليلاً على خدمة قابلة للفوترة.","owner":"فريق دورة الإيرادات","record":"قرار الموافقة أو الوديعة · حالة المخطط مقابل المنفذ"},"handover":"يتبع الانتقال للإجراء فحوص الفريق المعتمدة؛ وتبقى الحقائق المالية غير المحسومة مخصصة للمراجعة."},{"title":"توثيق ما نُفذ فعلياً","patient":"يوثق الفريق السريري المسؤول الإجراء والإفاقة الأولية.","care":{"action":"وثق الإجراء والقياسات والأدوية والاستخدام الفعلي للمستهلكات. احتفظ بروابط الطلب والزيارة والمؤلف للإفاقة والمراجعة اللاحقة.","owner":"فرق الجراحة والتخدير والإفاقة","record":"ملاحظات الإجراء · الأدوية · التشغيلات المستخدمة · المؤلف"},"finance":{"action":"راجع رموز الإجراء المنفذ والكميات وفق التعريفة المناسبة. طابق صرف المستلزمات مع الاستخدام والمرتجعات قبل اعتماد بنود الرسوم.","owner":"فريق الفوترة والترميز","record":"أدلة الإجراء · مراجعة الترميز · الكميات · مراجع المرتجعات"},"handover":"تستلم الإفاقة الإجراء الموثق والعلاج الحالي والإجراءات المعلقة."},{"title":"الإفاقة أو النقل عند الحاجة","patient":"يعرف المريض والأسرة إن كانت الخطوة التالية خروجاً أو جناحاً أو عناية مركزة.","care":{"action":"سجّل الإفاقة والفريق المستلم. عند الحاجة للعناية انقل القياسات والأدوية وسياق الإجراء والفحوص المعلقة في التسليم.","owner":"فرق الجراحة والتخدير والإفاقة","record":"ملاحظة الإفاقة · الوجهة · الفريق المستلم · الإجراءات المعلقة"},"finance":{"action":"راجع التحول من حالة يومية إلى تنويم أو عناية وحدّث نطاق التقدير وتابع تعديل الموافقة المناسب.","owner":"فريق دورة الإيرادات","record":"تغير بيئة الرعاية · تعديل التقدير · تعديل الموافقة"},"handover":"العناية مسار مشروط وليست مرحلة روتينية لكل إجراء مخطط."},{"title":"تجهيز الخروج والمتابعة","patient":"يتلقى المريض تعليمات الخروج والأدوية الموصوفة وموعداً أو جهة متابعة.","care":{"action":"طابق الأدوية وسجّل التعليمات وعيّن مسؤول متابعة للتقارير المعلقة بما فيها عينات الإجراء عند انطباقها.","owner":"الطبيب والممرض","record":"سجل الخروج · الصرف الفعلي · المتابعة · مسؤولية التقرير"},"finance":{"action":"راجع مجموعة الخدمات النهائية مقابل التقدير والموافقات والصرف الفعلي. اشرح الالتزام المعتمد والبنود غير المحسومة للمريض.","owner":"فريق الفوترة والترميز","record":"مجموعة خدمات مراجعة · الفاتورة · شرح الالتزام"},"handover":"لتعليمات الخروج وللشرح المالي جهة تواصل محددة لكل منهما."},{"title":"فوترة النشاط المعتمد أو المطالبة به","patient":"يحصل المريض على بيان واضح لمسار الدفع المتفق عليه وأي رصيد متبقٍ.","care":{"action":"أتح أدلة الإجراء والفحوص والأدوية لاستفسارات الفوترة أو التوثيق السريري المخولة.","owner":"الطبيب والممرض","record":"الملاحظات الداعمة · التقارير · أدلة الخدمات"},"finance":{"action":"للتأمين تحقق من المطالبة وتابع الرد. للدفع المباشر راجع الفاتورة وتخصيص الوديعة. استخدم التبادل الوطني ضمن نطاقه المفعّل فقط.","owner":"فريق الفوترة والترميز","record":"المطالبة والرد أو الفاتورة · تخصيص الوديعة · أدلة الإرسال"},"handover":"إرسال المطالبة أو إصدار الفاتورة مستقل عن استلام المال."},{"title":"معالجة التغييرات والمرتجعات والأرصدة","patient":"يمكن للمريض تتبع التسوية أو الاسترداد المعتمد والرصيد النهائي.","care":{"action":"طابق المستلزمات غير المستخدمة وسجلات الأقسام المصححة. أبقِ متابعة ما بعد الإجراء والنتائج المعلقة بمسؤولين محددين.","owner":"مسؤولو المخزون والأقسام","record":"المرتجعات · السجلات المصححة · أدلة المتابعة"},"finance":{"action":"طابق النقد والودائع وإشعارات الدافع مع البنود المراجعة. حقق في الفروق واعتمد الاستردادات أو الأرصدة أو التسويات عبر إجراء المالية المعتمد.","owner":"فريق المالية والمطابقة","record":"تخصيص الدفع · الفرق · الاسترداد أو التسوية المعتمدة"},"handover":"يوضح الإقفال المسدد والمفتوح مع الحفاظ على التاريخ الأصلي."}]},{"title":"الفحوص والعلاج والمتابعة في سياق واحد.","summary":"يجمع التنويم تقارير التشخيص والأدوية والمستلزمات في الرعاية اليومية. يعالج المسار المالي تكرار الخدمات والكميات الجزئية ومراجعة الدافع مع حفظ السياق السريري.","stages":[{"title":"الدخول بسياق مشترك","patient":"يعرف المريض الجناح والفريق المسؤول والخطوات الإدارية المتوقعة.","care":{"action":"اربط الدخول والهوية والموقع والطبيب المسؤول واستلم الإحالة والأدوية الحالية والتاريخ المناسب.","owner":"فريق وصول المريض","record":"زيارة التنويم · السرير · الإحالة · سياق الأدوية"},"finance":{"action":"راجع الوثيقة والعقد وموافقة الدخول وافتراضات التقدير. حدد المنافع أو الموافقة الناقصة كغير محسومة.","owner":"فريق دورة الإيرادات","record":"أدلة الوثيقة · الموافقة · التقدير · مسؤولية المراجعة"},"handover":"يتلقى الجناح الإحالة السريرية وجهة التواصل الإدارية المحددة."},{"title":"التقييم وطلب الفحوص","patient":"يفهم المريض الفحوص والتصوير التي يطلبها فريق الرعاية.","care":{"action":"وثق التقييم والقياسات والطلبات. اربط كل عينة ومعرّف تصوير بالزيارة الطالبة والأولوية.","owner":"الطبيب والممرض","record":"التقييم · القياسات · الطلبات · معرّفات العينات والدراسات"},"finance":{"action":"تحقق إن كانت الخدمات مغطاة أو تتطلب موافقة إضافية وحدد مسؤول القرارات المعلقة وأبلغ بتغير التقدير.","owner":"فريق دورة الإيرادات","record":"مراجعة نطاق الخدمات · طلب الموافقة · تعديل التقدير"},"handover":"تبقى حالة الطلب والموافقة والأولوية السريرية حالات مستقلة."},{"title":"مراجعة التقارير وتحديث الخطة","patient":"يشرح الفريق المعالج النتائج المراجعة وخطوة الرعاية التالية.","care":{"action":"راجع تقارير المختبر والأشعة الصادرة وسجّل الخطة وحدد مسؤولي النتائج المعلقة أو المعدلة.","owner":"الطبيب والممرض","record":"التقارير الصادرة · ملاحظة المراجعة · خطة الرعاية · مسؤول المتابعة"},"finance":{"action":"راجع أدلة الخدمات المكتملة مقابل الرموز والتعريفات. تصحيح التقرير وحده لا يبرر رسوماً ثانية.","owner":"فريق الفوترة والترميز","record":"الخدمات المنفذة · مراجعة الترميز · التحقق من الرسوم المكررة"},"handover":"تنتقل الخطة الحالية وإصدار التقرير للمناوبة التالية بمؤلفيهما وأوقاتهما."},{"title":"توفير الدواء وإعطاؤه","patient":"تُشرح للمريض تغييرات الأدوية وأي مسؤولية صرف متبقية.","care":{"action":"تحقق من الوصفة الحالية والتشغيلة والكمية وسجّل الصرف الفعلي. يوثق التمريض الإعطاء والجرعات الفائتة أو المعدلة في المسار السريري.","owner":"الصيدلي وفريق التمريض","record":"الوصفة · الصرف الفعلي · الإعطاء · الكمية المتبقية"},"finance":{"action":"طبّق أساس الرسوم وتحويل الوحدات المعتمدين وطابق الصرف الجزئي والمرتجعات والتصحيحات مع سجلات المصدر.","owner":"فريق الفوترة والترميز","record":"الكمية الفعلية · أساس الرسوم · مرجع الإرجاع أو التصحيح"},"handover":"سجل الصرف ليس دليلاً على إعطاء الدواء؛ ويبقى كلاهما قابلاً للتتبع."},{"title":"استمرار الرعاية وضبط المستلزمات","patient":"تعرف كل مناوبة الخطة الحالية والفحوص المعلقة والشخص المسؤول عن المتابعة.","care":{"action":"راجع القياسات والطلبات المتكررة والإجراءات المعلقة عند التسليم. سجّل صرف مستلزمات الأقسام والمرتجعات والتحويلات بكمياتها الفعلية.","owner":"الطبيب والممرض","record":"التسليم · الطلبات الجديدة · حركات المستلزمات · الإجراءات المفتوحة"},"finance":{"action":"راجع تواريخ الخدمات الجديدة وأدلة التكرار وفق التغطية والموافقات وميّز العمل المتكرر الفعلي عن تكرار السجلات أو إعادة الرسائل.","owner":"فريق دورة الإيرادات","record":"تواريخ الخدمات · أدلة العمل المتكرر · مراجعة الموافقة · المطابقة"},"handover":"عند الحاجة للتصعيد للعناية ينقل التسليم الموثق العلاج الحالي والمسؤوليات المعلقة."},{"title":"الخروج بمسؤوليات معلقة محددة","patient":"يتلقى المريض قائمة أدوية وتعليمات وخطة متابعة وجهة تواصل للتقارير المعلقة.","care":{"action":"وثق قرار الخروج وملخصه وطابق الأدوية وخصص متابعة للتقارير غير المكتملة أو المواعيد المطلوبة.","owner":"الطبيب والممرض","record":"الملخص · مطابقة الأدوية · قائمة النتائج المعلقة · المتابعة"},"finance":{"action":"طابق أدلة خدمات الجناح والصيدلية والتشخيص وراجع الترميز وحقائق التزام المريض قبل شرح البيان المالي.","owner":"فريق الفوترة والترميز","record":"الرسوم المراجعة · أدلة الترميز · مراجعة الالتزام · البيان"},"handover":"تبقى النتيجة أو استجابة الدافع المعلقة بمسؤول محدد بعد الخروج ولا تختفي بانتهاء الزيارة."},{"title":"معالجة رد الدافع","patient":"يُوجّه المريض للفريق المسؤول عن استفسارات الرصيد المراجع.","care":{"action":"أجب عن الاستفسار السريري المخوّل بأدلة مرتبطة بالزيارة مع حفظ الملاحظة الأصلية والتعديل المعتمد.","owner":"الطبيب والممرض","record":"طلب الأدلة · رد المؤلف · التعديل المعتمد"},"finance":{"action":"قدّم عبر المسار المفعّل وصنّف الردود وعالج نقص البيانات أو نزاع التغطية أو الاعتراض السريري بمساراتها المستقلة.","owner":"فريق دورة الإيرادات","record":"المطالبة · تصنيف الرد · المعالجة · مرجع الإعادة أو الاعتراض"},"handover":"رفض الدافع مسؤولية مراجعة؛ وتتطلب التسويات التعاقدية والتزام المريض قرارات مستقلة."},{"title":"مطابقة الدفع واستمرار المتابعة","patient":"يرى المريض تغيرات الرصيد المفسرة مع استمرار المتابعة السريرية.","care":{"action":"أبقِ مسؤولية المتابعة قائمة وطابق سجلات التشخيص أو الأدوية أو المخزون المصححة مع مراجعها الأصلية.","owner":"الطبيب والممرض","record":"سجل المتابعة · تاريخ التصحيح · المخزون المطابق"},"finance":{"action":"خصص الدفع الفعلي مقابل بنود المطالبة أو الفاتورة المراجعة وحقق في التسويات الجزئية واحتفظ بالتعديلات المعتمدة والأرصدة المتبقية.","owner":"فريق المالية والمطابقة","record":"تخصيص الدفع · البنود غير المطابقة · اعتماد التسوية · الرصيد المفتوح"},"handover":"للاكتمال السريري والمطابقة المالية أدلة ومسؤول مستقل لكل منهما."}]},{"title":"زيارة تخصصية تربط أقسام المستشفى حول المريض.","summary":"تقود استشارة تخصصية إلى فحوص مطلوبة وإجراء يومي عند الحاجة. يرى المريض الخطوة التالية وتقدير دفع مباشر واضحاً مع ارتباط الخدمات والمخزون والمدفوعات.","stages":[{"title":"حجز الزيارة التخصصية","patient":"يختار المريض موعداً متاحاً ويتلقى معلومات التحضير والتواصل.","care":{"action":"اربط الشخص والعيادة والطبيب ونوع الزيارة وسجّل الإحالة واحتياجات التواصل في الزيارة.","owner":"فريق وصول المريض","record":"المريض · الحجز · الإحالة · الزيارة"},"finance":{"action":"أكد مسار الدفع وتعريفة الاستشارة واشرح مشمولات التقدير الأولي وما يحتاج قراراً سريرياً.","owner":"فريق الفوترة والترميز","record":"تقدير الاستشارة · مسار الدفع · الافتراضات المعلنة"},"handover":"يصل المريض بموعد وفريق محدد ونطاق إداري أولي واضح."},{"title":"الاستشارة والاتفاق على الخطوة التالية","patient":"يشرح الأخصائي الفحوص المطلوبة وطريقة مناقشة النتائج.","care":{"action":"وثق التقييم والفحوص المختبرية أو التصوير المطلوب بالسؤال السريري والأولوية ومسؤولية مراجعة النتائج.","owner":"الطبيب والممرض","record":"ملاحظة الاستشارة · الطلبات · مسؤول مراجعة النتائج"},"finance":{"action":"حدّث التقدير للنطاق المطلوب بالخدمات المهيأة. عند اختيار التأمين ابدأ مراجعة الأهلية والموافقة بدلاً من افتراض الدفع المباشر.","owner":"فريق الفوترة والترميز","record":"التقدير المحدث · مسار الدفع المختار · مراجعة التغطية عند الحاجة"},"handover":"يميّز المريض الفحص المقترح عن الخدمة المنفذة والرسوم النهائية."},{"title":"إكمال زيارات أقسام التشخيص","patient":"يزور المريض الأقسام المطلوبة بطلبات مترابطة ومعلومات التحضير.","care":{"action":"اجمع العينات وعرّفها واربط معرّفات التصوير وأعد التقارير المراجعة. سجّل المستلزمات المستخدمة ومسؤولية التقارير المتأخرة أو المصححة.","owner":"الطبيب والممرض","record":"العينة · الدراسة · التقرير · استخدام المستلزمات · التواصل"},"finance":{"action":"راجع نشاط التشخيص الفعلي مقابل التقدير وقواعد الرسوم. لا تتحول الطلبات الملغاة أو الرسائل المتكررة لخدمات إضافية منفذة.","owner":"فريق الفوترة والترميز","record":"الخدمات المنفذة · مراجعة الرسوم · مراجع الطلبات الملغاة"},"handover":"يتلقى الأخصائي نتائج مرتبطة بالسؤال السريري الأصلي والإصدار المراجع."},{"title":"إضافة إجراء يومي عند الحاجة فقط","patient":"يتلقى المريض شرح الإجراء الإضافي والتحضير والنطاق المالي المعدل.","care":{"action":"عند الحاجة جدول الموارد وأكمل الموافقة والفحوص المعتمدة ووثق الإجراء والإفاقة وتتبّع الأدوية والمستلزمات الفعلية.","owner":"فرق الجراحة والتخدير والإفاقة","record":"طلب الإجراء · الجلسة · الموافقة · سجل الإجراء والإفاقة"},"finance":{"action":"أصدر تقديراً معدلاً وسجّل الشروط المتفق عليها أو الموافقة المناسبة. بعد الإجراء راجع النطاق المنفذ ومرتجعات المستلزمات غير المستخدمة.","owner":"فريق الفوترة والترميز","record":"التقدير المعدل · الاتفاق أو الموافقة · أدلة رسوم الإجراء"},"handover":"إذا لم يُقرر الإجراء يُتجاوز هذا المسار وتستمر الزيارة إلى خطة الرعاية المتفق عليها."},{"title":"مراجعة الوصفة وصرفها","patient":"يتلقى المريض الكمية المتوفرة فعلياً وتعليمات الاستخدام وجهة تواصل لأي كمية متبقية.","care":{"action":"تحقق من الدواء واختر التشغيلة المناسبة وسجّل الصرف الفعلي والاستبدال المخوّل مع طلب الوصفة والزيارة.","owner":"الصيدلي وفريق التمريض","record":"الوصفة · التشغيلة · الكمية · وقت التسليم · الاستبدال إن اعتُمد"},"finance":{"action":"راجع الكميات المصروفة وتحويل الوحدات واشرح رسوم الدواء أو مسار الصرف الخارجي المتفق عليه مستقلاً.","owner":"فريق الفوترة والترميز","record":"دليل الصرف · الرسوم المنطبقة · تخصيص مسار الدفع"},"handover":"للوصفة المتبقية وحركة المخزون ومراجعة الرسوم مسؤولون مستقلون."},{"title":"إنهاء الزيارة بخطة متابعة","patient":"يعرف المريض متى ومع من تُراجع النتائج أو العلاج أو تقرير الإجراء المعلق.","care":{"action":"سجّل النتائج المراجعة والخطة وحدد جهة التواصل للتقارير المعلقة واحجز المتابعة عند الحاجة.","owner":"الطبيب والممرض","record":"ملخص الزيارة · التقارير المراجعة · البنود المعلقة · حجز المتابعة"},"finance":{"action":"قارن النشاط النهائي المراجع بالتقدير واشرح الفروق والإلغاءات وحقائق التزام المريض المنطبقة.","owner":"فريق الفوترة والترميز","record":"مقارنة التقدير · الرسوم المراجعة · الشرح المالي"},"handover":"للمريض جهة متابعة سريرية وجهة مالية لاستفسارات البيان."},{"title":"الفوترة وتخصيص الدفع وشرحه","patient":"يتلقى المريض فاتورة مفسرة ومرجع الدفع وأي رصيد متبقٍ.","care":{"action":"احتفظ بأدلة الاستشارة والتشخيص والإجراء والصرف الداعمة لمجموعة الخدمات المعتمدة.","owner":"الطبيب والممرض","record":"ملاحظات مرتبطة بالزيارة · التقارير · أدلة الإجراء والصرف"},"finance":{"action":"خصص النقد والودائع الفعلية لبنود الفاتورة. للتأمين أو الدفع المختلط افصل المسؤولية وفق القواعد المعتمدة وتابع المطالبة مستقلاً.","owner":"فريق المالية والمطابقة","record":"الفاتورة · تخصيص الدفع · مسؤولية الدافع أو المريض · المطالبة عند اختيارها"},"handover":"يُستخدم تبادل الفواتير والمطالبات الوطني ضمن نطاق الربط المعتمد والمفعّل فقط."},{"title":"معالجة المرتجعات والاسترداد والعمل المفتوح","patient":"يمكن للمريض الاستفسار عن تقرير معلق أو دواء متبقٍ أو استرداد معتمد بمرجع الزيارة نفسه.","care":{"action":"أبقِ مسؤولية النتائج ومتابعة الأدوية قائمة وطابق مرتجعات المخزون والصيدلية المعتمدة دون حذف التاريخ الأصلي.","owner":"الطبيب والممرض","record":"العمل السريري المفتوح · إرجاع المستلزمات · مرجع الصرف الأصلي"},"finance":{"action":"راجع الأثر المالي للمرتجعات والودائع غير المستخدمة أو الخدمات المصححة واعتمد الأرصدة أو الاسترداد وطابقها بالمعاملات الفعلية.","owner":"فريق المالية والمطابقة","record":"سبب التسوية · الموافقة · الاسترداد أو الرصيد · الرصيد المطابق"},"handover":"قد تكتمل الزيارة سريرياً بينما يبقى تقرير أو مطالبة أو استرداد محدد قيد المتابعة."}]}]}},{"slug":"/platform/drg","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/drg","title":"DRG / Casemix / Grouper Integration software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license.","description":"Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license. Defined coding/casemix…","answers":[{"question":"What does MANSOQ DRG / Casemix / Grouper Integration cover?","answer":"Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license. Prepare coded episode: Identify the encounter and approved coding inputs required by the selected grouper. Review diagnosis, procedure and episode completeness with the coding owner before grouping. Agree the grouper: Confirm the grouper release, licence, supported input format and delivery route. Establish whether processing is external or supplied in the accepted deployment; test representative coded cases. Review grouping output: Keep the returned grouping result with its episode, input version and review responsibility. Validate errors and unexpected group assignments before using the result in casemix analysis. Correct & compare: Preserve previous results when coding is corrected or a grouper version changes. Agree financial use and reporting definitions separately, then re-test representative episodes after changes.","href":"/platform/drg#module-workflow"},{"question":"What setup data does DRG / Casemix / Grouper Integration need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Clinical workflow configuration (clinical_workflows.csv); Interface specification (interfaces.csv); Assumptions & decisions (assumptions_decisions.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/drg#module-setup"},{"question":"How does DRG / Casemix / Grouper Integration handle exceptions?","answer":"Incomplete coding inputs Return the episode to the named coding reviewer and record missing inputs instead of accepting an unsupported group. Output changes after grouper upgrade Compare the same accepted inputs across versions, explain differences and approve the reporting impact.","href":"/platform/drg#module-exceptions"},{"question":"How does DRG / Casemix / Grouper Integration connect with other systems?","answer":"DRG capability requires an agreed licensed grouper and supported integration. No particular grouper, national reimbursement rule or automatic financial outcome is implied.","href":"/platform/drg#module-connections"}],"module":{"name":"DRG / Casemix / Grouper Integration","functions":["Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license."],"workflow":[{"title":"Prepare coded episode","action":"Identify the encounter and approved coding inputs required by the selected grouper. Review diagnosis, procedure and episode completeness with the coding owner before grouping.","owner":"Clinical coding team","record":"Episode reference, coding inputs and completeness review"},{"title":"Agree the grouper","action":"Confirm the grouper release, licence, supported input format and delivery route. Establish whether processing is external or supplied in the accepted deployment; test representative coded cases.","owner":"Coding and integration owner","record":"Grouper version, licence, mapping and test evidence"},{"title":"Review grouping output","action":"Keep the returned grouping result with its episode, input version and review responsibility. Validate errors and unexpected group assignments before using the result in casemix analysis.","owner":"Casemix reviewer","record":"Grouping result, input version and review evidence"},{"title":"Correct & compare","action":"Preserve previous results when coding is corrected or a grouper version changes. Agree financial use and reporting definitions separately, then re-test representative episodes after changes.","owner":"Coding, analytics and finance","record":"Correction reason, result versions and approved reporting use"}],"exceptions":[{"situation":"Incomplete coding inputs","response":"Return the episode to the named coding reviewer and record missing inputs instead of accepting an unsupported group."},{"situation":"Output changes after grouper upgrade","response":"Compare the same accepted inputs across versions, explain differences and approve the reporting impact."}],"connection":"DRG capability requires an agreed licensed grouper and supported integration. No particular grouper, national reimbursement rule or automatic financial outcome is implied.","scenarios":[{"title":"Accepted coded episode to casemix review","situation":"Coding staff prepare an episode for the selected licensed grouper and analytics review.","preparation":"Complete coded inputs, episode identifier, grouper licence and version and approved processing route.","steps":["Review episode and coding completeness against the selected grouper inputs.","Send or process the accepted input through the agreed integration route.","Link the returned result to its episode and input version and review exceptions.","Use only accepted results in the agreed casemix view and approved financial scope."],"acceptance":"The result is reproducible from the identified inputs and grouper version."},{"title":"Coding correction across a grouper upgrade","situation":"An episode is corrected while reporting moves to another accepted grouper version.","preparation":"Prior inputs and results, correction reason, both versions and reporting approval.","steps":["Preserve the original episode inputs and grouping result.","Have the coding reviewer approve the corrected clinical inputs.","Compare outputs using the accepted versions and explain differences.","Approve the reporting effect and retain both historical and corrected result references."],"acceptance":"A changed group is attributable to coding or version changes rather than an unexplained overwrite."}],"setupFiles":[{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/drg?lang=ar","title":"تكامل DRG ومزيج الحالات والتجميع | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل.","description":"مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل. مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم…","answers":[{"question":"ما نطاق تكامل DRG ومزيج الحالات والتجميع في منسوق؟","answer":"مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل. تحضير الحالة المرمزة: حدد الزيارة ومدخلات الترميز المطلوبة لأداة التجميع المختارة. راجع اكتمال التشخيص والإجراء والحالة مع مسؤول الترميز قبل التجميع. تحديد أداة التجميع: أكد إصدار الأداة وترخيصها وصيغة المدخلات وطريقة التنفيذ. حدد المعالجة الخارجية أو المشمولة واختبر حالات مرمزة نموذجية. مراجعة ناتج التجميع: احفظ نتيجة التجميع والحالة وإصدار المدخلات ومسؤولية المراجعة. تحقق من الأخطاء والمجموعات غير المتوقعة قبل تحليل مزيج الحالات. التصحيح والمقارنة: احفظ النتائج السابقة عند تصحيح الترميز أو تغيير إصدار الأداة. اتفق على الاستخدام المالي وتعريفات التقارير وأعد اختبار حالات نموذجية بعد التغيير.","href":"/platform/drg#module-workflow"},{"question":"ما بيانات إعداد تكامل DRG ومزيج الحالات والتجميع؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة المسارات السريرية (clinical_workflows.csv)؛ مواصفات الربط (interfaces.csv)؛ الافتراضات والقرارات (assumptions_decisions.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/drg#module-setup"},{"question":"كيف يتعامل تكامل DRG ومزيج الحالات والتجميع مع الاستثناءات؟","answer":"مدخلات ترميز غير مكتملة أعد الحالة لمراجع الترميز المحدد وسجّل المدخلات المفقودة دون قبول مجموعة غير مدعومة. تغير الناتج بعد تحديث الأداة قارن المدخلات نفسها عبر الإصدارات وفسر الفروق واعتمد أثرها على التقارير.","href":"/platform/drg#module-exceptions"},{"question":"كيف يتصل تكامل DRG ومزيج الحالات والتجميع بالأنظمة الأخرى؟","answer":"تتطلب قدرة DRG أداة تجميع مرخّصة متفقاً عليها وربطاً مدعوماً. لا يفترض ذلك أداة معينة أو قاعدة سداد وطنية أو نتيجة مالية تلقائية.","href":"/platform/drg#module-connections"}],"module":{"name":"تكامل DRG ومزيج الحالات والتجميع","functions":["مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل."],"workflow":[{"title":"تحضير الحالة المرمزة","action":"حدد الزيارة ومدخلات الترميز المطلوبة لأداة التجميع المختارة. راجع اكتمال التشخيص والإجراء والحالة مع مسؤول الترميز قبل التجميع.","owner":"فريق الترميز السريري","record":"مرجع الحالة ومدخلات الترميز ومراجعة الاكتمال"},{"title":"تحديد أداة التجميع","action":"أكد إصدار الأداة وترخيصها وصيغة المدخلات وطريقة التنفيذ. حدد المعالجة الخارجية أو المشمولة واختبر حالات مرمزة نموذجية.","owner":"مسؤول الترميز والربط","record":"إصدار الأداة والترخيص والمواءمة وأدلة الاختبار"},{"title":"مراجعة ناتج التجميع","action":"احفظ نتيجة التجميع والحالة وإصدار المدخلات ومسؤولية المراجعة. تحقق من الأخطاء والمجموعات غير المتوقعة قبل تحليل مزيج الحالات.","owner":"مراجع مزيج الحالات","record":"نتيجة التجميع وإصدار المدخلات وأدلة المراجعة"},{"title":"التصحيح والمقارنة","action":"احفظ النتائج السابقة عند تصحيح الترميز أو تغيير إصدار الأداة. اتفق على الاستخدام المالي وتعريفات التقارير وأعد اختبار حالات نموذجية بعد التغيير.","owner":"الترميز والتحليلات والمالية","record":"سبب التصحيح وإصدارات النتائج والاستخدام المعتمد"}],"exceptions":[{"situation":"مدخلات ترميز غير مكتملة","response":"أعد الحالة لمراجع الترميز المحدد وسجّل المدخلات المفقودة دون قبول مجموعة غير مدعومة."},{"situation":"تغير الناتج بعد تحديث الأداة","response":"قارن المدخلات نفسها عبر الإصدارات وفسر الفروق واعتمد أثرها على التقارير."}],"connection":"تتطلب قدرة DRG أداة تجميع مرخّصة متفقاً عليها وربطاً مدعوماً. لا يفترض ذلك أداة معينة أو قاعدة سداد وطنية أو نتيجة مالية تلقائية.","scenarios":[{"title":"حالة مرمزة معتمدة لمراجعة مزيج الحالات","situation":"يجهز فريق الترميز حالة لأداة التجميع المرخصة ومراجعة التحليلات.","preparation":"مدخلات كاملة ومعرّف حالة وترخيص وإصدار أداة ومسار معالجة معتمد.","steps":["راجع اكتمال الحالة والترميز وفق مدخلات الأداة.","عالج المدخل المعتمد عبر مسار الربط المتفق عليه.","اربط النتيجة بالحالة والإصدار وراجع الاستثناءات.","استخدم النتائج المقبولة فقط للتحليل والنطاق المالي المعتمد."],"acceptance":"يمكن إعادة إنتاج النتيجة من المدخلات وإصدار الأداة المحددين."},{"title":"تصحيح ترميز أثناء تحديث أداة التجميع","situation":"تُصحح حالة أثناء انتقال التقارير لإصدار أداة معتمد آخر.","preparation":"مدخلات ونتائج سابقة وسبب تصحيح وإصداران واعتماد تقارير.","steps":["احفظ المدخلات والنتيجة الأصلية.","يعتمد مراجع الترميز المدخلات المصححة.","قارن المخرجات بالإصدارات المعتمدة وفسر الفروق.","اعتمد أثر التقارير واحفظ مراجع النتائج السابقة والمصححة."],"acceptance":"ينسب تغير المجموعة للترميز أو الإصدار دون استبدال غير مفسر."}],"setupFiles":[{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/emergency","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/emergency","title":"Emergency Care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Emergency encounter context, observations and accountable care handovers according to verified operational scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Emergency encounter context, observations and accountable care handovers according to verified operational scope.","description":"Emergency encounter context, observations and accountable care handovers according to verified operational scope. Emergency encounter context, observations and accountable care…","answers":[{"question":"What does MANSOQ Emergency Care cover?","answer":"Emergency encounter context, observations and accountable care handovers according to verified operational scope. Receive: Record the arrival and establish identity using the locally approved process, including the temporary-identity route where required. Open the emergency encounter and assign the location and team. Assess & prioritize: Capture the presenting concern and observations. Configure your approved triage categories and escalation responsibilities; clinical priority remains the care team’s decision. Treat & observe: Document care, medication and urgent requests. Keep results and repeat observations attached to the encounter and identify who owns each outstanding action during observation. Determine destination: Document discharge, admission or transfer with the receiving team, current treatment and pending requests. Billing and insurance tasks follow their authorized workflow without replacing clinical disposition.","href":"/platform/emergency#module-workflow"},{"question":"What setup data does Emergency Care need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Rooms, wards and beds (locations.csv); Users & department access (user_access.csv); Doctors & operational clinics (doctors.csv); Clinical workflow configuration (clinical_workflows.csv); Assets, devices & hardware (assets_devices.csv); Services & department catalogue (services.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/emergency#module-setup"},{"question":"How does Emergency Care handle exceptions?","answer":"Identity remains unresolved Use the approved temporary identification procedure, flag later matching and preserve all encounter references during correction. Deterioration during observation Record the reassessment and invoke the local escalation pathway; carry the current medication and orders into the receiving service.","href":"/platform/emergency#module-exceptions"},{"question":"How does Emergency Care connect with other systems?","answer":"Emergency documentation connects to selected diagnostic, inpatient and critical-care services. Triage rules, escalation thresholds and emergency policies must be approved locally.","href":"/platform/emergency#module-connections"}],"module":{"name":"Emergency Care","functions":["Emergency encounter context, observations and accountable care handovers according to verified operational scope."],"workflow":[{"title":"Receive","action":"Record the arrival and establish identity using the locally approved process, including the temporary-identity route where required. Open the emergency encounter and assign the location and team.","owner":"Emergency registration","record":"Patient identification, arrival and emergency encounter"},{"title":"Assess & prioritize","action":"Capture the presenting concern and observations. Configure your approved triage categories and escalation responsibilities; clinical priority remains the care team’s decision.","owner":"Triage nurse and emergency clinician","record":"Assessment, observations and locally approved priority"},{"title":"Treat & observe","action":"Document care, medication and urgent requests. Keep results and repeat observations attached to the encounter and identify who owns each outstanding action during observation.","owner":"Emergency care and department teams","record":"Orders, administration, results and observation records"},{"title":"Determine destination","action":"Document discharge, admission or transfer with the receiving team, current treatment and pending requests. Billing and insurance tasks follow their authorized workflow without replacing clinical disposition.","owner":"Emergency clinician and receiving team","record":"Disposition, receiving location and handover record"}],"exceptions":[{"situation":"Identity remains unresolved","response":"Use the approved temporary identification procedure, flag later matching and preserve all encounter references during correction."},{"situation":"Deterioration during observation","response":"Record the reassessment and invoke the local escalation pathway; carry the current medication and orders into the receiving service."}],"connection":"Emergency documentation connects to selected diagnostic, inpatient and critical-care services. Triage rules, escalation thresholds and emergency policies must be approved locally.","scenarios":[{"title":"Arrival, assessment and discharge","situation":"A walk-in patient is assessed, treated and discharged after emergency review.","preparation":"Arrival and triage policy, emergency locations, clinician roles and service catalogue.","steps":["Reception establishes identity and the emergency encounter.","The nurse records observations and the clinician determines priority and requests.","The team documents treatment and reviews completed investigations.","The clinician records disposition, advice and follow-up while billing follows performed activity."],"acceptance":"Clinical disposition, treatment, results and follow-up are recorded independently of financial tasks."},{"title":"Unidentified arrival followed by admission","situation":"Urgent care starts using the approved temporary-identity procedure and the person is later identified.","preparation":"Temporary identifier process, identity reviewer, admission location and handover policy.","steps":["Use the locally approved identity process and record the arrival and assessment.","Document treatment, requests and observations against the temporary encounter context.","An authorized reviewer resolves identity while retaining all clinical references.","Hand over to the admitting team with active treatment, pending results and the corrected identity."],"acceptance":"The identity correction preserves the care timeline and the receiving team knows every outstanding action."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/emergency?lang=ar","title":"رعاية الطوارئ | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه.","description":"سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه. سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه..","answers":[{"question":"ما نطاق رعاية الطوارئ في منسوق؟","answer":"سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه. الاستقبال: سجّل الوصول وحدد الهوية وفق الإجراء المحلي المعتمد بما في ذلك مسار الهوية المؤقتة عند الحاجة. افتح زيارة الطوارئ وحدد الموقع والفريق. التقييم وتحديد الأولوية: سجّل الشكوى والقياسات. هيئ فئات الفرز ومسؤوليات التصعيد المعتمدة؛ تبقى الأولوية السريرية قرار فريق الرعاية. العلاج والملاحظة: وثق الرعاية والأدوية والطلبات العاجلة. اربط النتائج والقياسات المتكررة بالزيارة وحدد مسؤول كل إجراء معلق أثناء الملاحظة. تحديد الوجهة: وثق الخروج أو التنويم أو النقل مع الفريق المستلم والعلاج الحالي والطلبات المعلقة. تتبع الفوترة والتأمين مسارهما المخوّل دون استبدال قرار الرعاية.","href":"/platform/emergency#module-workflow"},{"question":"ما بيانات إعداد رعاية الطوارئ؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الغرف والأجنحة والأسرة (locations.csv)؛ المستخدمون وصلاحيات الأقسام (user_access.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ الخدمات ودليل الأقسام (services.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/emergency#module-setup"},{"question":"كيف يتعامل رعاية الطوارئ مع الاستثناءات؟","answer":"عدم اكتمال الهوية استخدم إجراء الهوية المؤقتة المعتمد وحدد الحاجة للمطابقة اللاحقة واحتفظ بمراجع الزيارة عند التصحيح. تدهور أثناء الملاحظة سجّل إعادة التقييم وفعّل مسار التصعيد المحلي وانقل الأدوية والطلبات الحالية للخدمة المستلمة.","href":"/platform/emergency#module-exceptions"},{"question":"كيف يتصل رعاية الطوارئ بالأنظمة الأخرى؟","answer":"يرتبط توثيق الطوارئ بالتشخيص والتنويم والعناية الحرجة المختارة. يجب اعتماد قواعد الفرز وحدود التصعيد وسياسات الطوارئ محلياً.","href":"/platform/emergency#module-connections"}],"module":{"name":"رعاية الطوارئ","functions":["سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه."],"workflow":[{"title":"الاستقبال","action":"سجّل الوصول وحدد الهوية وفق الإجراء المحلي المعتمد بما في ذلك مسار الهوية المؤقتة عند الحاجة. افتح زيارة الطوارئ وحدد الموقع والفريق.","owner":"تسجيل الطوارئ","record":"هوية المريض والوصول وزيارة الطوارئ"},{"title":"التقييم وتحديد الأولوية","action":"سجّل الشكوى والقياسات. هيئ فئات الفرز ومسؤوليات التصعيد المعتمدة؛ تبقى الأولوية السريرية قرار فريق الرعاية.","owner":"ممرض الفرز وطبيب الطوارئ","record":"التقييم والقياسات والأولوية المحلية المعتمدة"},{"title":"العلاج والملاحظة","action":"وثق الرعاية والأدوية والطلبات العاجلة. اربط النتائج والقياسات المتكررة بالزيارة وحدد مسؤول كل إجراء معلق أثناء الملاحظة.","owner":"فرق الطوارئ والأقسام","record":"الطلبات وإعطاء الأدوية والنتائج وسجلات الملاحظة"},{"title":"تحديد الوجهة","action":"وثق الخروج أو التنويم أو النقل مع الفريق المستلم والعلاج الحالي والطلبات المعلقة. تتبع الفوترة والتأمين مسارهما المخوّل دون استبدال قرار الرعاية.","owner":"طبيب الطوارئ والفريق المستلم","record":"قرار الوجهة والموقع المستلم وسجل التسليم"}],"exceptions":[{"situation":"عدم اكتمال الهوية","response":"استخدم إجراء الهوية المؤقتة المعتمد وحدد الحاجة للمطابقة اللاحقة واحتفظ بمراجع الزيارة عند التصحيح."},{"situation":"تدهور أثناء الملاحظة","response":"سجّل إعادة التقييم وفعّل مسار التصعيد المحلي وانقل الأدوية والطلبات الحالية للخدمة المستلمة."}],"connection":"يرتبط توثيق الطوارئ بالتشخيص والتنويم والعناية الحرجة المختارة. يجب اعتماد قواعد الفرز وحدود التصعيد وسياسات الطوارئ محلياً.","scenarios":[{"title":"الوصول والتقييم والخروج","situation":"يصل مريض دون موعد ويُقيّم ويُعالج ويخرج بعد مراجعة الطوارئ.","preparation":"سياسة الوصول والفرز ومواقع الطوارئ والأدوار وكتالوج الخدمات.","steps":["يحدد الاستقبال الهوية وزيارة الطوارئ.","يسجل الممرض القياسات ويحدد الطبيب الأولوية والطلبات.","يوثق الفريق العلاج ويراجع الفحوص المكتملة.","يوثق الطبيب الوجهة والتعليمات والمتابعة وتتبع الفوترة النشاط المنفذ."],"acceptance":"يسجل قرار الرعاية والعلاج والنتائج والمتابعة مستقلاً عن المهام المالية."},{"title":"وصول مجهول الهوية ثم التنويم","situation":"تبدأ الرعاية العاجلة بإجراء هوية مؤقتة معتمد ثم تتحدد هوية الشخص.","preparation":"إجراء المعرّف المؤقت ومراجع الهوية وموقع التنويم وسياسة التسليم.","steps":["استخدم إجراء الهوية المحلي وسجّل الوصول والتقييم.","وثق العلاج والطلبات والقياسات بسياق الزيارة المؤقتة.","يحسم مراجع مخوّل الهوية مع الاحتفاظ بكل المراجع السريرية.","سلّم لفريق التنويم العلاج والنتائج المعلقة والهوية المصححة."],"acceptance":"يحفظ تصحيح الهوية تسلسل الرعاية ويعرف الفريق المستلم كل إجراء معلق."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/extensions","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/extensions","title":"RCM, analytics, AI & healthcare integrations | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Clinical, revenue, Saudi, intelligence and connectivity extensions with exact dependencies.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Clinical, revenue, Saudi, intelligence and connectivity extensions with exact dependencies.","description":"Extend MANSOQ with revenue cycle, clinical documentation, analytics, assistive AI and interfaces. Check required modules, release scope and activation gates.","answers":[],"overview":{"title":"Make your platform more capable.","summary":"Add clinical depth, revenue, intelligence and connections.","areas":[{"name":"Clinical depth","purpose":"Connect documentation, orders and patient access.","functions":["Clinical Documentation & Care Planning","Orders, Results & Medication","Patient Access"]},{"name":"Revenue cycle","purpose":"Connect care activity, billing and payer follow-up.","functions":["Billing & Finance","Revenue Cycle Management"]},{"name":"Intelligence","purpose":"Bring operational insight and reviewed assistance into your scope.","functions":["Advanced Analytics","Reviewed AI Assistance"]},{"name":"Connected systems","purpose":"Connect your systems, devices and governed network.","functions":["System & Device Interfaces","Network Governance"]},{"name":"Saudi compatibility","purpose":"Connect insurance exchange, invoicing and supported coding.","functions":["SBS Specific Mapping Tooling","Full Supported SBS Catalogue Tooling","DRG / Casemix / Grouper Integration","NPHIES","ZATCA E-invoicing"]}]}},"ar":{"url":"https://mansoq.com/platform/extensions?lang=ar","title":"الإيرادات والتحليلات والذكاء والتكاملات | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"إضافات سريرية وإيرادية وسعودية وتحليلية واتصالية بمتطلبات دقيقة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"إضافات سريرية وإيرادية وسعودية وتحليلية واتصالية بمتطلبات دقيقة.","description":"أضف دورة الإيرادات والتوثيق والتحليلات والذكاء المساند والاتصالات إلى منسوق، مع الوحدات المطلوبة ونطاق الإصدار وبوابات التفعيل.","answers":[],"overview":{"title":"امنح منصتك إمكانات أوسع.","summary":"أضف العمق السريري والإيرادات والتحليلات والربط.","areas":[{"name":"عمق سريري","purpose":"اربط التوثيق والطلبات ووصول المريض.","functions":["التوثيق السريري وتخطيط الرعاية","الطلبات والنتائج والأدوية","وصول المريض إلى الرعاية"]},{"name":"دورة الإيرادات","purpose":"اربط نشاط الرعاية والفوترة ومتابعة الجهات الدافعة.","functions":["الفوترة والمالية","إدارة دورة الإيراد"]},{"name":"الذكاء والتحليلات","purpose":"أضف التحليلات التشغيلية والمساعدة الخاضعة للمراجعة إلى نطاقك.","functions":["التحليلات المتقدمة","مساندة الذكاء الاصطناعي الخاضعة للمراجعة"]},{"name":"الأنظمة المترابطة","purpose":"اربط أنظمتك وأجهزتك وشبكتك المحكومة.","functions":["اتصالات الأنظمة والأجهزة","حوكمة الشبكة"]},{"name":"التوافق السعودي","purpose":"اربط التبادل التأميني والفوترة والترميز المدعوم.","functions":["أدوات مواءمة أكواد SBS المحددة","أدوات كتالوج SBS المدعوم الكامل","تكامل DRG ومزيج الحالات والتجميع","نفيس","الفوترة الإلكترونية مع زاتكا"]}]}}},{"slug":"/platform/home-palliative","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/home-palliative","title":"Home & Palliative Care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope.","description":"Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope. Visits, care plans and…","answers":[{"question":"What does MANSOQ Home & Palliative Care cover?","answer":"Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope. Enroll & plan: Establish the person’s care context, consent and caregiver contacts. Define the service zone, multidisciplinary team and approved home or palliative-care plan with escalation responsibilities. Schedule the visit: Assign the practitioner and visit time, accounting for service area and travel constraints. Confirm required equipment, medication and the information the visiting team needs. Deliver & document: Record the encounter, observations, symptom review and delivered care. Keep medication and service requests with the current plan and document the caregiver discussion and next responsibilities. Continue care: Plan the next visit or referral and hand over unresolved needs to the multidisciplinary team. Reconcile supplied items and delivered services through inventory and billing where selected.","href":"/platform/home-palliative#module-workflow"},{"question":"What setup data does Home & Palliative Care need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Services & department catalogue (services.csv); Clinical workflow configuration (clinical_workflows.csv); Inventory & medication items (stock_items.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/home-palliative#module-setup"},{"question":"How does Home & Palliative Care handle exceptions?","answer":"Visit cancelled or patient unavailable Record the disposition, contact the care coordinator and review rescheduling and any time-sensitive care responsibility. Symptoms require escalation Use the approved clinical contact and referral pathway; document the assessment, advice and receiving service.","href":"/platform/home-palliative#module-exceptions"},{"question":"How does Home & Palliative Care connect with other systems?","answer":"Home-care documentation, scheduling, stock and remote support are selected separately. Offline work, remote devices and route optimization must be explicitly confirmed for the chosen deployment.","href":"/platform/home-palliative#module-connections"}],"module":{"name":"Home & Palliative Care","functions":["Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope."],"workflow":[{"title":"Enroll & plan","action":"Establish the person’s care context, consent and caregiver contacts. Define the service zone, multidisciplinary team and approved home or palliative-care plan with escalation responsibilities.","owner":"Care coordinator and responsible clinician","record":"Patient, consent, caregiver and care-plan references"},{"title":"Schedule the visit","action":"Assign the practitioner and visit time, accounting for service area and travel constraints. Confirm required equipment, medication and the information the visiting team needs.","owner":"Scheduling and visiting team","record":"Practitioner schedule, visit booking and required resources"},{"title":"Deliver & document","action":"Record the encounter, observations, symptom review and delivered care. Keep medication and service requests with the current plan and document the caregiver discussion and next responsibilities.","owner":"Visiting clinician and nurse","record":"Visit notes, observations, medication and care-plan updates"},{"title":"Continue care","action":"Plan the next visit or referral and hand over unresolved needs to the multidisciplinary team. Reconcile supplied items and delivered services through inventory and billing where selected.","owner":"Multidisciplinary and operations team","record":"Follow-up plan, referrals, stock and charge records"}],"exceptions":[{"situation":"Visit cancelled or patient unavailable","response":"Record the disposition, contact the care coordinator and review rescheduling and any time-sensitive care responsibility."},{"situation":"Symptoms require escalation","response":"Use the approved clinical contact and referral pathway; document the assessment, advice and receiving service."}],"connection":"Home-care documentation, scheduling, stock and remote support are selected separately. Offline work, remote devices and route optimization must be explicitly confirmed for the chosen deployment.","scenarios":[{"title":"Home visit with ongoing symptom support","situation":"A multidisciplinary team delivers a planned visit and updates the continuing care plan.","preparation":"Service area, caregiver contacts, consent, visiting-team schedule and approved symptom documentation.","steps":["Confirm the care plan, visit resources and caregiver contact.","Assign the visit to an available practitioner and confirm required supplies.","Document observations, symptom review, delivered care and caregiver discussion.","Update follow-up responsibility and reconcile supplied items and services."],"acceptance":"Visit notes, plan changes, resources and the next visit owner remain connected to the person."},{"title":"Cancelled visit followed by clinical escalation","situation":"A patient is unavailable for a visit and a later caregiver contact reports a change in symptoms.","preparation":"Cancellation disposition, clinical contact, reassessment and referral pathway.","steps":["Record the visit disposition and notify the care coordinator.","Document the caregiver report and route it to the responsible clinician.","The clinician follows the approved assessment and escalation procedure.","Update the referral or next visit plan and hand over unresolved needs."],"acceptance":"Cancelled service, reported symptoms and subsequent clinical actions are recorded as distinct events."}],"setupFiles":[{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/home-palliative?lang=ar","title":"الرعاية المنزلية والتلطيفية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل.","description":"الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل. الزيارات وخطط الرعاية والتوثيق متعدد التخصصات…","answers":[{"question":"ما نطاق الرعاية المنزلية والتلطيفية في منسوق؟","answer":"الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل. التسجيل والتخطيط: حدد سياق الرعاية والموافقة ووسائل التواصل مع مقدم الرعاية. عرّف منطقة الخدمة والفريق والخطة المنزلية أو التلطيفية المعتمدة ومسؤوليات التصعيد. جدولة الزيارة: حدد الممارس ووقت الزيارة مع مراعاة المنطقة والتنقل. أكد الأجهزة والأدوية والمعلومات المطلوبة للفريق الزائر. التقديم والتوثيق: سجّل الزيارة والقياسات ومراجعة الأعراض والرعاية المقدمة. اربط الأدوية والخدمات بالخطة ووثق نقاش مقدم الرعاية والمسؤوليات التالية. استمرار الرعاية: خطط للزيارة التالية أو الإحالة وسلّم الاحتياجات غير المحسومة للفريق المتعدد التخصصات. طابق المستلزمات والخدمات عبر المخزون والفوترة عند اختيارهما.","href":"/platform/home-palliative#module-workflow"},{"question":"ما بيانات إعداد الرعاية المنزلية والتلطيفية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة الجدولة (scheduling.csv)؛ الخدمات ودليل الأقسام (services.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ أصناف المخزون والأدوية (stock_items.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/home-palliative#module-setup"},{"question":"كيف يتعامل الرعاية المنزلية والتلطيفية مع الاستثناءات؟","answer":"إلغاء الزيارة أو غياب المريض سجّل الحالة وتواصل مع منسق الرعاية وراجع إعادة الجدولة ومسؤوليات الرعاية العاجلة. أعراض تستدعي التصعيد استخدم مسار التواصل والإحالة السريري المعتمد ووثق التقييم والمشورة والخدمة المستلمة.","href":"/platform/home-palliative#module-exceptions"},{"question":"كيف يتصل الرعاية المنزلية والتلطيفية بالأنظمة الأخرى؟","answer":"يُختار توثيق الرعاية المنزلية والمواعيد والمخزون والدعم البعيد بصورة مستقلة. يجب تأكيد العمل دون اتصال والأجهزة البعيدة وتحسين المسارات للنشر المختار.","href":"/platform/home-palliative#module-connections"}],"module":{"name":"الرعاية المنزلية والتلطيفية","functions":["الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل."],"workflow":[{"title":"التسجيل والتخطيط","action":"حدد سياق الرعاية والموافقة ووسائل التواصل مع مقدم الرعاية. عرّف منطقة الخدمة والفريق والخطة المنزلية أو التلطيفية المعتمدة ومسؤوليات التصعيد.","owner":"منسق الرعاية والطبيب المسؤول","record":"المريض والموافقة ومقدم الرعاية ومراجع الخطة"},{"title":"جدولة الزيارة","action":"حدد الممارس ووقت الزيارة مع مراعاة المنطقة والتنقل. أكد الأجهزة والأدوية والمعلومات المطلوبة للفريق الزائر.","owner":"فريق الجدولة والزيارة","record":"جدول الممارس وحجز الزيارة والموارد المطلوبة"},{"title":"التقديم والتوثيق","action":"سجّل الزيارة والقياسات ومراجعة الأعراض والرعاية المقدمة. اربط الأدوية والخدمات بالخطة ووثق نقاش مقدم الرعاية والمسؤوليات التالية.","owner":"الطبيب والممرض الزائران","record":"ملاحظات الزيارة والقياسات والأدوية وتحديثات الخطة"},{"title":"استمرار الرعاية","action":"خطط للزيارة التالية أو الإحالة وسلّم الاحتياجات غير المحسومة للفريق المتعدد التخصصات. طابق المستلزمات والخدمات عبر المخزون والفوترة عند اختيارهما.","owner":"الفريق المتعدد التخصصات والتشغيل","record":"خطة المتابعة والإحالات والمخزون والرسوم"}],"exceptions":[{"situation":"إلغاء الزيارة أو غياب المريض","response":"سجّل الحالة وتواصل مع منسق الرعاية وراجع إعادة الجدولة ومسؤوليات الرعاية العاجلة."},{"situation":"أعراض تستدعي التصعيد","response":"استخدم مسار التواصل والإحالة السريري المعتمد ووثق التقييم والمشورة والخدمة المستلمة."}],"connection":"يُختار توثيق الرعاية المنزلية والمواعيد والمخزون والدعم البعيد بصورة مستقلة. يجب تأكيد العمل دون اتصال والأجهزة البعيدة وتحسين المسارات للنشر المختار.","scenarios":[{"title":"زيارة منزلية مع دعم أعراض مستمر","situation":"يقدم فريق متعدد التخصصات زيارة مخططة ويحدث خطة الرعاية.","preparation":"منطقة خدمة وتواصل مقدم الرعاية وموافقة وجدول الفريق وتوثيق الأعراض.","steps":["أكد الخطة والموارد والتواصل مع مقدم الرعاية.","عين الزيارة لممارس متاح وأكد المستلزمات.","وثق القياسات والأعراض والرعاية والنقاش.","حدّث مسؤولية المتابعة وطابق المستلزمات والخدمات."],"acceptance":"ترتبط الملاحظات وتغييرات الخطة والموارد ومسؤول الزيارة التالية بالشخص."},{"title":"إلغاء زيارة ثم تصعيد سريري","situation":"يتعذر حضور المريض لزيارة ثم يبلغ مقدم الرعاية تغير الأعراض.","preparation":"حالة إلغاء وجهة تواصل سريرية وإعادة تقييم ومسار إحالة.","steps":["سجّل حالة الزيارة وأبلغ المنسق.","وثق بلاغ مقدم الرعاية وأحله للطبيب المسؤول.","يتبع الطبيب إجراء التقييم والتصعيد المعتمد.","حدّث الإحالة أو الزيارة التالية وسلّم الاحتياجات المعلقة."],"acceptance":"تسجل الخدمة الملغاة والأعراض المبلغ عنها والإجراءات اللاحقة كأحداث مختلفة."}],"setupFiles":[{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/icu","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/icu","title":"Intensive Care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified.","description":"Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified. Verified critical-care…","answers":[{"question":"What does MANSOQ Intensive Care cover?","answer":"Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified. Receive into the unit: Link the admitted patient to the critical-care location and responsible team. Review the referral, current treatments and outstanding investigations at the initial handover. Observe & document: Keep observations, assessments and care documentation in the encounter. Agree measurement units, recording frequency and local escalation responsibility; automated device feeds require an accepted device connection. Coordinate treatment: Connect orders, medication administration and diagnostic reports to the current plan. Reconcile changes with the bedside team and document the owner of each pending action. Handover & transfer: Review the current record and outstanding responsibilities at each shift or unit transfer. TeleICU review can be added with separately defined remote access, response ownership and device scope.","href":"/platform/icu#module-workflow"},{"question":"What setup data does Intensive Care need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Rooms, wards and beds (locations.csv); Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Assets, devices & hardware (assets_devices.csv); Interface specification (interfaces.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/icu#module-setup"},{"question":"How does Intensive Care handle exceptions?","answer":"Missing or stale device observation Verify the device and encounter mapping, check the timestamp and follow the approved bedside recording and interface recovery procedure. Change in clinical condition Document reassessment and activate the local clinical escalation process; the platform record supports the team’s clinical decision.","href":"/platform/icu#module-exceptions"},{"question":"How does Intensive Care connect with other systems?","answer":"ICU clinical records do not imply every monitor, ventilator or alarm is integrated. Specify device models, supported protocols, responsible clinicians and downtime procedures in the selected scope.","href":"/platform/icu#module-connections"}],"module":{"name":"Intensive Care","functions":["Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified."],"workflow":[{"title":"Receive into the unit","action":"Link the admitted patient to the critical-care location and responsible team. Review the referral, current treatments and outstanding investigations at the initial handover.","owner":"ICU receiving team","record":"Encounter, bed location, team and referral context"},{"title":"Observe & document","action":"Keep observations, assessments and care documentation in the encounter. Agree measurement units, recording frequency and local escalation responsibility; automated device feeds require an accepted device connection.","owner":"ICU nurse and clinician","record":"Observation time, values, units and care documentation"},{"title":"Coordinate treatment","action":"Connect orders, medication administration and diagnostic reports to the current plan. Reconcile changes with the bedside team and document the owner of each pending action.","owner":"Bedside care and department teams","record":"Medication administrations, requests, reports and care plan"},{"title":"Handover & transfer","action":"Review the current record and outstanding responsibilities at each shift or unit transfer. TeleICU review can be added with separately defined remote access, response ownership and device scope.","owner":"Outgoing and receiving care teams","record":"Handover record, destination and unresolved actions"}],"exceptions":[{"situation":"Missing or stale device observation","response":"Verify the device and encounter mapping, check the timestamp and follow the approved bedside recording and interface recovery procedure."},{"situation":"Change in clinical condition","response":"Document reassessment and activate the local clinical escalation process; the platform record supports the team’s clinical decision."}],"connection":"ICU clinical records do not imply every monitor, ventilator or alarm is integrated. Specify device models, supported protocols, responsible clinicians and downtime procedures in the selected scope.","scenarios":[{"title":"Critical-care admission and shift handover","situation":"A patient enters ICU and the next shift must receive a complete current care context.","preparation":"ICU bed, care-team roster, observation definitions, medication workflow and handover policy.","steps":["Receive the referral and assign the patient to the unit location.","Document assessments, observations, medication and diagnostic requests.","Review completed results and update the plan with the responsible clinician.","Hand over current treatment and pending work to the next named team."],"acceptance":"The receiving team can identify the current plan, medication, observation times and pending requests."},{"title":"Device feed interruption during unit transfer","situation":"A selected device connection stops supplying observations while the patient moves to another location.","preparation":"Accepted device mapping, timestamp checks, manual recording procedure and receiving-bed configuration.","steps":["Flag stale or missing source observations and verify the last accepted timestamp.","Continue the approved bedside recording and escalation process.","Update the accepted patient, encounter and device-location mapping for the receiving unit.","Reconcile recovered observations and hand over the gap and treatment record."],"acceptance":"No recovered observation is attributed to another patient; the data gap and bedside responsibility are documented."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/icu?lang=ar","title":"العناية المركزة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار.","description":"نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار. نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية…","answers":[{"question":"ما نطاق العناية المركزة في منسوق؟","answer":"نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار. الاستقبال في الوحدة: اربط المريض المنوّم بموقع العناية الحرجة والفريق المسؤول. راجع الإحالة والعلاجات الحالية والفحوص المعلقة عند التسليم الأول. المراقبة والتوثيق: احفظ القياسات والتقييمات وتوثيق الرعاية في الزيارة. حدد الوحدات وتكرار التسجيل ومسؤولية التصعيد المحلية؛ تتطلب التغذية الآلية ربط جهاز معتمداً. تنسيق العلاج: اربط الطلبات وإعطاء الأدوية والتقارير بالخطة الحالية. طابق التغييرات مع فريق السرير ووثق مسؤول كل إجراء معلق. التسليم والنقل: راجع السجل والمسؤوليات المعلقة عند تغيير المناوبة أو الوحدة. يمكن إضافة المراجعة عن بُعد مع تعريف مستقل للوصول والمسؤوليات ونطاق الأجهزة.","href":"/platform/icu#module-workflow"},{"question":"ما بيانات إعداد العناية المركزة؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الغرف والأجنحة والأسرة (locations.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة الجدولة (scheduling.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ مواصفات الربط (interfaces.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/icu#module-setup"},{"question":"كيف يتعامل العناية المركزة مع الاستثناءات؟","answer":"قياس جهاز مفقود أو قديم تحقق من مواءمة الجهاز والزيارة والوقت واتبع إجراء التسجيل عند السرير واستعادة الربط. تغير الحالة السريرية وثق إعادة التقييم وفعّل التصعيد السريري المحلي؛ يدعم سجل المنصة قرار الفريق.","href":"/platform/icu#module-exceptions"},{"question":"كيف يتصل العناية المركزة بالأنظمة الأخرى؟","answer":"لا يعني توفر سجل العناية ربط كل شاشة أو جهاز تنفس أو إنذار. حدد طرازات الأجهزة والبروتوكولات والأطباء المسؤولين وإجراءات التعطل ضمن النطاق المختار.","href":"/platform/icu#module-connections"}],"module":{"name":"العناية المركزة","functions":["نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار."],"workflow":[{"title":"الاستقبال في الوحدة","action":"اربط المريض المنوّم بموقع العناية الحرجة والفريق المسؤول. راجع الإحالة والعلاجات الحالية والفحوص المعلقة عند التسليم الأول.","owner":"فريق العناية المستلم","record":"الزيارة وموقع السرير والفريق وسياق الإحالة"},{"title":"المراقبة والتوثيق","action":"احفظ القياسات والتقييمات وتوثيق الرعاية في الزيارة. حدد الوحدات وتكرار التسجيل ومسؤولية التصعيد المحلية؛ تتطلب التغذية الآلية ربط جهاز معتمداً.","owner":"ممرض وطبيب العناية","record":"وقت القياس والقيم والوحدات وتوثيق الرعاية"},{"title":"تنسيق العلاج","action":"اربط الطلبات وإعطاء الأدوية والتقارير بالخطة الحالية. طابق التغييرات مع فريق السرير ووثق مسؤول كل إجراء معلق.","owner":"فريق السرير والأقسام","record":"إعطاء الأدوية والطلبات والتقارير وخطة الرعاية"},{"title":"التسليم والنقل","action":"راجع السجل والمسؤوليات المعلقة عند تغيير المناوبة أو الوحدة. يمكن إضافة المراجعة عن بُعد مع تعريف مستقل للوصول والمسؤوليات ونطاق الأجهزة.","owner":"فريقا التسليم والاستلام","record":"سجل التسليم والوجهة والإجراءات المعلقة"}],"exceptions":[{"situation":"قياس جهاز مفقود أو قديم","response":"تحقق من مواءمة الجهاز والزيارة والوقت واتبع إجراء التسجيل عند السرير واستعادة الربط."},{"situation":"تغير الحالة السريرية","response":"وثق إعادة التقييم وفعّل التصعيد السريري المحلي؛ يدعم سجل المنصة قرار الفريق."}],"connection":"لا يعني توفر سجل العناية ربط كل شاشة أو جهاز تنفس أو إنذار. حدد طرازات الأجهزة والبروتوكولات والأطباء المسؤولين وإجراءات التعطل ضمن النطاق المختار.","scenarios":[{"title":"تنويم عناية حرجة وتسليم مناوبة","situation":"يدخل مريض العناية ويحتاج فريق المناوبة التالية سياق الرعاية الحالي كاملاً.","preparation":"سرير عناية وفريق وتعريفات قياس ومسار أدوية وسياسة تسليم.","steps":["استلم الإحالة وحدد موقع المريض في الوحدة.","وثق التقييمات والقياسات والأدوية والطلبات.","راجع النتائج وحدّث الخطة مع الطبيب المسؤول.","سلّم العلاج والعمل المعلق للفريق التالي المحدد."],"acceptance":"يحدد الفريق المستلم الخطة والأدوية وأوقات القياس والطلبات المعلقة."},{"title":"انقطاع تغذية جهاز أثناء نقل الوحدة","situation":"يتوقف ربط جهاز مختار عن إرسال القياسات أثناء نقل المريض.","preparation":"مواءمة جهاز معتمدة وفحص أوقات وتسجيل يدوي وتهيئة سرير مستلم.","steps":["حدد القياسات القديمة أو المفقودة وآخر وقت معتمد.","استمر بالتسجيل والتصعيد عند السرير وفق الإجراء.","حدّث مواءمة المريض والزيارة والجهاز والموقع للوحدة المستلمة.","طابق القياسات بعد التعافي وسلّم فجوة البيانات وسجل العلاج."],"acceptance":"لا ينسب قياس مستعاد لمريض آخر وتوثق الفجوة ومسؤولية السرير."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/inpatient","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/inpatient","title":"Inpatient Care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow.","description":"Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow. Admissions, discharge and transfers, Wards and bed…","answers":[{"question":"What does MANSOQ Inpatient Care cover?","answer":"Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow. Admit & locate: Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context. Coordinate care: Record assessments and observations, maintain the care plan and track service requests. Keep clinical notes, results and outstanding actions available to authorized ward staff. Medication & transfers: Connect medication requests, administration records and pharmacy dispensing. On a ward or team transfer, review the current plan, location and unresolved tasks with the receiving team. Discharge & reconcile: Complete the discharge record, medication instructions and follow-up responsibility. Review documented service activity and open financial items through billing and the selected revenue-cycle workflow.","href":"/platform/inpatient#module-workflow"},{"question":"What setup data does Inpatient Care need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Rooms, wards and beds (locations.csv); Users & department access (user_access.csv); Doctors & operational clinics (doctors.csv); Clinical workflow configuration (clinical_workflows.csv); Assets, devices & hardware (assets_devices.csv); Inventory & medication items (stock_items.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/inpatient#module-setup"},{"question":"How does Inpatient Care handle exceptions?","answer":"Bed or team changes during admission Update the destination and responsibility, then verify medication, orders and unresolved tasks at handover. Discharge with a pending result Record the outstanding request, the reviewing clinician and the patient communication plan before closing the pathway.","href":"/platform/inpatient#module-exceptions"},{"question":"How does Inpatient Care connect with other systems?","answer":"An inpatient encounter brings the stay together. ICU, surgery, pharmacy and departmental interfaces retain their own configuration, access and acceptance requirements.","href":"/platform/inpatient#module-connections"}],"module":{"name":"Inpatient Care","functions":["Admissions, discharge and transfers","Wards and bed workflow","Nursing documentation and care context","Medication and departmental orders","Discharge and charge linkage"],"workflow":[{"title":"Admit & locate","action":"Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context.","owner":"Admissions and ward team","record":"Admission encounter, location and care-team assignment"},{"title":"Coordinate care","action":"Record assessments and observations, maintain the care plan and track service requests. Keep clinical notes, results and outstanding actions available to authorized ward staff.","owner":"Ward nurses and clinicians","record":"Observations, care documentation, orders and reports"},{"title":"Medication & transfers","action":"Connect medication requests, administration records and pharmacy dispensing. On a ward or team transfer, review the current plan, location and unresolved tasks with the receiving team.","owner":"Ward, pharmacy and receiving team","record":"Medication administrations, dispense records and transfer context"},{"title":"Discharge & reconcile","action":"Complete the discharge record, medication instructions and follow-up responsibility. Review documented service activity and open financial items through billing and the selected revenue-cycle workflow.","owner":"Discharge coordinator and finance","record":"Discharge summary, follow-up plan and financial account"}],"exceptions":[{"situation":"Bed or team changes during admission","response":"Update the destination and responsibility, then verify medication, orders and unresolved tasks at handover."},{"situation":"Discharge with a pending result","response":"Record the outstanding request, the reviewing clinician and the patient communication plan before closing the pathway."}],"connection":"An inpatient encounter brings the stay together. ICU, surgery, pharmacy and departmental interfaces retain their own configuration, access and acceptance requirements.","scenarios":[{"title":"Admission through planned discharge","situation":"A patient enters a ward, receives daily care and leaves with a follow-up plan.","preparation":"Ward and bed locations, care roles, medication and departmental services, discharge documentation.","steps":["Admissions opens the stay and assigns the ward and responsible team.","Ward staff document observations, care and orders; pharmacy and departments fulfil the selected requests.","At each handover the receiving team reviews current treatment and outstanding work.","The discharge team completes the summary, medication instructions and follow-up, then finance reconciles recorded services."],"acceptance":"The stay, care records, medication activity and discharge responsibility remain connected."},{"title":"Ward transfer with a pending investigation","situation":"A patient changes ward before a requested diagnostic report is complete.","preparation":"Receiving location, permitted care team and unresolved request list.","steps":["Record the destination and receiving responsibility without creating an unrelated patient.","Review active medication and care documentation at transfer.","Carry the pending request and name the clinician who will review its result.","Reconcile the returned report and discharge actions with the receiving team."],"acceptance":"The report remains linked to the original request and has an explicit follow-up owner after transfer."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/inpatient?lang=ar","title":"رعاية التنويم | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"الدخول والنقل والخروج والأجنحة والأسرة والتمريض والطلبات والأدوية ضمن مسار تنويم متكامل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"الدخول والنقل والخروج والأجنحة والأسرة والتمريض والطلبات والأدوية ضمن مسار تنويم متكامل.","description":"الدخول والنقل والخروج والأجنحة والأسرة والتمريض والطلبات والأدوية ضمن مسار تنويم متكامل. الدخول والخروج والنقل، مسار الأجنحة والأسرة، توثيق التمريض وسياق الرعاية، الأدوية وطلبات…","answers":[{"question":"ما نطاق رعاية التنويم في منسوق؟","answer":"الدخول والنقل والخروج والأجنحة والأسرة والتمريض والطلبات والأدوية ضمن مسار تنويم متكامل. التنويم وتحديد الموقع: أنشئ زيارة التنويم وحدد الجناح والسرير المناسبين. أكد الفريق المسؤول واحتفظ بسياق الإحالة أو الطوارئ. تنسيق الرعاية: سجّل التقييمات والقياسات وحدّث خطة الرعاية وتابع طلبات الخدمات. أتح الملاحظات والنتائج والإجراءات المعلقة لفريق الجناح المخوّل. الأدوية والنقل: اربط طلبات الأدوية وسجلات إعطائها وصرفها. راجع الخطة الحالية والموقع والمهام غير المكتملة مع الفريق المستلم عند النقل. الخروج والمطابقة: أكمل سجل الخروج وتعليمات الأدوية ومسؤولية المتابعة. راجع الخدمات الموثقة والبنود المالية المفتوحة عبر الفوترة ومسار الإيرادات المختار.","href":"/platform/inpatient#module-workflow"},{"question":"ما بيانات إعداد رعاية التنويم؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الغرف والأجنحة والأسرة (locations.csv)؛ المستخدمون وصلاحيات الأقسام (user_access.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ أصناف المخزون والأدوية (stock_items.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/inpatient#module-setup"},{"question":"كيف يتعامل رعاية التنويم مع الاستثناءات؟","answer":"تغيير السرير أو الفريق أثناء التنويم حدّث الوجهة والمسؤولية وتحقق من الأدوية والطلبات والمهام المعلقة عند التسليم. الخروج مع نتيجة معلقة سجّل الطلب المعلق والطبيب المراجع وخطة إبلاغ المريض قبل إغلاق المسار.","href":"/platform/inpatient#module-exceptions"},{"question":"كيف يتصل رعاية التنويم بالأنظمة الأخرى؟","answer":"تجمع زيارة التنويم تفاصيل الإقامة. للعناية المركزة والجراحة والصيدلية واتصالات الأقسام متطلبات تهيئة وصلاحيات وقبول مستقلة.","href":"/platform/inpatient#module-connections"}],"module":{"name":"رعاية التنويم","functions":["الدخول والخروج والنقل","مسار الأجنحة والأسرة","توثيق التمريض وسياق الرعاية","الأدوية وطلبات الأقسام","ربط الخروج والرسوم"],"workflow":[{"title":"التنويم وتحديد الموقع","action":"أنشئ زيارة التنويم وحدد الجناح والسرير المناسبين. أكد الفريق المسؤول واحتفظ بسياق الإحالة أو الطوارئ.","owner":"فريق التنويم والجناح","record":"زيارة التنويم والموقع وتعيين فريق الرعاية"},{"title":"تنسيق الرعاية","action":"سجّل التقييمات والقياسات وحدّث خطة الرعاية وتابع طلبات الخدمات. أتح الملاحظات والنتائج والإجراءات المعلقة لفريق الجناح المخوّل.","owner":"ممرضو الجناح والأطباء","record":"القياسات وتوثيق الرعاية والطلبات والتقارير"},{"title":"الأدوية والنقل","action":"اربط طلبات الأدوية وسجلات إعطائها وصرفها. راجع الخطة الحالية والموقع والمهام غير المكتملة مع الفريق المستلم عند النقل.","owner":"الجناح والصيدلية والفريق المستلم","record":"إعطاء الأدوية وسجلات الصرف وسياق النقل"},{"title":"الخروج والمطابقة","action":"أكمل سجل الخروج وتعليمات الأدوية ومسؤولية المتابعة. راجع الخدمات الموثقة والبنود المالية المفتوحة عبر الفوترة ومسار الإيرادات المختار.","owner":"منسق الخروج والمالية","record":"ملخص الخروج وخطة المتابعة والحساب المالي"}],"exceptions":[{"situation":"تغيير السرير أو الفريق أثناء التنويم","response":"حدّث الوجهة والمسؤولية وتحقق من الأدوية والطلبات والمهام المعلقة عند التسليم."},{"situation":"الخروج مع نتيجة معلقة","response":"سجّل الطلب المعلق والطبيب المراجع وخطة إبلاغ المريض قبل إغلاق المسار."}],"connection":"تجمع زيارة التنويم تفاصيل الإقامة. للعناية المركزة والجراحة والصيدلية واتصالات الأقسام متطلبات تهيئة وصلاحيات وقبول مستقلة.","scenarios":[{"title":"من التنويم إلى الخروج المخطط","situation":"يدخل مريض جناحاً ويتلقى رعاية يومية ثم يخرج بخطة متابعة.","preparation":"الجناح والأسرة وأدوار الرعاية والأدوية والخدمات وتوثيق الخروج.","steps":["يفتح التنويم الإقامة ويعين الجناح والفريق المسؤول.","يوثق الجناح القياسات والرعاية والطلبات وتنفذ الصيدلية والأقسام الطلبات المختارة.","يراجع الفريق المستلم العلاج الحالي والعمل المعلق عند كل تسليم.","يكمل فريق الخروج الملخص وتعليمات الأدوية والمتابعة وتطابق المالية الخدمات."],"acceptance":"ترتبط الإقامة وسجلات الرعاية ونشاط الأدوية ومسؤولية الخروج."},{"title":"نقل بين الأجنحة مع فحص معلق","situation":"ينتقل مريض لجناح آخر قبل اكتمال تقرير تشخيصي مطلوب.","preparation":"موقع مستلم وفريق مخوّل وقائمة طلبات غير مكتملة.","steps":["سجّل الوجهة والمسؤولية المستلمة دون إنشاء مريض غير مرتبط.","راجع الأدوية النشطة وتوثيق الرعاية عند النقل.","انقل الطلب المعلق وحدد الطبيب المراجع للنتيجة.","طابق التقرير وإجراءات الخروج مع الفريق المستلم."],"acceptance":"يبقى التقرير مرتبطاً بالطلب الأصلي وله مسؤول متابعة بعد النقل."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/integrations","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/integrations","title":"System & Device Interfaces software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually.","description":"Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually. Actual HIS, LIS, RIS/PACS, identity, device…","answers":[{"question":"What does MANSOQ System & Device Interfaces cover?","answer":"Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually. Define the exchange: Name source and target systems, message types, direction, protocol and version. Agree whether the connection carries identity, encounters, orders, results, devices or financial activity and identify its owners. Map identifiers & data: Map patient, facility, practitioner and encounter identifiers alongside service codes, units, timestamps and statuses. Define required fields, transformations and the treatment of unsupported values. Test & accept: Use the agreed test environment, credentials and endpoint. Verify valid, invalid, duplicate and delayed messages, acknowledgements, ordering and reconciliation before approving production access. Operate & recover: Monitor failed and pending exchanges and assign support responsibility. Follow approved retry and duplicate rules, then reconcile records after downtime, credential rotation or interface version changes.","href":"/platform/integrations#module-workflow"},{"question":"What setup data does System & Device Interfaces need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Interface specification (interfaces.csv); Assets, devices & hardware (assets_devices.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/integrations#module-setup"},{"question":"How does System & Device Interfaces handle exceptions?","answer":"Duplicate message or missing acknowledgement Check the original business identity and accepted idempotency rules; reconcile the target before deciding whether to retry. Source terminology changes Version the mapping, review affected records and test both old and new values before activating the change.","href":"/platform/integrations#module-exceptions"},{"question":"How does System & Device Interfaces connect with other systems?","answer":"Available protocols and adapters are release-specific. A third-party system name or standards logo is not proof of an active connector; accept the exact data, direction, license and support scope.","href":"/platform/integrations#module-connections"}],"module":{"name":"System & Device Interfaces","functions":["Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually."],"workflow":[{"title":"Define the exchange","action":"Name source and target systems, message types, direction, protocol and version. Agree whether the connection carries identity, encounters, orders, results, devices or financial activity and identify its owners.","owner":"Source and target owners","record":"Interface scope, message inventory and responsibility"},{"title":"Map identifiers & data","action":"Map patient, facility, practitioner and encounter identifiers alongside service codes, units, timestamps and statuses. Define required fields, transformations and the treatment of unsupported values.","owner":"Integration and data team","record":"Field mapping, terminology and identifier crosswalk"},{"title":"Test & accept","action":"Use the agreed test environment, credentials and endpoint. Verify valid, invalid, duplicate and delayed messages, acknowledgements, ordering and reconciliation before approving production access.","owner":"Integration owner and receiving users","record":"Test cases, acknowledgements, reconciliation and acceptance"},{"title":"Operate & recover","action":"Monitor failed and pending exchanges and assign support responsibility. Follow approved retry and duplicate rules, then reconcile records after downtime, credential rotation or interface version changes.","owner":"Integration operations team","record":"Message trace, failure queue, retry and recovery evidence"}],"exceptions":[{"situation":"Duplicate message or missing acknowledgement","response":"Check the original business identity and accepted idempotency rules; reconcile the target before deciding whether to retry."},{"situation":"Source terminology changes","response":"Version the mapping, review affected records and test both old and new values before activating the change."}],"connection":"Available protocols and adapters are release-specific. A third-party system name or standards logo is not proof of an active connector; accept the exact data, direction, license and support scope.","scenarios":[{"title":"External diagnostic result exchange","situation":"An external diagnostic system returns accepted reports to the MANSOQ clinical context.","preparation":"Accepted protocol and version, patient/encounter crosswalk, test codes, units and response rules.","steps":["Define message direction, required fields and the owner of each source identifier.","Test matched, invalid, duplicate and delayed results in the accepted environment.","Approve production exchange only after mappings and reconciliation pass.","Monitor pending messages and confirm each accepted report’s clinical destination."],"acceptance":"Every accepted result has an identifiable source, business identity and receiving patient/encounter."},{"title":"Outage, duplicate retry and mapping change","situation":"A source replays messages after downtime while its terminology edition is changing.","preparation":"Message trace, duplicate policy, mapping versions, recovery owner and representative test cases.","steps":["Retain original message identities and investigate receipt before retrying.","Separate already accepted messages from unprocessed work under the agreed duplicate rules.","Version the terminology change and test historical and new codes.","Reconcile recovered records and approve the change before regular operation resumes."],"acceptance":"Recovery does not create unexplained duplicates, and source-to-target mapping changes are traceable."}],"setupFiles":[{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/integrations?lang=ar","title":"اتصالات الأنظمة والأجهزة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه.","description":"تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه. تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر…","answers":[{"question":"ما نطاق اتصالات الأنظمة والأجهزة في منسوق؟","answer":"تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه. تعريف التبادل: حدد المصدر والوجهة وأنواع الرسائل والاتجاه والبروتوكول والإصدار. حدد الهوية أو الزيارات أو الطلبات أو النتائج أو الأجهزة أو النشاط المالي والمسؤولين. مواءمة المعرّفات والبيانات: واءم معرّفات المريض والمنشأة والممارس والزيارة ورموز الخدمات والوحدات والأوقات والحالات. حدد الحقول المطلوبة والتحويلات والقيم غير المدعومة. الاختبار والقبول: استخدم بيئة الاختبار وبيانات الاتصال والوجهة المتفق عليها. تحقق من الرسائل الصحيحة والخاطئة والمكررة والمتأخرة والإقرارات والترتيب والمطابقة قبل اعتماد الإنتاج. التشغيل والتعافي: راقب التبادلات الفاشلة والمعلقة وحدد مسؤول الدعم. اتبع قواعد الإعادة والتكرار وطابق السجلات بعد التعطل أو تغيير بيانات الاتصال أو إصدار الربط.","href":"/platform/integrations#module-workflow"},{"question":"ما بيانات إعداد اتصالات الأنظمة والأجهزة؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: مواصفات الربط (interfaces.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/integrations#module-setup"},{"question":"كيف يتعامل اتصالات الأنظمة والأجهزة مع الاستثناءات؟","answer":"رسالة مكررة أو إقرار مفقود تحقق من الهوية الأصلية وقواعد منع التكرار وطابق الوجهة قبل قرار الإعادة. تغير مصطلحات المصدر احفظ إصدار المواءمة وراجع السجلات المتأثرة واختبر القيم القديمة والجديدة قبل التفعيل.","href":"/platform/integrations#module-exceptions"},{"question":"كيف يتصل اتصالات الأنظمة والأجهزة بالأنظمة الأخرى؟","answer":"البروتوكولات والأدوات المتاحة مرتبطة بالإصدار. لا يثبت اسم نظام خارجي أو شعار معيار وجود ربط فعّال؛ اعتمد البيانات والاتجاه والترخيص والدعم المحددين.","href":"/platform/integrations#module-connections"}],"module":{"name":"اتصالات الأنظمة والأجهزة","functions":["تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه."],"workflow":[{"title":"تعريف التبادل","action":"حدد المصدر والوجهة وأنواع الرسائل والاتجاه والبروتوكول والإصدار. حدد الهوية أو الزيارات أو الطلبات أو النتائج أو الأجهزة أو النشاط المالي والمسؤولين.","owner":"مسؤولو المصدر والوجهة","record":"نطاق الاتصال وقائمة الرسائل والمسؤولية"},{"title":"مواءمة المعرّفات والبيانات","action":"واءم معرّفات المريض والمنشأة والممارس والزيارة ورموز الخدمات والوحدات والأوقات والحالات. حدد الحقول المطلوبة والتحويلات والقيم غير المدعومة.","owner":"فريق الربط والبيانات","record":"مواءمة الحقول والمصطلحات وجدول المعرّفات"},{"title":"الاختبار والقبول","action":"استخدم بيئة الاختبار وبيانات الاتصال والوجهة المتفق عليها. تحقق من الرسائل الصحيحة والخاطئة والمكررة والمتأخرة والإقرارات والترتيب والمطابقة قبل اعتماد الإنتاج.","owner":"مسؤول الربط والمستخدمون المستلمون","record":"حالات الاختبار والإقرارات والمطابقة والقبول"},{"title":"التشغيل والتعافي","action":"راقب التبادلات الفاشلة والمعلقة وحدد مسؤول الدعم. اتبع قواعد الإعادة والتكرار وطابق السجلات بعد التعطل أو تغيير بيانات الاتصال أو إصدار الربط.","owner":"فريق تشغيل الربط","record":"تتبع الرسائل وقائمة الأعطال والإعادة وأدلة التعافي"}],"exceptions":[{"situation":"رسالة مكررة أو إقرار مفقود","response":"تحقق من الهوية الأصلية وقواعد منع التكرار وطابق الوجهة قبل قرار الإعادة."},{"situation":"تغير مصطلحات المصدر","response":"احفظ إصدار المواءمة وراجع السجلات المتأثرة واختبر القيم القديمة والجديدة قبل التفعيل."}],"connection":"البروتوكولات والأدوات المتاحة مرتبطة بالإصدار. لا يثبت اسم نظام خارجي أو شعار معيار وجود ربط فعّال؛ اعتمد البيانات والاتجاه والترخيص والدعم المحددين.","scenarios":[{"title":"تبادل نتيجة تشخيصية خارجية","situation":"يعيد نظام تشخيص خارجي تقارير معتمدة لسياق الرعاية في منسوق.","preparation":"بروتوكول وإصدار ومواءمة مريض وزيارة ورموز ووحدات وقواعد رد معتمدة.","steps":["حدد اتجاه الرسائل والحقول ومالك كل معرّف مصدر.","اختبر النتائج المطابقة والخاطئة والمكررة والمتأخرة.","اعتمد الإنتاج بعد نجاح المواءمة والمطابقة.","راقب الرسائل المعلقة وأكد وجهة كل تقرير معتمد."],"acceptance":"لكل نتيجة معتمدة مصدر وهوية ومرجع مريض وزيارة مستلمين."},{"title":"تعطل وإعادة مكررة وتغيير مواءمة","situation":"يعيد مصدر الرسائل بعد تعطل أثناء تغير إصدار المصطلحات.","preparation":"تتبع رسائل وسياسة تكرار وإصدارات مواءمة ومسؤول تعافٍ واختبارات.","steps":["احفظ هويات الرسائل وحقق في الاستلام قبل الإعادة.","افصل الرسائل المقبولة عن العمل غير المعالج وفق قواعد التكرار.","احفظ إصدار تغيير المصطلحات واختبر الرموز القديمة والجديدة.","طابق السجلات المستعادة واعتمد التغيير قبل العودة."],"acceptance":"لا ينتج التعافي تكراراً غير مفسر وتُتبع تغييرات المواءمة."}],"setupFiles":[{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/inventory","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/inventory","title":"Inventory software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Stock, stores and departmental supply operation within the agreed supported scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Stock, stores and departmental supply operation within the agreed supported scope.","description":"Stock, stores and departmental supply operation within the agreed supported scope. Stock, stores and departmental supply operation within the agreed supported scope..","answers":[{"question":"What does MANSOQ Inventory cover?","answer":"Stock, stores and departmental supply operation within the agreed supported scope. Define stock: Configure products, stores, units and supplier references. Import opening quantities by lot and location with cost and expiry information; reconcile the opening file to an approved stock count. Request & receive: Create supply requests and delivery records, confirm the supplying and receiving locations and inspect actual received quantities. Retain references to the original request and supplier. Issue & transfer: Select the item and lot for departmental use, dispensing or transfer. Confirm source, destination and quantity so physical movement can be reconciled with the correct inventory record. Count & reconcile: Review on-hand stock, expiry and pending deliveries. Investigate count variances and record authorized adjustments and returns with a reason; agree the finance export when external accounting is used.","href":"/platform/inventory#module-workflow"},{"question":"What setup data does Inventory need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Inventory & medication items (stock_items.csv); Stock lots & opening quantities (stock_balances.csv); Opening inventory (inventory_opening.csv); Assets, devices & hardware (assets_devices.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/inventory#module-setup"},{"question":"How does Inventory handle exceptions?","answer":"Short delivery or damaged items Record actual receipt, identify the affected lots and route the discrepancy to the supplier and inventory owner. Count differs from recorded balance Review unposted receipts and issues, approve the adjustment reason and retain the before-and-after reconciliation.","href":"/platform/inventory#module-exceptions"},{"question":"How does Inventory connect with other systems?","answer":"Stock and supply records support departmental activity. Procurement approvals, accounting exports, barcode devices and external warehouse systems require explicit scope and testing.","href":"/platform/inventory#module-connections"}],"module":{"name":"Inventory","functions":["Stock, stores and departmental supply operation within the agreed supported scope."],"workflow":[{"title":"Define stock","action":"Configure products, stores, units and supplier references. Import opening quantities by lot and location with cost and expiry information; reconcile the opening file to an approved stock count.","owner":"Inventory administrator","record":"Products, locations, units, lots and opening balances"},{"title":"Request & receive","action":"Create supply requests and delivery records, confirm the supplying and receiving locations and inspect actual received quantities. Retain references to the original request and supplier.","owner":"Storekeeper and receiving team","record":"Supply request, supply delivery and received quantities"},{"title":"Issue & transfer","action":"Select the item and lot for departmental use, dispensing or transfer. Confirm source, destination and quantity so physical movement can be reconciled with the correct inventory record.","owner":"Storekeeper and department user","record":"Lot-level stock movement and destination"},{"title":"Count & reconcile","action":"Review on-hand stock, expiry and pending deliveries. Investigate count variances and record authorized adjustments and returns with a reason; agree the finance export when external accounting is used.","owner":"Inventory and finance owners","record":"Count evidence, variance, adjustment and return records"}],"exceptions":[{"situation":"Short delivery or damaged items","response":"Record actual receipt, identify the affected lots and route the discrepancy to the supplier and inventory owner."},{"situation":"Count differs from recorded balance","response":"Review unposted receipts and issues, approve the adjustment reason and retain the before-and-after reconciliation."}],"connection":"Stock and supply records support departmental activity. Procurement approvals, accounting exports, barcode devices and external warehouse systems require explicit scope and testing.","scenarios":[{"title":"Receive supplies and issue them to a department","situation":"A store receives a supplier delivery and later supplies a clinical department.","preparation":"Products, units, source and destination stores, supplier references and opening lots.","steps":["Confirm the supply request, item and expected quantity.","Record actual received lots, quantities, cost and expiry against the delivery.","Issue or transfer the required quantity to the named department and location.","Review remaining stock and reconcile receipt and issue references to the accepted count."],"acceptance":"Each movement has a source, destination and lot reference, and balances reconcile."},{"title":"Short delivery discovered during stock count","situation":"Delivered quantities differ from the request and a later count shows an unresolved variance.","preparation":"Receiving inspection, supplier escalation, count evidence and adjustment authority.","steps":["Record the delivered quantity rather than copying the order quantity.","Separate damaged or disputed items under the approved stock procedure.","Review pending receipt and issue records against the physical count.","Approve a documented correction or adjustment and reconcile supplier and finance references."],"acceptance":"The variance has an identified cause, owner and approved resolution with before-and-after totals."}],"setupFiles":[{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"template":"/implementation/templates/inventory_opening.csv","example":"/implementation/examples/inventory_opening.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/inventory?lang=ar","title":"المخزون | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه.","description":"تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه. تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه..","answers":[{"question":"ما نطاق المخزون في منسوق؟","answer":"تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه. تعريف المخزون: هيئ المنتجات والمستودعات والوحدات ومراجع الموردين. استورد الكميات الافتتاحية حسب التشغيلة والموقع والتكلفة والصلاحية وطابق الملف مع جرد معتمد. الطلب والاستلام: أنشئ طلبات التوريد وسجلات التسليم وأكد مواقع التوريد والاستلام وافحص الكميات المستلمة فعلياً. احتفظ بمراجع الطلب الأصلي والمورد. الصرف والتحويل: اختر الصنف والتشغيلة للاستخدام في القسم أو الصرف أو التحويل. أكد المصدر والوجهة والكمية لمطابقة الحركة الفعلية بسجل المخزون الصحيح. الجرد والمطابقة: راجع المخزون المتوفر والصلاحية والتسليمات المعلقة. حقق في فروق الجرد وسجّل التسويات والمرتجعات المخولة وأسبابها واتفق على التصدير المالي عند استخدام محاسبة خارجية.","href":"/platform/inventory#module-workflow"},{"question":"ما بيانات إعداد المخزون؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: أصناف المخزون والأدوية (stock_items.csv)؛ التشغيلات وأرصدة المخزون (stock_balances.csv)؛ المخزون الافتتاحي (inventory_opening.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/inventory#module-setup"},{"question":"كيف يتعامل المخزون مع الاستثناءات؟","answer":"تسليم ناقص أو أصناف تالفة سجّل الاستلام الفعلي وحدد التشغيلات المتأثرة وأحل الفرق للمورد ومسؤول المخزون. اختلاف الجرد عن الرصيد المسجل راجع الاستلام والصرف غير المسجلين واعتمد سبب التسوية واحتفظ بالمطابقة قبل التعديل وبعده.","href":"/platform/inventory#module-exceptions"},{"question":"كيف يتصل المخزون بالأنظمة الأخرى؟","answer":"تدعم سجلات المخزون والتوريد نشاط الأقسام. تتطلب موافقات المشتريات والتصدير المحاسبي وأجهزة الرموز والمستودعات الخارجية نطاقاً واختبارات محددة.","href":"/platform/inventory#module-connections"}],"module":{"name":"المخزون","functions":["تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه."],"workflow":[{"title":"تعريف المخزون","action":"هيئ المنتجات والمستودعات والوحدات ومراجع الموردين. استورد الكميات الافتتاحية حسب التشغيلة والموقع والتكلفة والصلاحية وطابق الملف مع جرد معتمد.","owner":"مدير المخزون","record":"المنتجات والمواقع والوحدات والتشغيلات والأرصدة الافتتاحية"},{"title":"الطلب والاستلام","action":"أنشئ طلبات التوريد وسجلات التسليم وأكد مواقع التوريد والاستلام وافحص الكميات المستلمة فعلياً. احتفظ بمراجع الطلب الأصلي والمورد.","owner":"أمين المستودع وفريق الاستلام","record":"طلب التوريد وتسليم التوريد والكميات المستلمة"},{"title":"الصرف والتحويل","action":"اختر الصنف والتشغيلة للاستخدام في القسم أو الصرف أو التحويل. أكد المصدر والوجهة والكمية لمطابقة الحركة الفعلية بسجل المخزون الصحيح.","owner":"أمين المستودع ومستخدم القسم","record":"حركة المخزون على مستوى التشغيلة والوجهة"},{"title":"الجرد والمطابقة","action":"راجع المخزون المتوفر والصلاحية والتسليمات المعلقة. حقق في فروق الجرد وسجّل التسويات والمرتجعات المخولة وأسبابها واتفق على التصدير المالي عند استخدام محاسبة خارجية.","owner":"مسؤولو المخزون والمالية","record":"أدلة الجرد والفروق والتسويات والمرتجعات"}],"exceptions":[{"situation":"تسليم ناقص أو أصناف تالفة","response":"سجّل الاستلام الفعلي وحدد التشغيلات المتأثرة وأحل الفرق للمورد ومسؤول المخزون."},{"situation":"اختلاف الجرد عن الرصيد المسجل","response":"راجع الاستلام والصرف غير المسجلين واعتمد سبب التسوية واحتفظ بالمطابقة قبل التعديل وبعده."}],"connection":"تدعم سجلات المخزون والتوريد نشاط الأقسام. تتطلب موافقات المشتريات والتصدير المحاسبي وأجهزة الرموز والمستودعات الخارجية نطاقاً واختبارات محددة.","scenarios":[{"title":"استلام مستلزمات وصرفها لقسم","situation":"يستلم مستودع توريداً ثم يزود قسماً سريرياً.","preparation":"منتجات ووحدات ومستودعات مصدر ووجهة ومورد وتشغيلات افتتاحية.","steps":["أكد طلب التوريد والصنف والكمية المتوقعة.","سجّل التشغيلات والكميات والتكلفة والصلاحية المستلمة فعلياً.","اصرف أو انقل الكمية للقسم والموقع المحددين.","راجع الرصيد وطابق مراجع الاستلام والصرف بالجرد المعتمد."],"acceptance":"لكل حركة مصدر ووجهة ومرجع تشغيلة وتتطابق الأرصدة."},{"title":"توريد ناقص يُكتشف أثناء الجرد","situation":"تختلف الكميات المستلمة عن الطلب ويظهر فرق غير محسوم في جرد لاحق.","preparation":"فحص الاستلام وتصعيد المورد وأدلة الجرد وصلاحية التسوية.","steps":["سجّل الكمية المستلمة دون نسخ كمية الطلب.","افصل الأصناف التالفة أو المختلف عليها وفق الإجراء.","راجع الاستلام والصرف المعلقين مقابل الجرد الفعلي.","اعتمد تصحيحاً أو تسوية موثقة وطابق المورد والمالية."],"acceptance":"للفرق سبب ومسؤول ومعالجة معتمدة وإجماليات قبل المعالجة وبعدها."}],"setupFiles":[{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"template":"/implementation/templates/inventory_opening.csv","example":"/implementation/examples/inventory_opening.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/laboratory","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/laboratory","title":"Laboratory software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Lab orders, specimen and result workflows with native operation distinct from external LIS integration.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Lab orders, specimen and result workflows with native operation distinct from external LIS integration.","description":"Lab orders, specimen and result workflows with native operation distinct from external LIS integration. Lab orders, specimen and result workflows with native operation distinct…","answers":[{"question":"What does MANSOQ Laboratory cover?","answer":"Lab orders, specimen and result workflows with native operation distinct from external LIS integration. Request: Select the test from the service catalogue and link it to the patient, encounter and ordering clinician. Include the clinical question, priority and required specimen information. Collect & receive: Record specimen type, collection information, accession identifier, received time and condition. Keep processing notes and the original request linked so recollection can be traced. Record & review: Keep observations and diagnostic reports with the request and specimen. Configure the approved test definitions, units and result interpretation; name the result reviewer and critical-result communication route. Release & follow up: Make the approved report available in the clinical encounter. Preserve amendment reasons, reviewer responsibility and communication evidence; the ordering team owns the clinical follow-up.","href":"/platform/laboratory#module-workflow"},{"question":"What setup data does Laboratory need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Services & department catalogue (services.csv); Assets, devices & hardware (assets_devices.csv); Interface specification (interfaces.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/laboratory#module-setup"},{"question":"How does Laboratory handle exceptions?","answer":"Rejected or insufficient specimen Record the condition and reason, retain the original request reference and arrange recollection under the approved laboratory procedure. Critical or corrected result Follow the locally approved reviewer and notification procedure; record who was informed and preserve the previous report and correction reason.","href":"/platform/laboratory#module-exceptions"},{"question":"How does Laboratory connect with other systems?","answer":"Native requests, specimens, observations and reports are distinct from an external LIS or analyzer connection. Device protocols, code mappings, acknowledgements and downtime recovery require interface testing for the chosen release.","href":"/platform/laboratory#module-connections"}],"module":{"name":"Laboratory","functions":["Lab orders, specimen and result workflows with native operation distinct from external LIS integration."],"workflow":[{"title":"Request","action":"Select the test from the service catalogue and link it to the patient, encounter and ordering clinician. Include the clinical question, priority and required specimen information.","owner":"Ordering clinician","record":"Service request, test code, encounter and priority"},{"title":"Collect & receive","action":"Record specimen type, collection information, accession identifier, received time and condition. Keep processing notes and the original request linked so recollection can be traced.","owner":"Collection and laboratory staff","record":"Specimen, accession, collection, receipt and processing notes"},{"title":"Record & review","action":"Keep observations and diagnostic reports with the request and specimen. Configure the approved test definitions, units and result interpretation; name the result reviewer and critical-result communication route.","owner":"Laboratory reviewer","record":"Observations, report status, values, units and interpretation"},{"title":"Release & follow up","action":"Make the approved report available in the clinical encounter. Preserve amendment reasons, reviewer responsibility and communication evidence; the ordering team owns the clinical follow-up.","owner":"Laboratory and ordering team","record":"Released report, amendment history and follow-up responsibility"}],"exceptions":[{"situation":"Rejected or insufficient specimen","response":"Record the condition and reason, retain the original request reference and arrange recollection under the approved laboratory procedure."},{"situation":"Critical or corrected result","response":"Follow the locally approved reviewer and notification procedure; record who was informed and preserve the previous report and correction reason."}],"connection":"Native requests, specimens, observations and reports are distinct from an external LIS or analyzer connection. Device protocols, code mappings, acknowledgements and downtime recovery require interface testing for the chosen release.","scenarios":[{"title":"A requested blood test, from collection to review","situation":"A clinic clinician requests a test; collection staff and the laboratory complete the diagnostic record.","preparation":"Approved test code, specimen definition, collection location, units and result-review role.","steps":["Create the request with the patient, encounter and clinical reason.","Record collection and receipt against one accession identifier, including specimen condition.","Enter or receive the accepted observations and review the diagnostic report with its units and status.","Release the report to the ordering team and document clinical follow-up responsibility."],"acceptance":"Request, specimen, observations and report agree on identity, and a clinician owns result review."},{"title":"Rejected specimen, recollection and corrected report","situation":"The first specimen fails the local acceptance procedure and a later report requires correction.","preparation":"Specimen rejection reasons, recollection procedure, report reviewer and critical-result contact route.","steps":["Record the rejected condition and retain the original request reference.","Collect a replacement with a distinct traceable specimen record and verify identifiers.","Have the reviewer validate the new result and document any correction reason and prior report.","Notify the responsible care team according to the approved critical or amended-result procedure."],"acceptance":"The rejected specimen, replacement and report versions are traceable, with recorded communication responsibility."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/laboratory?lang=ar","title":"المختبر | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي.","description":"مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي. مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي..","answers":[{"question":"ما نطاق المختبر في منسوق؟","answer":"مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي. الطلب: اختر الفحص من كتالوج الخدمات واربطه بالمريض والزيارة والطبيب الطالب. أضف السؤال السريري والأولوية ومعلومات العينة المطلوبة. الجمع والاستلام: سجّل نوع العينة ومعلومات الجمع ومعرّف التسجيل ووقت الاستلام والحالة. اربط ملاحظات المعالجة بالطلب الأصلي لتتبع إعادة الجمع. التسجيل والمراجعة: اربط القياسات والتقارير التشخيصية بالطلب والعينة. هيئ تعريفات الفحوص والوحدات وتفسير النتائج المعتمد وحدد مراجع النتيجة ومسار إبلاغ النتائج الحرجة. الإصدار والمتابعة: أتح التقرير المعتمد في الزيارة السريرية. احتفظ بأسباب التعديل ومسؤولية المراجع ودليل الإبلاغ؛ يتولى الفريق الطالب المتابعة السريرية.","href":"/platform/laboratory#module-workflow"},{"question":"ما بيانات إعداد المختبر؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الخدمات ودليل الأقسام (services.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ مواصفات الربط (interfaces.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/laboratory#module-setup"},{"question":"كيف يتعامل المختبر مع الاستثناءات؟","answer":"عينة مرفوضة أو غير كافية سجّل الحالة والسبب واحتفظ بمرجع الطلب الأصلي ونظّم إعادة الجمع وفق إجراء المختبر المعتمد. نتيجة حرجة أو مصححة اتبع إجراءات المراجعة والإبلاغ المحلية وسجّل الشخص الذي تم إبلاغه واحتفظ بالتقرير السابق وسبب التصحيح.","href":"/platform/laboratory#module-exceptions"},{"question":"كيف يتصل المختبر بالأنظمة الأخرى؟","answer":"تختلف الطلبات والعينات والقياسات والتقارير الداخلية عن ربط نظام مختبر أو محلل خارجي. تتطلب بروتوكولات الأجهزة ومواءمة الرموز والإقرارات والتعافي اختبار اتصال للإصدار المختار.","href":"/platform/laboratory#module-connections"}],"module":{"name":"المختبر","functions":["مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي."],"workflow":[{"title":"الطلب","action":"اختر الفحص من كتالوج الخدمات واربطه بالمريض والزيارة والطبيب الطالب. أضف السؤال السريري والأولوية ومعلومات العينة المطلوبة.","owner":"الطبيب الطالب","record":"طلب الخدمة ورمز الفحص والزيارة والأولوية"},{"title":"الجمع والاستلام","action":"سجّل نوع العينة ومعلومات الجمع ومعرّف التسجيل ووقت الاستلام والحالة. اربط ملاحظات المعالجة بالطلب الأصلي لتتبع إعادة الجمع.","owner":"فريق جمع العينات والمختبر","record":"العينة ومعرّفها والجمع والاستلام وملاحظات المعالجة"},{"title":"التسجيل والمراجعة","action":"اربط القياسات والتقارير التشخيصية بالطلب والعينة. هيئ تعريفات الفحوص والوحدات وتفسير النتائج المعتمد وحدد مراجع النتيجة ومسار إبلاغ النتائج الحرجة.","owner":"مراجع المختبر","record":"القياسات وحالة التقرير والقيم والوحدات والتفسير"},{"title":"الإصدار والمتابعة","action":"أتح التقرير المعتمد في الزيارة السريرية. احتفظ بأسباب التعديل ومسؤولية المراجع ودليل الإبلاغ؛ يتولى الفريق الطالب المتابعة السريرية.","owner":"المختبر والفريق الطالب","record":"التقرير الصادر وتاريخ التعديلات ومسؤولية المتابعة"}],"exceptions":[{"situation":"عينة مرفوضة أو غير كافية","response":"سجّل الحالة والسبب واحتفظ بمرجع الطلب الأصلي ونظّم إعادة الجمع وفق إجراء المختبر المعتمد."},{"situation":"نتيجة حرجة أو مصححة","response":"اتبع إجراءات المراجعة والإبلاغ المحلية وسجّل الشخص الذي تم إبلاغه واحتفظ بالتقرير السابق وسبب التصحيح."}],"connection":"تختلف الطلبات والعينات والقياسات والتقارير الداخلية عن ربط نظام مختبر أو محلل خارجي. تتطلب بروتوكولات الأجهزة ومواءمة الرموز والإقرارات والتعافي اختبار اتصال للإصدار المختار.","scenarios":[{"title":"فحص دم مطلوب من الجمع إلى المراجعة","situation":"يطلب طبيب العيادة فحصاً ويكمل فريق الجمع والمختبر السجل التشخيصي.","preparation":"رمز فحص وتعريف عينة وموقع جمع ووحدات ودور مراجعة معتمدة.","steps":["أنشئ الطلب بالمريض والزيارة والسبب السريري.","سجّل الجمع والاستلام بمعرّف عينة واحد وحالتها.","سجّل أو استقبل القياسات المعتمدة وراجع التقرير ووحداته وحالته.","أصدر التقرير للفريق الطالب ووثق مسؤولية المتابعة."],"acceptance":"تتطابق الهوية عبر الطلب والعينة والقياسات والتقرير ويتولى طبيب مراجعة النتيجة."},{"title":"رفض عينة وإعادة جمع وتصحيح تقرير","situation":"لا تجتاز العينة الأولى القبول المحلي ويحتاج تقرير لاحق للتصحيح.","preparation":"أسباب رفض العينة وإعادة الجمع ومراجع التقرير ومسار الإبلاغ.","steps":["سجّل سبب رفض العينة واحتفظ بمرجع الطلب.","اجمع بديلاً بسجل عينة مستقل قابل للتتبع وتحقق من المعرّفات.","يتحقق المراجع من النتيجة ويوثق سبب التصحيح والتقرير السابق.","أبلغ فريق الرعاية وفق إجراء النتائج الحرجة أو المعدلة المعتمد."],"acceptance":"يمكن تتبع العينة المرفوضة والبديلة وإصدارات التقرير ومسؤولية الإبلاغ."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/managed-revenue","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/managed-revenue","title":"Managed Revenue People Services software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Qualified people, authorized access and an accepted operating scope, separate from RCM software.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Qualified people, authorized access and an accepted operating scope, separate from RCM software.","description":"Qualified people, authorized access and an accepted operating scope, separate from RCM software. Qualified people, authorized access and an accepted operating scope, separate…","answers":[{"question":"What does MANSOQ Managed Revenue People Services cover?","answer":"Qualified people, authorized access and an accepted operating scope, separate from RCM software. Agree responsibilities: Specify delegated revenue tasks, authorized users, provider and payer boundaries and service coverage. Name the organization that retains each clinical, contractual and financial decision. Prepare the work: Establish source access, work queues and the documents needed for eligibility, coding, authorization or claim tasks. Approve handover rules and quality checks before processing live work. Process & escalate: Perform only the agreed tasks through authorized workflows. Route missing clinical evidence, contracting questions and payer disputes to the retained owner and keep submission authority explicit. Review service delivery: Reconcile completed work, remittance and outstanding exceptions with the provider. Review agreed measures, support coverage and change requests against the service terms without promising unsupported financial outcomes.","href":"/platform/managed-revenue#module-workflow"},{"question":"What setup data does Managed Revenue People Services need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include administration agreements (rcm_administration_agreements.csv); Access & approvals (access_matrix.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); Support handover (support_handover.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/managed-revenue#module-setup"},{"question":"How does Managed Revenue People Services handle exceptions?","answer":"Missing authority or supporting evidence Hold the affected administrative task, identify the provider owner and obtain the accepted evidence before proceeding. Work falls outside delegated scope Route it back to the provider and record a scope decision or controlled change request.","href":"/platform/managed-revenue#module-exceptions"},{"question":"How does Managed Revenue People Services connect with other systems?","answer":"People services are distinct from software licensing and integration activation. Agree staffing, delegated authority, hours, deliverables and support terms in the service proposal.","href":"/platform/managed-revenue#module-connections"}],"module":{"name":"Managed Revenue People Services","functions":["Qualified people, authorized access and an accepted operating scope, separate from RCM software."],"workflow":[{"title":"Agree responsibilities","action":"Specify delegated revenue tasks, authorized users, provider and payer boundaries and service coverage. Name the organization that retains each clinical, contractual and financial decision.","owner":"Provider and service lead","record":"Delegation, service scope, access and responsibility matrix"},{"title":"Prepare the work","action":"Establish source access, work queues and the documents needed for eligibility, coding, authorization or claim tasks. Approve handover rules and quality checks before processing live work.","owner":"Revenue operations lead","record":"Work inventory, required evidence and queue ownership"},{"title":"Process & escalate","action":"Perform only the agreed tasks through authorized workflows. Route missing clinical evidence, contracting questions and payer disputes to the retained owner and keep submission authority explicit.","owner":"Managed team and provider owners","record":"Task disposition, review, evidence and escalation"},{"title":"Review service delivery","action":"Reconcile completed work, remittance and outstanding exceptions with the provider. Review agreed measures, support coverage and change requests against the service terms without promising unsupported financial outcomes.","owner":"Provider finance and service lead","record":"Service review, reconciled work and unresolved exceptions"}],"exceptions":[{"situation":"Missing authority or supporting evidence","response":"Hold the affected administrative task, identify the provider owner and obtain the accepted evidence before proceeding."},{"situation":"Work falls outside delegated scope","response":"Route it back to the provider and record a scope decision or controlled change request."}],"connection":"People services are distinct from software licensing and integration activation. Agree staffing, delegated authority, hours, deliverables and support terms in the service proposal.","scenarios":[{"title":"Delegated claim preparation service","situation":"A provider assigns an agreed administrative claim workstream to a managed team.","preparation":"Written delegated tasks, source access, queue ownership, quality checks and submission authority.","steps":["Confirm the provider-retained clinical and contractual responsibilities.","Prepare the work inventory and required source documentation.","The managed team performs agreed tasks and routes missing facts to the provider owner.","Review quality, completed work and unresolved exceptions against the service terms."],"acceptance":"Every delegated task has an owner, disposition and evidence; clinical and submission authority remain explicit."},{"title":"Disputed payer response outside delegation","situation":"The managed team receives a response that needs a provider clinical or contract decision.","preparation":"Original response, delegated boundary, provider reviewer, deadline and escalation contact.","steps":["Classify the returned issue without assuming authority to resolve it.","Collect the permitted evidence and identify the retained provider owner.","Escalate the clinical or contract decision with references and due date.","Resume only the accepted administrative task and record the final service disposition."],"acceptance":"The scope exception is documented and no unauthorized clinical or financial decision is taken by the service team."}],"setupFiles":[{"template":"/implementation/templates/rcm_administration_agreements.csv","example":"/implementation/examples/rcm_administration_agreements.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/support_handover.csv","example":"/implementation/examples/support_handover.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/managed-revenue?lang=ar","title":"خدمات فريق إدارة الإيرادات | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد.","description":"أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد. أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد..","answers":[{"question":"ما نطاق خدمات فريق إدارة الإيرادات في منسوق؟","answer":"أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد. تحديد المسؤوليات: حدد مهام الإيرادات المفوضة والمستخدمين وحدود المزود والدافع وتغطية الخدمة. حدد الجهة التي تحتفظ بالقرار السريري والتعاقدي والمالي. تحضير العمل: جهز الوصول للمصادر وقوائم العمل والوثائق اللازمة للأهلية والترميز والموافقة والمطالبة. اعتمد التسليم وفحوص الجودة قبل العمل الفعلي. المعالجة والتصعيد: نفذ المهام المتفق عليها فقط عبر المسارات المخولة. أحل الأدلة السريرية الناقصة ومسائل العقود ونزاعات الدافع للمسؤول وحدد صلاحية الإرسال. مراجعة تقديم الخدمة: طابق العمل المكتمل والسداد والاستثناءات مع المزود. راجع المقاييس والتغطية والتغييرات وفق الشروط دون وعد بنتائج مالية غير مدعومة.","href":"/platform/managed-revenue#module-workflow"},{"question":"ما بيانات إعداد خدمات فريق إدارة الإيرادات؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة دورة الإيرادات · اتفاقيات الإدارة المفوّضة (rcm_administration_agreements.csv)؛ الصلاحيات والموافقات (access_matrix.csv)؛ ضوابط الإيرادات والمطابقة (rcm_financial_controls.csv)؛ تسليم الدعم (support_handover.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/managed-revenue#module-setup"},{"question":"كيف يتعامل خدمات فريق إدارة الإيرادات مع الاستثناءات؟","answer":"صلاحية أو دليل داعم مفقود أوقف المهمة الإدارية المتأثرة وحدد مسؤول المزود واحصل على الدليل المعتمد قبل الاستمرار. عمل خارج نطاق التفويض أعده للمزود وسجّل قرار النطاق أو طلب تغيير محكوم.","href":"/platform/managed-revenue#module-exceptions"},{"question":"كيف يتصل خدمات فريق إدارة الإيرادات بالأنظمة الأخرى؟","answer":"خدمات الفرق مستقلة عن ترخيص البرمجيات وتفعيل الربط. اتفق على الكوادر والتفويض والساعات والمخرجات والدعم في عرض الخدمة.","href":"/platform/managed-revenue#module-connections"}],"module":{"name":"خدمات فريق إدارة الإيرادات","functions":["أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد."],"workflow":[{"title":"تحديد المسؤوليات","action":"حدد مهام الإيرادات المفوضة والمستخدمين وحدود المزود والدافع وتغطية الخدمة. حدد الجهة التي تحتفظ بالقرار السريري والتعاقدي والمالي.","owner":"المزود وقائد الخدمة","record":"التفويض ونطاق الخدمة والوصول ومصفوفة المسؤوليات"},{"title":"تحضير العمل","action":"جهز الوصول للمصادر وقوائم العمل والوثائق اللازمة للأهلية والترميز والموافقة والمطالبة. اعتمد التسليم وفحوص الجودة قبل العمل الفعلي.","owner":"قائد تشغيل الإيرادات","record":"قائمة العمل والأدلة المطلوبة ومسؤولية القوائم"},{"title":"المعالجة والتصعيد","action":"نفذ المهام المتفق عليها فقط عبر المسارات المخولة. أحل الأدلة السريرية الناقصة ومسائل العقود ونزاعات الدافع للمسؤول وحدد صلاحية الإرسال.","owner":"الفريق المدار ومسؤولو المزود","record":"حالة المهمة والمراجعة والأدلة والتصعيد"},{"title":"مراجعة تقديم الخدمة","action":"طابق العمل المكتمل والسداد والاستثناءات مع المزود. راجع المقاييس والتغطية والتغييرات وفق الشروط دون وعد بنتائج مالية غير مدعومة.","owner":"مالية المزود وقائد الخدمة","record":"مراجعة الخدمة والعمل المطابق والاستثناءات"}],"exceptions":[{"situation":"صلاحية أو دليل داعم مفقود","response":"أوقف المهمة الإدارية المتأثرة وحدد مسؤول المزود واحصل على الدليل المعتمد قبل الاستمرار."},{"situation":"عمل خارج نطاق التفويض","response":"أعده للمزود وسجّل قرار النطاق أو طلب تغيير محكوم."}],"connection":"خدمات الفرق مستقلة عن ترخيص البرمجيات وتفعيل الربط. اتفق على الكوادر والتفويض والساعات والمخرجات والدعم في عرض الخدمة.","scenarios":[{"title":"خدمة مفوضة لإعداد المطالبات","situation":"يفوض مزود مسار إعداد مطالبات إدارياً متفقاً عليه لفريق مدار.","preparation":"مهام مفوضة مكتوبة ووصول مصادر ومسؤول قوائم وفحوص جودة وصلاحية إرسال.","steps":["أكد مسؤوليات المزود السريرية والتعاقدية المحتفظ بها.","جهز قائمة العمل ووثائق المصدر.","ينفذ الفريق المهام المتفق عليها ويحيل النقص للمزود.","راجع الجودة والعمل والاستثناءات وفق الشروط."],"acceptance":"لكل مهمة مسؤول وحالة ودليل وتبقى صلاحية الرعاية والإرسال صريحة."},{"title":"رد دافع متنازع عليه خارج التفويض","situation":"يتلقى الفريق رداً يتطلب قراراً سريرياً أو تعاقدياً من المزود.","preparation":"رد أصلي وحدود تفويض ومراجع مزود وموعد وتصعيد.","steps":["صنف المشكلة دون افتراض صلاحية حسمها.","اجمع الأدلة المسموحة وحدد مسؤول المزود.","صعّد القرار بالمراجع والموعد.","استأنف المهمة الإدارية المعتمدة وسجّل حالتها النهائية."],"acceptance":"يوثق استثناء النطاق ولا يتخذ الفريق قراراً سريرياً أو مالياً غير مخوّل."}],"setupFiles":[{"template":"/implementation/templates/rcm_administration_agreements.csv","example":"/implementation/examples/rcm_administration_agreements.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/support_handover.csv","example":"/implementation/examples/support_handover.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/operating-room","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/operating-room","title":"Operating Room software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope.","description":"Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope. Verified case booking, preparation, perioperative…","answers":[{"question":"What does MANSOQ Operating Room cover?","answer":"Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope. Plan the procedure: Connect the procedure request to the patient and encounter. Configure theatres, practitioners, sessions, equipment and service codes; confirm the responsible surgeon, anesthesia team and receiving ward. Prepare & verify: Record preparation, consent references and the locally approved safety checklist. Review the relevant record, medication and required investigations before moving to the procedure. Document the procedure: Keep clinical documentation, observations, medication and used supplies with the encounter. Link performed services and consumables to the relevant stock and charge records where those modules are selected. Recover & hand over: Record recovery status and the next care plan. Transfer the current treatment, pending requests and responsibilities to the ward or discharge team, then reconcile documented service activity.","href":"/platform/operating-room#module-workflow"},{"question":"What setup data does Operating Room need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Rooms, wards and beds (locations.csv); Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Services & department catalogue (services.csv); Assets, devices & hardware (assets_devices.csv); Inventory & medication items (stock_items.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/operating-room#module-setup"},{"question":"How does Operating Room handle exceptions?","answer":"Procedure cancelled or rescheduled Record the reason, update the session and resources and review any preparation, stock or financial activity already recorded. Unplanned transfer to critical care Name the receiving team and carry anesthesia, medication, observations and outstanding actions into the handover.","href":"/platform/operating-room#module-exceptions"},{"question":"How does Operating Room connect with other systems?","answer":"Theatre scheduling and clinical records are composed with inpatient, medication, inventory and billing capabilities. Anesthesia-device capture and external theatre systems need separate interface acceptance.","href":"/platform/operating-room#module-connections"}],"module":{"name":"Operating Room","functions":["Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope."],"workflow":[{"title":"Plan the procedure","action":"Connect the procedure request to the patient and encounter. Configure theatres, practitioners, sessions, equipment and service codes; confirm the responsible surgeon, anesthesia team and receiving ward.","owner":"Theatre coordinator","record":"Procedure request, theatre session, team and resources"},{"title":"Prepare & verify","action":"Record preparation, consent references and the locally approved safety checklist. Review the relevant record, medication and required investigations before moving to the procedure.","owner":"Surgical and anesthesia team","record":"Preparation notes, consent and checklist evidence"},{"title":"Document the procedure","action":"Keep clinical documentation, observations, medication and used supplies with the encounter. Link performed services and consumables to the relevant stock and charge records where those modules are selected.","owner":"Procedure team","record":"Procedure notes, observations, medication and consumables"},{"title":"Recover & hand over","action":"Record recovery status and the next care plan. Transfer the current treatment, pending requests and responsibilities to the ward or discharge team, then reconcile documented service activity.","owner":"Recovery and receiving team","record":"Recovery record, handover and service reconciliation"}],"exceptions":[{"situation":"Procedure cancelled or rescheduled","response":"Record the reason, update the session and resources and review any preparation, stock or financial activity already recorded."},{"situation":"Unplanned transfer to critical care","response":"Name the receiving team and carry anesthesia, medication, observations and outstanding actions into the handover."}],"connection":"Theatre scheduling and clinical records are composed with inpatient, medication, inventory and billing capabilities. Anesthesia-device capture and external theatre systems need separate interface acceptance.","scenarios":[{"title":"Planned day surgery","situation":"A patient follows a scheduled procedure through preparation, surgery and recovery.","preparation":"Theatre, surgeon, anesthesia team, procedure service, approved checklist and recovery location.","steps":["Schedule the procedure and confirm staff, room and required resources.","Review preparation, consent and required investigations with the clinical team.","Document the procedure, medication, observations and used consumables.","Record recovery and handover, arrange discharge follow-up and reconcile performed services."],"acceptance":"Procedure, recovery, stock and charge records share the correct encounter and responsible team."},{"title":"Cancelled session with an unplanned transfer","situation":"A procedure plan changes and the patient needs a different receiving service.","preparation":"Cancellation rules, resource update authority, receiving team and medication handover.","steps":["Record the clinical and scheduling reason for the changed plan.","Review any preparation, medication, stock or charges already recorded.","Confirm the new receiving location and transfer the current record and outstanding work.","Reconcile resource availability and retained financial references after the change."],"acceptance":"The cancelled plan is retained and the new team receives current treatment and unresolved actions."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/operating-room?lang=ar","title":"غرفة العمليات | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية.","description":"نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية. نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد…","answers":[{"question":"ما نطاق غرفة العمليات في منسوق؟","answer":"نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية. تخطيط الإجراء: اربط طلب الإجراء بالمريض والزيارة. هيئ غرف العمليات والأطباء والجلسات والأجهزة ورموز الخدمات وأكد الجراح وفريق التخدير والجناح المستلم. التحضير والتحقق: سجّل التحضير ومراجع الموافقة وقائمة السلامة المحلية المعتمدة. راجع السجل والأدوية والفحوص المطلوبة قبل الإجراء. توثيق الإجراء: احفظ التوثيق السريري والقياسات والأدوية والمستلزمات المستخدمة مع الزيارة. اربط الخدمات والمستهلكات بالمخزون والرسوم عند اختيار وحداتها. الإفاقة والتسليم: سجّل حالة الإفاقة وخطة الرعاية التالية. سلّم العلاج الحالي والطلبات المعلقة والمسؤوليات للجناح أو فريق الخروج ثم طابق نشاط الخدمات الموثق.","href":"/platform/operating-room#module-workflow"},{"question":"ما بيانات إعداد غرفة العمليات؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الغرف والأجنحة والأسرة (locations.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة الجدولة (scheduling.csv)؛ الخدمات ودليل الأقسام (services.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ أصناف المخزون والأدوية (stock_items.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/operating-room#module-setup"},{"question":"كيف يتعامل غرفة العمليات مع الاستثناءات؟","answer":"إلغاء الإجراء أو تأجيله سجّل السبب وحدّث الجلسة والموارد وراجع التحضير والمخزون والنشاط المالي المسجل. نقل غير مخطط للعناية الحرجة حدد الفريق المستلم وانقل التخدير والأدوية والقياسات والإجراءات المعلقة للتسليم.","href":"/platform/operating-room#module-exceptions"},{"question":"كيف يتصل غرفة العمليات بالأنظمة الأخرى؟","answer":"تُجمع جدولة العمليات والسجلات السريرية مع التنويم والأدوية والمخزون والفوترة. يتطلب التقاط بيانات أجهزة التخدير والأنظمة الخارجية اعتماد ربط مستقلاً.","href":"/platform/operating-room#module-connections"}],"module":{"name":"غرفة العمليات","functions":["نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية."],"workflow":[{"title":"تخطيط الإجراء","action":"اربط طلب الإجراء بالمريض والزيارة. هيئ غرف العمليات والأطباء والجلسات والأجهزة ورموز الخدمات وأكد الجراح وفريق التخدير والجناح المستلم.","owner":"منسق العمليات","record":"طلب الإجراء وجلسة العمليات والفريق والموارد"},{"title":"التحضير والتحقق","action":"سجّل التحضير ومراجع الموافقة وقائمة السلامة المحلية المعتمدة. راجع السجل والأدوية والفحوص المطلوبة قبل الإجراء.","owner":"فريق الجراحة والتخدير","record":"ملاحظات التحضير والموافقة وأدلة القائمة"},{"title":"توثيق الإجراء","action":"احفظ التوثيق السريري والقياسات والأدوية والمستلزمات المستخدمة مع الزيارة. اربط الخدمات والمستهلكات بالمخزون والرسوم عند اختيار وحداتها.","owner":"فريق الإجراء","record":"ملاحظات الإجراء والقياسات والأدوية والمستهلكات"},{"title":"الإفاقة والتسليم","action":"سجّل حالة الإفاقة وخطة الرعاية التالية. سلّم العلاج الحالي والطلبات المعلقة والمسؤوليات للجناح أو فريق الخروج ثم طابق نشاط الخدمات الموثق.","owner":"فريق الإفاقة والفريق المستلم","record":"سجل الإفاقة والتسليم ومطابقة الخدمات"}],"exceptions":[{"situation":"إلغاء الإجراء أو تأجيله","response":"سجّل السبب وحدّث الجلسة والموارد وراجع التحضير والمخزون والنشاط المالي المسجل."},{"situation":"نقل غير مخطط للعناية الحرجة","response":"حدد الفريق المستلم وانقل التخدير والأدوية والقياسات والإجراءات المعلقة للتسليم."}],"connection":"تُجمع جدولة العمليات والسجلات السريرية مع التنويم والأدوية والمخزون والفوترة. يتطلب التقاط بيانات أجهزة التخدير والأنظمة الخارجية اعتماد ربط مستقلاً.","scenarios":[{"title":"جراحة يوم مخططة","situation":"يتبع مريض إجراء مجدولاً من التحضير للجراحة والإفاقة.","preparation":"غرفة عمليات وجراح وفريق تخدير وخدمة إجراء وقائمة معتمدة وموقع إفاقة.","steps":["جدول الإجراء وأكد الفريق والغرفة والموارد.","راجع التحضير والموافقة والفحوص مع الفريق.","وثق الإجراء والأدوية والقياسات والمستهلكات.","سجّل الإفاقة والتسليم ونظم متابعة الخروج وطابق الخدمات."],"acceptance":"ترتبط سجلات الإجراء والإفاقة والمخزون والرسوم بالزيارة والفريق الصحيحين."},{"title":"إلغاء جلسة ونقل غير مخطط","situation":"تتغير خطة إجراء ويحتاج المريض خدمة مستلمة مختلفة.","preparation":"قواعد الإلغاء وصلاحية تحديث الموارد والفريق المستلم وتسليم الأدوية.","steps":["سجّل السبب السريري والجدولي لتغير الخطة.","راجع التحضير والأدوية والمخزون والرسوم المسجلة.","أكد موقع الاستلام وانقل السجل والعمل المعلق.","طابق توافر الموارد والمراجع المالية بعد التغيير."],"acceptance":"تحفظ الخطة الملغاة ويتلقى الفريق الجديد العلاج الحالي والإجراءات المعلقة."}],"setupFiles":[{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/orders-medication","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/orders-medication","title":"Orders, Results & Medication software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Required order/result and medication scope for the chosen workflow, separate from native departmental operation.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Required order/result and medication scope for the chosen workflow, separate from native departmental operation.","description":"Required order/result and medication scope for the chosen workflow, separate from native departmental operation. Required order/result and medication scope for the chosen…","answers":[{"question":"What does MANSOQ Orders, Results & Medication cover?","answer":"Required order/result and medication scope for the chosen workflow, separate from native departmental operation. Define destinations: Configure requestable services, medication catalogues and departmental destinations. Agree order statuses, required information and which roles may create, change or cancel requests. Place the request: Link the order to the patient and encounter with the requested item, quantity and clinical context. For medication, record the dosage instructions and authorizing prescriber. Fulfil & track: Route work to the selected department or pharmacy. Track request status and linked specimen, diagnostic report, dispense or administration records without treating these distinct events as one completion. Review & reconcile: Review completed results and medication activity, document cancellations or changes and resolve outstanding requests at handover. Charge capture follows the performed service and selected billing configuration.","href":"/platform/orders-medication#module-workflow"},{"question":"What setup data does Orders, Results & Medication need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Services & department catalogue (services.csv); Inventory & medication items (stock_items.csv); Medication catalogue (medication_catalogue.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/orders-medication#module-setup"},{"question":"How does Orders, Results & Medication handle exceptions?","answer":"Request cancelled after work starts Confirm the actual departmental activity and review the cancellation, result and charge consequences with the relevant owner. Duplicate or conflicting medication request Have the authorized clinician and pharmacist review the requests and preserve the decision and original records.","href":"/platform/orders-medication#module-exceptions"},{"question":"How does Orders, Results & Medication connect with other systems?","answer":"Order management coordinates requests. Laboratory processing, imaging systems, dispensing and administration need the corresponding operational modules; an interface alone does not supply departmental operation.","href":"/platform/orders-medication#module-connections"}],"module":{"name":"Orders, Results & Medication","functions":["Required order/result and medication scope for the chosen workflow, separate from native departmental operation."],"workflow":[{"title":"Define destinations","action":"Configure requestable services, medication catalogues and departmental destinations. Agree order statuses, required information and which roles may create, change or cancel requests.","owner":"Clinical and catalogue administrators","record":"Service definitions, medication products and routing rules"},{"title":"Place the request","action":"Link the order to the patient and encounter with the requested item, quantity and clinical context. For medication, record the dosage instructions and authorizing prescriber.","owner":"Ordering clinician","record":"Service or medication request and author"},{"title":"Fulfil & track","action":"Route work to the selected department or pharmacy. Track request status and linked specimen, diagnostic report, dispense or administration records without treating these distinct events as one completion.","owner":"Department, pharmacy and nursing team","record":"Request status, fulfilment records and linked results"},{"title":"Review & reconcile","action":"Review completed results and medication activity, document cancellations or changes and resolve outstanding requests at handover. Charge capture follows the performed service and selected billing configuration.","owner":"Responsible clinician and billing team","record":"Result review, cancelled requests and charge links"}],"exceptions":[{"situation":"Request cancelled after work starts","response":"Confirm the actual departmental activity and review the cancellation, result and charge consequences with the relevant owner."},{"situation":"Duplicate or conflicting medication request","response":"Have the authorized clinician and pharmacist review the requests and preserve the decision and original records."}],"connection":"Order management coordinates requests. Laboratory processing, imaging systems, dispensing and administration need the corresponding operational modules; an interface alone does not supply departmental operation.","scenarios":[{"title":"Consultation creates diagnostic and medication requests","situation":"A clinician requests an investigation and medication during the same encounter.","preparation":"Service destinations, medication catalogue, permitted prescribers and departmental queues.","steps":["Create distinct service and medication requests with their clinical context.","Route the service to its department and the prescription to pharmacy review.","Link returned reports, actual dispensing and any administration as separate fulfilment records.","The clinician reviews results and the team resolves remaining requests and relevant charges."],"acceptance":"A requested item is not confused with a performed, dispensed or administered item."},{"title":"Changed request after partial fulfilment","situation":"A clinician changes the care plan after the department or pharmacy has started work.","preparation":"Change and cancellation permissions, fulfilment status and charge-correction policy.","steps":["Review the original order and what has actually been performed or dispensed.","Record the authorized change or cancellation and its reason.","Communicate the updated plan to the receiving department and pharmacy.","Reconcile existing fulfilment and charges and name any remaining action owner."],"acceptance":"Original requests, fulfilment and changes remain traceable, with no assumed completion."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/orders-medication?lang=ar","title":"الطلبات والنتائج والأدوية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام.","description":"نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام. نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام..","answers":[{"question":"ما نطاق الطلبات والنتائج والأدوية في منسوق؟","answer":"نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام. تعريف الوجهات: هيئ الخدمات القابلة للطلب وكتالوجات الأدوية ووجهات الأقسام. اتفق على حالات الطلب والمعلومات المطلوبة وأدوار الإنشاء والتغيير والإلغاء. إنشاء الطلب: اربط الطلب بالمريض والزيارة والصنف والكمية والسياق السريري. سجّل تعليمات الجرعة والطبيب المخوّل للأدوية. التنفيذ والتتبع: وجّه العمل للقسم أو الصيدلية المختارة. تابع حالة الطلب والعينة والتقرير والصرف أو الإعطاء المرتبطين دون اعتبار هذه الأحداث المختلفة إكمالاً واحداً. المراجعة والمطابقة: راجع النتائج ونشاط الأدوية ووثق الإلغاء والتغييرات وأكمل الطلبات المعلقة عند التسليم. يتبع التقاط الرسوم الخدمة المنفذة وتهيئة الفوترة المختارة.","href":"/platform/orders-medication#module-workflow"},{"question":"ما بيانات إعداد الطلبات والنتائج والأدوية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الخدمات ودليل الأقسام (services.csv)؛ أصناف المخزون والأدوية (stock_items.csv)؛ دليل الأدوية (medication_catalogue.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/orders-medication#module-setup"},{"question":"كيف يتعامل الطلبات والنتائج والأدوية مع الاستثناءات؟","answer":"إلغاء طلب بعد بدء التنفيذ أكد النشاط المنفذ وراجع أثر الإلغاء على النتيجة والرسوم مع المسؤول. طلب دواء مكرر أو متعارض اطلب مراجعة الطبيب والصيدلي المخولين واحتفظ بالقرار والسجلات الأصلية.","href":"/platform/orders-medication#module-exceptions"},{"question":"كيف يتصل الطلبات والنتائج والأدوية بالأنظمة الأخرى؟","answer":"تنسق إدارة الطلبات الطلبات. تحتاج معالجة المختبر والأشعة والصرف والإعطاء وحداتها التشغيلية؛ لا يوفر الاتصال وحده تشغيل القسم.","href":"/platform/orders-medication#module-connections"}],"module":{"name":"الطلبات والنتائج والأدوية","functions":["نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام."],"workflow":[{"title":"تعريف الوجهات","action":"هيئ الخدمات القابلة للطلب وكتالوجات الأدوية ووجهات الأقسام. اتفق على حالات الطلب والمعلومات المطلوبة وأدوار الإنشاء والتغيير والإلغاء.","owner":"مديرو الكتالوج والتهيئة السريرية","record":"تعريفات الخدمات ومنتجات الأدوية وقواعد التوجيه"},{"title":"إنشاء الطلب","action":"اربط الطلب بالمريض والزيارة والصنف والكمية والسياق السريري. سجّل تعليمات الجرعة والطبيب المخوّل للأدوية.","owner":"الطبيب الطالب","record":"طلب الخدمة أو الدواء والمؤلف"},{"title":"التنفيذ والتتبع","action":"وجّه العمل للقسم أو الصيدلية المختارة. تابع حالة الطلب والعينة والتقرير والصرف أو الإعطاء المرتبطين دون اعتبار هذه الأحداث المختلفة إكمالاً واحداً.","owner":"القسم والصيدلية والتمريض","record":"حالة الطلب وسجلات التنفيذ والنتائج المرتبطة"},{"title":"المراجعة والمطابقة","action":"راجع النتائج ونشاط الأدوية ووثق الإلغاء والتغييرات وأكمل الطلبات المعلقة عند التسليم. يتبع التقاط الرسوم الخدمة المنفذة وتهيئة الفوترة المختارة.","owner":"الطبيب المسؤول وفريق الفوترة","record":"مراجعة النتائج والطلبات الملغاة وروابط الرسوم"}],"exceptions":[{"situation":"إلغاء طلب بعد بدء التنفيذ","response":"أكد النشاط المنفذ وراجع أثر الإلغاء على النتيجة والرسوم مع المسؤول."},{"situation":"طلب دواء مكرر أو متعارض","response":"اطلب مراجعة الطبيب والصيدلي المخولين واحتفظ بالقرار والسجلات الأصلية."}],"connection":"تنسق إدارة الطلبات الطلبات. تحتاج معالجة المختبر والأشعة والصرف والإعطاء وحداتها التشغيلية؛ لا يوفر الاتصال وحده تشغيل القسم.","scenarios":[{"title":"استشارة تنتج طلبات تشخيص وأدوية","situation":"يطلب طبيب فحصاً ودواء في الزيارة نفسها.","preparation":"وجهات خدمات وكتالوج أدوية وأطباء مخولون وقوائم أقسام.","steps":["أنشئ طلب خدمة وطلب دواء مستقلين بسياقهما.","وجه الخدمة للقسم والوصفة لمراجعة الصيدلية.","اربط التقارير والصرف الفعلي والإعطاء كسجلات تنفيذ مستقلة.","يراجع الطبيب النتائج ويعالج الفريق الطلبات والرسوم المعلقة."],"acceptance":"لا يُخلط الصنف المطلوب مع المنفذ أو المصروف أو المعطى."},{"title":"تغيير طلب بعد تنفيذ جزئي","situation":"يغير الطبيب الخطة بعد بدء القسم أو الصيدلية العمل.","preparation":"صلاحيات التغيير والإلغاء وحالة التنفيذ وسياسة تصحيح الرسوم.","steps":["راجع الطلب الأصلي والمنفذ أو المصروف فعلياً.","سجّل التغيير أو الإلغاء المخوّل وسببه.","أبلغ القسم والصيدلية بالخطة المحدثة.","طابق التنفيذ والرسوم وحدد مسؤول الإجراء المتبقي."],"acceptance":"تظل الطلبات والتنفيذ والتغييرات قابلة للتتبع دون إكمال مفترض."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/outpatient","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/outpatient","title":"Outpatient Care software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope.","description":"Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope. Registration, availability and appointments, Queues and…","answers":[{"question":"What does MANSOQ Outpatient Care cover?","answer":"Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope. Book & arrive: Configure clinic services, practitioner resources, sessions and visit types. Book into the intended slot, record arrival and route the visit to the appropriate clinical team. Consult: Open the encounter, review relevant history and allergies, capture observations and document the assessment. Use approved forms and keep the author and encounter attached to the record. Order & act: Create service and medication requests with their clinical context. Route them to the selected laboratory, radiology or pharmacy workflow; review completed results before determining the next action. Close & follow up: Document the care plan and follow-up responsibility, complete the encounter and link performed services to billing. Insurance verification, claims and electronic invoices depend on the selected revenue extensions.","href":"/platform/outpatient#module-workflow"},{"question":"What setup data does Outpatient Care need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Departments (departments.csv); Rooms, wards and beds (locations.csv); Doctors & operational clinics (doctors.csv); Doctor schedules · every department (doctor_schedules.csv); Services & department catalogue (services.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/outpatient#module-setup"},{"question":"How does Outpatient Care handle exceptions?","answer":"Cancellation or missed appointment Record the booking disposition, review resource availability and apply the approved rebooking and charging policy. Referral to another specialty Carry the reason, current record and outstanding requests into the receiving team’s workflow; name the follow-up owner.","href":"/platform/outpatient#module-exceptions"},{"question":"How does Outpatient Care connect with other systems?","answer":"Scheduling and encounters form the visit pathway. Department operation, results exchange, medication and insurance processing are configured through their own modules.","href":"/platform/outpatient#module-connections"}],"module":{"name":"Outpatient Care","functions":["Registration, availability and appointments","Queues and encounter context","Clinical documentation and relevant results","Orders, prescriptions and follow-up","Core visit billing"],"workflow":[{"title":"Book & arrive","action":"Configure clinic services, practitioner resources, sessions and visit types. Book into the intended slot, record arrival and route the visit to the appropriate clinical team.","owner":"Reception and scheduling","record":"Resource, schedule, booking, patient and visit type"},{"title":"Consult","action":"Open the encounter, review relevant history and allergies, capture observations and document the assessment. Use approved forms and keep the author and encounter attached to the record.","owner":"Clinician and nurse","record":"Encounter, observations, conditions, allergies and notes"},{"title":"Order & act","action":"Create service and medication requests with their clinical context. Route them to the selected laboratory, radiology or pharmacy workflow; review completed results before determining the next action.","owner":"Clinician and department teams","record":"Service requests, prescriptions and linked reports"},{"title":"Close & follow up","action":"Document the care plan and follow-up responsibility, complete the encounter and link performed services to billing. Insurance verification, claims and electronic invoices depend on the selected revenue extensions.","owner":"Care coordinator and billing team","record":"Follow-up booking, encounter completion and charges"}],"exceptions":[{"situation":"Cancellation or missed appointment","response":"Record the booking disposition, review resource availability and apply the approved rebooking and charging policy."},{"situation":"Referral to another specialty","response":"Carry the reason, current record and outstanding requests into the receiving team’s workflow; name the follow-up owner."}],"connection":"Scheduling and encounters form the visit pathway. Department operation, results exchange, medication and insurance processing are configured through their own modules.","scenarios":[{"title":"First consultation with diagnostic follow-up","situation":"A new patient books a consultation and the clinician requests investigations before a return visit.","preparation":"Clinic, practitioner session, visit service, diagnostic catalogue and permitted clinical roles.","steps":["Reception registers the person and books an available practitioner slot.","The clinician records the assessment, observations and reason for each investigation.","The selected departments return reports linked to the original encounter.","The care coordinator books the follow-up and billing reviews the performed services."],"acceptance":"The follow-up owner, pending results and charge references can be traced back to the consultation."},{"title":"Rescheduled specialist referral","situation":"A patient’s specialty appointment changes after another clinician has already documented the referral.","preparation":"Referral context, receiving clinic, updated resource schedule and cancellation policy.","steps":["Keep the original referral and record why the appointment changed.","Rebook the receiving service against accepted availability.","The specialist reviews the existing context and documents the new encounter and requests.","Assign the next follow-up and review any prior booking or billing effect."],"acceptance":"The referral survives rescheduling and the receiving team has the relevant clinical history."}],"setupFiles":[{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/outpatient?lang=ar","title":"رعاية العيادات الخارجية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"التسجيل والمواعيد وقوائم الزيارات والاستشارات والمتابعة مع النطاق السريري والفوترة المطلوبين.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"التسجيل والمواعيد وقوائم الزيارات والاستشارات والمتابعة مع النطاق السريري والفوترة المطلوبين.","description":"التسجيل والمواعيد وقوائم الزيارات والاستشارات والمتابعة مع النطاق السريري والفوترة المطلوبين. التسجيل والتوافر والمواعيد، قوائم الانتظار وسياق الزيارة، التوثيق السريري والنتائج ذات…","answers":[{"question":"ما نطاق رعاية العيادات الخارجية في منسوق؟","answer":"التسجيل والمواعيد وقوائم الزيارات والاستشارات والمتابعة مع النطاق السريري والفوترة المطلوبين. الحجز والوصول: هيئ خدمات العيادة والأطباء والجلسات وأنواع الزيارات. احجز في الفترة المناسبة وسجّل الوصول ووجّه الزيارة للفريق السريري. الاستشارة: افتح الزيارة وراجع التاريخ المرضي والحساسيات وسجّل القياسات والتقييم. استخدم النماذج المعتمدة واحتفظ بارتباط المؤلف والزيارة بالسجل. الطلبات والتنفيذ: أنشئ طلبات الخدمات والأدوية بسياقها السريري. وجّهها للمختبر أو الأشعة أو الصيدلية المختارة وراجع النتائج المكتملة قبل تحديد الخطوة التالية. الإغلاق والمتابعة: وثق خطة الرعاية ومسؤولية المتابعة وأكمل الزيارة واربط الخدمات المنفذة بالفوترة. يعتمد التأمين والمطالبات والفواتير الإلكترونية على إضافات الإيرادات المختارة.","href":"/platform/outpatient#module-workflow"},{"question":"ما بيانات إعداد رعاية العيادات الخارجية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الأقسام (departments.csv)؛ الغرف والأجنحة والأسرة (locations.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ جداول الأطباء لجميع الأقسام (doctor_schedules.csv)؛ الخدمات ودليل الأقسام (services.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/outpatient#module-setup"},{"question":"كيف يتعامل رعاية العيادات الخارجية مع الاستثناءات؟","answer":"إلغاء الموعد أو عدم الحضور سجّل حالة الحجز وراجع توافر المورد وطبّق سياسة إعادة الحجز والرسوم المعتمدة. إحالة إلى تخصص آخر انقل سبب الإحالة والسجل والطلبات المعلقة لمسار الفريق المستلم وحدد مسؤول المتابعة.","href":"/platform/outpatient#module-exceptions"},{"question":"كيف يتصل رعاية العيادات الخارجية بالأنظمة الأخرى؟","answer":"تشكل المواعيد والزيارات مسار الزيارة. يهيأ تشغيل الأقسام وتبادل النتائج والأدوية والتأمين عبر وحداتها.","href":"/platform/outpatient#module-connections"}],"module":{"name":"رعاية العيادات الخارجية","functions":["التسجيل والتوافر والمواعيد","قوائم الانتظار وسياق الزيارة","التوثيق السريري والنتائج ذات الصلة","الطلبات والوصفات والمتابعة","الفوترة الأساسية للزيارة"],"workflow":[{"title":"الحجز والوصول","action":"هيئ خدمات العيادة والأطباء والجلسات وأنواع الزيارات. احجز في الفترة المناسبة وسجّل الوصول ووجّه الزيارة للفريق السريري.","owner":"الاستقبال والمواعيد","record":"المورد والجدول والحجز والمريض ونوع الزيارة"},{"title":"الاستشارة","action":"افتح الزيارة وراجع التاريخ المرضي والحساسيات وسجّل القياسات والتقييم. استخدم النماذج المعتمدة واحتفظ بارتباط المؤلف والزيارة بالسجل.","owner":"الطبيب والممرض","record":"الزيارة والقياسات والتشخيصات والحساسيات والملاحظات"},{"title":"الطلبات والتنفيذ","action":"أنشئ طلبات الخدمات والأدوية بسياقها السريري. وجّهها للمختبر أو الأشعة أو الصيدلية المختارة وراجع النتائج المكتملة قبل تحديد الخطوة التالية.","owner":"الطبيب وفرق الأقسام","record":"طلبات الخدمات والوصفات والتقارير المرتبطة"},{"title":"الإغلاق والمتابعة","action":"وثق خطة الرعاية ومسؤولية المتابعة وأكمل الزيارة واربط الخدمات المنفذة بالفوترة. يعتمد التأمين والمطالبات والفواتير الإلكترونية على إضافات الإيرادات المختارة.","owner":"منسق الرعاية وفريق الفوترة","record":"حجز المتابعة وإكمال الزيارة والرسوم"}],"exceptions":[{"situation":"إلغاء الموعد أو عدم الحضور","response":"سجّل حالة الحجز وراجع توافر المورد وطبّق سياسة إعادة الحجز والرسوم المعتمدة."},{"situation":"إحالة إلى تخصص آخر","response":"انقل سبب الإحالة والسجل والطلبات المعلقة لمسار الفريق المستلم وحدد مسؤول المتابعة."}],"connection":"تشكل المواعيد والزيارات مسار الزيارة. يهيأ تشغيل الأقسام وتبادل النتائج والأدوية والتأمين عبر وحداتها.","scenarios":[{"title":"استشارة أولى مع متابعة تشخيصية","situation":"يحجز مريض جديد استشارة ويطلب الطبيب فحوصاً قبل زيارة متابعة.","preparation":"عيادة وجلسة طبيب وخدمة زيارة وكتالوج تشخيص وصلاحيات سريرية.","steps":["يسجل الاستقبال الشخص ويحجز فترة متاحة للطبيب.","يوثق الطبيب التقييم والقياسات وسبب كل فحص.","تعيد الأقسام المختارة تقارير مرتبطة بالزيارة الأصلية.","يحجز منسق الرعاية المتابعة وتراجع الفوترة الخدمات المنفذة."],"acceptance":"يمكن تتبع مسؤول المتابعة والنتائج المعلقة ومراجع الرسوم للاستشارة."},{"title":"إحالة تخصصية مع إعادة جدولة","situation":"يتغير موعد تخصصي بعد توثيق الإحالة من طبيب آخر.","preparation":"سياق الإحالة والعيادة المستلمة وجدول محدث وسياسة الإلغاء.","steps":["احفظ الإحالة الأصلية وسجّل سبب تغيير الموعد.","أعد الحجز للخدمة المستلمة حسب التوافر المعتمد.","يراجع المختص السياق ويوثق الزيارة الجديدة والطلبات.","حدد المتابعة التالية وراجع أثر الحجز أو الفوترة السابقة."],"acceptance":"تظل الإحالة محفوظة بعد إعادة الجدولة ويتوفر التاريخ المناسب للفريق المستلم."}],"setupFiles":[{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/patient-access","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/patient-access","title":"Patient Access software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified.","description":"Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified. Registration, scheduling, encounter access and…","answers":[{"question":"What does MANSOQ Patient Access cover?","answer":"Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified. Publish availability: Configure practitioner or location resources, session dates, opening hours and slot rules. Link services and approved booking permissions to the resource. Register & book: Identify the patient, review contact and identifier information and book the intended service. Preserve referral and payer details where the selected care and revenue workflow requires them. Arrive & route: Record arrival and queue information, open or link the encounter and direct the person to the responsible clinic or department. Confirm the next responsibility rather than leaving a booking without a care destination. Reschedule & follow up: Record completion, cancellation or missed attendance, then arrange an appropriate follow-up. Apply the configured revisit and charging policy using the selected billing workflow.","href":"/platform/patient-access#module-workflow"},{"question":"What setup data does Patient Access need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Departments (departments.csv); Rooms, wards and beds (locations.csv); Doctors & operational clinics (doctors.csv); Doctor schedules · every department (doctor_schedules.csv); Services & department catalogue (services.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/patient-access#module-setup"},{"question":"How does Patient Access handle exceptions?","answer":"Overlapping resource schedules Review session dates, resource assignments and slot rules before publishing corrected availability. Patient returns under a revisit rule Check the originating visit, valid period and applicable service charge; keep the decision linked to the booking.","href":"/platform/patient-access#module-exceptions"},{"question":"How does Patient Access connect with other systems?","answer":"Access links a person to a care service. Public booking channels, patient communications and external identity or insurance services require selected and accepted connections.","href":"/platform/patient-access#module-connections"}],"module":{"name":"Patient Access","functions":["Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified."],"workflow":[{"title":"Publish availability","action":"Configure practitioner or location resources, session dates, opening hours and slot rules. Link services and approved booking permissions to the resource.","owner":"Scheduling administrator","record":"Schedulable resource, schedule and slot configuration"},{"title":"Register & book","action":"Identify the patient, review contact and identifier information and book the intended service. Preserve referral and payer details where the selected care and revenue workflow requires them.","owner":"Reception team","record":"Patient, booking, referral and coverage references"},{"title":"Arrive & route","action":"Record arrival and queue information, open or link the encounter and direct the person to the responsible clinic or department. Confirm the next responsibility rather than leaving a booking without a care destination.","owner":"Reception and care coordinator","record":"Arrival, queue token and encounter linkage"},{"title":"Reschedule & follow up","action":"Record completion, cancellation or missed attendance, then arrange an appropriate follow-up. Apply the configured revisit and charging policy using the selected billing workflow.","owner":"Scheduling and billing team","record":"Booking disposition, follow-up and billing references"}],"exceptions":[{"situation":"Overlapping resource schedules","response":"Review session dates, resource assignments and slot rules before publishing corrected availability."},{"situation":"Patient returns under a revisit rule","response":"Check the originating visit, valid period and applicable service charge; keep the decision linked to the booking."}],"connection":"Access links a person to a care service. Public booking channels, patient communications and external identity or insurance services require selected and accepted connections.","scenarios":[{"title":"New patient books a clinic service","situation":"Reception converts an available practitioner session into a patient visit.","preparation":"Practitioner resource, session, slot, service and registration permissions.","steps":["Check patient identity and contact details before booking.","Choose the intended service and available slot under the configured schedule.","Record arrival and queue or encounter linkage.","Hand the person to the responsible clinic and record the booking disposition."],"acceptance":"Booking, arrival and encounter refer to the same patient and intended care resource."},{"title":"Resource change and revisit booking","situation":"A practitioner session changes and a returning patient needs rebooking under the accepted revisit rules.","preparation":"Updated session, original visit reference, revisit period and billing authority.","steps":["Review the session change and affected bookings.","Retain the original visit and check revisit validity and service context.","Rebook against accepted availability and explain the new care destination.","Review any charge consequence through the configured billing workflow."],"acceptance":"The schedule change, original visit and new booking remain linked; the revisit charge decision is evidenced."}],"setupFiles":[{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/patient-access?lang=ar","title":"وصول المريض إلى الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة.","description":"التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة. التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من…","answers":[{"question":"ما نطاق وصول المريض إلى الرعاية في منسوق؟","answer":"التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة. تحديد التوافر: هيئ موارد الأطباء أو المواقع وتواريخ الجلسات وساعات العمل وقواعد الفترات. اربط الخدمات وصلاحيات الحجز المعتمدة بالمورد. التسجيل والحجز: حدد المريض وراجع التواصل والمعرّفات واحجز الخدمة المطلوبة. احفظ تفاصيل الإحالة والدافع عند طلبها من مسار الرعاية والإيرادات المختار. الوصول والتوجيه: سجّل الوصول ومعلومات قائمة الانتظار وافتح الزيارة أو اربطها ووجّه الشخص للعيادة أو القسم المسؤول. أكد المسؤولية التالية للحجز. إعادة الجدولة والمتابعة: سجّل الإكمال أو الإلغاء أو عدم الحضور ونظّم المتابعة المناسبة. طبّق سياسة إعادة الزيارة والرسوم عبر مسار الفوترة المختار.","href":"/platform/patient-access#module-workflow"},{"question":"ما بيانات إعداد وصول المريض إلى الرعاية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الأقسام (departments.csv)؛ الغرف والأجنحة والأسرة (locations.csv)؛ الأطباء والعيادات التشغيلية (doctors.csv)؛ جداول الأطباء لجميع الأقسام (doctor_schedules.csv)؛ الخدمات ودليل الأقسام (services.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/patient-access#module-setup"},{"question":"كيف يتعامل وصول المريض إلى الرعاية مع الاستثناءات؟","answer":"تداخل جداول الموارد راجع تواريخ الجلسات وتعيين الموارد وقواعد الفترات قبل نشر التوافر المصحح. عودة المريض وفق قاعدة إعادة الزيارة تحقق من الزيارة الأصلية والفترة الصالحة والرسوم المنطبقة واربط القرار بالحجز.","href":"/platform/patient-access#module-exceptions"},{"question":"كيف يتصل وصول المريض إلى الرعاية بالأنظمة الأخرى؟","answer":"يربط الاستقبال الشخص بخدمة رعاية. تحتاج قنوات الحجز العامة والتواصل والهوية أو التأمين الخارجي اتصالات مختارة ومعتمدة.","href":"/platform/patient-access#module-connections"}],"module":{"name":"وصول المريض إلى الرعاية","functions":["التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة."],"workflow":[{"title":"تحديد التوافر","action":"هيئ موارد الأطباء أو المواقع وتواريخ الجلسات وساعات العمل وقواعد الفترات. اربط الخدمات وصلاحيات الحجز المعتمدة بالمورد.","owner":"مدير المواعيد","record":"مورد الجدولة والجدول وتهيئة الفترات"},{"title":"التسجيل والحجز","action":"حدد المريض وراجع التواصل والمعرّفات واحجز الخدمة المطلوبة. احفظ تفاصيل الإحالة والدافع عند طلبها من مسار الرعاية والإيرادات المختار.","owner":"فريق الاستقبال","record":"المريض والحجز ومراجع الإحالة والتغطية"},{"title":"الوصول والتوجيه","action":"سجّل الوصول ومعلومات قائمة الانتظار وافتح الزيارة أو اربطها ووجّه الشخص للعيادة أو القسم المسؤول. أكد المسؤولية التالية للحجز.","owner":"الاستقبال ومنسق الرعاية","record":"الوصول ورمز الانتظار وارتباط الزيارة"},{"title":"إعادة الجدولة والمتابعة","action":"سجّل الإكمال أو الإلغاء أو عدم الحضور ونظّم المتابعة المناسبة. طبّق سياسة إعادة الزيارة والرسوم عبر مسار الفوترة المختار.","owner":"فريق المواعيد والفوترة","record":"حالة الحجز والمتابعة ومراجع الفوترة"}],"exceptions":[{"situation":"تداخل جداول الموارد","response":"راجع تواريخ الجلسات وتعيين الموارد وقواعد الفترات قبل نشر التوافر المصحح."},{"situation":"عودة المريض وفق قاعدة إعادة الزيارة","response":"تحقق من الزيارة الأصلية والفترة الصالحة والرسوم المنطبقة واربط القرار بالحجز."}],"connection":"يربط الاستقبال الشخص بخدمة رعاية. تحتاج قنوات الحجز العامة والتواصل والهوية أو التأمين الخارجي اتصالات مختارة ومعتمدة.","scenarios":[{"title":"مريض جديد يحجز خدمة عيادة","situation":"يحول الاستقبال جلسة طبيب متاحة لزيارة مريض.","preparation":"مورد طبيب وجلسة وفترة وخدمة وصلاحيات تسجيل.","steps":["تحقق من الهوية والتواصل قبل الحجز.","اختر الخدمة والفترة المتاحة وفق الجدول.","سجّل الوصول وارتباط الانتظار أو الزيارة.","وجه الشخص للعيادة المسؤولة وسجّل حالة الحجز."],"acceptance":"يشير الحجز والوصول والزيارة للمريض ومورد الرعاية المطلوب نفسيهما."},{"title":"تغيير مورد وحجز إعادة زيارة","situation":"تتغير جلسة طبيب ويحتاج مريض عائد إعادة حجز وفق قواعد الزيارة.","preparation":"جلسة محدثة ومرجع زيارة أصلية وفترة إعادة زيارة وصلاحية فوترة.","steps":["راجع تغير الجلسة والحجوزات المتأثرة.","احفظ الزيارة الأصلية وتحقق من صلاحية الإعادة والخدمة.","أعد الحجز حسب التوافر المعتمد ووضح وجهة الرعاية.","راجع أثر الرسوم عبر الفوترة المهيأة."],"acceptance":"يرتبط تغيير الجدول والزيارة الأصلية والحجز الجديد ويوثق قرار رسوم الإعادة."}],"setupFiles":[{"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/pharmacy","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/pharmacy","title":"Pharmacy software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list.","description":"Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list. Medication requests, dispensing and stock operation beyond prescribing or…","answers":[{"question":"What does MANSOQ Pharmacy cover?","answer":"Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list. Prescribe: Create the medication request with the encounter, product, dose, route, frequency and duration. Keep allergy and current medication context available for professional review. Verify & prepare: Review the prescription in the pharmacy queue, confirm the item and quantity and choose the appropriate stock lot. Record any substitution through the authorized process rather than silently changing the prescription. Dispense & hand over: Record prepared and handed-over medication, quantity, days supply and instructions. Link the dispense record to the patient, location, authorizing request and applicable charge. Track & reconcile: Review outstanding prescriptions, completed dispensing and inventory movements. Handle returns and corrections through the approved stock and finance processes; inpatient administration remains a separate clinical record.","href":"/platform/pharmacy#module-workflow"},{"question":"What setup data does Pharmacy need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Inventory & medication items (stock_items.csv); Stock lots & opening quantities (stock_balances.csv); Medication catalogue (medication_catalogue.csv); Clinical workflow configuration (clinical_workflows.csv); Assets, devices & hardware (assets_devices.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/pharmacy#module-setup"},{"question":"How does Pharmacy handle exceptions?","answer":"Partial quantity or unavailable stock Record the quantity actually dispensed, retain the remaining prescription responsibility and apply approved substitution or replenishment rules. Expired lot or returned medication Follow the quarantine and return policy; reconcile the inventory movement and financial effect without deleting the dispense history.","href":"/platform/pharmacy#module-exceptions"},{"question":"How does Pharmacy connect with other systems?","answer":"Prescribing, dispensing, administration and stock are linked but separate records. Formulary rules, unit conversions, payer coverage and external dispensers need their own accepted configuration.","href":"/platform/pharmacy#module-connections"}],"module":{"name":"Pharmacy","functions":["Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list."],"workflow":[{"title":"Prescribe","action":"Create the medication request with the encounter, product, dose, route, frequency and duration. Keep allergy and current medication context available for professional review.","owner":"Prescribing clinician","record":"Medication request and dosage instructions"},{"title":"Verify & prepare","action":"Review the prescription in the pharmacy queue, confirm the item and quantity and choose the appropriate stock lot. Record any substitution through the authorized process rather than silently changing the prescription.","owner":"Pharmacist","record":"Prescription queue, inventory item, lot and substitution record"},{"title":"Dispense & hand over","action":"Record prepared and handed-over medication, quantity, days supply and instructions. Link the dispense record to the patient, location, authorizing request and applicable charge.","owner":"Pharmacy dispensing team","record":"Dispense order, timestamps, quantity, item and charge"},{"title":"Track & reconcile","action":"Review outstanding prescriptions, completed dispensing and inventory movements. Handle returns and corrections through the approved stock and finance processes; inpatient administration remains a separate clinical record.","owner":"Pharmacy, inventory and ward teams","record":"Dispense history, stock balance and administration links"}],"exceptions":[{"situation":"Partial quantity or unavailable stock","response":"Record the quantity actually dispensed, retain the remaining prescription responsibility and apply approved substitution or replenishment rules."},{"situation":"Expired lot or returned medication","response":"Follow the quarantine and return policy; reconcile the inventory movement and financial effect without deleting the dispense history."}],"connection":"Prescribing, dispensing, administration and stock are linked but separate records. Formulary rules, unit conversions, payer coverage and external dispensers need their own accepted configuration.","scenarios":[{"title":"Prescription to documented handover","situation":"A clinician prescribes a medication and the patient receives the reviewed quantity from pharmacy.","preparation":"Medication catalogue, dosage units, valid stock lots, pharmacy roles and charge configuration.","steps":["The clinician records the medication request and dosage instructions in the encounter.","The pharmacist reviews the prescription, product and available lot.","Record the actual quantity, days supply, preparation and handover with patient instructions.","Reconcile the dispense record, stock movement and applicable charge; administration is recorded separately if relevant."],"acceptance":"The authorized request, dispensed lot, handed-over quantity and stock movement are traceable."},{"title":"Partial dispense followed by a return","situation":"Only part of a prescribed quantity is available and a later return needs stock and financial review.","preparation":"Partial-dispense policy, outstanding prescription owner, return and quarantine rules.","steps":["Review the prescribed and available quantities with the pharmacist.","Record only the actual dispense and retain responsibility for the remainder.","On return, verify the original dispense and apply the approved inspection and quarantine procedure.","Reconcile accepted stock and financial effects while preserving the dispensing history."],"acceptance":"Requested, dispensed, outstanding and returned quantities remain distinguishable."}],"setupFiles":[{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/pharmacy?lang=ar","title":"الصيدلية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته.","description":"طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته. طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته..","answers":[{"question":"ما نطاق الصيدلية في منسوق؟","answer":"طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته. الوصف: أنشئ طلب الدواء بالزيارة والمنتج والجرعة وطريقة الإعطاء والتكرار والمدة. أتح سياق الحساسيات والأدوية الحالية للمراجعة المهنية. التحقق والتحضير: راجع الوصفة في قائمة الصيدلية وأكد الصنف والكمية واختر التشغيلة المناسبة. سجّل أي استبدال عبر الإجراء المخوّل دون تغيير الوصفة ضمنياً. الصرف والتسليم: سجّل تحضير الدواء وتسليمه والكمية وأيام التغطية والتعليمات. اربط الصرف بالمريض والموقع والطلب المخوّل والرسوم المنطبقة. التتبع والمطابقة: راجع الوصفات المعلقة والصرف المكتمل وحركات المخزون. عالج المرتجعات والتصحيحات عبر إجراءات المخزون والمالية المعتمدة؛ يبقى إعطاء الدواء للمنوّم سجلاً سريرياً مستقلاً.","href":"/platform/pharmacy#module-workflow"},{"question":"ما بيانات إعداد الصيدلية؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: أصناف المخزون والأدوية (stock_items.csv)؛ التشغيلات وأرصدة المخزون (stock_balances.csv)؛ دليل الأدوية (medication_catalogue.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/pharmacy#module-setup"},{"question":"كيف يتعامل الصيدلية مع الاستثناءات؟","answer":"كمية جزئية أو مخزون غير متوفر سجّل الكمية المصروفة فعلياً واحتفظ بمسؤولية الكمية المتبقية وطبّق قواعد الاستبدال أو التوريد المعتمدة. تشغيلة منتهية أو دواء مرتجع اتبع سياسة العزل والمرتجعات وطابق حركة المخزون والأثر المالي دون حذف تاريخ الصرف.","href":"/platform/pharmacy#module-exceptions"},{"question":"كيف يتصل الصيدلية بالأنظمة الأخرى؟","answer":"الوصف والصرف والإعطاء والمخزون سجلات مترابطة ومستقلة. تحتاج قواعد قائمة الأدوية وتحويل الوحدات والتغطية والصرف الخارجي تهيئة معتمدة لكل منها.","href":"/platform/pharmacy#module-connections"}],"module":{"name":"الصيدلية","functions":["طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته."],"workflow":[{"title":"الوصف","action":"أنشئ طلب الدواء بالزيارة والمنتج والجرعة وطريقة الإعطاء والتكرار والمدة. أتح سياق الحساسيات والأدوية الحالية للمراجعة المهنية.","owner":"الطبيب الواصف","record":"طلب الدواء وتعليمات الجرعة"},{"title":"التحقق والتحضير","action":"راجع الوصفة في قائمة الصيدلية وأكد الصنف والكمية واختر التشغيلة المناسبة. سجّل أي استبدال عبر الإجراء المخوّل دون تغيير الوصفة ضمنياً.","owner":"الصيدلي","record":"قائمة الوصفات وصنف المخزون والتشغيلة وسجل الاستبدال"},{"title":"الصرف والتسليم","action":"سجّل تحضير الدواء وتسليمه والكمية وأيام التغطية والتعليمات. اربط الصرف بالمريض والموقع والطلب المخوّل والرسوم المنطبقة.","owner":"فريق صرف الصيدلية","record":"أمر الصرف والأوقات والكمية والصنف والرسوم"},{"title":"التتبع والمطابقة","action":"راجع الوصفات المعلقة والصرف المكتمل وحركات المخزون. عالج المرتجعات والتصحيحات عبر إجراءات المخزون والمالية المعتمدة؛ يبقى إعطاء الدواء للمنوّم سجلاً سريرياً مستقلاً.","owner":"الصيدلية والمخزون والجناح","record":"تاريخ الصرف ورصيد المخزون وروابط إعطاء الدواء"}],"exceptions":[{"situation":"كمية جزئية أو مخزون غير متوفر","response":"سجّل الكمية المصروفة فعلياً واحتفظ بمسؤولية الكمية المتبقية وطبّق قواعد الاستبدال أو التوريد المعتمدة."},{"situation":"تشغيلة منتهية أو دواء مرتجع","response":"اتبع سياسة العزل والمرتجعات وطابق حركة المخزون والأثر المالي دون حذف تاريخ الصرف."}],"connection":"الوصف والصرف والإعطاء والمخزون سجلات مترابطة ومستقلة. تحتاج قواعد قائمة الأدوية وتحويل الوحدات والتغطية والصرف الخارجي تهيئة معتمدة لكل منها.","scenarios":[{"title":"من الوصفة إلى تسليم موثق","situation":"يصف الطبيب دواء ويتلقى المريض الكمية المراجعة من الصيدلية.","preparation":"كتالوج أدوية ووحدات جرعات وتشغيلات صالحة وأدوار الصيدلية والرسوم.","steps":["يسجّل الطبيب طلب الدواء وتعليمات الجرعة في الزيارة.","يراجع الصيدلي الوصفة والمنتج والتشغيلة المتاحة.","سجّل الكمية وأيام التغطية والتحضير والتسليم والتعليمات.","طابق الصرف وحركة المخزون والرسوم وسجّل الإعطاء مستقلاً عند انطباقه."],"acceptance":"يمكن تتبع الطلب المخوّل والتشغيلة والكمية المسلمة وحركة المخزون."},{"title":"صرف جزئي يتبعه مرتجع","situation":"يتوفر جزء من الكمية الموصوفة ويحتاج مرتجع لاحق مراجعة مخزنية ومالية.","preparation":"سياسة صرف جزئي ومسؤول الكمية المعلقة وقواعد المرتجعات والعزل.","steps":["راجع الكمية الموصوفة والمتاحة مع الصيدلي.","سجّل الصرف الفعلي واحتفظ بمسؤولية الباقي.","عند الإرجاع تحقق من الصرف الأصلي وطبّق الفحص والعزل.","طابق آثار المخزون والمال المعتمدة مع حفظ تاريخ الصرف."],"acceptance":"تظل الكميات المطلوبة والمصروفة والمعلقة والمرتجعة مميزة."}],"setupFiles":[{"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/radiology","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/radiology","title":"Radiology software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope.","description":"Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope. Verified radiology requests, departmental operation and…","answers":[{"question":"What does MANSOQ Radiology cover?","answer":"Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope. Refer & schedule: Create the imaging request with the clinical question, patient, encounter and requested procedure. Confirm modality, department availability and required preparation before the scheduled examination. Acquire & identify: Connect departmental work to the request and accession information. When PACS is selected, verify patient, study and encounter identifiers before accepting the linked imaging study. Interpret & report: Attach the diagnostic report to the correct clinical request. Confirm author, report status and clinical communication responsibility; agree the external reporting workflow if interpretation occurs in another system. Communicate & amend: Return the report to the authorized care team, document critical findings through the approved pathway and retain addenda with their reason and owner. Track outstanding reports at handover.","href":"/platform/radiology#module-workflow"},{"question":"What setup data does Radiology need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Services & department catalogue (services.csv); Assets, devices & hardware (assets_devices.csv); Interface specification (interfaces.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/radiology#module-setup"},{"question":"How does Radiology handle exceptions?","answer":"Study linked to the wrong encounter Hold clinical distribution, compare source identifiers and have an authorized owner correct the mapping before release. RIS or PACS unavailable Use the accepted downtime procedure, retain request identities and reconcile delayed studies and reports after recovery.","href":"/platform/radiology#module-exceptions"},{"question":"How does Radiology connect with other systems?","answer":"Radiology request and report context is separate from image storage, viewing, acquisition hardware and RIS/PACS integration. Agree each included component and test DICOM study linkage and report exchange where selected.","href":"/platform/radiology#module-connections"}],"module":{"name":"Radiology","functions":["Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope."],"workflow":[{"title":"Refer & schedule","action":"Create the imaging request with the clinical question, patient, encounter and requested procedure. Confirm modality, department availability and required preparation before the scheduled examination.","owner":"Referring clinician and imaging coordinator","record":"Service request, procedure, modality and appointment"},{"title":"Acquire & identify","action":"Connect departmental work to the request and accession information. When PACS is selected, verify patient, study and encounter identifiers before accepting the linked imaging study.","owner":"Radiographer and interface owner","record":"Accession, study identifiers, imaging source and request status"},{"title":"Interpret & report","action":"Attach the diagnostic report to the correct clinical request. Confirm author, report status and clinical communication responsibility; agree the external reporting workflow if interpretation occurs in another system.","owner":"Reporting clinician","record":"Diagnostic report, author, status and linked study"},{"title":"Communicate & amend","action":"Return the report to the authorized care team, document critical findings through the approved pathway and retain addenda with their reason and owner. Track outstanding reports at handover.","owner":"Radiology and referring team","record":"Final report, addendum and communication record"}],"exceptions":[{"situation":"Study linked to the wrong encounter","response":"Hold clinical distribution, compare source identifiers and have an authorized owner correct the mapping before release."},{"situation":"RIS or PACS unavailable","response":"Use the accepted downtime procedure, retain request identities and reconcile delayed studies and reports after recovery."}],"connection":"Radiology request and report context is separate from image storage, viewing, acquisition hardware and RIS/PACS integration. Agree each included component and test DICOM study linkage and report exchange where selected.","scenarios":[{"title":"Scheduled imaging with a linked report","situation":"A clinician requests an imaging procedure and the department returns its report to the encounter.","preparation":"Procedure and modality catalogue, scheduling resource, reporting role and selected RIS/PACS mapping.","steps":["Create and schedule the imaging request with the clinical question and preparation.","Verify patient, encounter and accession identifiers at examination.","Link the accepted study source and authored diagnostic report to the original request.","Release the report to the referring team and document review and follow-up."],"acceptance":"The request, accepted imaging source and report belong to the same person and care context."},{"title":"Delayed PACS study with a report addendum","situation":"An accepted external imaging connection is unavailable and the reporting clinician later adds findings.","preparation":"Accepted downtime procedure, original accession, interface owner and report amendment policy.","steps":["Keep the request and accession identity while using the agreed downtime process.","After recovery, reconcile the delayed study to the correct person and encounter.","The reporting clinician reviews the study and records the addendum with its author and reason.","Communicate any relevant finding and preserve the original report and receiving-team responsibility."],"acceptance":"Recovery produces no unmatched study, and both report versions and communication are retained."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/radiology?lang=ar","title":"الأشعة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة.","description":"طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة. طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات…","answers":[{"question":"ما نطاق الأشعة في منسوق؟","answer":"طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة. الإحالة والجدولة: أنشئ طلب التصوير بالسؤال السريري والمريض والزيارة والإجراء المطلوب. أكد نوع التصوير وتوافر القسم والتحضير المطلوب قبل الفحص المجدول. التصوير والتعريف: اربط عمل القسم بالطلب ومعلومات التسجيل. عند اختيار الأرشفة الطبية تحقق من معرّفات المريض والدراسة والزيارة قبل قبول الدراسة المرتبطة. التفسير والتقرير: اربط التقرير التشخيصي بالطلب السريري الصحيح. أكد المؤلف وحالة التقرير ومسؤولية الإبلاغ واتفق على مسار التقارير الخارجي إذا جرى التفسير في نظام آخر. الإبلاغ والتعديل: أعد التقرير لفريق الرعاية المخوّل ووثق النتائج الحرجة عبر المسار المعتمد واحتفظ بالإضافات وأسبابها ومسؤوليها. تابع التقارير المعلقة عند التسليم.","href":"/platform/radiology#module-workflow"},{"question":"ما بيانات إعداد الأشعة؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الخدمات ودليل الأقسام (services.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ مواصفات الربط (interfaces.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/radiology#module-setup"},{"question":"كيف يتعامل الأشعة مع الاستثناءات؟","answer":"دراسة مرتبطة بزيارة خاطئة أوقف التوزيع السريري وقارن معرّفات المصدر واطلب تصحيح المواءمة من مسؤول مخوّل قبل الإصدار. تعطل نظام الأشعة أو الأرشفة استخدم إجراء التعطل المعتمد واحتفظ بمعرّفات الطلبات وطابق الدراسات والتقارير المتأخرة بعد التعافي.","href":"/platform/radiology#module-exceptions"},{"question":"كيف يتصل الأشعة بالأنظمة الأخرى؟","answer":"سياق طلبات الأشعة وتقاريرها مستقل عن حفظ الصور وعرضها وأجهزة التصوير وربط أنظمة الأشعة والأرشفة. حدد المكونات المشمولة واختبر ارتباط الدراسات وتبادل التقارير عند اختيارهما.","href":"/platform/radiology#module-connections"}],"module":{"name":"الأشعة","functions":["طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة."],"workflow":[{"title":"الإحالة والجدولة","action":"أنشئ طلب التصوير بالسؤال السريري والمريض والزيارة والإجراء المطلوب. أكد نوع التصوير وتوافر القسم والتحضير المطلوب قبل الفحص المجدول.","owner":"الطبيب المحيل ومنسق الأشعة","record":"طلب الخدمة والإجراء ونوع التصوير والموعد"},{"title":"التصوير والتعريف","action":"اربط عمل القسم بالطلب ومعلومات التسجيل. عند اختيار الأرشفة الطبية تحقق من معرّفات المريض والدراسة والزيارة قبل قبول الدراسة المرتبطة.","owner":"فني الأشعة ومسؤول الربط","record":"معرّف التسجيل والدراسة ومصدر الصور وحالة الطلب"},{"title":"التفسير والتقرير","action":"اربط التقرير التشخيصي بالطلب السريري الصحيح. أكد المؤلف وحالة التقرير ومسؤولية الإبلاغ واتفق على مسار التقارير الخارجي إذا جرى التفسير في نظام آخر.","owner":"الطبيب المعد للتقرير","record":"التقرير التشخيصي والمؤلف والحالة والدراسة المرتبطة"},{"title":"الإبلاغ والتعديل","action":"أعد التقرير لفريق الرعاية المخوّل ووثق النتائج الحرجة عبر المسار المعتمد واحتفظ بالإضافات وأسبابها ومسؤوليها. تابع التقارير المعلقة عند التسليم.","owner":"الأشعة والفريق المحيل","record":"التقرير النهائي والإضافة وسجل الإبلاغ"}],"exceptions":[{"situation":"دراسة مرتبطة بزيارة خاطئة","response":"أوقف التوزيع السريري وقارن معرّفات المصدر واطلب تصحيح المواءمة من مسؤول مخوّل قبل الإصدار."},{"situation":"تعطل نظام الأشعة أو الأرشفة","response":"استخدم إجراء التعطل المعتمد واحتفظ بمعرّفات الطلبات وطابق الدراسات والتقارير المتأخرة بعد التعافي."}],"connection":"سياق طلبات الأشعة وتقاريرها مستقل عن حفظ الصور وعرضها وأجهزة التصوير وربط أنظمة الأشعة والأرشفة. حدد المكونات المشمولة واختبر ارتباط الدراسات وتبادل التقارير عند اختيارهما.","scenarios":[{"title":"تصوير مجدول وتقرير مرتبط","situation":"يطلب طبيب إجراء تصوير ويعيد القسم تقريره للزيارة.","preparation":"كتالوج الإجراء ونوع التصوير والجدولة ودور التقرير ومواءمة الأنظمة المختارة.","steps":["أنشئ طلب التصوير وجدوله بالسؤال السريري والتحضير.","تحقق من المريض والزيارة ومعرّف التسجيل عند الفحص.","اربط مصدر الدراسة المعتمد والتقرير بالطلب الأصلي.","أصدر التقرير للفريق المحيل ووثق المراجعة والمتابعة."],"acceptance":"يتبع الطلب ومصدر الصور المعتمد والتقرير الشخص وسياق الرعاية نفسيهما."},{"title":"دراسة أرشفة متأخرة وإضافة للتقرير","situation":"يتعطل اتصال تصوير خارجي معتمد ويضيف الطبيب لاحقاً نتائج للتقرير.","preparation":"إجراء تعطل معتمد ومعرّف التسجيل ومسؤول الربط وسياسة تعديل التقارير.","steps":["احفظ هوية الطلب والتسجيل أثناء إجراء التعطل.","بعد التعافي طابق الدراسة المتأخرة بالشخص والزيارة.","يراجع الطبيب الدراسة ويسجّل الإضافة ومؤلفها وسببها.","أبلغ النتائج المناسبة واحفظ التقرير الأصلي ومسؤولية الفريق المستلم."],"acceptance":"لا تبقى دراسة غير مطابقة بعد التعافي وتحفظ نسختا التقرير والإبلاغ."}],"setupFiles":[{"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/releases","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/releases","title":"Live service status, versions & roadmap | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Review exact product scope, supported interfaces and release notes. Marketing catalogue versions and clinical software releases have different purposes.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Review exact product scope, supported interfaces and release notes. Marketing catalogue versions and clinical software releases have different purposes.","description":"Live MANSOQ service status, monitored incident history, product versions, deployed builds and published roadmap. Subscribe to platform updates.","answers":[]},"ar":{"url":"https://mansoq.com/platform/releases?lang=ar","title":"الحالة المباشرة والإصدارات وخارطة الطريق | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"راجع نطاق المنتج الدقيق والاتصالات المدعومة وملاحظات الإصدار. تختلف إصدارات الكتالوج التسويقي عن إصدارات البرمجيات السريرية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"راجع نطاق المنتج الدقيق والاتصالات المدعومة وملاحظات الإصدار. تختلف إصدارات الكتالوج التسويقي عن إصدارات البرمجيات السريرية.","description":"الحالة المباشرة لخدمات منسوق وسجل الحوادث المراقب وإصدارات المنتجات وأرقام البناء وخارطة الطريق المنشورة. اشترك في التحديثات.","answers":[]}},{"slug":"/platform/revenue-cycle","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/revenue-cycle","title":"Revenue Cycle Management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation.","description":"A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation. A complete…","answers":[{"question":"What does MANSOQ Revenue Cycle Management cover?","answer":"A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation. Establish the rules: Configure legal organizations, administration agreements, provider contracts, products, issued policies and member classes in dependency order. Keep source evidence, effective dates and approval with each configuration version. Verify coverage: Resolve member eligibility, provider network, benefit rules, exclusions, limits and tariff applicability for the requested service. An unknown fact creates a named review item; it must not silently become an assumed price or patient liability. Authorize & prepare: Prepare required authorization and supporting evidence. Keep requested and approved services, quantities and validity separate. Review the provisional estimate, unresolved facts and expiry before accepting financial preparation. Capture & submit: Attest performed activity, reconcile charges and assemble the claim with coding and attachments. Validate the payload and submission identity; production transmission requires approved credentials, endpoints, exchange package and activation evidence. Resolve responses: Distinguish transport validation, payer business errors and adjudicated denials. Route corrections, evidence requests, contract disputes and clinical appeals to the right owner with the original business references and applicable deadlines. Settle & explain: Link remittance advice to claims, distinguish adjudication from cash settlement and reconcile partial payments, deductions and unmatched cash. Review ageing, exceptions and decision traces without converting unresolved balances into patient charges.","href":"/platform/revenue-cycle#module-workflow"},{"question":"What setup data does Revenue Cycle Management need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include organizations (rcm_organizations.csv); provider contracts (rcm_provider_contracts.csv); issued policies (rcm_issued_policies.csv); benefit classes (rcm_benefit_classes.csv); benefit rules (rcm_benefit_rules.csv); tariffs (rcm_tariffs.csv); Provider networks & participation (rcm_networks.csv); Member coverage mapping (rcm_member_coverage.csv); Rules, exceptions & publication (rcm_rule_publications.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/revenue-cycle#module-setup"},{"question":"How does Revenue Cycle Management handle exceptions?","answer":"Benefit or deductible balance unknown Name the missing source and owner. Keep the estimate provisional with its assumptions and expiry; no default amount replaces the unresolved value. Rejected transmission versus denied claim Use the accepted identity rules for transport retry and payer correction. Classify adjudicated denial separately and choose its evidenced remedy and responsible reviewer. Partial or unmatched payment Keep claim, advice and bank references distinct. Investigate the variance and approve allocation or adjustment without overwriting the settlement history.","href":"/platform/revenue-cycle#module-exceptions"},{"question":"How does Revenue Cycle Management connect with other systems?","answer":"Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. Catalogue reference data is not certified production configuration; payer credentials, terminology rights and external finance connections are each accepted before use.","href":"/platform/revenue-cycle#module-connections"}],"module":{"name":"Revenue Cycle Management","functions":["A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation."],"workflow":[{"title":"Establish the rules","action":"Configure legal organizations, administration agreements, provider contracts, products, issued policies and member classes in dependency order. Keep source evidence, effective dates and approval with each configuration version.","owner":"Contracting and configuration team","record":"Organizations, contracts, policies, classes and evidence versions"},{"title":"Verify coverage","action":"Resolve member eligibility, provider network, benefit rules, exclusions, limits and tariff applicability for the requested service. An unknown fact creates a named review item; it must not silently become an assumed price or patient liability.","owner":"Eligibility and benefits team","record":"Eligibility trace, benefit version, tariff and uncertainty"},{"title":"Authorize & prepare","action":"Prepare required authorization and supporting evidence. Keep requested and approved services, quantities and validity separate. Review the provisional estimate, unresolved facts and expiry before accepting financial preparation.","owner":"Authorization and revenue reviewer","record":"Authorization, evidence, estimate and reservation reference"},{"title":"Capture & submit","action":"Attest performed activity, reconcile charges and assemble the claim with coding and attachments. Validate the payload and submission identity; production transmission requires approved credentials, endpoints, exchange package and activation evidence.","owner":"Charge, coding and claims team","record":"Attested charges, claim bundle, validation and response"},{"title":"Resolve responses","action":"Distinguish transport validation, payer business errors and adjudicated denials. Route corrections, evidence requests, contract disputes and clinical appeals to the right owner with the original business references and applicable deadlines.","owner":"Denial and clinical review teams","record":"Reason code, remedy, owner, evidence and deadline"},{"title":"Settle & explain","action":"Link remittance advice to claims, distinguish adjudication from cash settlement and reconcile partial payments, deductions and unmatched cash. Review ageing, exceptions and decision traces without converting unresolved balances into patient charges.","owner":"Finance and revenue leadership","record":"Remittance, cash ledger, reconciliation and decision trace"}],"exceptions":[{"situation":"Benefit or deductible balance unknown","response":"Name the missing source and owner. Keep the estimate provisional with its assumptions and expiry; no default amount replaces the unresolved value."},{"situation":"Rejected transmission versus denied claim","response":"Use the accepted identity rules for transport retry and payer correction. Classify adjudicated denial separately and choose its evidenced remedy and responsible reviewer."},{"situation":"Partial or unmatched payment","response":"Keep claim, advice and bank references distinct. Investigate the variance and approve allocation or adjustment without overwriting the settlement history."}],"connection":"Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. Catalogue reference data is not certified production configuration; payer credentials, terminology rights and external finance connections are each accepted before use.","scenarios":[{"title":"Insured visit from verification to settlement","situation":"A provider processes a documented insured visit using approved configuration and an accepted production exchange.","preparation":"Evidenced contract, issued policy, benefits, network, tariff, authorization rules and accepted exchange credentials.","steps":["Verify member and service eligibility, network and benefit facts; preserve the decision trace.","Resolve required authorization and review the provisional estimate and its assumptions.","Attest performed services, assemble the coded claim and validate the accepted submission package.","Track payer response and advice, then reconcile cash allocation and remaining exceptions."],"acceptance":"Coverage, authorized activity, submission, adjudication and settlement are traceable as distinct decisions."},{"title":"Uncertain benefit, denial and partial payment","situation":"An estimate has incomplete benefit evidence, and later claim lines receive mixed payer decisions.","preparation":"Named benefits reviewer, evidence register, denial reasons, deadlines and remittance controls.","steps":["Keep the estimate uncertain and identify the unresolved policy or utilization fact.","Obtain approved evidence before financial activation; do not default the unknown balance.","Classify each returned error or denial and route the evidenced remedy to its owner.","Link partial advice and cash to claims, investigate variance and retain approved adjustments."],"acceptance":"Uncertainty, rejection, denial and unpaid balance remain distinct, with owners and evidence for each."}],"setupFiles":[{"template":"/implementation/templates/rcm_organizations.csv","example":"/implementation/examples/rcm_organizations.csv"},{"template":"/implementation/templates/rcm_provider_contracts.csv","example":"/implementation/examples/rcm_provider_contracts.csv"},{"template":"/implementation/templates/rcm_issued_policies.csv","example":"/implementation/examples/rcm_issued_policies.csv"},{"template":"/implementation/templates/rcm_benefit_classes.csv","example":"/implementation/examples/rcm_benefit_classes.csv"},{"template":"/implementation/templates/rcm_benefit_rules.csv","example":"/implementation/examples/rcm_benefit_rules.csv"},{"template":"/implementation/templates/rcm_tariffs.csv","example":"/implementation/examples/rcm_tariffs.csv"},{"template":"/implementation/templates/rcm_networks.csv","example":"/implementation/examples/rcm_networks.csv"},{"template":"/implementation/templates/rcm_member_coverage.csv","example":"/implementation/examples/rcm_member_coverage.csv"},{"template":"/implementation/templates/rcm_rule_publications.csv","example":"/implementation/examples/rcm_rule_publications.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/revenue-cycle?lang=ar","title":"إدارة دورة الإيراد | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة.","description":"مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة. مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات…","answers":[{"question":"ما نطاق إدارة دورة الإيراد في منسوق؟","answer":"مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة. تأسيس القواعد: هيئ المؤسسات القانونية واتفاقات الإدارة وعقود المزود والمنتجات والوثائق المصدرة وفئات الأعضاء بترتيب الاعتماد. احفظ الأدلة والتواريخ والموافقة مع كل إصدار. التحقق من التغطية: حدد أهلية العضو والشبكة والمنافع والاستثناءات والحدود والتعرفة للخدمة. تنتج المعلومة المجهولة بند مراجعة محدداً دون افتراض سعر أو مسؤولية للمريض. الموافقة والتحضير: جهز الموافقة المطلوبة والأدلة. افصل الخدمات والكميات والفترات المطلوبة عن المعتمدة وراجع التقدير المؤقت والمعلومات غير المحسومة والصلاحية قبل قبول التحضير المالي. الالتقاط والإرسال: اعتمد النشاط المنفذ وطابق الرسوم واجمع المطالبة والترميز والمرفقات. تحقق من البيانات وهوية الإرسال؛ يتطلب الإرسال الفعلي بيانات اتصال وحزمة تبادل وأدلة تفعيل معتمدة. معالجة الردود: ميّز تحقق النقل وأخطاء الدافع والرفض بعد التقييم. وجّه التصحيحات وطلبات الأدلة ونزاعات العقود والاعتراضات السريرية للمسؤول المناسب بمراجعها الأصلية ومواعيدها. التسوية والتفسير: اربط إشعارات السداد بالمطالبات وافصل التقييم عن تسوية النقد وطابق الدفعات الجزئية والخصومات والنقد غير المطابق. راجع الأعمار والاستثناءات والتتبع دون تحويل الأرصدة غير المحسومة لرسوم على المريض.","href":"/platform/revenue-cycle#module-workflow"},{"question":"ما بيانات إعداد إدارة دورة الإيراد؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: تهيئة دورة الإيرادات · الجهات المتعاقدة (rcm_organizations.csv)؛ تهيئة دورة الإيرادات · عقود مقدمي الخدمة (rcm_provider_contracts.csv)؛ تهيئة دورة الإيرادات · الوثائق الصادرة (rcm_issued_policies.csv)؛ تهيئة دورة الإيرادات · فئات المنافع (rcm_benefit_classes.csv)؛ تهيئة دورة الإيرادات · قواعد المنافع (rcm_benefit_rules.csv)؛ تهيئة دورة الإيرادات · قوائم الأسعار التعاقدية (rcm_tariffs.csv)؛ شبكات مقدمي الخدمة والمشاركة (rcm_networks.csv)؛ مواءمة تغطية الأعضاء (rcm_member_coverage.csv)؛ القواعد والاستثناءات والنشر (rcm_rule_publications.csv)؛ ضوابط الإيرادات والمطابقة (rcm_financial_controls.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/revenue-cycle#module-setup"},{"question":"كيف يتعامل إدارة دورة الإيراد مع الاستثناءات؟","answer":"رصيد منفعة أو تحمّل غير معلوم حدد المصدر المفقود والمسؤول واحتفظ بتقدير مؤقت بافتراضاته وصلاحيته؛ لا تستبدل القيمة غير المحسومة بمبلغ افتراضي. رفض الإرسال مقابل رفض المطالبة استخدم قواعد الهوية المعتمدة لإعادة النقل وتصحيح الدافع وصنف الرفض بعد التقييم مستقلاً وحدد معالجته بالدليل والمراجع المسؤول. دفعة جزئية أو غير مطابقة افصل مراجع المطالبة والإشعار والبنك وحقق في الفرق واعتمد التخصيص أو التسوية دون استبدال تاريخ السداد.","href":"/platform/revenue-cycle#module-exceptions"},{"question":"كيف يتصل إدارة دورة الإيراد بالأنظمة الأخرى؟","answer":"مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. البيانات المرجعية ليست تهيئة إنتاج معتمدة؛ تُعتمد بيانات الدافع وحقوق المصطلحات والاتصالات المالية كلٌ على حدة قبل الاستخدام.","href":"/platform/revenue-cycle#module-connections"}],"module":{"name":"إدارة دورة الإيراد","functions":["مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة."],"workflow":[{"title":"تأسيس القواعد","action":"هيئ المؤسسات القانونية واتفاقات الإدارة وعقود المزود والمنتجات والوثائق المصدرة وفئات الأعضاء بترتيب الاعتماد. احفظ الأدلة والتواريخ والموافقة مع كل إصدار.","owner":"فريق العقود والتهيئة","record":"المؤسسات والعقود والوثائق والفئات وإصدارات الأدلة"},{"title":"التحقق من التغطية","action":"حدد أهلية العضو والشبكة والمنافع والاستثناءات والحدود والتعرفة للخدمة. تنتج المعلومة المجهولة بند مراجعة محدداً دون افتراض سعر أو مسؤولية للمريض.","owner":"فريق الأهلية والمنافع","record":"تتبع الأهلية وإصدار المنافع والتعرفة وعدم اليقين"},{"title":"الموافقة والتحضير","action":"جهز الموافقة المطلوبة والأدلة. افصل الخدمات والكميات والفترات المطلوبة عن المعتمدة وراجع التقدير المؤقت والمعلومات غير المحسومة والصلاحية قبل قبول التحضير المالي.","owner":"فريق الموافقات ومراجع الإيرادات","record":"الموافقة والأدلة والتقدير ومرجع الحجز"},{"title":"الالتقاط والإرسال","action":"اعتمد النشاط المنفذ وطابق الرسوم واجمع المطالبة والترميز والمرفقات. تحقق من البيانات وهوية الإرسال؛ يتطلب الإرسال الفعلي بيانات اتصال وحزمة تبادل وأدلة تفعيل معتمدة.","owner":"فريق الرسوم والترميز والمطالبات","record":"الرسوم المعتمدة وحزمة المطالبة والتحقق والرد"},{"title":"معالجة الردود","action":"ميّز تحقق النقل وأخطاء الدافع والرفض بعد التقييم. وجّه التصحيحات وطلبات الأدلة ونزاعات العقود والاعتراضات السريرية للمسؤول المناسب بمراجعها الأصلية ومواعيدها.","owner":"فرق الرفض والمراجعة السريرية","record":"رمز السبب والمعالجة والمسؤول والأدلة والموعد النهائي"},{"title":"التسوية والتفسير","action":"اربط إشعارات السداد بالمطالبات وافصل التقييم عن تسوية النقد وطابق الدفعات الجزئية والخصومات والنقد غير المطابق. راجع الأعمار والاستثناءات والتتبع دون تحويل الأرصدة غير المحسومة لرسوم على المريض.","owner":"المالية وقيادة الإيرادات","record":"إشعارات السداد ودفتر النقد والمطابقة وتتبع القرار"}],"exceptions":[{"situation":"رصيد منفعة أو تحمّل غير معلوم","response":"حدد المصدر المفقود والمسؤول واحتفظ بتقدير مؤقت بافتراضاته وصلاحيته؛ لا تستبدل القيمة غير المحسومة بمبلغ افتراضي."},{"situation":"رفض الإرسال مقابل رفض المطالبة","response":"استخدم قواعد الهوية المعتمدة لإعادة النقل وتصحيح الدافع وصنف الرفض بعد التقييم مستقلاً وحدد معالجته بالدليل والمراجع المسؤول."},{"situation":"دفعة جزئية أو غير مطابقة","response":"افصل مراجع المطالبة والإشعار والبنك وحقق في الفرق واعتمد التخصيص أو التسوية دون استبدال تاريخ السداد."}],"connection":"مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. البيانات المرجعية ليست تهيئة إنتاج معتمدة؛ تُعتمد بيانات الدافع وحقوق المصطلحات والاتصالات المالية كلٌ على حدة قبل الاستخدام.","scenarios":[{"title":"زيارة مؤمّنة من التحقق للتسوية","situation":"يعالج مزود زيارة مؤمنة موثقة بتهيئة معتمدة وتبادل إنتاج مقبول.","preparation":"عقد موثق ووثيقة ومنافع وشبكة وتعرفة وقواعد موافقات وبيانات تبادل معتمدة.","steps":["تحقق من العضو والخدمة والشبكة والمنافع واحفظ تتبع القرار.","أكمل الموافقة المطلوبة وراجع التقدير المؤقت وافتراضاته.","اعتمد الخدمات المنفذة واجمع المطالبة المرمزة وتحقق من الحزمة.","تابع رد الدافع والإشعار وطابق النقد والاستثناءات."],"acceptance":"تتبع التغطية والنشاط المخوّل والإرسال والتقييم والتسوية كقرارات مستقلة."},{"title":"منفعة غير مؤكدة ورفض ودفعة جزئية","situation":"ينقص تقدير دليل منفعة وتتلقى بنود مطالبة لاحقة قرارات مختلفة.","preparation":"مراجع منافع وسجل أدلة وأسباب رفض ومواعيد وضوابط سداد.","steps":["احتفظ بالتقدير غير المؤكد وحدد حقيقة الوثيقة أو الاستخدام المفقودة.","احصل على الدليل قبل التفعيل المالي دون افتراض رصيد.","صنف كل خطأ أو رفض ووجّه المعالجة المثبتة لمسؤولها.","اربط الإشعار والنقد الجزئيين وحقق في الفرق واحفظ التسويات."],"acceptance":"يميز عدم اليقين ورفض النقل والرفض المالي والرصيد غير المدفوع بمسؤوليها وأدلتها."}],"setupFiles":[{"template":"/implementation/templates/rcm_organizations.csv","example":"/implementation/examples/rcm_organizations.csv"},{"template":"/implementation/templates/rcm_provider_contracts.csv","example":"/implementation/examples/rcm_provider_contracts.csv"},{"template":"/implementation/templates/rcm_issued_policies.csv","example":"/implementation/examples/rcm_issued_policies.csv"},{"template":"/implementation/templates/rcm_benefit_classes.csv","example":"/implementation/examples/rcm_benefit_classes.csv"},{"template":"/implementation/templates/rcm_benefit_rules.csv","example":"/implementation/examples/rcm_benefit_rules.csv"},{"template":"/implementation/templates/rcm_tariffs.csv","example":"/implementation/examples/rcm_tariffs.csv"},{"template":"/implementation/templates/rcm_networks.csv","example":"/implementation/examples/rcm_networks.csv"},{"template":"/implementation/templates/rcm_member_coverage.csv","example":"/implementation/examples/rcm_member_coverage.csv"},{"template":"/implementation/templates/rcm_rule_publications.csv","example":"/implementation/examples/rcm_rule_publications.csv"},{"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/sbs-coding","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/sbs-coding","title":"Full Supported SBS Catalogue Tooling software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed.","description":"Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed. Full supported catalogue import, mapping and update…","answers":[{"question":"What does MANSOQ Full Supported SBS Catalogue Tooling cover?","answer":"Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed. Select the edition: Identify the supported Saudi Billing System catalogue release and usage rights. Agree whether the selected scope uses specified service codes or the full licensed catalogue. Map local services: Connect each provider service to the approved code and effective period. Preserve local service identifiers, descriptions and mapping evidence; resolve unmatched services through coding review. Validate use: Check required codes, inactive entries, duplicates and mapping completeness. Review representative service activity through the selected charge and claim workflow before accepting the mapping. Maintain versions: Review edition changes and effective dates with the catalogue owner. Preserve earlier mappings for historical records and test affected downstream pricing and claims before activation.","href":"/platform/sbs-coding#module-workflow"},{"question":"What setup data does Full Supported SBS Catalogue Tooling need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Service catalogue (service_catalogue.csv); Service prices & SBS mapping (service_billing.csv); Assumptions & decisions (assumptions_decisions.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/sbs-coding#module-setup"},{"question":"How does Full Supported SBS Catalogue Tooling handle exceptions?","answer":"Local service has no accepted code Assign coding review and record the unresolved mapping; do not select a plausible code merely to complete the file. Catalogue code retired Review the replacement and effective date, preserve historical use and test active service mappings.","href":"/platform/sbs-coding#module-exceptions"},{"question":"How does Full Supported SBS Catalogue Tooling connect with other systems?","answer":"SBS mapping is distinct from catalogue licensing and from NPHIES exchange acceptance. A mapping file does not grant catalogue rights or certify a claim.","href":"/platform/sbs-coding#module-connections"}],"module":{"name":"Full Supported SBS Catalogue Tooling","functions":["Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed."],"workflow":[{"title":"Select the edition","action":"Identify the supported Saudi Billing System catalogue release and usage rights. Agree whether the selected scope uses specified service codes or the full licensed catalogue.","owner":"Coding and licensing owner","record":"Catalogue edition, license and selected code scope"},{"title":"Map local services","action":"Connect each provider service to the approved code and effective period. Preserve local service identifiers, descriptions and mapping evidence; resolve unmatched services through coding review.","owner":"Service catalogue and coding team","record":"Local service, SBS code and effective mapping"},{"title":"Validate use","action":"Check required codes, inactive entries, duplicates and mapping completeness. Review representative service activity through the selected charge and claim workflow before accepting the mapping.","owner":"Coding reviewer","record":"Mapping validation and representative claim evidence"},{"title":"Maintain versions","action":"Review edition changes and effective dates with the catalogue owner. Preserve earlier mappings for historical records and test affected downstream pricing and claims before activation.","owner":"Catalogue governance owner","record":"Mapping version, change approval and historical references"}],"exceptions":[{"situation":"Local service has no accepted code","response":"Assign coding review and record the unresolved mapping; do not select a plausible code merely to complete the file."},{"situation":"Catalogue code retired","response":"Review the replacement and effective date, preserve historical use and test active service mappings."}],"connection":"SBS mapping is distinct from catalogue licensing and from NPHIES exchange acceptance. A mapping file does not grant catalogue rights or certify a claim.","scenarios":[{"title":"Map a provider’s consultation and diagnostic services","situation":"A service catalogue needs approved SBS mappings before selected downstream billing and claims use.","preparation":"Licensed edition, local service identifiers, code scope, effective dates and coding reviewer.","steps":["Identify the exact catalogue edition and permitted scope.","Map each local service to an accepted code with its effective period.","Validate missing, duplicate and inactive mappings with the coding owner.","Rehearse representative charges and claim coding before publishing the mapping."],"acceptance":"Each active local service has reviewed mapping evidence; catalogue rights and claim acceptance remain separate."},{"title":"Edition change with an unmatched new service","situation":"A catalogue update retires codes while a new local procedure has no accepted mapping.","preparation":"Old and new editions, historical references, mapping decisions and affected service inventory.","steps":["Inventory affected active and historical service mappings.","Keep the unmatched service unresolved and route it to coding review.","Approve replacement codes and effective dates while retaining historical mappings.","Re-test downstream pricing and claim inputs before activating the new edition."],"acceptance":"Edition changes and unresolved mappings are explicit and historical records retain their original coding context."}],"setupFiles":[{"template":"/implementation/templates/service_catalogue.csv","example":"/implementation/examples/service_catalogue.csv"},{"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/sbs-coding?lang=ar","title":"أدوات كتالوج SBS المدعوم الكامل | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية.","description":"أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية. أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على…","answers":[{"question":"ما نطاق أدوات كتالوج SBS المدعوم الكامل في منسوق؟","answer":"أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية. اختيار الإصدار: حدد إصدار نظام الفوترة السعودي المدعوم وحقوق استخدامه. اتفق على رموز محددة أو الكتالوج المرخّص الكامل. مواءمة الخدمات المحلية: اربط خدمة المزود بالرمز والفترة المعتمدين. احفظ المعرّفات والأوصاف المحلية وأدلة المواءمة وعالج الخدمات غير المطابقة بمراجعة الترميز. التحقق من الاستخدام: تحقق من الرموز المطلوبة والمعطلة والتكرار واكتمال المواءمة. راجع نشاط خدمات نموذجي عبر الرسوم والمطالبات المختارة قبل الاعتماد. إدارة الإصدارات: راجع تغييرات الإصدار والتواريخ مع المسؤول. احفظ المواءمات السابقة للسجلات التاريخية واختبر الأسعار والمطالبات المتأثرة قبل التفعيل.","href":"/platform/sbs-coding#module-workflow"},{"question":"ما بيانات إعداد أدوات كتالوج SBS المدعوم الكامل؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: دليل الخدمات (service_catalogue.csv)؛ أسعار الخدمات ومواءمة SBS (service_billing.csv)؛ الافتراضات والقرارات (assumptions_decisions.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/sbs-coding#module-setup"},{"question":"كيف يتعامل أدوات كتالوج SBS المدعوم الكامل مع الاستثناءات؟","answer":"خدمة محلية بلا رمز معتمد أحلها لمراجعة الترميز وسجّل المواءمة غير المحسومة دون اختيار رمز تخميني لإكمال الملف. إيقاف رمز كتالوج راجع البديل وتاريخه واحفظ الاستخدام التاريخي واختبر مواءمات الخدمات النشطة.","href":"/platform/sbs-coding#module-exceptions"},{"question":"كيف يتصل أدوات كتالوج SBS المدعوم الكامل بالأنظمة الأخرى؟","answer":"مواءمة SBS مستقلة عن ترخيص الكتالوج وقبول تبادل نفيس. لا يمنح ملف المواءمة حقوق الكتالوج أو اعتماد المطالبة.","href":"/platform/sbs-coding#module-connections"}],"module":{"name":"أدوات كتالوج SBS المدعوم الكامل","functions":["أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية."],"workflow":[{"title":"اختيار الإصدار","action":"حدد إصدار نظام الفوترة السعودي المدعوم وحقوق استخدامه. اتفق على رموز محددة أو الكتالوج المرخّص الكامل.","owner":"مسؤول الترميز والترخيص","record":"إصدار الكتالوج والترخيص ونطاق الرموز"},{"title":"مواءمة الخدمات المحلية","action":"اربط خدمة المزود بالرمز والفترة المعتمدين. احفظ المعرّفات والأوصاف المحلية وأدلة المواءمة وعالج الخدمات غير المطابقة بمراجعة الترميز.","owner":"فريق كتالوج الخدمات والترميز","record":"الخدمة المحلية ورمز SBS والمواءمة السارية"},{"title":"التحقق من الاستخدام","action":"تحقق من الرموز المطلوبة والمعطلة والتكرار واكتمال المواءمة. راجع نشاط خدمات نموذجي عبر الرسوم والمطالبات المختارة قبل الاعتماد.","owner":"مراجع الترميز","record":"تحقق المواءمة وأدلة مطالبات نموذجية"},{"title":"إدارة الإصدارات","action":"راجع تغييرات الإصدار والتواريخ مع المسؤول. احفظ المواءمات السابقة للسجلات التاريخية واختبر الأسعار والمطالبات المتأثرة قبل التفعيل.","owner":"مسؤول حوكمة الكتالوج","record":"إصدار المواءمة واعتماد التغيير والمراجع التاريخية"}],"exceptions":[{"situation":"خدمة محلية بلا رمز معتمد","response":"أحلها لمراجعة الترميز وسجّل المواءمة غير المحسومة دون اختيار رمز تخميني لإكمال الملف."},{"situation":"إيقاف رمز كتالوج","response":"راجع البديل وتاريخه واحفظ الاستخدام التاريخي واختبر مواءمات الخدمات النشطة."}],"connection":"مواءمة SBS مستقلة عن ترخيص الكتالوج وقبول تبادل نفيس. لا يمنح ملف المواءمة حقوق الكتالوج أو اعتماد المطالبة.","scenarios":[{"title":"مواءمة استشارات وفحوص مزود","situation":"يحتاج كتالوج خدمات مواءمات SBS معتمدة قبل الفوترة والمطالبات المختارة.","preparation":"إصدار مرخص ومعرّفات خدمات ونطاق رموز وتواريخ ومراجع ترميز.","steps":["حدد الإصدار والنطاق المسموح.","واءم كل خدمة برمز معتمد وفترته.","تحقق من المواءمات الناقصة والمكررة والمعطلة مع المسؤول.","جرّب الرسوم والترميز قبل نشر المواءمة."],"acceptance":"لكل خدمة نشطة دليل مواءمة مراجع وتبقى حقوق الكتالوج وقبول المطالبات مستقلين."},{"title":"تغيير إصدار وخدمة جديدة غير مطابقة","situation":"يوقف تحديث الكتالوج رموزاً وتبقى خدمة جديدة دون مواءمة معتمدة.","preparation":"إصداران قديم وجديد ومراجع تاريخية وقرارات مواءمة وخدمات متأثرة.","steps":["احصر مواءمات الخدمات النشطة والتاريخية المتأثرة.","أبقِ الخدمة غير المطابقة دون حسم وأحلها للترميز.","اعتمد البدائل والتواريخ واحفظ المواءمات التاريخية.","أعد اختبار الأسعار ومدخلات المطالبة قبل التفعيل."],"acceptance":"تظهر تغيرات الإصدار والمواءمات غير المحسومة وتحفظ السجلات التاريخية سياقها."}],"setupFiles":[{"template":"/implementation/templates/service_catalogue.csv","example":"/implementation/examples/service_catalogue.csv"},{"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/platform/teleicu","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/platform/teleicu","title":"TeleICU software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately.","description":"A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately. A defined remote critical-care coordination…","answers":[{"question":"What does MANSOQ TeleICU cover?","answer":"A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately. Establish hub & spoke: Identify participating facilities, critical-care beds and specialist coverage. Agree which organization owns care, which records remote staff may access and the escalation contacts for each site. Prepare the case: Link the person and encounter to the shared review context. Confirm available observations, notes and imaging sources; commission camera or device connections only within the agreed scope. Review remotely: Let the authorized specialist review the case and document the assessment and recommendations. Name the bedside owner who receives and acts on the plan; remote advice does not silently transfer clinical responsibility. Follow & escalate: Track the next review and handover responsibilities. Maintain contact and downtime procedures for unavailable video, incomplete source information or a case requiring direct escalation.","href":"/platform/teleicu#module-workflow"},{"question":"What setup data does TeleICU need?","answer":"Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Assets, devices & hardware (assets_devices.csv); Interface specification (interfaces.csv); Access & approvals (access_matrix.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.","href":"/platform/teleicu#module-setup"},{"question":"How does TeleICU handle exceptions?","answer":"Remote connection unavailable Switch to the approved communication procedure, keep bedside responsibility explicit and reconcile review documentation after recovery. Source data is incomplete Identify the missing observation or record and request it from the local owner; record the limits of the remote review.","href":"/platform/teleicu#module-exceptions"},{"question":"How does TeleICU connect with other systems?","answer":"Specialist workflow, video, cameras and clinical/device exchange have distinct delivery boundaries. Confirm each facility’s network, equipment and supported integrations before commissioning.","href":"/platform/teleicu#module-connections"}],"module":{"name":"TeleICU","functions":["A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately."],"workflow":[{"title":"Establish hub & spoke","action":"Identify participating facilities, critical-care beds and specialist coverage. Agree which organization owns care, which records remote staff may access and the escalation contacts for each site.","owner":"Programme and facility owners","record":"Hub/spoke roster, access boundary and coverage plan"},{"title":"Prepare the case","action":"Link the person and encounter to the shared review context. Confirm available observations, notes and imaging sources; commission camera or device connections only within the agreed scope.","owner":"Local bedside team","record":"Case context, observations and accepted device sources"},{"title":"Review remotely","action":"Let the authorized specialist review the case and document the assessment and recommendations. Name the bedside owner who receives and acts on the plan; remote advice does not silently transfer clinical responsibility.","owner":"Remote specialist and bedside clinician","record":"Review note, recommendation and responsible local owner"},{"title":"Follow & escalate","action":"Track the next review and handover responsibilities. Maintain contact and downtime procedures for unavailable video, incomplete source information or a case requiring direct escalation.","owner":"Programme coordinator","record":"Follow-up responsibility, escalation and support evidence"}],"exceptions":[{"situation":"Remote connection unavailable","response":"Switch to the approved communication procedure, keep bedside responsibility explicit and reconcile review documentation after recovery."},{"situation":"Source data is incomplete","response":"Identify the missing observation or record and request it from the local owner; record the limits of the remote review."}],"connection":"Specialist workflow, video, cameras and clinical/device exchange have distinct delivery boundaries. Confirm each facility’s network, equipment and supported integrations before commissioning.","scenarios":[{"title":"Remote specialist review for a spoke facility","situation":"A bedside team requests specialist input using the agreed hub-and-spoke programme.","preparation":"Facility roster, specialist coverage, approved record access and accepted video/device scope.","steps":["The local team prepares the patient context, observations and review question.","The authorized remote specialist reviews the available sources and documents recommendations.","The bedside clinician confirms responsibility for clinical action and the shared plan.","The programme coordinator records follow-up and escalation ownership."],"acceptance":"The specialist recommendation and local action owner are distinguishable and linked to the case."},{"title":"Remote review with unavailable video","situation":"A planned specialist review cannot use its accepted video connection.","preparation":"Downtime contacts, local clinical owner, alternative communication and documentation procedure.","steps":["Record the unavailable connection and the case information still accessible.","Use the approved alternative contact route and state the limitations of the review.","The local team retains bedside decisions and records advice and actions.","After recovery reconcile the review record and schedule any required reassessment."],"acceptance":"The communication gap, limitations, recommendations and clinical ownership remain explicit."}],"setupFiles":[{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}},"ar":{"url":"https://mansoq.com/platform/teleicu?lang=ar","title":"العناية المركزة عن بُعد | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل.","description":"تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل. تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات…","answers":[{"question":"ما نطاق العناية المركزة عن بُعد في منسوق؟","answer":"تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل. إنشاء المركز والمواقع: حدد المنشآت المشاركة وأسرة العناية وتغطية المختصين. اتفق على الجهة المسؤولة عن الرعاية والسجلات المتاحة للفريق البعيد وجهات التصعيد بكل موقع. تحضير الحالة: اربط الشخص والزيارة بسياق المراجعة المشترك. أكد مصادر القياسات والملاحظات والصور وشغّل اتصالات الكاميرات والأجهزة ضمن النطاق المتفق عليه. المراجعة عن بُعد: يُراجع المختص المخوّل الحالة ويوثق التقييم والتوصيات. حدد مسؤول السرير الذي يستقبل الخطة وينفذها؛ لا تنقل المشورة المسؤولية السريرية ضمنياً. المتابعة والتصعيد: تابع المراجعة التالية ومسؤوليات التسليم. حافظ على إجراءات التواصل والتعطل عند غياب الفيديو أو نقص المعلومات أو الحاجة لتصعيد مباشر.","href":"/platform/teleicu#module-workflow"},{"question":"ما بيانات إعداد العناية المركزة عن بُعد؟","answer":"هيّئ الإصدار المختار بقوالب الحساب، ثم تحقق من المراجع وراجع المعاينة قبل الاستيراد. تشمل ملفات الإعداد والتخطيط: الأطباء والعيادات التشغيلية (doctors.csv)؛ تهيئة الجدولة (scheduling.csv)؛ الأصول والأجهزة والمعدات (assets_devices.csv)؛ مواصفات الربط (interfaces.csv)؛ الصلاحيات والموافقات (access_matrix.csv)؛ تهيئة المسارات السريرية (clinical_workflows.csv)؛ إعدادات الوظائف · إغلاقات الجدولة (product_settings.csv)؛ اختبارات القبول (uat_cases.csv). يوضح دليل كل ملف هل يستورد سجلات إعداد أم يوثق الترحيل والقرارات.","href":"/platform/teleicu#module-setup"},{"question":"كيف يتعامل العناية المركزة عن بُعد مع الاستثناءات؟","answer":"تعذر الاتصال عن بُعد انتقل لإجراء التواصل المعتمد وحدد مسؤولية السرير وطابق توثيق المراجعة بعد التعافي. بيانات المصدر ناقصة حدد القياس أو السجل المفقود واطلبه من المسؤول المحلي وسجّل حدود المراجعة عن بُعد.","href":"/platform/teleicu#module-exceptions"},{"question":"كيف يتصل العناية المركزة عن بُعد بالأنظمة الأخرى؟","answer":"لمسار المختص والفيديو والكاميرات والتبادل السريري والأجهزة حدود تنفيذ مستقلة. أكد شبكة كل منشأة وأجهزتها والاتصالات المدعومة قبل التشغيل.","href":"/platform/teleicu#module-connections"}],"module":{"name":"العناية المركزة عن بُعد","functions":["تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل."],"workflow":[{"title":"إنشاء المركز والمواقع","action":"حدد المنشآت المشاركة وأسرة العناية وتغطية المختصين. اتفق على الجهة المسؤولة عن الرعاية والسجلات المتاحة للفريق البعيد وجهات التصعيد بكل موقع.","owner":"مسؤولو البرنامج والمنشآت","record":"سجل المركز والمواقع وحدود الوصول وخطة التغطية"},{"title":"تحضير الحالة","action":"اربط الشخص والزيارة بسياق المراجعة المشترك. أكد مصادر القياسات والملاحظات والصور وشغّل اتصالات الكاميرات والأجهزة ضمن النطاق المتفق عليه.","owner":"الفريق المحلي عند السرير","record":"سياق الحالة والقياسات ومصادر الأجهزة المعتمدة"},{"title":"المراجعة عن بُعد","action":"يُراجع المختص المخوّل الحالة ويوثق التقييم والتوصيات. حدد مسؤول السرير الذي يستقبل الخطة وينفذها؛ لا تنقل المشورة المسؤولية السريرية ضمنياً.","owner":"المختص البعيد وطبيب السرير","record":"ملاحظة المراجعة والتوصية والمسؤول المحلي"},{"title":"المتابعة والتصعيد","action":"تابع المراجعة التالية ومسؤوليات التسليم. حافظ على إجراءات التواصل والتعطل عند غياب الفيديو أو نقص المعلومات أو الحاجة لتصعيد مباشر.","owner":"منسق البرنامج","record":"مسؤولية المتابعة والتصعيد وأدلة الدعم"}],"exceptions":[{"situation":"تعذر الاتصال عن بُعد","response":"انتقل لإجراء التواصل المعتمد وحدد مسؤولية السرير وطابق توثيق المراجعة بعد التعافي."},{"situation":"بيانات المصدر ناقصة","response":"حدد القياس أو السجل المفقود واطلبه من المسؤول المحلي وسجّل حدود المراجعة عن بُعد."}],"connection":"لمسار المختص والفيديو والكاميرات والتبادل السريري والأجهزة حدود تنفيذ مستقلة. أكد شبكة كل منشأة وأجهزتها والاتصالات المدعومة قبل التشغيل.","scenarios":[{"title":"مراجعة مختص بعيد لمنشأة طرفية","situation":"يطلب فريق سرير مشورة مختص ضمن برنامج المركز والمواقع المتفق عليه.","preparation":"سجل منشآت وتغطية مختص ووصول للسجلات ونطاق فيديو وأجهزة معتمد.","steps":["يجهز الفريق المحلي السياق والقياسات وسؤال المراجعة.","يراجع المختص المخوّل المصادر ويوثق التوصيات.","يؤكد طبيب السرير مسؤولية التصرف والخطة.","يسجّل المنسق مسؤولية المتابعة والتصعيد."],"acceptance":"تُميز توصية المختص ومسؤولية التصرف المحلي وترتبطان بالحالة."},{"title":"مراجعة بعيدة مع غياب الفيديو","situation":"لا تستطيع مراجعة مختص مخططة استخدام اتصال الفيديو المعتمد.","preparation":"جهات التعطل ومسؤول سريري محلي وتواصل بديل وإجراء توثيق.","steps":["سجّل تعطل الاتصال ومعلومات الحالة المتاحة.","استخدم التواصل البديل المعتمد ووضح حدود المراجعة.","يحتفظ الفريق المحلي بقرارات السرير ويوثق المشورة والإجراءات.","بعد التعافي طابق السجل وجدول إعادة التقييم المطلوبة."],"acceptance":"تبقى فجوة التواصل وحدود المراجعة والتوصيات ومسؤولية الرعاية واضحة."}],"setupFiles":[{"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"}]}}},{"slug":"/pricing","lastModified":"2026-10-18T19:22:00.000Z","en":{"url":"https://mansoq.com/pricing","title":"Healthcare software plans & package builder | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Start with Core and a complete care workflow. Add relevant departments and extensions, then review software, delivery and recurring obligations together.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Start with Core and a complete care workflow. Add relevant departments and extensions, then review software, delivery and recurring obligations together.","description":"Compare MANSOQ plans and build your healthcare package on one page. Choose care setting, modules, implementation and support; review trial eligibility.","answers":[],"pricing":{"plans":[{"name":"Essentials","description":"The selected care workflow, Core and required clinical components.","includedProducts":["core"],"enterprise":false,"trialDays":0},{"name":"Premium","description":"Core and the selected care workflow, connected revenue operations and advanced analytics.","includedProducts":["core","revenue_cycle","analytics"],"enterprise":false,"trialDays":0},{"name":"Diamond","description":"A deeper composition with full supported SBS tooling and configured integration scope.","includedProducts":["core","revenue_cycle","analytics","sbs_full","interfaces"],"enterprise":false,"trialDays":0},{"name":"Enterprise","description":"Negotiated network, integration, deployment and service scope. No trial.","includedProducts":["core","network_governance","implementation"],"enterprise":true,"trialDays":0},{"name":"Essential","description":"Complete the care workflow.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient"],"enterprise":false,"careProduct":"clinics","tier":"essential","baseCapacity":50,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":2,"standardExternalInterfaces":0,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":690,"monthlyManaged":300,"monthlyTotal":990,"setupBudgetRange":[1500,3000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Premium","description":"Reduce repeat work and find exceptions sooner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces"],"enterprise":false,"careProduct":"clinics","tier":"premium","baseCapacity":150,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":6,"standardExternalInterfaces":1,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":1090,"monthlyManaged":900,"monthlyTotal":1990,"setupBudgetRange":[2500,5000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Diamond","description":"Give agreed operational queues an accountable owner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces"],"enterprise":false,"careProduct":"clinics","tier":"diamond","baseCapacity":250,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":1690,"monthlyManaged":1800,"monthlyTotal":3490,"setupBudgetRange":[4000,8000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Enterprise","description":"Govern care and operations across the organization.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"clinics","tier":"enterprise","baseCapacity":550,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","trialDays":0},{"name":"Essential","description":"Complete the care workflow.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory"],"enterprise":false,"careProduct":"polyclinics","tier":"essential","baseCapacity":50,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":1490,"monthlyManaged":1000,"monthlyTotal":2490,"setupBudgetRange":[5000,10000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Premium","description":"Reduce repeat work and find exceptions sooner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces"],"enterprise":false,"careProduct":"polyclinics","tier":"premium","baseCapacity":150,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":2790,"monthlyManaged":2200,"monthlyTotal":4990,"setupBudgetRange":[8000,18000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Diamond","description":"Give agreed operational queues an accountable owner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces"],"enterprise":false,"careProduct":"polyclinics","tier":"diamond","baseCapacity":250,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":4,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":4490,"monthlyManaged":4500,"monthlyTotal":8990,"setupBudgetRange":[15000,30000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Enterprise","description":"Govern care and operations across the organization.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"polyclinics","tier":"enterprise","baseCapacity":550,"capacityDefinition":"A named independent clinician delivering care. Assisting nursing, administration and support accounts do not add a clinician fee.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","trialDays":0},{"name":"Essential","description":"Complete the care workflow.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"essential","baseCapacity":50,"capacityDefinition":"A commissioned, enabled ICU bed under the contract; no clinician shift or clinical alarm surveillance is included.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":4500,"monthlyManaged":2000,"monthlyTotal":6500,"setupBudgetRange":[10000,20000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Premium","description":"Reduce repeat work and find exceptions sooner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"premium","baseCapacity":150,"capacityDefinition":"A commissioned, enabled ICU bed under the contract; no clinician shift or clinical alarm surveillance is included.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":8500,"monthlyManaged":4000,"monthlyTotal":12500,"setupBudgetRange":[20000,50000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Diamond","description":"Give agreed operational queues an accountable owner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"diamond","baseCapacity":250,"capacityDefinition":"A commissioned, enabled ICU bed under the contract; no clinician shift or clinical alarm surveillance is included.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":4,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":14000,"monthlyManaged":8000,"monthlyTotal":22000,"setupBudgetRange":[40000,100000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Enterprise","description":"Govern care and operations across the organization.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"teleicu","tier":"enterprise","baseCapacity":550,"capacityDefinition":"A commissioned, enabled ICU bed under the contract; no clinician shift or clinical alarm surveillance is included.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","trialDays":0},{"name":"Essential","description":"Complete the care workflow.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative"],"enterprise":false,"careProduct":"home_palliative","tier":"essential","baseCapacity":50,"capacityDefinition":"A unique patient with a completed contracted visit or active remote episode during the month, counted once across branches. Archived or deceased patients do not remain billable.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":990,"monthlyManaged":1000,"monthlyTotal":1990,"setupBudgetRange":[3000,6000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Premium","description":"Reduce repeat work and find exceptions sooner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces"],"enterprise":false,"careProduct":"home_palliative","tier":"premium","baseCapacity":150,"capacityDefinition":"A unique patient with a completed contracted visit or active remote episode during the month, counted once across branches. Archived or deceased patients do not remain billable.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":1,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":1790,"monthlyManaged":2200,"monthlyTotal":3990,"setupBudgetRange":[5000,10000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Diamond","description":"Give agreed operational queues an accountable owner.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces"],"enterprise":false,"careProduct":"home_palliative","tier":"diamond","baseCapacity":250,"capacityDefinition":"A unique patient with a completed contracted visit or active remote episode during the month, counted once across branches. Archived or deceased patients do not remain billable.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":3,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","currency":"SAR","monthlySoftware":2490,"monthlyManaged":4500,"monthlyTotal":6990,"setupBudgetRange":[8000,20000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"Enterprise","description":"Govern care and operations across the organization.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"home_palliative","tier":"enterprise","baseCapacity":550,"capacityDefinition":"A unique patient with a completed contracted visit or active remote episode during the month, counted once across branches. Archived or deceased patients do not remain billable.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","trialDays":0}],"trialBoundary":"Published package duration does not establish eligibility or activation. The selected products and agreed evaluation scope apply.","builder":"/pricing#configuration"}},"ar":{"url":"https://mansoq.com/pricing?lang=ar","title":"باقات أنظمة الرعاية وبناء الحزمة | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"ابدأ بكور ومسار رعاية متكامل. أضف الأقسام والإضافات المناسبة ثم راجع البرمجيات والتنفيذ والالتزامات المتكررة معاً.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"ابدأ بكور ومسار رعاية متكامل. أضف الأقسام والإضافات المناسبة ثم راجع البرمجيات والتنفيذ والالتزامات المتكررة معاً.","description":"قارن باقات منسوق وابنِ حزمة الرعاية في صفحة واحدة. اختر بيئة الرعاية والوحدات والتنفيذ والدعم وراجع أهلية الفترة التجريبية.","answers":[],"pricing":{"plans":[{"name":"الأساسية","description":"مسار الرعاية المختار وكور والمكونات السريرية المطلوبة.","includedProducts":["core"],"enterprise":false,"trialDays":0},{"name":"بريميوم","description":"كور ومسار الرعاية المختار وتشغيل الإيرادات المترابط والتحليلات المتقدمة.","includedProducts":["core","revenue_cycle","analytics"],"enterprise":false,"trialDays":0},{"name":"الماسية","description":"تكوين أعمق بأدوات SBS المدعوم الكامل ونطاق تكامل مهيأ.","includedProducts":["core","revenue_cycle","analytics","sbs_full","interfaces"],"enterprise":false,"trialDays":0},{"name":"المؤسسات","description":"نطاق شبكة وتكامل وتنفيذ وخدمة متفاوض عليه، دون تجربة.","includedProducts":["core","network_governance","implementation"],"enterprise":true,"trialDays":0},{"name":"الأساسية","description":"أكمل مسار الرعاية.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient"],"enterprise":false,"careProduct":"clinics","tier":"essential","baseCapacity":50,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":2,"standardExternalInterfaces":0,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":690,"monthlyManaged":300,"monthlyTotal":990,"setupBudgetRange":[1500,3000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"بريميوم","description":"قلل العمل المتكرر واكتشف الاستثناءات مبكراً.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces"],"enterprise":false,"careProduct":"clinics","tier":"premium","baseCapacity":150,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":6,"standardExternalInterfaces":1,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":1090,"monthlyManaged":900,"monthlyTotal":1990,"setupBudgetRange":[2500,5000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"الماسية","description":"حدد مسؤولاً عن قوائم التشغيل المتفق عليها.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces"],"enterprise":false,"careProduct":"clinics","tier":"diamond","baseCapacity":250,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":1690,"monthlyManaged":1800,"monthlyTotal":3490,"setupBudgetRange":[4000,8000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"المؤسسات","description":"حوكم الرعاية والتشغيل على مستوى المؤسسة.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"clinics","tier":"enterprise","baseCapacity":550,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","trialDays":0},{"name":"الأساسية","description":"أكمل مسار الرعاية.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory"],"enterprise":false,"careProduct":"polyclinics","tier":"essential","baseCapacity":50,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":1490,"monthlyManaged":1000,"monthlyTotal":2490,"setupBudgetRange":[5000,10000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"بريميوم","description":"قلل العمل المتكرر واكتشف الاستثناءات مبكراً.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces"],"enterprise":false,"careProduct":"polyclinics","tier":"premium","baseCapacity":150,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":2790,"monthlyManaged":2200,"monthlyTotal":4990,"setupBudgetRange":[8000,18000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"الماسية","description":"حدد مسؤولاً عن قوائم التشغيل المتفق عليها.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces"],"enterprise":false,"careProduct":"polyclinics","tier":"diamond","baseCapacity":250,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":4,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":4490,"monthlyManaged":4500,"monthlyTotal":8990,"setupBudgetRange":[15000,30000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"المؤسسات","description":"حوكم الرعاية والتشغيل على مستوى المؤسسة.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","outpatient","pharmacy","laboratory","inventory","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"polyclinics","tier":"enterprise","baseCapacity":550,"capacityDefinition":"ممارس سريري مستقل مسمّى يقدم الرعاية. لا تضاف رسوم طبيب لحسابات التمريض المساعد والإدارة والدعم.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","trialDays":0},{"name":"الأساسية","description":"أكمل مسار الرعاية.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"essential","baseCapacity":50,"capacityDefinition":"سرير عناية مركزة مفعّل ومقبول ضمن العقد؛ لا يشمل نوبات الكادر أو مراقبة الإنذارات السريرية.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":4500,"monthlyManaged":2000,"monthlyTotal":6500,"setupBudgetRange":[10000,20000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"بريميوم","description":"قلل العمل المتكرر واكتشف الاستثناءات مبكراً.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"premium","baseCapacity":150,"capacityDefinition":"سرير عناية مركزة مفعّل ومقبول ضمن العقد؛ لا يشمل نوبات الكادر أو مراقبة الإنذارات السريرية.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":2,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":8500,"monthlyManaged":4000,"monthlyTotal":12500,"setupBudgetRange":[20000,50000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"الماسية","description":"حدد مسؤولاً عن قوائم التشغيل المتفق عليها.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces"],"enterprise":false,"careProduct":"teleicu","tier":"diamond","baseCapacity":250,"capacityDefinition":"سرير عناية مركزة مفعّل ومقبول ضمن العقد؛ لا يشمل نوبات الكادر أو مراقبة الإنذارات السريرية.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":4,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":14000,"monthlyManaged":8000,"monthlyTotal":22000,"setupBudgetRange":[40000,100000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"المؤسسات","description":"حوكم الرعاية والتشغيل على مستوى المؤسسة.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","teleicu","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"teleicu","tier":"enterprise","baseCapacity":550,"capacityDefinition":"سرير عناية مركزة مفعّل ومقبول ضمن العقد؛ لا يشمل نوبات الكادر أو مراقبة الإنذارات السريرية.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","trialDays":0},{"name":"الأساسية","description":"أكمل مسار الرعاية.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative"],"enterprise":false,"careProduct":"home_palliative","tier":"essential","baseCapacity":50,"capacityDefinition":"مريض فريد لديه زيارة متعاقد عليها مكتملة أو حلقة رعاية عن بُعد نشطة خلال الشهر؛ يحتسب مرة واحدة بين الفروع. لا يستمر احتساب المرضى المؤرشفين أو المتوفين.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1800},"includedSites":1,"managedHoursPerMonth":4,"standardExternalInterfaces":0,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":990,"monthlyManaged":1000,"monthlyTotal":1990,"setupBudgetRange":[3000,6000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"بريميوم","description":"قلل العمل المتكرر واكتشف الاستثناءات مبكراً.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces"],"enterprise":false,"careProduct":"home_palliative","tier":"premium","baseCapacity":150,"capacityDefinition":"مريض فريد لديه زيارة متعاقد عليها مكتملة أو حلقة رعاية عن بُعد نشطة خلال الشهر؛ يحتسب مرة واحدة بين الفروع. لا يستمر احتساب المرضى المؤرشفين أو المتوفين.","customerOwnedStorage":false,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1500},"includedSites":1,"managedHoursPerMonth":12,"standardExternalInterfaces":1,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":1790,"monthlyManaged":2200,"monthlyTotal":3990,"setupBudgetRange":[5000,10000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"الماسية","description":"حدد مسؤولاً عن قوائم التشغيل المتفق عليها.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces"],"enterprise":false,"careProduct":"home_palliative","tier":"diamond","baseCapacity":250,"capacityDefinition":"مريض فريد لديه زيارة متعاقد عليها مكتملة أو حلقة رعاية عن بُعد نشطة خلال الشهر؛ يحتسب مرة واحدة بين الفروع. لا يستمر احتساب المرضى المؤرشفين أو المتوفين.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"collectionFeeBps":1000},"includedSites":1,"managedHoursPerMonth":24,"standardExternalInterfaces":3,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","currency":"SAR","monthlySoftware":2490,"monthlyManaged":4500,"monthlyTotal":6990,"setupBudgetRange":[8000,20000],"annualSoftwareDiscountPercent":10,"taxAndSetup":"VAT where applicable and final setup / migration scope are additional.","trialDays":0},{"name":"المؤسسات","description":"حوكم الرعاية والتشغيل على مستوى المؤسسة.","includedProducts":["core","clinical_documentation","orders_medication","billing_finance","patient_access","revenue_cycle","sbs_specific","nphies","zatca","implementation","migration","support","managed_revenue","home_palliative","analytics","interfaces","network_governance"],"enterprise":true,"careProduct":"home_palliative","tier":"enterprise","baseCapacity":550,"capacityDefinition":"مريض فريد لديه زيارة متعاقد عليها مكتملة أو حلقة رعاية عن بُعد نشطة خلال الشهر؛ يحتسب مرة واحدة بين الفروع. لا يستمر احتساب المرضى المؤرشفين أو المتوفين.","customerOwnedStorage":true,"rcmRaas":{"enabled":true,"scope":{"en":"Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required.","ar":"متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة."},"minimumFeeBps":450,"maximumFeeBps":750},"includedSites":null,"managedHoursPerMonth":null,"standardExternalInterfaces":null,"responsibilities":"يوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","trialDays":0}],"trialBoundary":"Published package duration does not establish eligibility or activation. The selected products and agreed evaluation scope apply.","builder":"/pricing#configuration"}}},{"slug":"/pricing/capabilities","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/pricing/capabilities","title":"Healthcare software capabilities comparison | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Compare Core, care workflows, departments, granular RCM, SBS tooling, DRG, interfaces and delivery. Users and facilities are optional inputs.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Compare Core, care workflows, departments, granular RCM, SBS tooling, DRG, interfaces and delivery. Users and facilities are optional inputs.","description":"Compare MANSOQ capabilities in a searchable table: Core, care, departments, RCM and services. Review functions, required companions and operating scope.","answers":[]},"ar":{"url":"https://mansoq.com/pricing/capabilities?lang=ar","title":"مقارنة قدرات أنظمة الرعاية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"قارن كور ومسارات الرعاية والأقسام ووحدات الإيرادات التفصيلية وأدوات SBS وDRG والاتصالات والتنفيذ. المستخدمون والمنشآت مدخلات اختيارية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"قارن كور ومسارات الرعاية والأقسام ووحدات الإيرادات التفصيلية وأدوات SBS وDRG والاتصالات والتنفيذ. المستخدمون والمنشآت مدخلات اختيارية.","description":"قارن قدرات منسوق في جدول قابل للبحث: كور والرعاية والأقسام والإيرادات والخدمات، مع الوظائف والمتطلبات والنطاق.","answers":[]}},{"slug":"/privacy","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/privacy","title":"Website Privacy Policy | MANSOQ","eyebrow":"MANSOQ Platform","summary":"This website collects business contact details and the information you choose to include in an enquiry. Do not submit patient information.","sections":[{"kind":"cards","intro":"","items":[{"text":"Name, business email, organization, optional phone and enquiry details are stored for MANSOQ follow-up. Access is limited to authorized relationship staff.","title":"Enquiries"},{"text":"The public site uses device storage for your reading preferences. Signed-in dashboard users receive an essential session cookie. No advertising tracking is installed.","title":"Website storage"},{"text":"Use the contact form to request access, correction or removal of your business enquiry. A team member will verify the request before acting.","title":"Your request"},{"text":"This marketing site is separate from the clinical application. Healthcare data policies are defined for each clinical deployment.","title":"Deployment boundaries"}],"title":"How the website uses information."}],"seoTitle":"Website Privacy Policy | MANSOQ","seoDescription":"This website collects business contact details and the information you choose to include in an enquiry. Do not submit patient information.","description":"This website collects business contact details and the information you choose to include in an enquiry. Do not submit patient information.","answers":[]},"ar":{"url":"https://mansoq.com/privacy?lang=ar","title":"سياسة خصوصية الموقع | منسوق","eyebrow":"منصة منسوق","summary":"يجمع هذا الموقع بيانات التواصل التجاري والمعلومات التي تختار تضمينها في الاستفسار. لا ترسل معلومات المرضى.","sections":[{"kind":"cards","intro":"","items":[{"text":"يُحفظ الاسم والبريد التجاري والمؤسسة والهاتف الاختياري وتفاصيل الاستفسار لمتابعة منسوق. ويقتصر الوصول على الموظفين المخولين.","title":"الاستفسارات"},{"text":"يستخدم الموقع تخزين الجهاز لتفضيلات القراءة. ويحصل مستخدمو لوحة التحكم على ملف جلسة ضروري. لا توجد أدوات تتبع إعلاني.","title":"تخزين الموقع"},{"text":"استخدم نموذج التواصل لطلب الوصول إلى استفسارك أو تصحيحه أو إزالته. يتحقق أحد أعضاء الفريق من الطلب قبل تنفيذه.","title":"طلبك"},{"text":"هذا الموقع التسويقي منفصل عن التطبيق السريري. وتُحدد سياسات البيانات الصحية لكل تطبيق سريري.","title":"حدود النشر"}],"title":"كيف يستخدم الموقع المعلومات."}],"seoTitle":"سياسة خصوصية الموقع | منسوق","seoDescription":"يجمع هذا الموقع بيانات التواصل التجاري والمعلومات التي تختار تضمينها في الاستفسار. لا ترسل معلومات المرضى.","description":"يجمع هذا الموقع بيانات التواصل التجاري والمعلومات التي تختار تضمينها في الاستفسار. لا ترسل معلومات المرضى.","answers":[]}},{"slug":"/resources","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/resources","title":"Healthcare implementation guides & resources | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Explore implementation, product releases, Saudi compatibility and practical comparison guides.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Explore implementation, product releases, Saudi compatibility and practical comparison guides.","description":"MANSOQ implementation resources: account setup, CSV templates, product workflows, migration and integration references, acceptance testing and support.","answers":[],"overview":{"title":"Clarity for your next step.","summary":"Practical guidance for choosing, implementing and operating MANSOQ.","areas":[{"name":"Find a clear answer.","purpose":"Understand your plans, product benefits, prices, managed services and data choices. Search the complete FAQ by topic.","functions":[],"details":"/faq"},{"name":"Plan your implementation.","purpose":"Prepare your account, people, workflows and data. Follow the setup guide with templates and acceptance steps through go-live.","functions":[],"details":"/resources/implementation"},{"name":"Help guides","purpose":"Follow step-by-step guides for your account, ordering, facility setup, security, invoices, export and support requests.","functions":[],"details":"/help"},{"name":"Migration & integration","purpose":"Plan the move from your existing systems, with data mappings, validation and cutover references.","functions":[],"details":"/resources/migration-integration"},{"name":"Compare approaches","purpose":"Compare the scope, responsibilities and evidence that matter to your facility.","functions":[],"details":"/compare"},{"name":"Saudi compatibility","purpose":"Review national workflows, clinical standards and the requirements for activation.","functions":[],"details":"/saudi"},{"name":"Product releases","purpose":"See published releases and the current platform service status.","functions":[],"details":"/platform/releases"},{"name":"Trust & responsibilities","purpose":"Understand access controls, audit records, data protection and operating boundaries.","functions":[],"details":"/company/trust"}]}},"ar":{"url":"https://mansoq.com/resources?lang=ar","title":"أدلة تنفيذ أنظمة الرعاية ومواردها | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استكشف التنفيذ وإصدارات المنتجات والتوافق مع المتطلبات السعودية وأدلة المقارنة العملية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استكشف التنفيذ وإصدارات المنتجات والتوافق مع المتطلبات السعودية وأدلة المقارنة العملية.","description":"موارد تنفيذ منسوق: إعداد الحساب وقوالب CSV ومسارات المنتجات ومراجع الترحيل والتكامل واختبارات القبول والدعم.","answers":[],"overview":{"title":"وضوح لخطوتك التالية.","summary":"إرشادات عملية لاختيار منسوق وتنفيذه وتشغيله.","areas":[{"name":"اعثر على إجابة واضحة.","purpose":"افهم الباقات وفوائد المنتجات والأسعار والخدمات المدارة وخيارات البيانات. ابحث في دليل الأسئلة الشائعة حسب الموضوع.","functions":[],"details":"/faq"},{"name":"خطط لتنفيذ منسوق.","purpose":"جهّز الحساب والفريق والمسارات والبيانات. اتبع دليل الإعداد مع القوالب وخطوات القبول حتى الإطلاق.","functions":[],"details":"/resources/implementation"},{"name":"أدلة المساعدة","purpose":"اتبع أدلة خطوة بخطوة للحساب والطلب وإعداد المنشأة والأمان والفواتير والتصدير وطلبات الدعم.","functions":[],"details":"/help"},{"name":"الترحيل والتكامل","purpose":"خطط للانتقال من أنظمتك الحالية مع مراجع مواءمة البيانات والتحقق والتحويل.","functions":[],"details":"/resources/migration-integration"},{"name":"قارن الأساليب","purpose":"قارن النطاق والمسؤوليات والأدلة التي تهم منشأتك.","functions":[],"details":"/compare"},{"name":"التوافق السعودي","purpose":"راجع المسارات الوطنية والمعايير السريرية ومتطلبات التفعيل.","functions":[],"details":"/saudi"},{"name":"إصدارات المنتجات","purpose":"اطّلع على الإصدارات المنشورة والحالة الحالية لخدمات المنصة.","functions":[],"details":"/platform/releases"},{"name":"الثقة والمسؤوليات","purpose":"تعرّف على ضوابط الوصول وسجلات التدقيق وحماية البيانات وحدود التشغيل.","functions":[],"details":"/company/trust"}]}}},{"slug":"/resources/implementation","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/resources/implementation","title":"Healthcare software implementation & CSV setup | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Agree the operational scope, prepare data and interfaces, rehearse the work and confirm rollout responsibilities.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Agree the operational scope, prepare data and interfaces, rehearse the work and confirm rollout responsibilities.","description":"Set up MANSOQ accounts and products with CSV templates, sample data, field guides and validation. Migration, integration, testing, cutover and support.","answers":[{"question":"How do I implement MANSOQ from account setup to go-live?","answer":"Agree products, release, facilities and data boundaries. Import foundation setup first, then product data with validated references. Approve interfaces and migration mappings, rehearse clinical and financial workflows and exceptions, reconcile totals, accept cutover and recovery, then hand over monitored support. Each stage identifies owners, required files and an acceptance gate.","href":"/resources/implementation#implementation-path"},{"question":"Which CSV templates can I download and upload?","answer":"Use templates for departments, users, roles and permissions, services and SBS mappings, doctors and schedules, assets, stock, devices and selected-product configuration. Download the matching sample and field dictionary. Setup files use the account import route; evidence registers and migration manifests have separately identified destinations. Validate before committing any import.","href":"/resources/implementation#templates"},{"question":"How do I migrate Epic, TrakCare or Oracle Health to MANSOQ?","answer":"Confirm the exact installed product and release and obtain authorized exports and dictionaries. Inventory clinical, operational, financial and attachment domains separately; preserve source identifiers. Approve the target adapter, mapping and test cohort, reconcile records and balances, rehearse final deltas and rollback, then accept the cutover. A FHIR clinical extract alone may not include schedules, claims, balances or images.","href":"/resources/migration-integration"}],"implementation":{"phases":[{"name":"Agree the scope","owner":"Sponsor + product owners","before":"Named sponsor, facility list and selected products.","steps":["List every legal entity, facility, department, product and operating mode. Separate native operation from a connection to another system.","Pin the application, interface and terminology releases. Confirm availability, licence rights, seats, facilities, storage and support terms against the proposal.","Name clinical, finance, data, security, integration and operations owners. Agree approvals, test evidence and decision deadlines.","Record each assumption: history to migrate, language, currency, time zone, shared identifiers, downtime, external credentials and who owns each system. Do not turn an unresolved assumption into a default.","Agree acceptance criteria and the exact tasks that are out of scope. Give each excluded task a reason, owner and follow-up path."],"acceptance":"Signed scope, release list and decision register.","exception":"Unavailable product, missing licence or unapproved data boundary: revise scope before account launch.","files":["project_scope","assumptions_decisions"]},{"name":"Create your account foundation","owner":"Verified account administrator","before":"Approved scope and an eligible agreement or trial.","steps":["Sign in with a verified account, select the correct organization and subscription, then open account setup. Only its administrator can save configuration.","Download the organization template inside setup. Enter legal name, registration, country and applicable VAT identifier; identifiers stay as text.","Import exactly the contracted number of facilities with licence, address, phone and IANA time zone. Licence values are customer declarations until verified.","Import departments and room, ward or bed locations. Facility numbers start at 1 and follow the saved facility order. Keep names unique within each facility.","Import the planned team. Seats include the account administrator. Staff records have no shared password; invitations and verified account sign-in grant access.","Set language, currency, working days and same-day opening hours. The slot duration must divide the available minutes. Use separate rows for same-day split sessions. Document full overnight clinical rosters in the scheduling preparation file and approve their release-specific configuration; the appointment CSV does not accept next-day end times or 24:00."],"acceptance":"Saved organization, facilities, departments, team and operating preferences.","exception":"Wrong organization or counts: correct before proceeding. A submitted setup is locked; route later changes through an approved change request.","files":["organization","facilities","departments","locations","staff","operations","access_matrix"]},{"name":"Configure each selected product","owner":"Department owners + administrator","before":"Foundation files saved and product releases agreed.","steps":["Open Your products · configuration data. The system requests datasets applicable to the selected capabilities. Download its exact version of each template.","Import custom roles only when needed, using published permission identifiers. Assign team emails to approved department roles; then import clinician qualifications, licence declarations and operational clinic affiliations.","Import local services before prices and SBS mappings. Enter gross prices in minor currency units, with currency. An SBS proposal needs its code, release and approval reference; it becomes a draft until terminology and authority checks pass.","Import doctor schedules after clinic affiliations. Supply department, location, weekday, dates and slots. Split overnight coverage into day-bound segments with explicit valid dates; overlapping doctor shifts are rejected.","Import stock items before opening lots and quantities. Reconcile units, lot, expiry, location and purchase price. Import devices with serial, model, department, location and protocol; commissioning remains a separate acceptance task.","Use the product guide below to enumerate every selected function. Record its local configuration, owner and approval in product settings. This register does not execute arbitrary settings; configure and test any release-specific workflow in its product workspace before activation.","Complete dataset decisions: provided with valid records, or not applicable with a reason. Review previews, apply and Save and continue. Resolve missing references before the server accepts the step.","Review setup manually, confirm your eligible payment or trial and provision the private application. Capacity, secure connection, health and imported record counts must pass before sign-in. Use an approved test workspace for the rehearsal stages; account provisioning is separate from clinical production acceptance."],"acceptance":"Cross-file validation passes; every applicable dataset has an explicit decision.","exception":"Unknown service, item, doctor, permission, location or overlapping shift: reject the batch and correct the source file. No partial product import is accepted at launch.","files":["roles","user_access","doctors","services","service_billing","doctor_schedules","stock_items","stock_balances","assets_devices","product_settings","dataset_decisions","clinical_workflows","scheduling"]},{"name":"Prepare revenue rules and authority","owner":"Finance + payer contracting owners","before":"Approved legal source documents, services and code release.","steps":["Follow the RCM sequence below: legal counterparties, insurer and TPA roles, delegation, provider contracts, products, issued policies, classes, benefits, tariffs, networks and enrolment.","Keep the risk-bearing insurer distinct from the administrator. Keep a commercial insurance product distinct from an issued policy. Record effective dates, currency, deadlines and amendments from the signed source.","Define covered and excluded services, limits, deductibles, co-pay, preauthorization conditions and precedence. Gross list price is not the payer-contracted allowed amount.","Stage source-backed configuration, review row errors and compare overlaps. Approve drafts before publishing a new immutable rule version. Each preparation register states its handling: imported natively in your workspace as drafts, evidence with workspace readback, or excluded and handled outside this setup (ZATCA onboarding). Readiness columns such as status, certification_status and allow_live_submission are declared, not applied; activation happens in the workspace. approval_reference is a reference, not an approval.","Rehearse eligibility, authorization, charge capture, corrected claim, denial, appeal, remittance, partial payment, reversal and reconciliation. Verify ownership and audit evidence at each transition."],"acceptance":"Approved rule version and reconciled financial test evidence.","exception":"Missing authority, contradictory dates, inferred cover or unmatched totals: hold financial activation and assign an owner. Follow the approved clinical contingency process independently.","files":["rcm_organizations","rcm_provider_contracts","rcm_insurance_products","rcm_issued_policies","rcm_benefit_classes","rcm_benefit_rules","rcm_tariffs","rcm_tariff_assignments"]},{"name":"Connect systems and devices","owner":"Integration + biomedical owners","before":"Approved message scope, identities and external onboarding.","steps":["Inventory every external source and destination: NPHIES, ZATCA, accounting, laboratory analysers, PACS/RIS, devices and network services. Agree protocol, release, direction and owner.","Approve identifier, service, terminology, unit, timestamp and status mappings. Keep patient matching rules explicit and route ambiguous identities for review.","Record readiness in account setup; store secrets in the approved credential manager. Separate sandbox and production endpoints, certificates, permissions and expiry dates.","For NPHIES, pin the currently certified implementation package and test the contracted transactions. For ZATCA, confirm the applicable phase and complete the required device and endpoint onboarding. Public documentation is not a production certificate.","Test normal messages, duplicates, timeout, out-of-order delivery, rejection, retry, outage and recovery. Confirm reconciliation, monitoring, alert owner and manual fallback."],"acceptance":"Each interface has accepted mapping, sandbox evidence and production approval.","exception":"Credentials, certification or hardware unavailable: mark the connection blocked, use an approved fallback and do not label it live.","files":["integrations","interfaces","assets_devices","rcm_nphies_configurations","rcm_production_endpoints","rcm_production_routing_rules","rcm_zatca_onboardings"]},{"name":"Reconcile existing data","owner":"Data + clinical + finance owners","before":"Approved data boundary, retention and source inventory.","steps":["Classify the source: patient master, active encounters, history, documents, open orders, medications, stock, coverage, unpaid invoices and open claims. Decide migrate, retain read-only, archive or exclude for each dataset.","Approve legal access, retention and secure transfer with the data owner. Keep patient and financial data out of public templates, email and screenshots. Use a secured project workspace.","Map each source field to the exact destination schema and release. Define null handling, duplicate keys, identifier systems, terminology, dates and attachment checksums. Do not merge ambiguous patient records automatically.","Run a dry import into an isolated test environment. Reject invalid rows; reconcile source count = accepted + rejected, monetary totals, stock units and attachment counts. Sample records with the department owners.","Freeze the source, define a delta extract and rehearse rollback before cutover. New-tenant bootstrap creates no patients; historical migration runs only after the approved mapping and importer exist."],"acceptance":"Signed mapping, batch hashes, rejected-row log and reconciled totals.","exception":"No legacy data: record not applicable with source-owner approval. Failed reconciliation: correct and rerun; retain the source system until acceptance.","files":["migration_mapping","migration_batches","medication_catalogue","inventory_opening"]},{"name":"Prove the complete journey","owner":"Product owners + security + finance","before":"Configured test environment and synthetic or authorized test data.","steps":["Turn each selected product function into a test with exact preconditions, actions and expected result. Include the handover to the next department and final financial state.","Test success, missing data, invalid identifiers, duplicate records, access denied, date boundaries, cancellations, corrections and concurrency. Verify no cross-facility exposure.","Test peak workload, backup restore, downtime, retry and recovery. Inspect audit history, external messages, receipt counts and stock/financial control totals.","Record actual results and evidence. Fix blocking defects, retest affected dependencies and obtain clinical, finance, security and operations sign-off. Never mark not-run as passed."],"acceptance":"Every in-scope test passed or has an explicit accepted exception and fallback.","exception":"Critical defect, unsafe workflow, data mismatch or access leak: block go-live and retest.","files":["uat_cases","clinical_workflows"]},{"name":"Prepare every role","owner":"Superusers + department leads","before":"Accepted workflows and role-based training environment.","steps":["Train administrators, reception, clinicians, nurses, departments, pharmacy, stores, finance, support and leadership on their own selected scope.","Use complete scenarios: normal work, correction, cancellation, handover, escalation, access denial and downtime. Include shift changes and after-hours ownership.","Record attendance and observed competency. Retrain failed tasks, identify superusers per shift and distribute the approved help and escalation routes."],"acceptance":"Required staff complete competency checks and know the fallback.","exception":"Absent or unsuccessful staff: schedule make-up training and keep supervised access until accepted.","files":["training","access_matrix"]},{"name":"Launch with a tested fallback","owner":"Go-live decision owner + operations","before":"Approved acceptance, training, migration and connection evidence.","steps":["Approve the change window, communication plan, freeze, backups, decision owner, rollback thresholds and downtime process. Test restore before the window.","Confirm the provisioned private application, agreed production release and recorded import counts. Payment or a valid trial, subscribed limits and application health remain mandatory. Production use needs the separate go-live decision after all acceptance checks.","Choose the app address; if using a custom domain, verify DNS ownership and secure connection. Product data imports with the facility bootstrap in one transaction; verified receipt counts must match the submitted files.","Apply the approved migration delta, validate record and control totals, run role-based smoke tests and verify external production responses. Record the exact release and import receipts.","The named owner decides go or rollback at each hold point. If rollback is triggered, stop new writes, preserve audit and transaction records, restore the approved state and reconcile work performed during the window."],"acceptance":"Signed go-live decision, verified import counts and production smoke-test evidence.","exception":"Capacity, DNS, health, import-count or critical test failure: keep launch blocked and follow the recorded fallback.","files":["domain","cutover_runbook","migration_batches","uat_cases"]},{"name":"Stabilize and hand over","owner":"Support owner + service owners","before":"Accepted go-live record and named support coverage.","steps":["Monitor application health, access errors, interface queues, rejected messages, claim states, finance reconciliation and stock discrepancies. Assign alerts to people and agree response times.","Reconcile daily through the agreed stabilization period. Review unresolved defects, user competency and fallback use with department owners.","Hand over contacts, coverage, escalation, release inventory, approved configuration, backup/restore evidence, certificate expiry and licence renewal ownership.","Close implementation only after acceptance criteria pass. Use controlled change requests for new products, sites, interfaces, rules and releases; repeat affected tests and update CSV templates when schemas change."],"acceptance":"Accepted support handover with accountable owners and renewal dates.","exception":"Unresolved critical issue: continue stabilization with a tracked owner; do not close the implementation.","files":["support_handover","assumptions_decisions"]}],"productInputs":{"core":["Identity rules and duplicate review","Facility boundaries, roles and permissions","Audit, retention and common configuration"],"outpatient":["Clinics, consultation rooms and specialties","Doctor affiliations, schedules and visit types","Documentation, orders, results and follow-up"],"inpatient":["Wards, beds and transfer states","Care teams, shift handovers and care plans","Medication, departmental orders and discharge"],"emergency":["Arrival and locally approved triage states","Urgent care roles, locations and escalation","Observation, admission, transfer and discharge"],"teleicu":["Hub/spoke facilities and specialist coverage","Patient context sources and device interfaces","Remote review, escalation and bedside responsibility"],"home_palliative":["Service zones, visit teams and travel constraints","Care plans, consent and caregiver contacts","Remote documentation, symptom review and escalation"],"operating_room":["Theatres, resources, sessions and equipment","Procedure preparation and approved safety checklist","Anesthesia, consumables, recovery and handover"],"icu":["Bed/monitor inventory and care-team coverage","Observations, devices and unit mappings","Medication, escalation and shift handover"],"pharmacy":["Medication catalogue, codes, units and conversions","Prescription verification, dispensing and returns","Stock lots, expiry and controlled access"],"laboratory":["Test catalogue, specimens and collection workflow","Analyzer mappings, units and reference intervals","Result validation, critical-result escalation and amended reports"],"radiology":["Modalities, procedure catalogue and scheduling","RIS/PACS accession identifiers and interfaces","Acquisition, reporting, addenda and critical-result escalation"],"inventory":["Stores, items, units and suppliers","Opening lots, quantities, cost and expiry","Receipt, issue, transfer, return and reconciliation"],"clinical_documentation":["Approved templates, author roles and signatures","Correction and amendment rules","Retention and encounter linkage"],"orders_medication":["Order types, approved catalogues and destinations","Statuses, authorization and cancellation","Results, medication links and responsibility"],"patient_access":["Identifiers, registration and matching","Visit types, booking resources and arrival","Consent, cancellation and referral ownership"],"billing_finance":["Gross prices, tax applicability and invoice ownership","Payments, refunds and reversals","Finance export, control totals and reconciliation"],"revenue_cycle":["Legal entities, contracts and issued policies","Benefits, networks, tariffs and rule versions","Eligibility through claim, denial, payment and reconciliation"],"sbs_specific":["Selected SBS codes and release rights","Local-service mapping and effective dates","Approval evidence and code validation"],"sbs_full":["Licensed catalogue release and scope","Full code mappings and catalogue import owner","Inactive codes, version changes and usage rights"],"drg":["Grouper version and licence","Coding inputs, completeness and grouping route","Casemix outputs, correction and financial use approval"],"nphies":["Provider identity, payer routes and certified package","Sandbox/production endpoints and secret references","Eligibility, authorization, claim and payment-response tests"],"zatca":["Legal taxpayer, VAT and applicable phase","Invoice sequences, tax categories and device onboarding","Clearance/reporting, retry and credential renewal"],"analytics":["Source ownership, metric definitions and access","Refresh, filters, grain and reconciliation","Export controls and dashboard acceptance"],"ai":["Approved use case, data access and model version","Human review, failure route and audit","Evaluation criteria and monitoring; no autonomous clinical assumption"],"interfaces":["Protocol/version, source/target and ownership","Identifier and terminology mapping","Retry, duplicates, queues, outage and recovery"],"network_governance":["Legal entities, facility and data boundaries","Delegated administration and cross-site roles","Patient continuity, shared catalogues and boundary tests"],"implementation":["Scope, owners, releases and acceptance","Configuration, tests, training and cutover","Support handover and controlled changes"],"migration":["Source inventory and retention decision","Field mapping, dry runs and rejected records","Cutover delta, control totals and rollback"],"support":["Coverage, contacts and severity rules","Alert ownership, escalation and restoration","Renewals, release maintenance and acceptance"],"equipment":["Device inventory, location and maintenance","Protocol, connectivity and commissioning","Acceptance tests and biomedical ownership"],"managed_revenue":["Delegated duties and payer authority","Work queues, source access and quality checks","Submission, remittance, reconciliation and reporting"],"rcm_eligibility":["Member/policy identifiers and payer route","Benefit version and service context","Unavailable, expired and conflicting cover handling"],"rcm_authorization":["Service/code mapping and evidence requirements","Requested, approved, denied and expired states","Partial approval, extension, cancellation and escalation"],"rcm_contracts":["Legal provider/insurer/administrator IDs","Signed effective dates and amendments","Allowed amounts, deadlines and evidence authority"],"rcm_networks":["Provider affiliations and network tiers","Effective dates and policy relationships","Out-of-network exceptions and precedence"],"rcm_benefits":["Issued policy, member class and limits","Exclusions, deductibles and co-pay","Accumulation, exceptions and rule precedence"],"rcm_tariffs":["Catalogue codes, currency and gross prices","Contracted allowed amounts and assignments","Effective overlap, negotiated exceptions and amendments"],"rcm_charge_capture":["Service event and charge identity","Quantity, unit, performer and documentation","Missing charge, duplicates, corrections and reversals"],"rcm_claims":["Submission authority, deadlines and routes","Payload completeness and attachments","Status polling, duplicates, cancellation and corrected claims"],"rcm_denials":["Payer reason codes and owner routing","Documentation correction and appeal deadlines","Appeal evidence, resubmission and disposition"],"rcm_remittance":["Payer payment reference and claim links","Advice lines, deductions and adjustments","Partial payment, reversal and unmatched advice"],"rcm_reconciliation":["Bank/ledger/payer identifiers and dates","Control totals, currencies and exceptions","Unallocated cash, settlement and approved adjustments"],"rcm_reporting":["Metric definitions and source lineage","Role-based queues and refresh windows","Financial totals, exports and management review"]},"materials":[{"id":"organization","title":"Your organization","purpose":"Use the registered details of your organization. Do not enter patient records here.","route":"setup","dependencies":[],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"legal_name","name":"Registered organization name","required":true,"format":"text","example":"Example Healthcare Organization"},{"id":"registration_number","name":"Commercial registration number","required":true,"format":"text","example":"EXAMPLE-CR-001"},{"id":"country","name":"Country","required":true,"format":"SA / AE / BH / KW / QA / OM / EG / OTHER","example":"SA"},{"id":"vat_number","name":"Tax registration number","required":false,"format":"text","example":""}],"template":"/implementation/templates/organization.csv","example":"/implementation/examples/organization.csv"},{"id":"facilities","title":"Facilities","purpose":"Add every facility included in your subscription. These become real, separate facilities in your app.","route":"setup","dependencies":["organization"],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"name","name":"Facility name","required":true,"format":"text","example":"Example Facility"},{"id":"type","name":"Facility type","required":true,"format":"hospital / clinic / polyclinic / laboratory / other","example":"clinic"},{"id":"license_number","name":"Facility license","required":true,"format":"text","example":"EXAMPLE-LICENSE-001"},{"id":"address","name":"Address","required":true,"format":"text","example":"Example training address"},{"id":"phone","name":"Phone","required":true,"format":"text","example":"+966500000000"},{"id":"timezone","name":"Time zone","required":true,"format":"Asia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTC","example":"Asia/Riyadh"}],"template":"/implementation/templates/facilities.csv","example":"/implementation/examples/facilities.csv"},{"id":"departments","title":"Departments","purpose":"Create departments, consultation rooms, wards and beds. You can add more inside your app.","route":"setup","dependencies":["facilities"],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"facility","name":"Facility number (starting at 1)","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"Department name","required":true,"format":"text","example":"Example Department"}],"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"id":"locations","title":"Rooms, wards and beds","purpose":"Create departments, consultation rooms, wards and beds. You can add more inside your app.","route":"setup","dependencies":["facilities"],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"Location name","required":true,"format":"text","example":"Example Room"},{"id":"kind","name":"Type","required":true,"format":"room / ward / bed","example":"room"},{"id":"parent","name":"Inside location (optional)","required":false,"format":"text","example":""}],"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"id":"staff","title":"Planned team","purpose":"Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.","route":"setup","dependencies":[],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"name","name":"Name","required":true,"format":"text","example":"Example Staff"},{"id":"email","name":"Work email","required":true,"format":"email","example":"staff@example.invalid"},{"id":"role","name":"Clinical role","required":true,"format":"facility_admin / doctor / nurse / pharmacist / reception / billing / member","example":"doctor"}],"template":"/implementation/templates/staff.csv","example":"/implementation/examples/staff.csv"},{"id":"operations","title":"Operating preferences","purpose":"Set working days, hours, patient identifiers and billing preferences. Your app starts with an empty patient database.","route":"setup","dependencies":[],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"working_days","name":"Working days","required":true,"format":"sun-thu / mon-fri / every-day","example":"sun-thu"},{"id":"opening_time","name":"Opening time (HH:MM)","required":true,"format":"text","example":"08:00"},{"id":"closing_time","name":"Closing time (HH:MM)","required":true,"format":"text","example":"17:00"},{"id":"slot_minutes","name":"Appointment duration (minutes)","required":true,"format":"integer 5–240","example":"15"},{"id":"patient_prefix","name":"Patient record prefix","required":false,"format":"text","example":"EXAMPLE"},{"id":"billing_currency","name":"Billing currency","required":true,"format":"SAR","example":"SAR"},{"id":"language","name":"Default language","required":true,"format":"ar / en","example":"en"}],"template":"/implementation/templates/operations.csv","example":"/implementation/examples/operations.csv"},{"id":"integrations","title":"Integration readiness","purpose":"Identify external systems. Credentials are entered securely in your own app after launch; approvals may be required before live use.","route":"setup","dependencies":[],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"nphies_provider_id","name":"NPHIES provider identifier","required":false,"format":"text","example":""},{"id":"payer_names","name":"Payers / insurers","required":false,"format":"text","example":""},{"id":"accounting_system","name":"Accounting system","required":false,"format":"text","example":""},{"id":"migration_required","name":"Existing data needs migration","required":false,"format":"true / false","example":"false"}],"template":"/implementation/templates/integrations.csv","example":"/implementation/examples/integrations.csv"},{"id":"domain","title":"Your app address","purpose":"Choose a unique address. Eligible packages can attach a domain after ownership and secure connection checks.","route":"setup","dependencies":[],"acceptance":"Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.","columns":[{"id":"slug","name":"App address, for example: my-clinic","required":true,"format":"text","example":"example-clinic"},{"id":"custom_domain","name":"Custom domain (optional)","required":false,"format":"text","example":""}],"template":"/implementation/templates/domain.csv","example":"/implementation/examples/domain.csv"},{"id":"roles","title":"Roles & permissions","purpose":"Security roles and explicit permissions","route":"setup","dependencies":[],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"role_name","name":"Role name","required":true,"format":"text","example":"Example scheduling role"},{"id":"permission_slug","name":"Permission identifier","required":true,"format":"text","example":"can_list_schedule"}],"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"id":"user_access","title":"Users & department access","purpose":"Facility organization memberships","route":"setup","dependencies":["staff","departments","roles"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"staff_email","name":"Staff email","required":true,"format":"email","example":"staff@example.invalid"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"Department name","required":true,"format":"text","example":"Example Department"},{"id":"role_name","name":"Approved role name","required":true,"format":"text","example":"Doctor"}],"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"id":"doctors","title":"Doctors & operational clinics","purpose":"User clinician profile and clinic affiliation","route":"setup","dependencies":["staff","departments","locations","user_access"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"staff_email","name":"Doctor email","required":true,"format":"email","example":"staff@example.invalid"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"Department","required":true,"format":"text","example":"Example Department"},{"id":"clinic_location","name":"Clinic location","required":true,"format":"text","example":"Example Room"},{"id":"qualification","name":"Qualification","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"license_number","name":"Practitioner licence","required":true,"format":"text","example":"EXAMPLE-LICENSE-001"},{"id":"primary_clinic","name":"Primary clinic","required":false,"format":"checkbox","example":"true"}],"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"id":"services","title":"Services & department catalogue","purpose":"Healthcare service directory","route":"setup","dependencies":["departments","locations"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"service_code","name":"Local service code","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"name_en","name":"English name","required":true,"format":"text","example":"Example service"},{"id":"name_ar","name":"Arabic name","required":true,"format":"text","example":"خدمة تدريبية"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"Department","required":true,"format":"text","example":"Example Department"},{"id":"location","name":"Location","required":true,"format":"text","example":"Example Room"},{"id":"internal_type","name":"Service function","required":true,"format":"general / scheduling / lab / pharmacy / store","example":"scheduling"}],"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"id":"service_billing","title":"Service prices & SBS mapping","purpose":"Draft charge definitions with release-bound SBS codes","route":"setup","dependencies":["services"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"service_code","name":"Local service code","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"gross_price_minor","name":"Gross price in minor currency units","required":true,"format":"integer 0–2147483647","example":"15000"},{"id":"currency","name":"Currency","required":true,"format":"SAR","example":"SAR"},{"id":"sbs_code","name":"SBS code","required":false,"format":"text","example":""},{"id":"sbs_release","name":"SBS release","required":false,"format":"text","example":""},{"id":"mapping_evidence","name":"Mapping approval reference","required":false,"format":"text","example":""}],"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"id":"doctor_schedules","title":"Doctor schedules · every department","purpose":"Practitioner schedules and availability","route":"setup","dependencies":["doctors","services"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"schedule_code","name":"Unique schedule code","required":true,"format":"text","example":"EXAMPLE-SCH-001"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"staff_email","name":"Doctor email","required":true,"format":"email","example":"staff@example.invalid"},{"id":"department","name":"Department","required":true,"format":"text","example":"Example Department"},{"id":"clinic_location","name":"Clinic location","required":true,"format":"text","example":"Example Room"},{"id":"weekday","name":"Weekday","required":true,"format":"mon / tue / wed / thu / fri / sat / sun","example":"sun"},{"id":"start_time","name":"Start time","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"End time","required":true,"format":"HH:MM","example":"12:00"},{"id":"slot_minutes","name":"Slot duration","required":true,"format":"integer 5–240","example":"15"},{"id":"valid_from","name":"Valid from","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"valid_to","name":"Valid to","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"}],"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"id":"stock_items","title":"Inventory & medication items","purpose":"Product knowledge catalogue","route":"setup","dependencies":["facilities"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"item_code","name":"Unique item code","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"Item name","required":true,"format":"text","example":"Training consumable"},{"id":"product_type","name":"Type","required":true,"format":"medication / consumable / nutritional_product","example":"consumable"},{"id":"unit_code","name":"UCUM unit code","required":true,"format":"text","example":"1"},{"id":"code_system","name":"Terminology system","required":false,"format":"text","example":""},{"id":"external_code","name":"External code","required":false,"format":"text","example":""}],"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"id":"stock_balances","title":"Stock lots & opening quantities","purpose":"Products, lots and location inventory balances","route":"setup","dependencies":["stock_items","locations"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"item_code","name":"Item code","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"location","name":"Storage location","required":true,"format":"text","example":"Example Room"},{"id":"lot_number","name":"Lot number","required":true,"format":"text","example":"EXAMPLE-LOT-001"},{"id":"expiry_date","name":"Expiry date","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"quantity","name":"Opening quantity","required":true,"format":"text","example":"10"},{"id":"purchase_price","name":"Unit purchase price","required":true,"format":"text","example":"1.50"}],"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"id":"assets_devices","title":"Assets, devices & hardware","purpose":"Device register, location and department assignment","route":"setup","dependencies":["departments","locations"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"asset_code","name":"Unique asset code","required":true,"format":"text","example":"EXAMPLE-LAB-001"},{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"Department","required":true,"format":"text","example":"Example Department"},{"id":"location","name":"Location","required":true,"format":"text","example":"Example Room"},{"id":"name","name":"Device name","required":true,"format":"text","example":"Training laboratory analyser"},{"id":"manufacturer","name":"Manufacturer","required":true,"format":"text","example":"Example manufacturer"},{"id":"model","name":"Model","required":true,"format":"text","example":"EXAMPLE-MODEL"},{"id":"serial_number","name":"Serial number","required":true,"format":"text","example":"EXAMPLE-SERIAL"},{"id":"care_type","name":"Product / department purpose","required":true,"format":"text","example":"laboratory"},{"id":"protocol","name":"Interface protocol and version","required":false,"format":"text","example":"TO-CONFIRM"},{"id":"maintenance_due","name":"Maintenance due","required":false,"format":"YYYY-MM-DD","example":"2027-10-09"}],"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"id":"product_settings","title":"Function settings · scheduling closures","purpose":"Registry function settings applied to native scheduling closures with readback","route":"setup","dependencies":["locations"],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"facility","name":"Facility number","required":true,"format":"integer 1–1000","example":"1"},{"id":"feature","name":"Selected feature ID","required":true,"format":"scheduling","example":"scheduling"},{"id":"function_key","name":"Function setting","required":true,"format":"scheduling.closures","example":"scheduling.closures"},{"id":"name","name":"Closure name","required":true,"format":"text","example":"Example closure"},{"id":"valid_from","name":"First closed date","required":true,"format":"YYYY-MM-DD","example":"2026-12-01"},{"id":"valid_to","name":"Last closed date","required":true,"format":"YYYY-MM-DD","example":"2026-12-01"},{"id":"start_time","name":"Closed from","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"Closed until","required":true,"format":"HH:MM","example":"17:00"},{"id":"location","name":"Room (blank closes the whole facility)","required":false,"format":"text","example":"Example Room"}],"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"id":"dataset_decisions","title":"Dataset completeness & exceptions","purpose":"Account setup review and product import evidence","route":"setup","dependencies":[],"acceptance":"Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.","columns":[{"id":"dataset_id","name":"Dataset identifier","required":true,"format":"text","example":"services"},{"id":"decision","name":"Decision","required":true,"format":"provided / not_applicable","example":"provided"},{"id":"reason","name":"Reason and approval","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/dataset_decisions.csv","example":"/implementation/examples/dataset_decisions.csv"},{"id":"rcm_organizations","title":"organizations","purpose":"Create the legal payer, insurer, administrator/TPA and provider counterparties that every downstream contract, policy, tariff and integration route names.","route":"register","dependencies":[],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"internal_code","name":"internal code","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"legal_name_ar","name":"legal name ar","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"legal_name_en","name":"legal name en","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"country_code","name":"country code","required":true,"format":"Source-backed value","example":"SA"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"commercial_registration","name":"commercial registration","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"tax_number","name":"tax number","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"license_number","name":"license number","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"parent_organization","name":"parent organization","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contact_directory","name":"contact directory","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_organizations.csv","example":"/implementation/examples/rcm_organizations.csv"},{"id":"rcm_insurer_roles","title":"insurer roles","purpose":"Mark which organization is the risk-bearing payer/insurer so policy, claim and settlement decisions do not infer that a TPA is the payer.","route":"register","dependencies":["rcm_organizations"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"organization","name":"organization","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"role","name":"role","required":true,"format":"Readiness condition: role=insurer","example":"insurer"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_scope","name":"network scope","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"notes","name":"notes","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_insurer_roles.csv","example":"/implementation/examples/rcm_insurer_roles.csv"},{"id":"rcm_tpa_roles","title":"tpa roles","purpose":"Declare delegated administrator/TPA roles when claims, eligibility, authorizations or portals are handled by an intermediary.","route":"register","dependencies":["rcm_organizations"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"organization","name":"organization","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"role","name":"role","required":true,"format":"Readiness condition: role=tpa","example":"tpa"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"portal_reference","name":"portal reference","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"escalation_matrix","name":"escalation matrix","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_tpa_roles.csv","example":"/implementation/examples/rcm_tpa_roles.csv"},{"id":"rcm_administration_agreements","title":"administration agreements","purpose":"Bind insurer-to-administrator delegation terms so routing and SLA ownership are explicit instead of inferred from names.","route":"register","dependencies":["rcm_insurer_roles","rcm_tpa_roles"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"insurer_org","name":"insurer org","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"administrator_org","name":"administrator org","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"claim_submission_deadline","name":"claim submission deadline","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"payment_sla","name":"payment sla","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"portal_url","name":"portal url","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"authorization_sla","name":"authorization sla","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"appeal_sla","name":"appeal sla","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contact_matrix","name":"contact matrix","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_administration_agreements.csv","example":"/implementation/examples/rcm_administration_agreements.csv"},{"id":"rcm_provider_contracts","title":"provider contracts","purpose":"Record the signed hospital-provider commercial contract that gives authority for allowed pricing, billing windows and settlement terms.","route":"register","dependencies":["rcm_organizations","rcm_insurer_roles"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"payer_or_insurer_org","name":"payer or insurer org","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"provider_facility","name":"provider facility","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contract_number","name":"contract number","required":true,"format":"Source-backed value","example":"EXAMPLE-CONTRACT-001"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"currency","name":"currency","required":true,"format":"Source-backed value","example":"SAR"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_tier","name":"network tier","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"claim_submission_deadline","name":"claim submission deadline","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"payment_terms","name":"payment terms","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"appeal_terms","name":"appeal terms","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_provider_contracts.csv","example":"/implementation/examples/rcm_provider_contracts.csv"},{"id":"rcm_insurance_products","title":"insurance products","purpose":"Define the insurer's commercial product/plan family before issued policies and classes inherit or override benefit rules.","route":"register","dependencies":["rcm_insurer_roles"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"insurer_org","name":"insurer org","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_code","name":"product code","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_name","name":"product name","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"jurisdiction","name":"jurisdiction","required":true,"format":"Source-backed value","example":"SA"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_type","name":"network type","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_category","name":"product category","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_insurance_products.csv","example":"/implementation/examples/rcm_insurance_products.csv"},{"id":"rcm_issued_policies","title":"issued policies","purpose":"Represent the actual policyholder/employer contract period, caps and endorsements that member coverages must point to.","route":"register","dependencies":["rcm_insurance_products"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"product","name":"product","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"policy_number","name":"policy number","required":true,"format":"Source-backed value","example":"EXAMPLE-POLICY"},{"id":"policyholder","name":"policyholder","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"effective_to","name":"effective to","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"global_policy_limit","name":"global policy limit","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"endorsement_reference","name":"endorsement reference","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"renewal_reference","name":"renewal reference","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-002"},{"id":"family_limit","name":"family limit","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-003"}],"template":"/implementation/templates/rcm_issued_policies.csv","example":"/implementation/examples/rcm_issued_policies.csv"},{"id":"rcm_benefit_classes","title":"benefit classes","purpose":"Create policy/class tiers such as VIP, A, B or Basic so benefits, limits and tariffs resolve at the correct insured class.","route":"register","dependencies":["rcm_insurance_products","rcm_issued_policies"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"product_or_policy","name":"product or policy","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"class_code","name":"class code","required":true,"format":"Source-backed value","example":"EXAMPLE-CLASS"},{"id":"class_name","name":"class name","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"rank","name":"rank","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"room_grade","name":"room grade","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"network_tier","name":"network tier","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"annual_limit","name":"annual limit","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"requires_referral","name":"requires referral","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_benefit_classes.csv","example":"/implementation/examples/rcm_benefit_classes.csv"},{"id":"rcm_benefit_rules","title":"benefit rules","purpose":"Load covered/uncovered services, copays, deductibles, coinsurance, authorization triggers, limits, exclusions and overrides.","route":"register","dependencies":["rcm_benefit_classes"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"benefit_class_or_policy_scope","name":"benefit class or policy scope","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"service_code_or_group","name":"service code or group","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"coverage_decision","name":"coverage decision","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"cost_share_rule","name":"cost share rule","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"authorization_required","name":"authorization required","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"limit_scope","name":"limit scope","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"limit_amount","name":"limit amount","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"frequency_limit","name":"frequency limit","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"diagnosis_restrictions","name":"diagnosis restrictions","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"network_restrictions","name":"network restrictions","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"exclusion_reason","name":"exclusion reason","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_benefit_rules.csv","example":"/implementation/examples/rcm_benefit_rules.csv"},{"id":"rcm_tariffs","title":"tariffs","purpose":"Define payer allowed-price lists separately from the hospital gross charge master so live invoices cannot confuse gross and allowed price.","route":"register","dependencies":["rcm_provider_contracts"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"tariff_code","name":"tariff code","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"tariff_name","name":"tariff name","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"currency","name":"currency","required":true,"format":"Source-backed value","example":"SAR"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"line_items","name":"line items","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"unit_basis","name":"unit basis","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"package_rules","name":"package rules","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"drug_markup_rules","name":"drug markup rules","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"rounding_rules","name":"rounding rules","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_tariffs.csv","example":"/implementation/examples/rcm_tariffs.csv"},{"id":"rcm_tariff_assignments","title":"tariff assignments","purpose":"Bind a contract/class/site/date context to exactly one applicable tariff precedence path.","route":"register","dependencies":["rcm_provider_contracts","rcm_benefit_classes","rcm_tariffs"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"provider_contract","name":"provider contract","required":true,"format":"Source-backed value","example":"EXAMPLE-CONTRACT-001"},{"id":"tariff","name":"tariff","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"priority","name":"priority","required":true,"format":"Source-backed value","example":"1"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"evidence state","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"facility_site","name":"facility site","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"department","name":"department","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"benefit_class","name":"benefit class","required":false,"format":"Source-backed value","example":"EXAMPLE-CLASS"},{"id":"network_tier","name":"network tier","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_tariff_assignments.csv","example":"/implementation/examples/rcm_tariff_assignments.csv"},{"id":"rcm_nphies_configurations","title":"nphies configurations","purpose":"Store facility identifiers, certified package pins and live-submission permission for the national NPHIES exchange.","route":"register","dependencies":["rcm_production_endpoints","rcm_production_routing_rules"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"facility_identifier","name":"facility identifier","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"environment","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"certification_status","name":"certification status","required":true,"format":"Readiness condition: certification_status=certified","example":"not_started"},{"id":"package_pin","name":"package pin","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"allow_live_submission","name":"allow live submission","required":true,"format":"Readiness condition: allow_live_submission=true","example":"false"},{"id":"onboarding_reference","name":"onboarding reference","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"certification_expiry","name":"certification expiry","required":false,"format":"Source-backed value","example":""},{"id":"notes","name":"notes","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_nphies_configurations.csv","example":"/implementation/examples/rcm_nphies_configurations.csv"},{"id":"rcm_production_endpoints","title":"production endpoints","purpose":"Configure the production integration endpoint and secret references without storing raw credentials in configuration rows.","route":"register","dependencies":["rcm_organizations"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"label","name":"label","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"environment","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"endpoint_url","name":"endpoint url","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"secret_reference","name":"secret reference","required":true,"format":"Source-backed value","example":"EXAMPLE-SECRET-REF-001"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"timeout_seconds","name":"timeout seconds","required":false,"format":"Source-backed value","example":""},{"id":"mtls_profile","name":"mtls profile","required":false,"format":"Readiness condition: mTLS_profile","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_production_endpoints.csv","example":"/implementation/examples/rcm_production_endpoints.csv"},{"id":"rcm_production_routing_rules","title":"production routing rules","purpose":"Map production eligibility, prior authorization, claim and payment transactions to the correct endpoint and payer/administrator route.","route":"register","dependencies":["rcm_production_endpoints","rcm_administration_agreements"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"transaction_type","name":"transaction type","required":true,"format":"Readiness condition: transaction_type in eligibility/prior_authorization/claim/payment","example":"claim"},{"id":"environment","name":"environment","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"endpoint","name":"endpoint","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"priority","name":"priority","required":true,"format":"Source-backed value","example":"1"},{"id":"effective_from","name":"effective from","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"payer_scope","name":"payer scope","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"retry_policy","name":"retry policy","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"fallback_queue","name":"fallback queue","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_production_routing_rules.csv","example":"/implementation/examples/rcm_production_routing_rules.csv"},{"id":"rcm_zatca_onboardings","title":"zatca onboardings","purpose":"Bind each legal taxpayer to ZATCA solution certificate and CSID secret references for legal invoice clearance/reporting.","route":"register","dependencies":["rcm_organizations"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"taxpayer_organization","name":"taxpayer organization","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"vat_registration_number","name":"vat registration number","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"environment","required":true,"format":"Readiness condition: environment=production","example":"TO-CONFIRM"},{"id":"solution_certificate_reference","name":"solution certificate reference","required":true,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"csid_secret_reference","name":"csid secret reference","required":true,"format":"Source-backed value","example":"EXAMPLE-SECRET-REF-001"},{"id":"status","name":"status","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"effective to","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"invoice_type_scope","name":"invoice type scope","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"phase_wave_reference","name":"phase wave reference","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-002"},{"id":"clearance_endpoint","name":"clearance endpoint","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"reporting_endpoint","name":"reporting endpoint","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-003"}],"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"id":"rcm_networks","title":"Provider networks & participation","purpose":"Record network participation, exclusions and effective periods before coverage is used.","route":"register","dependencies":["rcm_provider_contracts"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"network_code","name":"Network code","required":true,"format":"text","example":"EXAMPLE-NETWORK"},{"id":"provider_identifier","name":"Provider legal identifier","required":true,"format":"text","example":"EXAMPLE-PROVIDER"},{"id":"network_tier","name":"Network tier","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"effective_from","name":"Effective from","required":true,"format":"YYYY-MM-DD","example":"2026-10-10"},{"id":"effective_to","name":"Effective to","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"contract_reference","name":"Approved contract","required":true,"format":"text","example":"EXAMPLE-CONTRACT-001"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_networks.csv","example":"/implementation/examples/rcm_networks.csv"},{"id":"rcm_member_coverage","title":"Member coverage mapping","purpose":"Prepare coverage mappings using synthetic references here; actual member identities belong in the approved secure migration route.","route":"register","dependencies":["rcm_issued_policies","rcm_benefit_classes","rcm_networks"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"source_member_reference","name":"Source member reference","required":true,"format":"text; no patient identifiers in public examples","example":"EXAMPLE-MEMBER"},{"id":"policy_reference","name":"Issued policy reference","required":true,"format":"text","example":"EXAMPLE-POLICY"},{"id":"benefit_class_reference","name":"Benefit class","required":true,"format":"text","example":"EXAMPLE-CLASS"},{"id":"network_code","name":"Network code","required":true,"format":"text","example":"EXAMPLE-NETWORK"},{"id":"effective_from","name":"Effective from","required":true,"format":"YYYY-MM-DD","example":"2026-10-10"},{"id":"effective_to","name":"Effective to","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"identity_mapping_reference","name":"Secure identity mapping reference","required":true,"format":"text; secure workspace reference","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_member_coverage.csv","example":"/implementation/examples/rcm_member_coverage.csv"},{"id":"rcm_rule_publications","title":"Rules, exceptions & publication","purpose":"Review rule precedence, exceptions and test evidence before immutable publication by authorized owners.","route":"register","dependencies":["rcm_benefit_rules","rcm_tariff_assignments","uat_cases"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"rule_reference","name":"Rule reference","required":true,"format":"text","example":"EXAMPLE-RULE"},{"id":"rule_release","name":"Rule release","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"precedence","name":"Rule precedence","required":true,"format":"integer","example":"1"},{"id":"eligibility_condition","name":"Eligibility condition","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"exclusion","name":"Exclusion / reason","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"limit_or_copay","name":"Limit / deductible / copay","required":true,"format":"text; specify amount, unit and currency","example":"TO-CONFIRM"},{"id":"test_case_reference","name":"Test case","required":true,"format":"text","example":"EXAMPLE-UAT"},{"id":"maker_reference","name":"Prepared by","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"checker_reference","name":"Independent approval","required":true,"format":"text","example":"EXAMPLE-REF-002"},{"id":"evidence_reference","name":"Activation evidence","required":true,"format":"text","example":"EXAMPLE-REF-003"},{"id":"publication_status","name":"Publication status","required":true,"format":"draft / reviewed / approved / blocked","example":"draft"}],"template":"/implementation/templates/rcm_rule_publications.csv","example":"/implementation/examples/rcm_rule_publications.csv"},{"id":"rcm_financial_controls","title":"Revenue & reconciliation controls","purpose":"Reconcile normal, denied, partially paid, reversed and unmatched activity with explicit finance ownership.","route":"register","dependencies":["service_billing","rcm_provider_contracts","uat_cases"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"control_code","name":"Control code","required":true,"format":"text","example":"EXAMPLE-FIN-01"},{"id":"transaction_type","name":"Transaction type","required":true,"format":"charge / invoice / claim / remittance / reversal / refund / write_off","example":"claim"},{"id":"currency","name":"Currency","required":true,"format":"ISO 4217","example":"SAR"},{"id":"source_total","name":"Expected source total","required":true,"format":"decimal","example":"1000.00"},{"id":"target_total","name":"Observed target total","required":true,"format":"decimal","example":"1000.00"},{"id":"tolerance","name":"Approved tolerance","required":true,"format":"decimal; do not assume a tolerance","example":"0.00"},{"id":"exception_route","name":"Exception queue / owner","required":true,"format":"text","example":"Finance review"},{"id":"evidence_reference","name":"Reconciliation evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"id":"project_scope","title":"Project scope","purpose":"Freeze products, versions, facilities, delivery mode and acceptance scope.","route":"register","dependencies":[],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"product_id","name":"Catalogue product ID","required":true,"format":"text","example":"outpatient"},{"id":"release","name":"Agreed release","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"mode","name":"Operating mode","required":true,"format":"native / connected","example":"native"},{"id":"facility_scope","name":"Facility scope","required":true,"format":"text","example":"all"},{"id":"included","name":"Included in this project","required":true,"format":"true / false","example":"true"},{"id":"owner_role","name":"Accountable role","required":true,"format":"text","example":"Project owner"},{"id":"acceptance_test","name":"Acceptance evidence","required":true,"format":"text","example":"Approved end-to-end test"},{"id":"approval_reference","name":"Approval reference","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/project_scope.csv","example":"/implementation/examples/project_scope.csv"},{"id":"assumptions_decisions","title":"Assumptions & decisions","purpose":"Keep each unresolved assumption visible with an owner and closure test.","route":"register","dependencies":["project_scope"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"decision_id","name":"Decision ID","required":true,"format":"text","example":"DEC-001"},{"id":"topic","name":"Topic","required":true,"format":"text","example":"Legacy records"},{"id":"assumption","name":"Proposed assumption","required":true,"format":"text","example":"No historical patient import until approved"},{"id":"status","name":"Status","required":true,"format":"proposed / approved / rejected / open","example":"proposed"},{"id":"owner_role","name":"Decision owner","required":true,"format":"text","example":"Data owner"},{"id":"evidence_reference","name":"Evidence reference","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"impact_if_wrong","name":"Impact if wrong","required":true,"format":"text","example":"Migration scope must change"},{"id":"closure_test","name":"Closure test","required":true,"format":"text","example":"Source inventory approved"}],"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"id":"access_matrix","title":"Access & approvals","purpose":"Map roles to permitted actions and verify access across facility boundaries.","route":"register","dependencies":["facilities","staff"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"role","name":"Role","required":true,"format":"text","example":"doctor"},{"id":"facility_scope","name":"Facility scope","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"resource","name":"Resource","required":true,"format":"text","example":"Patient record"},{"id":"action","name":"Action","required":true,"format":"text","example":"read"},{"id":"allowed","name":"Allowed","required":true,"format":"true / false","example":"true"},{"id":"approver_role","name":"Approver","required":true,"format":"text","example":"Security owner"},{"id":"evidence_reference","name":"Test evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"id":"service_catalogue","title":"Service catalogue","purpose":"Define services and approved code mappings before orders, tariffs and interfaces.","route":"migration","dependencies":["departments"],"acceptance":"Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.","columns":[{"id":"service_code","name":"Local service code","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"name_en","name":"English name","required":true,"format":"text","example":"Example service"},{"id":"name_ar","name":"Arabic name","required":true,"format":"text","example":"خدمة تدريبية"},{"id":"department_code","name":"Department code","required":true,"format":"text","example":"EXAMPLE-DEPT-001"},{"id":"unit","name":"Unit of service","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"code_system","name":"Code system","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"release","name":"Catalogue release","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"external_code","name":"Approved external mapping","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"effective_from","name":"Effective from","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"}],"template":"/implementation/templates/service_catalogue.csv","example":"/implementation/examples/service_catalogue.csv"},{"id":"medication_catalogue","title":"Medication catalogue","purpose":"Pharmacy-approved catalogue. Example records are for training and contain no dose advice.","route":"migration","dependencies":["service_catalogue"],"acceptance":"Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.","columns":[{"id":"item_code","name":"Item code","required":true,"format":"text","example":"EXAMPLE-MED-001"},{"id":"name","name":"Display name","required":true,"format":"text","example":"Training medication only"},{"id":"code_system","name":"Code system","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"code","name":"Approved code","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"strength","name":"Strength with unit","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"form","name":"Dosage form","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"stock_unit","name":"Stock unit","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"dispense_unit","name":"Dispense unit","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"conversion_factor","name":"Approved unit conversion","required":true,"format":"decimal","example":"1"},{"id":"release","name":"Terminology release","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"id":"inventory_opening","title":"Opening inventory","purpose":"Load a signed stock count at a defined cutover time. Confirm whether zero cost is real before approval.","route":"migration","dependencies":["medication_catalogue"],"acceptance":"Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.","columns":[{"id":"item_code","name":"Item code","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"store_code","name":"Store code","required":true,"format":"text","example":"EXAMPLE-STORE-001"},{"id":"lot_number","name":"Lot number","required":true,"format":"text","example":"EXAMPLE-LOT-001"},{"id":"expiry_date","name":"Expiry date","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"quantity","name":"Opening quantity","required":true,"format":"decimal","example":"10"},{"id":"unit","name":"Stock unit","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"unit_cost","name":"Approved unit cost","required":true,"format":"decimal","example":"0"},{"id":"currency","name":"Currency","required":true,"format":"ISO 4217","example":"SAR"},{"id":"as_of","name":"Count timestamp","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T08:00:00+03:00"},{"id":"approval_reference","name":"Count approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/inventory_opening.csv","example":"/implementation/examples/inventory_opening.csv"},{"id":"clinical_workflows","title":"Clinical workflow configuration","purpose":"Record locally approved pathways, responsibilities and exception handling.","route":"register","dependencies":["departments","access_matrix"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"workflow_id","name":"Workflow ID","required":true,"format":"text","example":"EXAMPLE-WF-001"},{"id":"product_id","name":"Product ID","required":true,"format":"text","example":"outpatient"},{"id":"entry_event","name":"Entry event","required":true,"format":"text","example":"Patient arrival"},{"id":"responsible_role","name":"Responsible role","required":true,"format":"text","example":"Nurse"},{"id":"required_information","name":"Required information","required":true,"format":"text","example":"Verified identity and visit context"},{"id":"next_event","name":"Next event","required":true,"format":"text","example":"Clinical consultation"},{"id":"handover_owner","name":"Handover owner","required":true,"format":"text","example":"Doctor"},{"id":"exception_path","name":"Exception path","required":true,"format":"text","example":"Identity mismatch to review"},{"id":"approval_reference","name":"Workflow approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"id":"scheduling","title":"Scheduling configuration","purpose":"Plan resource availability, overlap rules, closures and time zone handling.","route":"register","dependencies":["operations","locations","staff"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"schedule_id","name":"Schedule ID","required":true,"format":"text","example":"EXAMPLE-SCH-001"},{"id":"facility_number","name":"Facility number","required":true,"format":"integer","example":"1"},{"id":"department_name","name":"Department","required":true,"format":"text","example":"Example Department"},{"id":"resource_name","name":"Staff or room","required":true,"format":"text","example":"Example Room"},{"id":"weekday","name":"Weekday","required":true,"format":"sun / mon / tue / wed / thu / fri / sat","example":"sun"},{"id":"start_time","name":"Start time","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"End time","required":true,"format":"HH:MM","example":"17:00"},{"id":"slot_minutes","name":"Slot duration","required":true,"format":"integer minutes","example":"15"},{"id":"timezone","name":"Time zone","required":true,"format":"IANA time zone","example":"Asia/Riyadh"},{"id":"approval_reference","name":"Scheduling approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"id":"interfaces","title":"Interface specification","purpose":"Define the agreed message contract. Store references to credentials, never the credentials themselves.","route":"register","dependencies":["facilities","service_catalogue","source_systems"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"EXAMPLE-IF-001"},{"id":"source_system","name":"Source system","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"target_system","name":"Target system","required":true,"format":"text","example":"MANSOQ"},{"id":"direction","name":"Direction","required":true,"format":"inbound / outbound / bidirectional","example":"inbound"},{"id":"protocol_version","name":"Protocol and version","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"message_scope","name":"Message scope","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"identifier_mapping","name":"Identifier mapping","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"secret_reference","name":"Secret manager reference","required":true,"format":"text","example":"REFERENCE-ONLY"},{"id":"retry_policy","name":"Retry and duplicate policy","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"failure_owner","name":"Failure owner","required":true,"format":"text","example":"Integration owner"},{"id":"test_reference","name":"Test evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"id":"migration_mapping","title":"Migration mapping","purpose":"Approve target fields, transformations and merge rules against the exact application release.","route":"register","dependencies":["project_scope"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"dataset","name":"Dataset","required":true,"format":"text","example":"Patient master"},{"id":"source_field","name":"Source field","required":true,"format":"text","example":"Legacy identifier"},{"id":"target_field","name":"Target field","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"transformation","name":"Transformation","required":true,"format":"text","example":"Preserve as text"},{"id":"identifier_system","name":"Identifier system","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"required","name":"Required","required":true,"format":"true / false","example":"true"},{"id":"null_policy","name":"Null policy","required":true,"format":"text","example":"Reject missing required ID"},{"id":"dedup_key","name":"Duplicate key","required":true,"format":"text","example":"Source system + identifier"},{"id":"validation","name":"Validation rule","required":true,"format":"text","example":"No duplicate source keys"},{"id":"approval_reference","name":"Mapping approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/migration_mapping.csv","example":"/implementation/examples/migration_mapping.csv"},{"id":"migration_batches","title":"Migration batch log","purpose":"Reconcile records and monetary or quantity totals, including rejects. Zero example counts do not mean a migration is complete.","route":"register","dependencies":["migration_mapping"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"batch_id","name":"Batch ID","required":true,"format":"text","example":"EXAMPLE-BATCH-001"},{"id":"dataset","name":"Dataset","required":true,"format":"text","example":"Patient master"},{"id":"file_hash","name":"SHA-256 file hash","required":true,"format":"64 hex characters","example":"2825f4a89ff1b4df487b710b7af407ee007bf4b0213bf09a77352937d8c5b34c"},{"id":"source_count","name":"Source records","required":true,"format":"integer","example":"0"},{"id":"accepted_count","name":"Accepted records","required":true,"format":"integer","example":"0"},{"id":"rejected_count","name":"Rejected records","required":true,"format":"integer","example":"0"},{"id":"control_total","name":"Financial or stock total","required":true,"format":"decimal","example":"0"},{"id":"status","name":"Status","required":true,"format":"staged / validated / loaded / reconciled / rolled_back","example":"staged"},{"id":"rollback_reference","name":"Rollback evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"Batch approval","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/migration_batches.csv","example":"/implementation/examples/migration_batches.csv"},{"id":"uat_cases","title":"Acceptance tests","purpose":"Record complete positive, negative, boundary, access and failure tests per product.","route":"register","dependencies":["project_scope","clinical_workflows"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"test_id","name":"Test ID","required":true,"format":"text","example":"UAT-001"},{"id":"product_id","name":"Product ID","required":true,"format":"text","example":"outpatient"},{"id":"scenario","name":"Scenario","required":true,"format":"text","example":"Visit from arrival to financial follow-up"},{"id":"preconditions","name":"Preconditions","required":true,"format":"text","example":"Approved setup and synthetic data"},{"id":"actions","name":"Exact actions","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"expected_result","name":"Expected result","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"actual_result","name":"Actual result","required":true,"format":"text","example":"NOT-RUN"},{"id":"status","name":"Status","required":true,"format":"not_run / pass / fail / blocked","example":"not_run"},{"id":"evidence_reference","name":"Evidence reference","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approver_role","name":"Approver","required":true,"format":"text","example":"Product owner"}],"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"},{"id":"training","title":"Training & competency","purpose":"Verify that each role can perform normal work, exceptions and downtime tasks.","route":"register","dependencies":["clinical_workflows","uat_cases"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"role","name":"Role","required":true,"format":"text","example":"Nurse"},{"id":"workflow","name":"Workflow","required":true,"format":"text","example":"Patient registration"},{"id":"trainer_role","name":"Trainer","required":true,"format":"text","example":"Superuser"},{"id":"session_date","name":"Session date","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"attendees_reference","name":"Attendance evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"competency_test","name":"Competency test","required":true,"format":"text","example":"Complete a synthetic visit"},{"id":"result","name":"Result","required":true,"format":"not_run / pass / fail","example":"not_run"},{"id":"follow_up","name":"Follow-up","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/training.csv","example":"/implementation/examples/training.csv"},{"id":"cutover_runbook","title":"Cutover & rollback","purpose":"Assign every cutover action, hold point, decision owner and tested rollback path.","route":"register","dependencies":["uat_cases","migration_batches","training"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"sequence","name":"Sequence","required":true,"format":"integer","example":"1"},{"id":"action","name":"Action","required":true,"format":"text","example":"Confirm the change window"},{"id":"owner_role","name":"Owner","required":true,"format":"text","example":"Project owner"},{"id":"dependency","name":"Dependency","required":false,"format":"text","example":""},{"id":"planned_time","name":"Planned time","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T20:00:00+03:00"},{"id":"verification","name":"Verification","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"rollback_trigger","name":"Rollback trigger","required":true,"format":"text","example":"Critical acceptance failure"},{"id":"rollback_action","name":"Rollback action","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"approval_reference","name":"Approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/cutover_runbook.csv","example":"/implementation/examples/cutover_runbook.csv"},{"id":"support_handover","title":"Support handover","purpose":"Document ownership, customer-declared support targets, restore tests and certificate renewals. These values are your own declarations and are never a MANSOQ service level.","route":"register","dependencies":["cutover_runbook"],"acceptance":"Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.","columns":[{"id":"service","name":"Service","required":true,"format":"text","example":"MANSOQ application"},{"id":"owner_role","name":"Owner","required":true,"format":"text","example":"Support lead"},{"id":"support_hours","name":"Customer-declared support hours","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"severity","name":"Customer-declared severity","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"response_target","name":"Customer-declared response target","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"escalation_route","name":"Customer-declared escalation route","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"monitoring_reference","name":"Monitoring evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"restore_test_reference","name":"Restore test","required":true,"format":"text","example":"EXAMPLE-REF-002"},{"id":"renewal_owner","name":"Certificate or license owner","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/support_handover.csv","example":"/implementation/examples/support_handover.csv"},{"id":"source_systems","title":"Existing systems & versions","purpose":"Inventory every source EHR, department system, archive and ERP separately, including the exact installed product and licensed extraction route.","route":"register","dependencies":["project_scope"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"system_id","name":"System ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"vendor","name":"Vendor","required":true,"format":"text","example":"Epic"},{"id":"product","name":"Installed product","required":true,"format":"text","example":"Epic EHR"},{"id":"release","name":"Installed release","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"environment","name":"Environment","required":true,"format":"test / production / archive","example":"test"},{"id":"facility_scope","name":"Facilities covered","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"source_owner","name":"Source administrator role","required":true,"format":"text","example":"Source EHR administrator"},{"id":"export_route","name":"Approved extraction route","required":true,"format":"text","example":"EHI export assessment pending"},{"id":"licence_reference","name":"Licence/access evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"specification_reference","name":"Release-specific specification","required":true,"format":"text","example":"https://open.epic.com/TechnicalSpecifications"}],"template":"/implementation/templates/source_systems.csv","example":"/implementation/examples/source_systems.csv"},{"id":"transition_scope","title":"Migration or coexistence scope","purpose":"Choose the action and decide the system of record for every included data domain, facility and period.","route":"register","dependencies":["source_systems"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"scope_id","name":"Scope ID","required":true,"format":"text","example":"SCOPE-001"},{"id":"system_id","name":"Source system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"action","name":"Transition action","required":true,"format":"migration / integration / phased / consolidation / archive / carve_out / exit / recovery","example":"migration"},{"id":"data_domain","name":"Data domain","required":true,"format":"text","example":"Appointments"},{"id":"facility_scope","name":"Facility boundary","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"history_from","name":"History start date","required":true,"format":"YYYY-MM-DD","example":"2020-01-01"},{"id":"history_to","name":"History end date","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"target_disposition","name":"Destination","required":true,"format":"native / connected / archive / excluded","example":"native"},{"id":"system_of_record","name":"Authoritative system after cutover","required":true,"format":"text","example":"MANSOQ after acceptance"},{"id":"reason","name":"Inclusion or exclusion reason","required":true,"format":"text","example":"Future appointment continuity"},{"id":"approval_reference","name":"Scope approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/transition_scope.csv","example":"/implementation/examples/transition_scope.csv"},{"id":"export_inventory","title":"Export files & checksums","purpose":"Register every vendor export file, attachment bundle and image batch without uploading its patient content to account setup.","route":"migration","dependencies":["transition_scope"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"export_id","name":"Export ID","required":true,"format":"text","example":"EXPORT-001"},{"id":"system_id","name":"Source system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope_id","name":"Scope ID","required":true,"format":"text","example":"SCOPE-001"},{"id":"format","name":"Actual format","required":true,"format":"CSV / TSV / NDJSON / XML / DICOM / PDF / native / other","example":"TSV"},{"id":"secure_file_reference","name":"Secure file reference","required":true,"format":"text","example":"secure-workspace://EXAMPLE/export-001"},{"id":"sha256","name":"File SHA-256","required":true,"format":"64 hex characters","example":"390a3d2a42b21012c44c65170f00cb0129db59d9b4b9e67193e195fa81c1bd09"},{"id":"expected_records","name":"Source record/object count","required":true,"format":"integer","example":"120"},{"id":"extracted_at","name":"Extraction timestamp","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T18:00:00+03:00"},{"id":"dictionary_reference","name":"Export dictionary","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"transfer_approval","name":"Transfer approval","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/export_inventory.csv","example":"/implementation/examples/export_inventory.csv"},{"id":"identity_rules","title":"Patient matching rules","purpose":"Define matching policy and a secure crosswalk schema. Actual identifiers and patient-level mappings belong in the restricted migration workspace.","route":"migration","dependencies":["source_systems","transition_scope"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"rule_id","name":"Matching rule ID","required":true,"format":"text","example":"MATCH-001"},{"id":"system_id","name":"Source system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"identifier_namespace","name":"Identifier namespace","required":true,"format":"text","example":"EXAMPLE-HOSPITAL-MRN"},{"id":"match_method","name":"Matching method","required":true,"format":"verified_identifier / reviewed_crosswalk / manual_review","example":"verified_identifier"},{"id":"normalization_rule","name":"Normalization rule","required":true,"format":"text","example":"Preserve original; compare approved canonical form"},{"id":"exception_policy","name":"Ambiguous/missing identity handling","required":true,"format":"text","example":"Quarantine and refer to identity steward"},{"id":"crosswalk_reference","name":"Secure crosswalk reference","required":true,"format":"text","example":"secure-workspace://EXAMPLE/crosswalk-schema"},{"id":"approver_role","name":"Identity steward","required":true,"format":"text","example":"Health information management"},{"id":"acceptance_reference","name":"Matching evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/identity_rules.csv","example":"/implementation/examples/identity_rules.csv"},{"id":"terminology_mapping","title":"Terminology & unit mappings","purpose":"Map local codes, terminology releases, units and missing values without inventing clinical meaning.","route":"migration","dependencies":["transition_scope","service_catalogue"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"mapping_id","name":"Mapping ID","required":true,"format":"text","example":"MAP-TERM-001"},{"id":"system_id","name":"Source system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"domain","name":"Domain","required":true,"format":"text","example":"Laboratory result"},{"id":"source_system","name":"Source code system","required":true,"format":"text","example":"EXAMPLE-LOCAL-LAB"},{"id":"source_code","name":"Source code","required":true,"format":"text","example":"EXAMPLE-LAB-001"},{"id":"target_system","name":"Target code system","required":false,"format":"text","example":""},{"id":"target_code","name":"Target code","required":false,"format":"text","example":""},{"id":"equivalence","name":"Equivalence","required":true,"format":"exact / broader / narrower / unmapped","example":"unmapped"},{"id":"unit_rule","name":"Unit or conversion rule","required":true,"format":"text","example":"No conversion until laboratory approval"},{"id":"approval_reference","name":"Terminology approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/terminology_mapping.csv","example":"/implementation/examples/terminology_mapping.csv"},{"id":"data_reconciliation","title":"Migration reconciliation","purpose":"Prove completeness, identify rejected records and reconcile clinical, image, appointment and financial totals.","route":"migration","dependencies":["export_inventory","migration_batches"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"check_id","name":"Check ID","required":true,"format":"text","example":"REC-001"},{"id":"scope_id","name":"Scope ID","required":true,"format":"text","example":"SCOPE-001"},{"id":"batch_id","name":"Migration batch ID","required":true,"format":"text","example":"EXAMPLE-BATCH-001"},{"id":"measure","name":"Reconciliation measure","required":true,"format":"text","example":"Future appointment count"},{"id":"source_value","name":"Source total","required":true,"format":"decimal","example":"120"},{"id":"target_value","name":"Target total","required":true,"format":"decimal","example":"118"},{"id":"held_or_rejected","name":"Held/rejected total","required":true,"format":"decimal","example":"2"},{"id":"tolerance","name":"Approved tolerance","required":true,"format":"decimal","example":"0"},{"id":"status","name":"Review status","required":true,"format":"open / passed / failed / waived","example":"open"},{"id":"evidence_reference","name":"Report/evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/data_reconciliation.csv","example":"/implementation/examples/data_reconciliation.csv"},{"id":"integration_scopes","title":"Integration scope & ownership","purpose":"Declare only the selected domains, direction, cadence, authoritative writer and operations owner.","route":"register","dependencies":["source_systems","transition_scope"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"IFACE-001"},{"id":"system_id","name":"Existing system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope","name":"Integration scope","required":true,"format":"identity_adt / clinical_read / orders_results / medications / appointments / revenue / imaging_devices / finance_inventory / sso","example":"orders_results"},{"id":"direction","name":"Direction","required":true,"format":"inbound / outbound / bidirectional","example":"inbound"},{"id":"cadence","name":"Delivery pattern","required":true,"format":"event / scheduled / on_demand","example":"event"},{"id":"system_of_record","name":"Authoritative writer","required":true,"format":"text","example":"Existing EHR owns orders; MANSOQ reviews results"},{"id":"owner_role","name":"Integration operations owner","required":true,"format":"text","example":"Integration operations"},{"id":"approval_reference","name":"Scope approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/integration_scopes.csv","example":"/implementation/examples/integration_scopes.csv"},{"id":"interface_contracts","title":"Interface contracts","purpose":"Capture release-specific protocol, events, acknowledgements, conflict rules and operational limits before building an adapter.","route":"register","dependencies":["integration_scopes"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"IFACE-001"},{"id":"protocol","name":"Protocol/profile","required":true,"format":"text","example":"HL7 v2.5.1 ORU assessment pending"},{"id":"specification_reference","name":"Specification reference","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"acknowledgement_rule","name":"Acknowledgement rule","required":true,"format":"text","example":"Application acceptance before completed status"},{"id":"deduplication_rule","name":"Replay/idempotency rule","required":true,"format":"text","example":"Source event ID plus version; retain processed receipt"},{"id":"conflict_rule","name":"Conflict/correction rule","required":true,"format":"text","example":"Source owns result corrections; quarantine identity conflicts"},{"id":"retry_limit","name":"Automatic retry limit","required":true,"format":"integer","example":"3"},{"id":"latency_target","name":"Agreed delivery target","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"downtime_route","name":"Downtime and replay route","required":true,"format":"text","example":"Documented downtime queue; replay after owner review"},{"id":"approval_reference","name":"Contract approval","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/interface_contracts.csv","example":"/implementation/examples/interface_contracts.csv"},{"id":"endpoint_access","title":"Endpoint access register","purpose":"Record endpoint ownership, secure credential references, access scopes, rotation and network approvals without storing secrets.","route":"register","dependencies":["interface_contracts"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"IFACE-001"},{"id":"environment","name":"Environment","required":true,"format":"test / production","example":"test"},{"id":"endpoint_reference","name":"Endpoint reference","required":true,"format":"text","example":"EXAMPLE-ENDPOINT-REF-001"},{"id":"auth_method","name":"Authentication method","required":true,"format":"text","example":"vendor-approved-oauth"},{"id":"credential_reference","name":"Credential-manager reference","required":true,"format":"text","example":"EXAMPLE-SECRET-REF-001"},{"id":"access_scope","name":"Granted scopes/actions","required":true,"format":"text","example":"Test-only read scope pending approval"},{"id":"network_approval","name":"Network/TLS evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"rotation_owner","name":"Rotation owner","required":true,"format":"text","example":"Security operations"},{"id":"approval_reference","name":"Access approval","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/endpoint_access.csv","example":"/implementation/examples/endpoint_access.csv"},{"id":"message_mapping","title":"Event & field mapping","purpose":"Map individual source fields and events to verified target operations with validation and rejected-data behavior.","route":"register","dependencies":["interface_contracts","terminology_mapping"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"IFACE-001"},{"id":"event","name":"Event/resource","required":true,"format":"text","example":"Result update"},{"id":"source_path","name":"Source field/path","required":true,"format":"text","example":"EXAMPLE-source-result-code"},{"id":"target_path","name":"Verified target field/action","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"transform_rule","name":"Transform/validation rule","required":true,"format":"text","example":"Approved code and unit mapping; preserve source value"},{"id":"required","name":"Required field","required":true,"format":"true / false","example":"true"},{"id":"rejection_route","name":"Invalid-data handling","required":true,"format":"text","example":"Quarantine; notify interface owner; no clinical write"},{"id":"approval_reference","name":"Mapping approval","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/message_mapping.csv","example":"/implementation/examples/message_mapping.csv"},{"id":"interface_tests","title":"Interface acceptance tests","purpose":"Test valid, denied, corrected, duplicated, delayed, failed and recovered events for each selected integration.","route":"register","dependencies":["message_mapping","endpoint_access"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"test_id","name":"Test ID","required":true,"format":"text","example":"IF-TEST-001"},{"id":"interface_id","name":"Interface ID","required":true,"format":"text","example":"IFACE-001"},{"id":"scenario","name":"Scenario","required":true,"format":"text","example":"Duplicate corrected laboratory result"},{"id":"fixture_reference","name":"Synthetic test fixture","required":true,"format":"text","example":"secure-test://EXAMPLE/corrected-result"},{"id":"expected","name":"Expected behavior","required":true,"format":"text","example":"One corrected result; no duplicate charge; receipt logged"},{"id":"status","name":"Execution status","required":true,"format":"not_run / passed / failed / blocked","example":"not_run"},{"id":"evidence_reference","name":"Test evidence","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"owner_role","name":"Test owner","required":true,"format":"text","example":"Clinical and integration owners"}],"template":"/implementation/templates/interface_tests.csv","example":"/implementation/examples/interface_tests.csv"},{"id":"archive_retention","title":"Archive, retention & exit","purpose":"Keep approved access to excluded history and define contractual retention, restoration, exit and decommission conditions.","route":"register","dependencies":["transition_scope","data_reconciliation"],"acceptance":"Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.","columns":[{"id":"archive_id","name":"Archive ID","required":true,"format":"text","example":"ARCH-001"},{"id":"system_id","name":"Source system ID","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope_id","name":"Scope ID","required":true,"format":"text","example":"SCOPE-001"},{"id":"retention_rule","name":"Approved retention rule","required":true,"format":"text","example":"TO-CONFIRM by records/privacy owner"},{"id":"access_rule","name":"Read-only access rule","required":true,"format":"text","example":"Approved care team access with audit"},{"id":"restore_test_reference","name":"Archive retrieval/restore test","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"exit_format","name":"Exit package format","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"decommission_gate","name":"Decommission gate","required":true,"format":"text","example":"Acceptance, legal hold review and archive access approved"},{"id":"owner_role","name":"Archive owner","required":true,"format":"text","example":"Records and privacy owners"},{"id":"approval_reference","name":"Archive/exit approval","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/archive_retention.csv","example":"/implementation/examples/archive_retention.csv"}]}},"ar":{"url":"https://mansoq.com/resources/implementation?lang=ar","title":"دليل تنفيذ أنظمة الرعاية وإعداد CSV | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"اتفق على النطاق التشغيلي وجهز البيانات والاتصالات وجرب العمل وأكد مسؤوليات الإطلاق.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اتفق على النطاق التشغيلي وجهز البيانات والاتصالات وجرب العمل وأكد مسؤوليات الإطلاق.","description":"إعداد حسابات منسوق ومنتجاته بقوالب CSV وأمثلة البيانات ودليل الحقول والتحقق. الترحيل والتكامل والاختبارات والتحويل والدعم.","answers":[{"question":"كيف أنفذ منسوق من إعداد الحساب إلى التشغيل؟","answer":"اتفق على المنتجات والإصدار والمنشآت وحدود البيانات. استورد الإعداد الأساسي أولاً ثم بيانات المنتجات مع المراجع المتحققة. اعتمد الاتصالات والمواءمة وجرّب المسارات السريرية والمالية والاستثناءات وطابق الإجماليات واعتمد التحويل والاستعادة ثم سلم الدعم المراقب. لكل مرحلة مسؤولون وملفات وبوابة قبول.","href":"/resources/implementation#implementation-path"},{"question":"ما قوالب CSV التي أستطيع تنزيلها ورفعها؟","answer":"استخدم قوالب الأقسام والمستخدمين والأدوار والصلاحيات والخدمات ومواءمة SBS والأطباء والجداول والأصول والمخزون والأجهزة وتهيئة المنتجات المختارة. نزّل المثال وقاموس الحقول. لملفات الإعداد مسار استيراد في الحساب، ولسجلات الأدلة وبيانات الترحيل وجهات موضحة بشكل مستقل. تحقق قبل تثبيت أي استيراد.","href":"/resources/implementation#templates"},{"question":"كيف أرحّل Epic أو TrakCare أو Oracle Health إلى منسوق؟","answer":"حدد المنتج والإصدار المثبتين واحصل على استخراج وقواميس معتمدة. احصر البيانات السريرية والتشغيلية والمالية والمرفقات بشكل مستقل واحتفظ بمعرّفات المصدر. اعتمد محوّل الوجهة والمواءمة وعينة الاختبار وطابق السجلات والأرصدة وجرّب التغييرات النهائية والتراجع ثم اعتمد التحويل. استخراج FHIR سريري وحده قد لا يشمل الجداول والمطالبات والأرصدة والصور.","href":"/resources/migration-integration"}],"implementation":{"phases":[{"name":"اعتماد النطاق","owner":"الراعي ومسؤولو المنتجات","before":"راعٍ محدد وقائمة المنشآت والمنتجات المختارة.","steps":["حدد الكيانات والمنشآت والأقسام والمنتجات وأنماط التشغيل. ميّز التشغيل الداخلي عن ربط نظام خارجي.","ثبّت إصدارات التطبيق والربط والمصطلحات. تحقق من التوافر والتراخيص والمستخدمين والمنشآت والتخزين والدعم في العرض.","سمّ مسؤولي التشغيل السريري والمالي والبيانات والأمن والربط. اعتمد الموافقات وأدلة الاختبار ومواعيد القرار.","سجل افتراضات الترحيل واللغة والعملة والمنطقة الزمنية والمعرفات والتعطل والاعتماد وملكية الأنظمة. لا تجعل الافتراض غير المحسوم قيمة افتراضية.","اعتمد معايير القبول والمهام المستثناة بدقة مع سبب ومسؤول ومسار متابعة."],"acceptance":"نطاق وإصدارات وسجل قرارات معتمدة.","exception":"منتج غير متاح أو ترخيص ناقص أو حدود بيانات غير معتمدة: عدّل النطاق قبل التشغيل.","files":["project_scope","assumptions_decisions"]},{"name":"إنشاء أساس الحساب","owner":"مدير الحساب الموثق","before":"نطاق معتمد واتفاقية أو تجربة مؤهلة.","steps":["سجّل بحساب موثق واختر المؤسسة والاشتراك الصحيحين وافتح الإعداد. يحفظ المدير وحده التهيئة.","نزّل قالب المؤسسة من الإعداد وأدخل الاسم القانوني والتسجيل والدولة ومعرّف الضريبة إن انطبق. احتفظ بالمعرفات كنص.","استورد عدد المنشآت المتعاقد عليه مع الترخيص والعنوان والهاتف والمنطقة الزمنية. تبقى بيانات الترخيص إقرارات حتى التحقق.","استورد الأقسام والغرف والأجنحة والأسرة. تبدأ أرقام المنشآت من ١ حسب ترتيب الحفظ وتكون الأسماء فريدة داخل المنشأة.","استورد الفريق المخطط. يشمل عدد المستخدمين مدير الحساب. لا توجد كلمة مرور مشتركة؛ تمنح الدعوات وتسجيل الحساب الموثق الوصول.","حدد اللغة والعملة والأيام وساعات العمل داخل اليوم. تقسم مدة الموعد الفترة بالكامل. سجّل الفترات المنقسمة داخل اليوم بصفوف منفصلة. وثّق المناوبات الليلية في ملف تحضير الجداول واعتمد تهيئتها الخاصة بالإصدار؛ لا يقبل قالب المواعيد نهاية في اليوم التالي أو 24:00."],"acceptance":"بيانات المؤسسة والمنشآت والأقسام والفريق والتشغيل محفوظة.","exception":"مؤسسة أو أعداد غير صحيحة: صحح قبل المتابعة. الإعداد المقدم مقفل؛ مرر التغييرات اللاحقة بطلب معتمد.","files":["organization","facilities","departments","locations","staff","operations","access_matrix"]},{"name":"تهيئة كل منتج مختار","owner":"مسؤولو الأقسام والمدير","before":"ملفات الأساس محفوظة وإصدارات المنتجات معتمدة.","steps":["افتح «منتجاتك · بيانات التهيئة». يطلب النظام البيانات المنطبقة على القدرات المختارة. نزّل الإصدار المطابق لكل قالب.","استورد الأدوار المخصصة عند الحاجة بمعرفات الصلاحيات المنشورة. اربط بريد الفريق بأدوار الأقسام ثم استورد مؤهلات الأطباء والتراخيص والعيادات التشغيلية.","استورد الخدمات قبل الأسعار ومواءمة SBS. أدخل السعر بوحدة العملة الصغرى والعملة. تتطلب المواءمة الرمز والإصدار ومرجع الاعتماد وتبقى مسودة حتى التحقق.","استورد الجداول بعد ربط العيادات مع القسم والموقع واليوم والتواريخ والمواعيد. قسّم المناوبات الليلية إلى فترات داخل اليوم؛ يُرفض تداخل جداول الطبيب.","استورد الأصناف قبل التشغيلات والأرصدة. طابق الوحدات والتشغيلة والانتهاء والموقع والتكلفة. استورد الأجهزة برقمها وطرازها وقسمها وموقعها وبروتوكولها؛ يبقى التشغيل الفعلي مهمة قبول.","استخدم دليل المنتجات لحصر كل وظيفة مختارة وسجّل إعدادها ومسؤولها واعتمادها. لا ينفذ السجل إعدادات عشوائية؛ هيئ المسارات الخاصة بالإصدار واختبرها في مساحة المنتج قبل التفعيل.","أكمل قرارات البيانات: مقدمة بسجلات صحيحة أو غير منطبقة بسبب. راجع المعاينة وطبّق واحفظ وصحح المراجع الناقصة قبل قبول الخطوة.","راجع الإعداد ووافق على التهيئة بحالة دفع أو تجربة مؤهلة. يجب نجاح السعة والاتصال والصحة ومطابقة الأعداد قبل الدخول. استخدم مساحة اختبار معتمدة للتجارب؛ تأسيس الحساب منفصل عن قبول التشغيل السريري."],"acceptance":"نجاح التحقق بين الملفات وقرار صريح لكل مجموعة منطبقة.","exception":"خدمة أو صنف أو طبيب أو صلاحية أو موقع غير معروف أو مناوبة متداخلة: صحح الملف. لا يقبل التشغيل استيراداً جزئياً.","files":["roles","user_access","doctors","services","service_billing","doctor_schedules","stock_items","stock_balances","assets_devices","product_settings","dataset_decisions","clinical_workflows","scheduling"]},{"name":"تهيئة قواعد الإيرادات والاعتماد","owner":"المالية ومسؤولو التعاقد","before":"مستندات قانونية وخدمات وإصدار ترميز معتمدة.","steps":["اتبع تسلسل دورة الإيرادات أدناه: الجهات وأدوار التأمين والإدارة والتفويض والعقود والمنتجات والوثائق والفئات والمنافع والتعريفات والشبكات والتسجيل.","ميّز شركة التأمين عن جهة الإدارة والمنتج التأميني عن الوثيقة الصادرة. سجل التواريخ والعملة والمواعيد والتعديلات من المصدر المعتمد.","حدد التغطية والاستثناءات والحدود والتحمل والمشاركة وشروط الموافقة والأولوية. سعر القائمة لا يساوي السعر المسموح المتعاقد عليه.","جهّز التهيئة الموثقة وراجع أخطاء الصفوف وتداخل الفترات. اعتمد المسودات قبل نشر إصدار قواعد جديد. يوضح كل سجل تحضير طريقة معالجته: يُستورد أصلياً في مساحة عملك كمسودات، أو دليل مع قراءة الحالة من مساحة العمل، أو مستبعد يُعالَج خارج هذا الإعداد (التسجيل لدى هيئة الزكاة). أعمدة الجاهزية مثل status وcertification_status وallow_live_submission قيم معلنة لا تُطبَّق؛ يجري التفعيل في مساحة العمل. approval_reference مرجع وليس اعتماداً.","جرّب الأهلية والموافقة وتسجيل الرسوم والمطالبة المصححة والرفض والاستئناف والتحصيل والسداد الجزئي والعكس والمطابقة. تحقق من المسؤولية والتدقيق لكل انتقال."],"acceptance":"إصدار قواعد معتمد وأدلة اختبار مالي مطابقة.","exception":"اعتماد ناقص أو تواريخ متعارضة أو تغطية مفترضة أو مجاميع غير مطابقة: أوقف التفعيل المالي وحدد مسؤولاً واتبع خطة الاستمرارية السريرية المعتمدة.","files":["rcm_organizations","rcm_provider_contracts","rcm_insurance_products","rcm_issued_policies","rcm_benefit_classes","rcm_benefit_rules","rcm_tariffs","rcm_tariff_assignments"]},{"name":"ربط الأنظمة والأجهزة","owner":"مسؤولو الربط والهندسة الطبية","before":"نطاق رسائل ومعرفات وإجراءات ربط خارجية معتمدة.","steps":["احصر المصادر والوجهات: نفيس والزكاة والمحاسبة والمحللات وPACS/RIS والأجهزة وخدمات الشبكة. اعتمد البروتوكول والإصدار والاتجاه والمسؤول.","اعتمد مواءمة المعرفات والخدمات والمصطلحات والوحدات والتوقيت والحالات. وضّح مطابقة الهوية وأحل الحالات الملتبسة للمراجعة.","سجل الجاهزية في الإعداد واحفظ الأسرار في مدير الاعتماد. افصل بيئتي الاختبار والإنتاج وعناوينهما وشهاداتهما وصلاحياتهما وانتهائها.","ثبّت حزمة نفيس المعتمدة واختبر المعاملات المتفق عليها. تحقق من مرحلة الزكاة وإجراءات ربط الأجهزة والعناوين المطلوبة. لا تُعد الوثائق العامة شهادة إنتاج.","اختبر الرسائل والتكرار والتأخير والترتيب والرفض والإعادة والانقطاع والاستعادة. تحقق من المطابقة والمراقبة ومسؤول التنبيه والبديل اليدوي."],"acceptance":"لكل ربط مواءمة وأدلة اختبار واعتماد إنتاج.","exception":"اعتماد أو شهادة أو جهاز غير متاح: سجل الربط محجوباً واعتمد بديلاً دون وصفه بأنه مفعل.","files":["integrations","interfaces","assets_devices","rcm_nphies_configurations","rcm_production_endpoints","rcm_production_routing_rules","rcm_zatca_onboardings"]},{"name":"مطابقة البيانات الحالية","owner":"مسؤولو البيانات والسريري والمالي","before":"حدود بيانات واحتفاظ وحصر مصادر معتمدة.","steps":["صنّف بيانات الهوية والزيارات والتاريخ والوثائق والطلبات والأدوية والمخزون والتغطية والفواتير والمطالبات. قرر الترحيل أو القراءة أو الأرشفة أو الاستثناء لكل مجموعة.","اعتمد الوصول والاحتفاظ والنقل الآمن مع المسؤول. أبعد بيانات المرضى والمال عن القوالب العامة والبريد والصور واستخدم مساحة مشروع آمنة.","واءم كل حقل مع مخطط الوجهة وإصدارها. حدد الفراغ والتكرار والمعرفات والمصطلحات والتواريخ وبصمات المرفقات. لا تدمج هويات ملتبسة آلياً.","نفذ استيراداً تجريبياً في بيئة معزولة. طابق المصدر مع المقبول والمرفوض والمجاميع المالية والمخزون والمرفقات، وراجع عينات مع مسؤولي الأقسام.","جمّد المصدر وحدد التغييرات اللاحقة وجرّب الرجوع قبل التحويل. لا ينشئ تأسيس المنشأة مرضى؛ ينفذ الترحيل بعد اعتماد المواءمة وأداة الاستيراد."],"acceptance":"مواءمة وبصمات وسجل مرفوضات ومجاميع مطابقة معتمدة.","exception":"لا توجد بيانات سابقة: سجل عدم الانطباق باعتماد المصدر. فشل المطابقة: صحح وأعد التشغيل واحتفظ بالنظام السابق حتى القبول.","files":["migration_mapping","migration_batches","medication_catalogue","inventory_opening"]},{"name":"إثبات الرحلة الكاملة","owner":"مسؤولو المنتجات والأمن والمالية","before":"بيئة اختبار مهيأة وبيانات تدريبية أو مصرح بها.","steps":["حوّل كل وظيفة مختارة إلى اختبار بشروط وإجراءات ونتيجة محددة يشمل التسليم للقسم التالي والحالة المالية النهائية.","اختبر النجاح والبيانات الناقصة والمعرفات والتكرار والصلاحيات وحدود التاريخ والإلغاء والتصحيح والتزامن. تحقق من عزل المنشآت.","اختبر ذروة العمل واستعادة النسخ والتعطل والإعادة والتعافي، وراجع التدقيق والرسائل وأعداد الاستيراد ومجاميع المخزون والمال.","سجل النتائج والأدلة وصحح العيوب المانعة وأعد اختبار المتطلبات المتأثرة واعتمد المسؤولين. لا تعتبر الاختبار غير المنفذ ناجحاً."],"acceptance":"كل اختبار مشمول ناجح أو له استثناء معتمد وبديل.","exception":"خلل حرج أو مسار غير آمن أو اختلاف بيانات أو كشف صلاحيات: امنع التشغيل وأعد الاختبار.","files":["uat_cases","clinical_workflows"]},{"name":"تهيئة كل دور","owner":"المستخدمون الرئيسيون وقادة الأقسام","before":"مسارات معتمدة وبيئة تدريب حسب الأدوار.","steps":["درب الإدارة والاستقبال والسريري والتمريض والأقسام والصيدلية والمخزون والمالية والدعم والقيادة حسب نطاقهم.","استخدم سيناريوهات العمل والتصحيح والإلغاء والتسليم والتصعيد والصلاحيات والتعطل مع تبديل المناوبات وخارج ساعات العمل.","سجل الحضور والكفاءة وأعد تدريب المهام غير المجتازة، وحدد مستخدماً رئيسياً لكل مناوبة ووزع مسارات المساعدة والتصعيد."],"acceptance":"اكتمال كفاءة الموظفين المطلوبين ومعرفتهم بالبديل.","exception":"غياب أو عدم اجتياز: حدد تدريباً بديلاً ووصولاً تحت الإشراف حتى القبول.","files":["training","access_matrix"]},{"name":"التشغيل ببديل مجرّب","owner":"مسؤول قرار التشغيل والعمليات","before":"أدلة قبول وتدريب وترحيل وربط معتمدة.","steps":["اعتمد نافذة التغيير والتواصل والتجميد والنسخ ومسؤول القرار وشروط الرجوع والتعطل، واختبر الاستعادة مسبقاً.","تحقق من التطبيق المؤسس وإصدار الإنتاج وأعداد الاستيراد. تبقى الدفعة أو التجربة والحدود والصحة إلزامية. يحتاج الاستخدام الإنتاجي قراراً مستقلاً بعد تحقق القبول.","اختر عنوان التطبيق وتحقق من ملكية DNS والاتصال للنطاق الخاص. تُستورد بيانات المنتجات مع التأسيس في معاملة واحدة وتطابق أعداد الإيصال الملفات المقدمة.","طبق تغييرات الترحيل المعتمدة وطابق السجلات والمجاميع ونفذ اختبارات الأدوار والربط. سجل الإصدار وإيصالات الاستيراد.","يقرر المسؤول الاستمرار أو الرجوع عند كل نقطة. عند الرجوع أوقف الكتابة واحفظ التدقيق والمعاملات واستعد الحالة المعتمدة وطابق العمل أثناء النافذة."],"acceptance":"قرار تشغيل وأعداد استيراد وأدلة تحقق إنتاج معتمدة.","exception":"فشل السعة أو النطاق أو الصحة أو الأعداد أو اختبار حرج: أبق التشغيل محجوباً واتبع البديل المسجل.","files":["domain","cutover_runbook","migration_batches","uat_cases"]},{"name":"الاستقرار وتسليم الدعم","owner":"مسؤول الدعم والخدمات","before":"سجل تشغيل معتمد وتغطية دعم محددة.","steps":["راقب الصحة والصلاحيات وطوابير الربط والرسائل والمطالبات والمطابقة والمخزون. اربط التنبيهات بأشخاص واتفق على أوقات الاستجابة.","طابق يومياً خلال فترة الاستقرار المتفق عليها وراجع العيوب والكفاءة واستخدام البديل مع مسؤولي الأقسام.","سلّم الاتصالات والتغطية والتصعيد والإصدارات والتهيئة وأدلة النسخ والاستعادة ومسؤولية انتهاء الشهادات والتراخيص.","أغلق التنفيذ بعد تحقق القبول. استخدم طلبات تغيير للمنتجات والمواقع والربط والقواعد والإصدارات وأعد الاختبارات وحدّث القوالب عند تغيير المخططات."],"acceptance":"تسليم دعم معتمد بمسؤولين وتواريخ تجديد.","exception":"مشكلة حرجة غير محلولة: واصل الاستقرار بمسؤول محدد ولا تغلق التنفيذ.","files":["support_handover","assumptions_decisions"]}],"productInputs":{"core":["Identity rules and duplicate review","Facility boundaries, roles and permissions","Audit, retention and common configuration"],"outpatient":["Clinics, consultation rooms and specialties","Doctor affiliations, schedules and visit types","Documentation, orders, results and follow-up"],"inpatient":["Wards, beds and transfer states","Care teams, shift handovers and care plans","Medication, departmental orders and discharge"],"emergency":["Arrival and locally approved triage states","Urgent care roles, locations and escalation","Observation, admission, transfer and discharge"],"teleicu":["Hub/spoke facilities and specialist coverage","Patient context sources and device interfaces","Remote review, escalation and bedside responsibility"],"home_palliative":["Service zones, visit teams and travel constraints","Care plans, consent and caregiver contacts","Remote documentation, symptom review and escalation"],"operating_room":["Theatres, resources, sessions and equipment","Procedure preparation and approved safety checklist","Anesthesia, consumables, recovery and handover"],"icu":["Bed/monitor inventory and care-team coverage","Observations, devices and unit mappings","Medication, escalation and shift handover"],"pharmacy":["Medication catalogue, codes, units and conversions","Prescription verification, dispensing and returns","Stock lots, expiry and controlled access"],"laboratory":["Test catalogue, specimens and collection workflow","Analyzer mappings, units and reference intervals","Result validation, critical-result escalation and amended reports"],"radiology":["Modalities, procedure catalogue and scheduling","RIS/PACS accession identifiers and interfaces","Acquisition, reporting, addenda and critical-result escalation"],"inventory":["Stores, items, units and suppliers","Opening lots, quantities, cost and expiry","Receipt, issue, transfer, return and reconciliation"],"clinical_documentation":["Approved templates, author roles and signatures","Correction and amendment rules","Retention and encounter linkage"],"orders_medication":["Order types, approved catalogues and destinations","Statuses, authorization and cancellation","Results, medication links and responsibility"],"patient_access":["Identifiers, registration and matching","Visit types, booking resources and arrival","Consent, cancellation and referral ownership"],"billing_finance":["Gross prices, tax applicability and invoice ownership","Payments, refunds and reversals","Finance export, control totals and reconciliation"],"revenue_cycle":["Legal entities, contracts and issued policies","Benefits, networks, tariffs and rule versions","Eligibility through claim, denial, payment and reconciliation"],"sbs_specific":["Selected SBS codes and release rights","Local-service mapping and effective dates","Approval evidence and code validation"],"sbs_full":["Licensed catalogue release and scope","Full code mappings and catalogue import owner","Inactive codes, version changes and usage rights"],"drg":["Grouper version and licence","Coding inputs, completeness and grouping route","Casemix outputs, correction and financial use approval"],"nphies":["Provider identity, payer routes and certified package","Sandbox/production endpoints and secret references","Eligibility, authorization, claim and payment-response tests"],"zatca":["Legal taxpayer, VAT and applicable phase","Invoice sequences, tax categories and device onboarding","Clearance/reporting, retry and credential renewal"],"analytics":["Source ownership, metric definitions and access","Refresh, filters, grain and reconciliation","Export controls and dashboard acceptance"],"ai":["Approved use case, data access and model version","Human review, failure route and audit","Evaluation criteria and monitoring; no autonomous clinical assumption"],"interfaces":["Protocol/version, source/target and ownership","Identifier and terminology mapping","Retry, duplicates, queues, outage and recovery"],"network_governance":["Legal entities, facility and data boundaries","Delegated administration and cross-site roles","Patient continuity, shared catalogues and boundary tests"],"implementation":["Scope, owners, releases and acceptance","Configuration, tests, training and cutover","Support handover and controlled changes"],"migration":["Source inventory and retention decision","Field mapping, dry runs and rejected records","Cutover delta, control totals and rollback"],"support":["Coverage, contacts and severity rules","Alert ownership, escalation and restoration","Renewals, release maintenance and acceptance"],"equipment":["Device inventory, location and maintenance","Protocol, connectivity and commissioning","Acceptance tests and biomedical ownership"],"managed_revenue":["Delegated duties and payer authority","Work queues, source access and quality checks","Submission, remittance, reconciliation and reporting"],"rcm_eligibility":["Member/policy identifiers and payer route","Benefit version and service context","Unavailable, expired and conflicting cover handling"],"rcm_authorization":["Service/code mapping and evidence requirements","Requested, approved, denied and expired states","Partial approval, extension, cancellation and escalation"],"rcm_contracts":["Legal provider/insurer/administrator IDs","Signed effective dates and amendments","Allowed amounts, deadlines and evidence authority"],"rcm_networks":["Provider affiliations and network tiers","Effective dates and policy relationships","Out-of-network exceptions and precedence"],"rcm_benefits":["Issued policy, member class and limits","Exclusions, deductibles and co-pay","Accumulation, exceptions and rule precedence"],"rcm_tariffs":["Catalogue codes, currency and gross prices","Contracted allowed amounts and assignments","Effective overlap, negotiated exceptions and amendments"],"rcm_charge_capture":["Service event and charge identity","Quantity, unit, performer and documentation","Missing charge, duplicates, corrections and reversals"],"rcm_claims":["Submission authority, deadlines and routes","Payload completeness and attachments","Status polling, duplicates, cancellation and corrected claims"],"rcm_denials":["Payer reason codes and owner routing","Documentation correction and appeal deadlines","Appeal evidence, resubmission and disposition"],"rcm_remittance":["Payer payment reference and claim links","Advice lines, deductions and adjustments","Partial payment, reversal and unmatched advice"],"rcm_reconciliation":["Bank/ledger/payer identifiers and dates","Control totals, currencies and exceptions","Unallocated cash, settlement and approved adjustments"],"rcm_reporting":["Metric definitions and source lineage","Role-based queues and refresh windows","Financial totals, exports and management review"]},"materials":[{"id":"organization","title":"منشأتك","purpose":"أدخل البيانات المسجلة للمنشأة. لا تدخل بيانات المرضى هنا.","route":"setup","dependencies":[],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"legal_name","name":"الاسم القانوني للمنشأة","required":true,"format":"text","example":"Example Healthcare Organization"},{"id":"registration_number","name":"رقم السجل التجاري","required":true,"format":"text","example":"EXAMPLE-CR-001"},{"id":"country","name":"الدولة","required":true,"format":"SA / AE / BH / KW / QA / OM / EG / OTHER","example":"SA"},{"id":"vat_number","name":"الرقم الضريبي","required":false,"format":"text","example":""}],"template":"/implementation/templates/organization.csv","example":"/implementation/examples/organization.csv"},{"id":"facilities","title":"المنشآت","purpose":"أضف جميع المنشآت ضمن اشتراكك لإنشائها في التطبيق.","route":"setup","dependencies":["organization"],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"name","name":"اسم المنشأة","required":true,"format":"text","example":"Example Facility"},{"id":"type","name":"نوع المنشأة","required":true,"format":"hospital / clinic / polyclinic / laboratory / other","example":"clinic"},{"id":"license_number","name":"ترخيص المنشأة","required":true,"format":"text","example":"EXAMPLE-LICENSE-001"},{"id":"address","name":"العنوان","required":true,"format":"text","example":"Example training address"},{"id":"phone","name":"الهاتف","required":true,"format":"text","example":"+966500000000"},{"id":"timezone","name":"المنطقة الزمنية","required":true,"format":"Asia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTC","example":"Asia/Riyadh"}],"template":"/implementation/templates/facilities.csv","example":"/implementation/examples/facilities.csv"},{"id":"departments","title":"الأقسام","purpose":"أنشئ الأقسام وغرف الفحص والأجنحة والأسرة. يمكنك إضافة المزيد داخل التطبيق.","route":"setup","dependencies":["facilities"],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"facility","name":"رقم المنشأة (يبدأ من 1)","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"اسم القسم","required":true,"format":"text","example":"Example Department"}],"template":"/implementation/templates/departments.csv","example":"/implementation/examples/departments.csv"},{"id":"locations","title":"الغرف والأجنحة والأسرة","purpose":"أنشئ الأقسام وغرف الفحص والأجنحة والأسرة. يمكنك إضافة المزيد داخل التطبيق.","route":"setup","dependencies":["facilities"],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"اسم الموقع","required":true,"format":"text","example":"Example Room"},{"id":"kind","name":"النوع","required":true,"format":"room / ward / bed","example":"room"},{"id":"parent","name":"يقع داخل الموقع (اختياري)","required":false,"format":"text","example":""}],"template":"/implementation/templates/locations.csv","example":"/implementation/examples/locations.csv"},{"id":"staff","title":"الفريق المخطط","purpose":"يصبح حسابك الموثق مدير المنشأة. ادعُ الموظفين من حسابك ضمن عدد المستخدمين المسموح.","route":"setup","dependencies":[],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"name","name":"الاسم","required":true,"format":"text","example":"Example Staff"},{"id":"email","name":"البريد المهني","required":true,"format":"email","example":"staff@example.invalid"},{"id":"role","name":"الدور السريري","required":true,"format":"facility_admin / doctor / nurse / pharmacist / reception / billing / member","example":"doctor"}],"template":"/implementation/templates/staff.csv","example":"/implementation/examples/staff.csv"},{"id":"operations","title":"تفضيلات التشغيل","purpose":"حدد الأيام والساعات ومعرّفات المرضى وتفضيلات الفوترة. يبدأ التطبيق دون بيانات مرضى.","route":"setup","dependencies":[],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"working_days","name":"أيام العمل","required":true,"format":"sun-thu / mon-fri / every-day","example":"sun-thu"},{"id":"opening_time","name":"وقت الفتح","required":true,"format":"text","example":"08:00"},{"id":"closing_time","name":"وقت الإغلاق","required":true,"format":"text","example":"17:00"},{"id":"slot_minutes","name":"مدة الموعد بالدقائق","required":true,"format":"integer 5–240","example":"15"},{"id":"patient_prefix","name":"بادئة ملفات المرضى","required":false,"format":"text","example":"EXAMPLE"},{"id":"billing_currency","name":"عملة الفوترة","required":true,"format":"SAR","example":"SAR"},{"id":"language","name":"اللغة الافتراضية","required":true,"format":"ar / en","example":"en"}],"template":"/implementation/templates/operations.csv","example":"/implementation/examples/operations.csv"},{"id":"integrations","title":"جاهزية التكامل","purpose":"حدد الأنظمة الخارجية. أدخل بيانات الاعتماد بأمان في تطبيقك بعد التشغيل؛ قد تتطلب الموافقات للاستخدام الفعلي.","route":"setup","dependencies":[],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"nphies_provider_id","name":"معرّف مقدم الخدمة في نفيس","required":false,"format":"text","example":""},{"id":"payer_names","name":"شركات التأمين","required":false,"format":"text","example":""},{"id":"accounting_system","name":"النظام المحاسبي","required":false,"format":"text","example":""},{"id":"migration_required","name":"تحتاج البيانات السابقة إلى ترحيل","required":false,"format":"true / false","example":"false"}],"template":"/implementation/templates/integrations.csv","example":"/implementation/examples/integrations.csv"},{"id":"domain","title":"عنوان تطبيقك","purpose":"اختر عنواناً فريداً. يمكن للباقات المؤهلة ربط نطاق بعد التحقق من الملكية والاتصال الآمن.","route":"setup","dependencies":[],"acceptance":"ارفع الملف في خطوة إعداد الحساب المطابقة، ثم راجع المعاينة وطبّق القيم واضغط «احفظ وتابع». قد تختلف الأعمدة باختلاف إصدار المنشأة؛ نزّل القالب من داخل الإعداد.","columns":[{"id":"slug","name":"عنوان التطبيق، مثال: my-clinic","required":true,"format":"text","example":"example-clinic"},{"id":"custom_domain","name":"نطاق خاص (اختياري)","required":false,"format":"text","example":""}],"template":"/implementation/templates/domain.csv","example":"/implementation/examples/domain.csv"},{"id":"roles","title":"الأدوار والصلاحيات","purpose":"بيانات تهيئة الأدوار والصلاحيات","route":"setup","dependencies":[],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"role_name","name":"اسم الدور","required":true,"format":"text","example":"Example scheduling role"},{"id":"permission_slug","name":"معرّف الصلاحية","required":true,"format":"text","example":"can_list_schedule"}],"template":"/implementation/templates/roles.csv","example":"/implementation/examples/roles.csv"},{"id":"user_access","title":"المستخدمون وصلاحيات الأقسام","purpose":"بيانات تهيئة المستخدمون وصلاحيات الأقسام","route":"setup","dependencies":["staff","departments","roles"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"staff_email","name":"بريد الموظف","required":true,"format":"email","example":"staff@example.invalid"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"اسم القسم","required":true,"format":"text","example":"Example Department"},{"id":"role_name","name":"اسم الدور المعتمد","required":true,"format":"text","example":"Doctor"}],"template":"/implementation/templates/user_access.csv","example":"/implementation/examples/user_access.csv"},{"id":"doctors","title":"الأطباء والعيادات التشغيلية","purpose":"بيانات تهيئة الأطباء والعيادات التشغيلية","route":"setup","dependencies":["staff","departments","locations","user_access"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"staff_email","name":"بريد الطبيب","required":true,"format":"email","example":"staff@example.invalid"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"القسم","required":true,"format":"text","example":"Example Department"},{"id":"clinic_location","name":"موقع العيادة","required":true,"format":"text","example":"Example Room"},{"id":"qualification","name":"المؤهل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"license_number","name":"ترخيص الممارس","required":true,"format":"text","example":"EXAMPLE-LICENSE-001"},{"id":"primary_clinic","name":"العيادة الرئيسية","required":false,"format":"checkbox","example":"true"}],"template":"/implementation/templates/doctors.csv","example":"/implementation/examples/doctors.csv"},{"id":"services","title":"الخدمات ودليل الأقسام","purpose":"بيانات تهيئة الخدمات ودليل الأقسام","route":"setup","dependencies":["departments","locations"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"service_code","name":"رمز الخدمة المحلي","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"name_en","name":"الاسم الإنجليزي","required":true,"format":"text","example":"Example service"},{"id":"name_ar","name":"الاسم العربي","required":true,"format":"text","example":"خدمة تدريبية"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"القسم","required":true,"format":"text","example":"Example Department"},{"id":"location","name":"الموقع","required":true,"format":"text","example":"Example Room"},{"id":"internal_type","name":"وظيفة الخدمة","required":true,"format":"general / scheduling / lab / pharmacy / store","example":"scheduling"}],"template":"/implementation/templates/services.csv","example":"/implementation/examples/services.csv"},{"id":"service_billing","title":"أسعار الخدمات ومواءمة SBS","purpose":"بيانات تهيئة أسعار الخدمات ومواءمة SBS","route":"setup","dependencies":["services"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"service_code","name":"رمز الخدمة المحلي","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"gross_price_minor","name":"السعر بوحدة العملة الصغرى","required":true,"format":"integer 0–2147483647","example":"15000"},{"id":"currency","name":"العملة","required":true,"format":"SAR","example":"SAR"},{"id":"sbs_code","name":"رمز SBS","required":false,"format":"text","example":""},{"id":"sbs_release","name":"إصدار SBS","required":false,"format":"text","example":""},{"id":"mapping_evidence","name":"مرجع اعتماد المواءمة","required":false,"format":"text","example":""}],"template":"/implementation/templates/service_billing.csv","example":"/implementation/examples/service_billing.csv"},{"id":"doctor_schedules","title":"جداول الأطباء لجميع الأقسام","purpose":"بيانات تهيئة جداول الأطباء لجميع الأقسام","route":"setup","dependencies":["doctors","services"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"schedule_code","name":"رمز الجدول الفريد","required":true,"format":"text","example":"EXAMPLE-SCH-001"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"staff_email","name":"بريد الطبيب","required":true,"format":"email","example":"staff@example.invalid"},{"id":"department","name":"القسم","required":true,"format":"text","example":"Example Department"},{"id":"clinic_location","name":"موقع العيادة","required":true,"format":"text","example":"Example Room"},{"id":"weekday","name":"يوم الأسبوع","required":true,"format":"mon / tue / wed / thu / fri / sat / sun","example":"sun"},{"id":"start_time","name":"وقت البداية","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"وقت النهاية","required":true,"format":"HH:MM","example":"12:00"},{"id":"slot_minutes","name":"مدة الموعد","required":true,"format":"integer 5–240","example":"15"},{"id":"valid_from","name":"ساري من","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"valid_to","name":"ساري حتى","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"}],"template":"/implementation/templates/doctor_schedules.csv","example":"/implementation/examples/doctor_schedules.csv"},{"id":"stock_items","title":"أصناف المخزون والأدوية","purpose":"بيانات تهيئة أصناف المخزون والأدوية","route":"setup","dependencies":["facilities"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"item_code","name":"رمز الصنف الفريد","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"name","name":"اسم الصنف","required":true,"format":"text","example":"Training consumable"},{"id":"product_type","name":"النوع","required":true,"format":"medication / consumable / nutritional_product","example":"consumable"},{"id":"unit_code","name":"رمز وحدة UCUM","required":true,"format":"text","example":"1"},{"id":"code_system","name":"نظام المصطلحات","required":false,"format":"text","example":""},{"id":"external_code","name":"الرمز الخارجي","required":false,"format":"text","example":""}],"template":"/implementation/templates/stock_items.csv","example":"/implementation/examples/stock_items.csv"},{"id":"stock_balances","title":"التشغيلات وأرصدة المخزون","purpose":"بيانات تهيئة التشغيلات وأرصدة المخزون","route":"setup","dependencies":["stock_items","locations"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"item_code","name":"رمز الصنف","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"location","name":"موقع التخزين","required":true,"format":"text","example":"Example Room"},{"id":"lot_number","name":"رقم التشغيلة","required":true,"format":"text","example":"EXAMPLE-LOT-001"},{"id":"expiry_date","name":"تاريخ الانتهاء","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"quantity","name":"الكمية الافتتاحية","required":true,"format":"text","example":"10"},{"id":"purchase_price","name":"سعر شراء الوحدة","required":true,"format":"text","example":"1.50"}],"template":"/implementation/templates/stock_balances.csv","example":"/implementation/examples/stock_balances.csv"},{"id":"assets_devices","title":"الأصول والأجهزة والمعدات","purpose":"بيانات تهيئة الأصول والأجهزة والمعدات","route":"setup","dependencies":["departments","locations"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"asset_code","name":"رمز الأصل الفريد","required":true,"format":"text","example":"EXAMPLE-LAB-001"},{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"department","name":"القسم","required":true,"format":"text","example":"Example Department"},{"id":"location","name":"الموقع","required":true,"format":"text","example":"Example Room"},{"id":"name","name":"اسم الجهاز","required":true,"format":"text","example":"Training laboratory analyser"},{"id":"manufacturer","name":"الشركة المصنعة","required":true,"format":"text","example":"Example manufacturer"},{"id":"model","name":"الطراز","required":true,"format":"text","example":"EXAMPLE-MODEL"},{"id":"serial_number","name":"الرقم التسلسلي","required":true,"format":"text","example":"EXAMPLE-SERIAL"},{"id":"care_type","name":"الغرض أو المنتج","required":true,"format":"text","example":"laboratory"},{"id":"protocol","name":"بروتوكول الربط وإصداره","required":false,"format":"text","example":"TO-CONFIRM"},{"id":"maintenance_due","name":"موعد الصيانة","required":false,"format":"YYYY-MM-DD","example":"2027-10-09"}],"template":"/implementation/templates/assets_devices.csv","example":"/implementation/examples/assets_devices.csv"},{"id":"product_settings","title":"إعدادات الوظائف · إغلاقات الجدولة","purpose":"بيانات تهيئة إعدادات الوظائف · إغلاقات الجدولة","route":"setup","dependencies":["locations"],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"facility","name":"رقم المنشأة","required":true,"format":"integer 1–1000","example":"1"},{"id":"feature","name":"معرّف الميزة المختارة","required":true,"format":"scheduling","example":"scheduling"},{"id":"function_key","name":"إعداد الوظيفة","required":true,"format":"scheduling.closures","example":"scheduling.closures"},{"id":"name","name":"اسم الإغلاق","required":true,"format":"text","example":"Example closure"},{"id":"valid_from","name":"أول تاريخ إغلاق","required":true,"format":"YYYY-MM-DD","example":"2026-12-01"},{"id":"valid_to","name":"آخر تاريخ إغلاق","required":true,"format":"YYYY-MM-DD","example":"2026-12-01"},{"id":"start_time","name":"الإغلاق من","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"الإغلاق حتى","required":true,"format":"HH:MM","example":"17:00"},{"id":"location","name":"الغرفة (اتركها فارغة لإغلاق المنشأة كاملة)","required":false,"format":"text","example":"Example Room"}],"template":"/implementation/templates/product_settings.csv","example":"/implementation/examples/product_settings.csv"},{"id":"dataset_decisions","title":"اكتمال البيانات والاستثناءات","purpose":"بيانات تهيئة اكتمال البيانات والاستثناءات","route":"setup","dependencies":[],"acceptance":"ارفع في «منتجاتك · بيانات التهيئة» ثم طبّق واحفظ للتحقق من الروابط. يستورد التشغيل السجلات المدعومة في معاملة واحدة ويطابق الأعداد. تُتحقق إعدادات الوظائف من السجل المدعوم وتُطبَّق أصلياً ويُتحقق من قراءتها؛ وتتطلب الأسعار والمواءمة والأجهزة اعتماداً قبل التفعيل.","columns":[{"id":"dataset_id","name":"معرّف مجموعة البيانات","required":true,"format":"text","example":"services"},{"id":"decision","name":"القرار","required":true,"format":"provided / not_applicable","example":"provided"},{"id":"reason","name":"السبب والاعتماد","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/dataset_decisions.csv","example":"/implementation/examples/dataset_decisions.csv"},{"id":"rcm_organizations","title":"تهيئة دورة الإيرادات · الجهات المتعاقدة","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":[],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"internal_code","name":"الرمز الداخلي","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"legal_name_ar","name":"الاسم القانوني بالعربية","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"legal_name_en","name":"الاسم القانوني بالإنجليزية","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"country_code","name":"رمز الدولة","required":true,"format":"Source-backed value","example":"SA"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"commercial_registration","name":"السجل التجاري","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"tax_number","name":"الرقم الضريبي","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"license_number","name":"رقم الترخيص","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"parent_organization","name":"الجهة الأم","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contact_directory","name":"دليل جهات الاتصال","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_organizations.csv","example":"/implementation/examples/rcm_organizations.csv"},{"id":"rcm_insurer_roles","title":"تهيئة دورة الإيرادات · أدوار شركات التأمين","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_organizations"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"organization","name":"الجهة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"role","name":"الدور","required":true,"format":"Readiness condition: role=insurer","example":"insurer"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_scope","name":"نطاق الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"notes","name":"ملاحظات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_insurer_roles.csv","example":"/implementation/examples/rcm_insurer_roles.csv"},{"id":"rcm_tpa_roles","title":"تهيئة دورة الإيرادات · أدوار شركات إدارة المطالبات","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_organizations"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"organization","name":"الجهة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"role","name":"الدور","required":true,"format":"Readiness condition: role=tpa","example":"tpa"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"portal_reference","name":"مرجع البوابة","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"escalation_matrix","name":"مصفوفة التصعيد","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_tpa_roles.csv","example":"/implementation/examples/rcm_tpa_roles.csv"},{"id":"rcm_administration_agreements","title":"تهيئة دورة الإيرادات · اتفاقيات الإدارة المفوّضة","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_insurer_roles","rcm_tpa_roles"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"insurer_org","name":"شركة التأمين","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"administrator_org","name":"جهة الإدارة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"claim_submission_deadline","name":"مهلة تقديم المطالبات","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"payment_sla","name":"مستوى خدمة السداد","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"portal_url","name":"رابط البوابة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"authorization_sla","name":"مستوى خدمة الموافقات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"appeal_sla","name":"مستوى خدمة الاعتراضات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contact_matrix","name":"مصفوفة جهات الاتصال","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_administration_agreements.csv","example":"/implementation/examples/rcm_administration_agreements.csv"},{"id":"rcm_provider_contracts","title":"تهيئة دورة الإيرادات · عقود مقدمي الخدمة","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_organizations","rcm_insurer_roles"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"payer_or_insurer_org","name":"الجهة الدافعة أو شركة التأمين","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"provider_facility","name":"منشأة مقدم الخدمة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"contract_number","name":"رقم العقد","required":true,"format":"Source-backed value","example":"EXAMPLE-CONTRACT-001"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"currency","name":"العملة","required":true,"format":"Source-backed value","example":"SAR"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_tier","name":"مستوى الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"claim_submission_deadline","name":"مهلة تقديم المطالبات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"payment_terms","name":"شروط السداد","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"appeal_terms","name":"شروط الاعتراض","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_provider_contracts.csv","example":"/implementation/examples/rcm_provider_contracts.csv"},{"id":"rcm_insurance_products","title":"تهيئة دورة الإيرادات · منتجات التأمين","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_insurer_roles"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"insurer_org","name":"شركة التأمين","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_code","name":"رمز المنتج","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_name","name":"اسم المنتج","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"jurisdiction","name":"الاختصاص التنظيمي","required":true,"format":"Source-backed value","example":"SA"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"network_type","name":"نوع الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"product_category","name":"فئة المنتج","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_insurance_products.csv","example":"/implementation/examples/rcm_insurance_products.csv"},{"id":"rcm_issued_policies","title":"تهيئة دورة الإيرادات · الوثائق الصادرة","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_insurance_products"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"product","name":"المنتج","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"policy_number","name":"رقم الوثيقة","required":true,"format":"Source-backed value","example":"EXAMPLE-POLICY"},{"id":"policyholder","name":"حامل الوثيقة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"effective_to","name":"ساري حتى","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"global_policy_limit","name":"الحد الإجمالي للوثيقة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"endorsement_reference","name":"مرجع الملحق","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"renewal_reference","name":"مرجع التجديد","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-002"},{"id":"family_limit","name":"حد الأسرة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-003"}],"template":"/implementation/templates/rcm_issued_policies.csv","example":"/implementation/examples/rcm_issued_policies.csv"},{"id":"rcm_benefit_classes","title":"تهيئة دورة الإيرادات · فئات المنافع","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_insurance_products","rcm_issued_policies"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"product_or_policy","name":"المنتج أو الوثيقة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"class_code","name":"رمز الفئة","required":true,"format":"Source-backed value","example":"EXAMPLE-CLASS"},{"id":"class_name","name":"اسم الفئة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"rank","name":"الترتيب","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"room_grade","name":"درجة الغرفة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"network_tier","name":"مستوى الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"annual_limit","name":"الحد السنوي","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"requires_referral","name":"يتطلب إحالة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_benefit_classes.csv","example":"/implementation/examples/rcm_benefit_classes.csv"},{"id":"rcm_benefit_rules","title":"تهيئة دورة الإيرادات · قواعد المنافع","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_benefit_classes"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"benefit_class_or_policy_scope","name":"فئة المنافع أو نطاق الوثيقة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"service_code_or_group","name":"رمز الخدمة أو مجموعتها","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"coverage_decision","name":"قرار التغطية","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"cost_share_rule","name":"قاعدة تقاسم التكلفة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"authorization_required","name":"تتطلب موافقة مسبقة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"limit_scope","name":"نطاق الحد","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"limit_amount","name":"قيمة الحد","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"frequency_limit","name":"حد التكرار","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"diagnosis_restrictions","name":"قيود التشخيص","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"network_restrictions","name":"قيود الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"exclusion_reason","name":"سبب الاستثناء","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_benefit_rules.csv","example":"/implementation/examples/rcm_benefit_rules.csv"},{"id":"rcm_tariffs","title":"تهيئة دورة الإيرادات · قوائم الأسعار التعاقدية","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_provider_contracts"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"tariff_code","name":"رمز قائمة الأسعار","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"tariff_name","name":"اسم قائمة الأسعار","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"currency","name":"العملة","required":true,"format":"Source-backed value","example":"SAR"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"line_items","name":"البنود","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"unit_basis","name":"أساس الوحدة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"package_rules","name":"قواعد الباقات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"drug_markup_rules","name":"قواعد هامش الأدوية","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"rounding_rules","name":"قواعد التقريب","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_tariffs.csv","example":"/implementation/examples/rcm_tariffs.csv"},{"id":"rcm_tariff_assignments","title":"تهيئة دورة الإيرادات · إسناد قوائم الأسعار","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_provider_contracts","rcm_benefit_classes","rcm_tariffs"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"provider_contract","name":"عقد مقدم الخدمة","required":true,"format":"Source-backed value","example":"EXAMPLE-CONTRACT-001"},{"id":"tariff","name":"قائمة الأسعار","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"priority","name":"الأولوية","required":true,"format":"Source-backed value","example":"1"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"evidence_state","name":"حالة الدليل","required":true,"format":"Readiness condition: evidence_state in activation-grade evidence","example":"absent"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"facility_site","name":"موقع المنشأة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"department","name":"القسم","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"benefit_class","name":"فئة المنافع","required":false,"format":"Source-backed value","example":"EXAMPLE-CLASS"},{"id":"network_tier","name":"مستوى الشبكة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_tariff_assignments.csv","example":"/implementation/examples/rcm_tariff_assignments.csv"},{"id":"rcm_nphies_configurations","title":"تهيئة دورة الإيرادات · إعدادات NPHIES","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_production_endpoints","rcm_production_routing_rules"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"facility_identifier","name":"معرّف المنشأة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"البيئة","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"certification_status","name":"حالة الاعتماد","required":true,"format":"Readiness condition: certification_status=certified","example":"not_started"},{"id":"package_pin","name":"إصدار الحزمة المثبت","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"allow_live_submission","name":"السماح بالإرسال الفعلي","required":true,"format":"Readiness condition: allow_live_submission=true","example":"false"},{"id":"onboarding_reference","name":"مرجع التسجيل","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"certification_expiry","name":"انتهاء الاعتماد","required":false,"format":"Source-backed value","example":""},{"id":"notes","name":"ملاحظات","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_nphies_configurations.csv","example":"/implementation/examples/rcm_nphies_configurations.csv"},{"id":"rcm_production_endpoints","title":"تهيئة دورة الإيرادات · نقاط الاتصال الإنتاجية","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_organizations"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"label","name":"التسمية","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"البيئة","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"endpoint_url","name":"رابط نقطة الاتصال","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"secret_reference","name":"مرجع السر","required":true,"format":"Source-backed value","example":"EXAMPLE-SECRET-REF-001"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"timeout_seconds","name":"مهلة الانتظار بالثواني","required":false,"format":"Source-backed value","example":""},{"id":"mtls_profile","name":"ملف mTLS","required":false,"format":"Readiness condition: mTLS_profile","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_production_endpoints.csv","example":"/implementation/examples/rcm_production_endpoints.csv"},{"id":"rcm_production_routing_rules","title":"تهيئة دورة الإيرادات · قواعد التوجيه الإنتاجي","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_production_endpoints","rcm_administration_agreements"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"transaction_type","name":"نوع المعاملة","required":true,"format":"Readiness condition: transaction_type in eligibility/prior_authorization/claim/payment","example":"claim"},{"id":"environment","name":"البيئة","required":true,"format":"Readiness condition: environment=production","example":"test"},{"id":"endpoint","name":"نقطة الاتصال","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"priority","name":"الأولوية","required":true,"format":"Source-backed value","example":"1"},{"id":"effective_from","name":"ساري من","required":true,"format":"Source-backed value","example":"2026-10-09"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"payer_scope","name":"نطاق الجهات الدافعة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"retry_policy","name":"سياسة إعادة المحاولة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"fallback_queue","name":"قائمة الانتظار البديلة","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/rcm_production_routing_rules.csv","example":"/implementation/examples/rcm_production_routing_rules.csv"},{"id":"rcm_zatca_onboardings","title":"تهيئة دورة الإيرادات · التسجيل لدى ZATCA","purpose":"سجل القيم والجهات والأدلة المعتمدة لهذه الخطوة من دورة الإيرادات.","route":"register","dependencies":["rcm_organizations"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"taxpayer_organization","name":"الجهة المكلفة ضريبياً","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"vat_registration_number","name":"رقم التسجيل في ضريبة القيمة المضافة","required":true,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"environment","name":"البيئة","required":true,"format":"Readiness condition: environment=production","example":"TO-CONFIRM"},{"id":"solution_certificate_reference","name":"مرجع شهادة الحل","required":true,"format":"Source-backed value","example":"EXAMPLE-REF-001"},{"id":"csid_secret_reference","name":"مرجع سر CSID","required":true,"format":"Source-backed value","example":"EXAMPLE-SECRET-REF-001"},{"id":"status","name":"الحالة","required":true,"format":"Readiness condition: status=active","example":"draft"},{"id":"effective_to","name":"ساري حتى","required":false,"format":"Source-backed value","example":"2026-10-09"},{"id":"invoice_type_scope","name":"نطاق أنواع الفواتير","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"phase_wave_reference","name":"مرجع موجة المرحلة","required":false,"format":"Source-backed value","example":"EXAMPLE-REF-002"},{"id":"clearance_endpoint","name":"نقطة اتصال الاعتماد","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"reporting_endpoint","name":"نقطة اتصال الإبلاغ","required":false,"format":"Source-backed value","example":"TO-CONFIRM"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-003"}],"template":"/implementation/templates/rcm_zatca_onboardings.csv","example":"/implementation/examples/rcm_zatca_onboardings.csv"},{"id":"rcm_networks","title":"شبكات مقدمي الخدمة والمشاركة","purpose":"سجّل المشاركة في الشبكة والاستثناءات وفترات السريان قبل استخدام التغطية.","route":"register","dependencies":["rcm_provider_contracts"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"network_code","name":"رمز الشبكة","required":true,"format":"text","example":"EXAMPLE-NETWORK"},{"id":"provider_identifier","name":"معرف مقدم الخدمة","required":true,"format":"text","example":"EXAMPLE-PROVIDER"},{"id":"network_tier","name":"مستوى الشبكة","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"effective_from","name":"بداية السريان","required":true,"format":"YYYY-MM-DD","example":"2026-10-10"},{"id":"effective_to","name":"نهاية السريان","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"contract_reference","name":"العقد المعتمد","required":true,"format":"text","example":"EXAMPLE-CONTRACT-001"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_networks.csv","example":"/implementation/examples/rcm_networks.csv"},{"id":"rcm_member_coverage","title":"مواءمة تغطية الأعضاء","purpose":"حضّر مواءمة التغطية بمراجع تجريبية؛ تحفظ هويات الأعضاء الفعلية في مسار الترحيل الآمن المعتمد.","route":"register","dependencies":["rcm_issued_policies","rcm_benefit_classes","rcm_networks"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"source_member_reference","name":"مرجع العضو بالمصدر","required":true,"format":"text; no patient identifiers in public examples","example":"EXAMPLE-MEMBER"},{"id":"policy_reference","name":"مرجع الوثيقة المصدرة","required":true,"format":"text","example":"EXAMPLE-POLICY"},{"id":"benefit_class_reference","name":"فئة المنافع","required":true,"format":"text","example":"EXAMPLE-CLASS"},{"id":"network_code","name":"رمز الشبكة","required":true,"format":"text","example":"EXAMPLE-NETWORK"},{"id":"effective_from","name":"بداية السريان","required":true,"format":"YYYY-MM-DD","example":"2026-10-10"},{"id":"effective_to","name":"نهاية السريان","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"identity_mapping_reference","name":"مرجع المواءمة الآمنة","required":true,"format":"text; secure workspace reference","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_member_coverage.csv","example":"/implementation/examples/rcm_member_coverage.csv"},{"id":"rcm_rule_publications","title":"القواعد والاستثناءات والنشر","purpose":"راجع أولوية القواعد والاستثناءات وأدلة الاختبار قبل النشر بإصدار ثابت من المسؤولين المخولين.","route":"register","dependencies":["rcm_benefit_rules","rcm_tariff_assignments","uat_cases"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"rule_reference","name":"مرجع القاعدة","required":true,"format":"text","example":"EXAMPLE-RULE"},{"id":"rule_release","name":"إصدار القواعد","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"precedence","name":"أولوية القاعدة","required":true,"format":"integer","example":"1"},{"id":"eligibility_condition","name":"شرط الأهلية","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"exclusion","name":"الاستثناء والسبب","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"limit_or_copay","name":"الحد والتحمل","required":true,"format":"text; specify amount, unit and currency","example":"TO-CONFIRM"},{"id":"test_case_reference","name":"حالة الاختبار","required":true,"format":"text","example":"EXAMPLE-UAT"},{"id":"maker_reference","name":"مسؤول الإعداد","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"checker_reference","name":"المراجع المستقل","required":true,"format":"text","example":"EXAMPLE-REF-002"},{"id":"evidence_reference","name":"دليل التفعيل","required":true,"format":"text","example":"EXAMPLE-REF-003"},{"id":"publication_status","name":"حالة النشر","required":true,"format":"draft / reviewed / approved / blocked","example":"draft"}],"template":"/implementation/templates/rcm_rule_publications.csv","example":"/implementation/examples/rcm_rule_publications.csv"},{"id":"rcm_financial_controls","title":"ضوابط الإيرادات والمطابقة","purpose":"طابق النشاط العادي والمرفوض والمدفوع جزئياً والمعكوس وغير المطابق مع مسؤولية مالية محددة.","route":"register","dependencies":["service_billing","rcm_provider_contracts","uat_cases"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"control_code","name":"رمز الضابط","required":true,"format":"text","example":"EXAMPLE-FIN-01"},{"id":"transaction_type","name":"نوع المعاملة","required":true,"format":"charge / invoice / claim / remittance / reversal / refund / write_off","example":"claim"},{"id":"currency","name":"العملة","required":true,"format":"ISO 4217","example":"SAR"},{"id":"source_total","name":"إجمالي المصدر المتوقع","required":true,"format":"decimal","example":"1000.00"},{"id":"target_total","name":"إجمالي الوجهة","required":true,"format":"decimal","example":"1000.00"},{"id":"tolerance","name":"الفارق المقبول","required":true,"format":"decimal; do not assume a tolerance","example":"0.00"},{"id":"exception_route","name":"مسار الاستثناء والمسؤول","required":true,"format":"text","example":"Finance review"},{"id":"evidence_reference","name":"دليل المطابقة","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"مرجع الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/rcm_financial_controls.csv","example":"/implementation/examples/rcm_financial_controls.csv"},{"id":"project_scope","title":"نطاق المشروع","purpose":"ثبّت المنتجات والإصدارات والمنشآت ونمط التنفيذ ونطاق القبول.","route":"register","dependencies":[],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"product_id","name":"معرّف المنتج","required":true,"format":"text","example":"outpatient"},{"id":"release","name":"الإصدار المتفق عليه","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"mode","name":"نمط التشغيل","required":true,"format":"native / connected","example":"native"},{"id":"facility_scope","name":"نطاق المنشآت","required":true,"format":"text","example":"all"},{"id":"included","name":"مشمول في المشروع","required":true,"format":"true / false","example":"true"},{"id":"owner_role","name":"الدور المسؤول","required":true,"format":"text","example":"Project owner"},{"id":"acceptance_test","name":"دليل القبول","required":true,"format":"text","example":"Approved end-to-end test"},{"id":"approval_reference","name":"مرجع الموافقة","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/project_scope.csv","example":"/implementation/examples/project_scope.csv"},{"id":"assumptions_decisions","title":"الافتراضات والقرارات","purpose":"أظهر كل افتراض غير محسوم مع مسؤول واختبار إغلاق.","route":"register","dependencies":["project_scope"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"decision_id","name":"معرّف القرار","required":true,"format":"text","example":"DEC-001"},{"id":"topic","name":"الموضوع","required":true,"format":"text","example":"Legacy records"},{"id":"assumption","name":"الافتراض المقترح","required":true,"format":"text","example":"No historical patient import until approved"},{"id":"status","name":"الحالة","required":true,"format":"proposed / approved / rejected / open","example":"proposed"},{"id":"owner_role","name":"مسؤول القرار","required":true,"format":"text","example":"Data owner"},{"id":"evidence_reference","name":"مرجع الدليل","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"impact_if_wrong","name":"أثر عدم صحة الافتراض","required":true,"format":"text","example":"Migration scope must change"},{"id":"closure_test","name":"اختبار الإغلاق","required":true,"format":"text","example":"Source inventory approved"}],"template":"/implementation/templates/assumptions_decisions.csv","example":"/implementation/examples/assumptions_decisions.csv"},{"id":"access_matrix","title":"الصلاحيات والموافقات","purpose":"واءم الأدوار والإجراءات المسموحة وتحقق من حدود الصلاحيات بين المنشآت.","route":"register","dependencies":["facilities","staff"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"role","name":"الدور","required":true,"format":"text","example":"doctor"},{"id":"facility_scope","name":"نطاق المنشآت","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"resource","name":"المورد","required":true,"format":"text","example":"Patient record"},{"id":"action","name":"الإجراء","required":true,"format":"text","example":"read"},{"id":"allowed","name":"مسموح","required":true,"format":"true / false","example":"true"},{"id":"approver_role","name":"المعتمد","required":true,"format":"text","example":"Security owner"},{"id":"evidence_reference","name":"دليل الاختبار","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/access_matrix.csv","example":"/implementation/examples/access_matrix.csv"},{"id":"service_catalogue","title":"دليل الخدمات","purpose":"حدد الخدمات ومواءمة الرموز المعتمدة قبل الطلبات والتعريفات والربط.","route":"migration","dependencies":["departments"],"acceptance":"ارفع ملف التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ السجلات في حسابك. استخدم مساحة الترحيل الآمنة للبيانات السريرية الفعلية واعتمد مواءمة المصدر والوجهة وأداة الاستيراد قبل التحميل. نفّذ تجربة وطابق الأعداد واحتفظ بالنتائج.","columns":[{"id":"service_code","name":"رمز الخدمة المحلي","required":true,"format":"text","example":"EXAMPLE-SVC-001"},{"id":"name_en","name":"الاسم الإنجليزي","required":true,"format":"text","example":"Example service"},{"id":"name_ar","name":"الاسم العربي","required":true,"format":"text","example":"خدمة تدريبية"},{"id":"department_code","name":"رمز القسم","required":true,"format":"text","example":"EXAMPLE-DEPT-001"},{"id":"unit","name":"وحدة الخدمة","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"code_system","name":"نظام الترميز","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"release","name":"إصدار الدليل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"external_code","name":"المواءمة الخارجية المعتمدة","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"effective_from","name":"ساري من","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"}],"template":"/implementation/templates/service_catalogue.csv","example":"/implementation/examples/service_catalogue.csv"},{"id":"medication_catalogue","title":"دليل الأدوية","purpose":"دليل معتمد من الصيدلية. السجلات أمثلة تدريبية ولا تتضمن توصيات جرعات.","route":"migration","dependencies":["service_catalogue"],"acceptance":"ارفع ملف التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ السجلات في حسابك. استخدم مساحة الترحيل الآمنة للبيانات السريرية الفعلية واعتمد مواءمة المصدر والوجهة وأداة الاستيراد قبل التحميل. نفّذ تجربة وطابق الأعداد واحتفظ بالنتائج.","columns":[{"id":"item_code","name":"رمز الصنف","required":true,"format":"text","example":"EXAMPLE-MED-001"},{"id":"name","name":"اسم العرض","required":true,"format":"text","example":"Training medication only"},{"id":"code_system","name":"نظام الترميز","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"code","name":"الرمز المعتمد","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"strength","name":"التركيز ووحدته","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"form","name":"الشكل الدوائي","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"stock_unit","name":"وحدة التخزين","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"dispense_unit","name":"وحدة الصرف","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"conversion_factor","name":"معامل التحويل المعتمد","required":true,"format":"decimal","example":"1"},{"id":"release","name":"إصدار المصطلحات","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/medication_catalogue.csv","example":"/implementation/examples/medication_catalogue.csv"},{"id":"inventory_opening","title":"المخزون الافتتاحي","purpose":"حمّل جرداً معتمداً في وقت تحويل محدد. تحقق من صحة التكلفة الصفرية قبل الاعتماد.","route":"migration","dependencies":["medication_catalogue"],"acceptance":"ارفع ملف التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ السجلات في حسابك. استخدم مساحة الترحيل الآمنة للبيانات السريرية الفعلية واعتمد مواءمة المصدر والوجهة وأداة الاستيراد قبل التحميل. نفّذ تجربة وطابق الأعداد واحتفظ بالنتائج.","columns":[{"id":"item_code","name":"رمز الصنف","required":true,"format":"text","example":"EXAMPLE-ITEM-001"},{"id":"store_code","name":"رمز المستودع","required":true,"format":"text","example":"EXAMPLE-STORE-001"},{"id":"lot_number","name":"رقم التشغيلة","required":true,"format":"text","example":"EXAMPLE-LOT-001"},{"id":"expiry_date","name":"تاريخ الانتهاء","required":true,"format":"YYYY-MM-DD","example":"2027-10-09"},{"id":"quantity","name":"الكمية الافتتاحية","required":true,"format":"decimal","example":"10"},{"id":"unit","name":"وحدة التخزين","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"unit_cost","name":"تكلفة الوحدة المعتمدة","required":true,"format":"decimal","example":"0"},{"id":"currency","name":"العملة","required":true,"format":"ISO 4217","example":"SAR"},{"id":"as_of","name":"وقت الجرد","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T08:00:00+03:00"},{"id":"approval_reference","name":"اعتماد الجرد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/inventory_opening.csv","example":"/implementation/examples/inventory_opening.csv"},{"id":"clinical_workflows","title":"تهيئة المسارات السريرية","purpose":"سجل المسارات والمسؤوليات ومعالجة الاستثناءات المعتمدة محلياً.","route":"register","dependencies":["departments","access_matrix"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"workflow_id","name":"معرّف المسار","required":true,"format":"text","example":"EXAMPLE-WF-001"},{"id":"product_id","name":"معرّف المنتج","required":true,"format":"text","example":"outpatient"},{"id":"entry_event","name":"حدث البداية","required":true,"format":"text","example":"Patient arrival"},{"id":"responsible_role","name":"الدور المسؤول","required":true,"format":"text","example":"Nurse"},{"id":"required_information","name":"المعلومات المطلوبة","required":true,"format":"text","example":"Verified identity and visit context"},{"id":"next_event","name":"الحدث التالي","required":true,"format":"text","example":"Clinical consultation"},{"id":"handover_owner","name":"مسؤول التسليم","required":true,"format":"text","example":"Doctor"},{"id":"exception_path","name":"مسار الاستثناء","required":true,"format":"text","example":"Identity mismatch to review"},{"id":"approval_reference","name":"اعتماد المسار","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/clinical_workflows.csv","example":"/implementation/examples/clinical_workflows.csv"},{"id":"scheduling","title":"تهيئة الجدولة","purpose":"خطط لتوافر الموارد والتعارض والإغلاق والمناطق الزمنية.","route":"register","dependencies":["operations","locations","staff"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"schedule_id","name":"معرّف الجدول","required":true,"format":"text","example":"EXAMPLE-SCH-001"},{"id":"facility_number","name":"رقم المنشأة","required":true,"format":"integer","example":"1"},{"id":"department_name","name":"القسم","required":true,"format":"text","example":"Example Department"},{"id":"resource_name","name":"الموظف أو الغرفة","required":true,"format":"text","example":"Example Room"},{"id":"weekday","name":"يوم الأسبوع","required":true,"format":"sun / mon / tue / wed / thu / fri / sat","example":"sun"},{"id":"start_time","name":"وقت البداية","required":true,"format":"HH:MM","example":"08:00"},{"id":"end_time","name":"وقت النهاية","required":true,"format":"HH:MM","example":"17:00"},{"id":"slot_minutes","name":"مدة الموعد","required":true,"format":"integer minutes","example":"15"},{"id":"timezone","name":"المنطقة الزمنية","required":true,"format":"IANA time zone","example":"Asia/Riyadh"},{"id":"approval_reference","name":"اعتماد الجدولة","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/scheduling.csv","example":"/implementation/examples/scheduling.csv"},{"id":"interfaces","title":"مواصفات الربط","purpose":"حدد عقد الرسائل المتفق عليه. خزّن مراجع الاعتماد ولا تخزّن الأسرار نفسها.","route":"register","dependencies":["facilities","service_catalogue","source_systems"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"interface_id","name":"معرّف الربط","required":true,"format":"text","example":"EXAMPLE-IF-001"},{"id":"source_system","name":"النظام المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"target_system","name":"النظام الهدف","required":true,"format":"text","example":"MANSOQ"},{"id":"direction","name":"الاتجاه","required":true,"format":"inbound / outbound / bidirectional","example":"inbound"},{"id":"protocol_version","name":"البروتوكول والإصدار","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"message_scope","name":"نطاق الرسائل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"identifier_mapping","name":"مواءمة المعرفات","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"secret_reference","name":"مرجع مدير الأسرار","required":true,"format":"text","example":"REFERENCE-ONLY"},{"id":"retry_policy","name":"سياسة الإعادة والتكرار","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"failure_owner","name":"مسؤول الأعطال","required":true,"format":"text","example":"Integration owner"},{"id":"test_reference","name":"دليل الاختبار","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/interfaces.csv","example":"/implementation/examples/interfaces.csv"},{"id":"migration_mapping","title":"مواءمة الترحيل","purpose":"اعتمد الحقول والتحويلات وقواعد الدمج للإصدار المحدد من التطبيق.","route":"register","dependencies":["project_scope"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"dataset","name":"مجموعة البيانات","required":true,"format":"text","example":"Patient master"},{"id":"source_field","name":"حقل المصدر","required":true,"format":"text","example":"Legacy identifier"},{"id":"target_field","name":"حقل الهدف","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"transformation","name":"التحويل","required":true,"format":"text","example":"Preserve as text"},{"id":"identifier_system","name":"نظام المعرفات","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"required","name":"مطلوب","required":true,"format":"true / false","example":"true"},{"id":"null_policy","name":"سياسة القيم الفارغة","required":true,"format":"text","example":"Reject missing required ID"},{"id":"dedup_key","name":"مفتاح التكرار","required":true,"format":"text","example":"Source system + identifier"},{"id":"validation","name":"قاعدة التحقق","required":true,"format":"text","example":"No duplicate source keys"},{"id":"approval_reference","name":"اعتماد المواءمة","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/migration_mapping.csv","example":"/implementation/examples/migration_mapping.csv"},{"id":"migration_batches","title":"سجل دفعات الترحيل","purpose":"طابق السجلات وإجمالي المبالغ أو الكميات، بما فيها المرفوضة. لا تعني أعداد المثال الصفرية اكتمال الترحيل.","route":"register","dependencies":["migration_mapping"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"batch_id","name":"معرّف الدفعة","required":true,"format":"text","example":"EXAMPLE-BATCH-001"},{"id":"dataset","name":"مجموعة البيانات","required":true,"format":"text","example":"Patient master"},{"id":"file_hash","name":"بصمة الملف SHA-256","required":true,"format":"64 hex characters","example":"2825f4a89ff1b4df487b710b7af407ee007bf4b0213bf09a77352937d8c5b34c"},{"id":"source_count","name":"عدد سجلات المصدر","required":true,"format":"integer","example":"0"},{"id":"accepted_count","name":"السجلات المقبولة","required":true,"format":"integer","example":"0"},{"id":"rejected_count","name":"السجلات المرفوضة","required":true,"format":"integer","example":"0"},{"id":"control_total","name":"إجمالي مالي أو مخزني","required":true,"format":"decimal","example":"0"},{"id":"status","name":"الحالة","required":true,"format":"staged / validated / loaded / reconciled / rolled_back","example":"staged"},{"id":"rollback_reference","name":"دليل الرجوع","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approval_reference","name":"اعتماد الدفعة","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/migration_batches.csv","example":"/implementation/examples/migration_batches.csv"},{"id":"uat_cases","title":"اختبارات القبول","purpose":"سجل اختبارات كاملة للنجاح والفشل والحدود والصلاحيات والأعطال لكل منتج.","route":"register","dependencies":["project_scope","clinical_workflows"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"test_id","name":"معرّف الاختبار","required":true,"format":"text","example":"UAT-001"},{"id":"product_id","name":"معرّف المنتج","required":true,"format":"text","example":"outpatient"},{"id":"scenario","name":"السيناريو","required":true,"format":"text","example":"Visit from arrival to financial follow-up"},{"id":"preconditions","name":"الشروط المسبقة","required":true,"format":"text","example":"Approved setup and synthetic data"},{"id":"actions","name":"الإجراءات الدقيقة","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"expected_result","name":"النتيجة المتوقعة","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"actual_result","name":"النتيجة الفعلية","required":true,"format":"text","example":"NOT-RUN"},{"id":"status","name":"الحالة","required":true,"format":"not_run / pass / fail / blocked","example":"not_run"},{"id":"evidence_reference","name":"مرجع الدليل","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"approver_role","name":"المعتمد","required":true,"format":"text","example":"Product owner"}],"template":"/implementation/templates/uat_cases.csv","example":"/implementation/examples/uat_cases.csv"},{"id":"training","title":"التدريب والكفاءة","purpose":"تحقق من قدرة كل دور على العمل الطبيعي والاستثناءات وإجراءات التعطل.","route":"register","dependencies":["clinical_workflows","uat_cases"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"role","name":"الدور","required":true,"format":"text","example":"Nurse"},{"id":"workflow","name":"المسار","required":true,"format":"text","example":"Patient registration"},{"id":"trainer_role","name":"المدرّب","required":true,"format":"text","example":"Superuser"},{"id":"session_date","name":"تاريخ الجلسة","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"attendees_reference","name":"دليل الحضور","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"competency_test","name":"اختبار الكفاءة","required":true,"format":"text","example":"Complete a synthetic visit"},{"id":"result","name":"النتيجة","required":true,"format":"not_run / pass / fail","example":"not_run"},{"id":"follow_up","name":"المتابعة","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/training.csv","example":"/implementation/examples/training.csv"},{"id":"cutover_runbook","title":"التحويل والرجوع","purpose":"حدد كل إجراء للتحويل ونقطة توقف ومسؤول قرار ومسار رجوع مجرّب.","route":"register","dependencies":["uat_cases","migration_batches","training"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"sequence","name":"الترتيب","required":true,"format":"integer","example":"1"},{"id":"action","name":"الإجراء","required":true,"format":"text","example":"Confirm the change window"},{"id":"owner_role","name":"المسؤول","required":true,"format":"text","example":"Project owner"},{"id":"dependency","name":"المتطلب السابق","required":false,"format":"text","example":""},{"id":"planned_time","name":"الوقت المخطط","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T20:00:00+03:00"},{"id":"verification","name":"التحقق","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"rollback_trigger","name":"شرط الرجوع","required":true,"format":"text","example":"Critical acceptance failure"},{"id":"rollback_action","name":"إجراء الرجوع","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"approval_reference","name":"الاعتماد","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/cutover_runbook.csv","example":"/implementation/examples/cutover_runbook.csv"},{"id":"support_handover","title":"تسليم الدعم","purpose":"وثق المسؤوليات وأهداف الدعم التي يحددها العميل واختبارات الاستعادة وتجديد الشهادات. هذه القيم إعلانات من جانبك وليست أبداً مستوى خدمة من MANSOQ.","route":"register","dependencies":["cutover_runbook"],"acceptance":"ارفع في إعداد الحساب ← ملفات التنفيذ وأدلة القبول. تحفظ البيانات في سجلات تنفيذ حسابك. راجع مع المسؤول وسجّل الاعتماد ومرجع الدليل. يسجل الملف القرارات ولا يفعّل إعدادات الإنتاج تلقائياً.","columns":[{"id":"service","name":"الخدمة","required":true,"format":"text","example":"MANSOQ application"},{"id":"owner_role","name":"المسؤول","required":true,"format":"text","example":"Support lead"},{"id":"support_hours","name":"ساعات الدعم التي يحددها العميل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"severity","name":"الخطورة التي يحددها العميل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"response_target","name":"وقت الاستجابة الذي يحدده العميل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"escalation_route","name":"مسار التصعيد الذي يحدده العميل","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"monitoring_reference","name":"دليل المراقبة","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"restore_test_reference","name":"اختبار الاستعادة","required":true,"format":"text","example":"EXAMPLE-REF-002"},{"id":"renewal_owner","name":"مسؤول تجديد الشهادة أو الترخيص","required":true,"format":"text","example":"TO-CONFIRM"}],"template":"/implementation/templates/support_handover.csv","example":"/implementation/examples/support_handover.csv"},{"id":"source_systems","title":"الأنظمة الحالية وإصداراتها","purpose":"سجل تحضير الأنظمة الحالية وإصداراتها للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["project_scope"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"system_id","name":"معرف النظام","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"vendor","name":"المورد","required":true,"format":"text","example":"Epic"},{"id":"product","name":"المنتج المثبت","required":true,"format":"text","example":"Epic EHR"},{"id":"release","name":"الإصدار المثبت","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"environment","name":"البيئة","required":true,"format":"test / production / archive","example":"test"},{"id":"facility_scope","name":"المنشآت المشمولة","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"source_owner","name":"مسؤول المصدر","required":true,"format":"text","example":"Source EHR administrator"},{"id":"export_route","name":"طريقة الاستخراج","required":true,"format":"text","example":"EHI export assessment pending"},{"id":"licence_reference","name":"دليل الترخيص والوصول","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"specification_reference","name":"مواصفات الإصدار","required":true,"format":"text","example":"https://open.epic.com/TechnicalSpecifications"}],"template":"/implementation/templates/source_systems.csv","example":"/implementation/examples/source_systems.csv"},{"id":"transition_scope","title":"نطاق الترحيل أو التعايش","purpose":"سجل تحضير نطاق الترحيل أو التعايش للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["source_systems"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"scope_id","name":"معرف النطاق","required":true,"format":"text","example":"SCOPE-001"},{"id":"system_id","name":"معرف المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"action","name":"إجراء الانتقال","required":true,"format":"migration / integration / phased / consolidation / archive / carve_out / exit / recovery","example":"migration"},{"id":"data_domain","name":"مجال البيانات","required":true,"format":"text","example":"Appointments"},{"id":"facility_scope","name":"حدود المنشآت","required":true,"format":"text","example":"EXAMPLE-FACILITY-001"},{"id":"history_from","name":"بداية التاريخ","required":true,"format":"YYYY-MM-DD","example":"2020-01-01"},{"id":"history_to","name":"نهاية التاريخ","required":true,"format":"YYYY-MM-DD","example":"2026-10-09"},{"id":"target_disposition","name":"الوجهة","required":true,"format":"native / connected / archive / excluded","example":"native"},{"id":"system_of_record","name":"النظام المرجعي بعد الانتقال","required":true,"format":"text","example":"MANSOQ after acceptance"},{"id":"reason","name":"سبب الإدراج أو الاستبعاد","required":true,"format":"text","example":"Future appointment continuity"},{"id":"approval_reference","name":"اعتماد النطاق","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/transition_scope.csv","example":"/implementation/examples/transition_scope.csv"},{"id":"export_inventory","title":"ملفات الاستخراج وبصماتها","purpose":"سجل تحضير ملفات الاستخراج وبصماتها للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"migration","dependencies":["transition_scope"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"export_id","name":"معرف الاستخراج","required":true,"format":"text","example":"EXPORT-001"},{"id":"system_id","name":"معرف المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope_id","name":"معرف النطاق","required":true,"format":"text","example":"SCOPE-001"},{"id":"format","name":"التنسيق الفعلي","required":true,"format":"CSV / TSV / NDJSON / XML / DICOM / PDF / native / other","example":"TSV"},{"id":"secure_file_reference","name":"مرجع الملف الآمن","required":true,"format":"text","example":"secure-workspace://EXAMPLE/export-001"},{"id":"sha256","name":"بصمة SHA-256","required":true,"format":"64 hex characters","example":"390a3d2a42b21012c44c65170f00cb0129db59d9b4b9e67193e195fa81c1bd09"},{"id":"expected_records","name":"عدد السجلات أو الكائنات","required":true,"format":"integer","example":"120"},{"id":"extracted_at","name":"وقت الاستخراج","required":true,"format":"ISO 8601 with offset","example":"2026-10-09T18:00:00+03:00"},{"id":"dictionary_reference","name":"قاموس الاستخراج","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"transfer_approval","name":"اعتماد النقل","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/export_inventory.csv","example":"/implementation/examples/export_inventory.csv"},{"id":"identity_rules","title":"قواعد مطابقة هوية المريض","purpose":"سجل تحضير قواعد مطابقة هوية المريض للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"migration","dependencies":["source_systems","transition_scope"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"rule_id","name":"معرف قاعدة المطابقة","required":true,"format":"text","example":"MATCH-001"},{"id":"system_id","name":"معرف المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"identifier_namespace","name":"نطاق المعرف","required":true,"format":"text","example":"EXAMPLE-HOSPITAL-MRN"},{"id":"match_method","name":"طريقة المطابقة","required":true,"format":"verified_identifier / reviewed_crosswalk / manual_review","example":"verified_identifier"},{"id":"normalization_rule","name":"قاعدة توحيد الصيغة","required":true,"format":"text","example":"Preserve original; compare approved canonical form"},{"id":"exception_policy","name":"معالجة الهوية الناقصة أو الملتبسة","required":true,"format":"text","example":"Quarantine and refer to identity steward"},{"id":"crosswalk_reference","name":"مرجع المطابقة الآمن","required":true,"format":"text","example":"secure-workspace://EXAMPLE/crosswalk-schema"},{"id":"approver_role","name":"مسؤول اعتماد الهوية","required":true,"format":"text","example":"Health information management"},{"id":"acceptance_reference","name":"دليل المطابقة","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/identity_rules.csv","example":"/implementation/examples/identity_rules.csv"},{"id":"terminology_mapping","title":"مواءمة المصطلحات والوحدات","purpose":"سجل تحضير مواءمة المصطلحات والوحدات للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"migration","dependencies":["transition_scope","service_catalogue"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"mapping_id","name":"معرف المواءمة","required":true,"format":"text","example":"MAP-TERM-001"},{"id":"system_id","name":"معرف المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"domain","name":"المجال","required":true,"format":"text","example":"Laboratory result"},{"id":"source_system","name":"نظام ترميز المصدر","required":true,"format":"text","example":"EXAMPLE-LOCAL-LAB"},{"id":"source_code","name":"رمز المصدر","required":true,"format":"text","example":"EXAMPLE-LAB-001"},{"id":"target_system","name":"نظام ترميز الوجهة","required":false,"format":"text","example":""},{"id":"target_code","name":"رمز الوجهة","required":false,"format":"text","example":""},{"id":"equivalence","name":"نوع التكافؤ","required":true,"format":"exact / broader / narrower / unmapped","example":"unmapped"},{"id":"unit_rule","name":"قاعدة الوحدة أو التحويل","required":true,"format":"text","example":"No conversion until laboratory approval"},{"id":"approval_reference","name":"اعتماد المصطلحات","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/terminology_mapping.csv","example":"/implementation/examples/terminology_mapping.csv"},{"id":"data_reconciliation","title":"مطابقة بيانات الترحيل","purpose":"سجل تحضير مطابقة بيانات الترحيل للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"migration","dependencies":["export_inventory","migration_batches"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"check_id","name":"معرف الفحص","required":true,"format":"text","example":"REC-001"},{"id":"scope_id","name":"معرف النطاق","required":true,"format":"text","example":"SCOPE-001"},{"id":"batch_id","name":"معرف دفعة الترحيل","required":true,"format":"text","example":"EXAMPLE-BATCH-001"},{"id":"measure","name":"مقياس المطابقة","required":true,"format":"text","example":"Future appointment count"},{"id":"source_value","name":"إجمالي المصدر","required":true,"format":"decimal","example":"120"},{"id":"target_value","name":"إجمالي الوجهة","required":true,"format":"decimal","example":"118"},{"id":"held_or_rejected","name":"الإجمالي المعلق أو المرفوض","required":true,"format":"decimal","example":"2"},{"id":"tolerance","name":"التفاوت المعتمد","required":true,"format":"decimal","example":"0"},{"id":"status","name":"حالة المراجعة","required":true,"format":"open / passed / failed / waived","example":"open"},{"id":"evidence_reference","name":"مرجع التقرير أو الدليل","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/data_reconciliation.csv","example":"/implementation/examples/data_reconciliation.csv"},{"id":"integration_scopes","title":"نطاق الربط والمسؤولية","purpose":"سجل تحضير نطاق الربط والمسؤولية للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["source_systems","transition_scope"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"interface_id","name":"معرف الربط","required":true,"format":"text","example":"IFACE-001"},{"id":"system_id","name":"معرف النظام الحالي","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope","name":"نطاق الربط","required":true,"format":"identity_adt / clinical_read / orders_results / medications / appointments / revenue / imaging_devices / finance_inventory / sso","example":"orders_results"},{"id":"direction","name":"الاتجاه","required":true,"format":"inbound / outbound / bidirectional","example":"inbound"},{"id":"cadence","name":"نمط الإرسال","required":true,"format":"event / scheduled / on_demand","example":"event"},{"id":"system_of_record","name":"النظام المخول بالكتابة","required":true,"format":"text","example":"Existing EHR owns orders; MANSOQ reviews results"},{"id":"owner_role","name":"مسؤول تشغيل الربط","required":true,"format":"text","example":"Integration operations"},{"id":"approval_reference","name":"اعتماد نطاق الربط","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/integration_scopes.csv","example":"/implementation/examples/integration_scopes.csv"},{"id":"interface_contracts","title":"عقود ومواصفات الربط","purpose":"سجل تحضير عقود ومواصفات الربط للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["integration_scopes"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"interface_id","name":"معرف الربط","required":true,"format":"text","example":"IFACE-001"},{"id":"protocol","name":"البروتوكول أو الملف","required":true,"format":"text","example":"HL7 v2.5.1 ORU assessment pending"},{"id":"specification_reference","name":"مرجع المواصفات","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"acknowledgement_rule","name":"قاعدة التأكيد","required":true,"format":"text","example":"Application acceptance before completed status"},{"id":"deduplication_rule","name":"قاعدة منع التكرار","required":true,"format":"text","example":"Source event ID plus version; retain processed receipt"},{"id":"conflict_rule","name":"قاعدة التعارض أو التصحيح","required":true,"format":"text","example":"Source owns result corrections; quarantine identity conflicts"},{"id":"retry_limit","name":"حد إعادة المحاولة","required":true,"format":"integer","example":"3"},{"id":"latency_target","name":"هدف وصول البيانات","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"downtime_route","name":"مسار التعطل وإعادة الإرسال","required":true,"format":"text","example":"Documented downtime queue; replay after owner review"},{"id":"approval_reference","name":"اعتماد المواصفات","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/interface_contracts.csv","example":"/implementation/examples/interface_contracts.csv"},{"id":"endpoint_access","title":"سجل الوصول إلى نقاط الربط","purpose":"سجل تحضير سجل الوصول إلى نقاط الربط للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["interface_contracts"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"interface_id","name":"معرف الربط","required":true,"format":"text","example":"IFACE-001"},{"id":"environment","name":"البيئة","required":true,"format":"test / production","example":"test"},{"id":"endpoint_reference","name":"مرجع نقطة الربط","required":true,"format":"text","example":"EXAMPLE-ENDPOINT-REF-001"},{"id":"auth_method","name":"طريقة المصادقة","required":true,"format":"text","example":"vendor-approved-oauth"},{"id":"credential_reference","name":"مرجع مدير بيانات الاعتماد","required":true,"format":"text","example":"EXAMPLE-SECRET-REF-001"},{"id":"access_scope","name":"نطاق الوصول الممنوح","required":true,"format":"text","example":"Test-only read scope pending approval"},{"id":"network_approval","name":"دليل الشبكة والتشفير","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"rotation_owner","name":"مسؤول التجديد","required":true,"format":"text","example":"Security operations"},{"id":"approval_reference","name":"اعتماد الوصول","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/endpoint_access.csv","example":"/implementation/examples/endpoint_access.csv"},{"id":"message_mapping","title":"مواءمة الأحداث والحقول","purpose":"سجل تحضير مواءمة الأحداث والحقول للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["interface_contracts","terminology_mapping"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"interface_id","name":"معرف الربط","required":true,"format":"text","example":"IFACE-001"},{"id":"event","name":"الحدث أو المورد","required":true,"format":"text","example":"Result update"},{"id":"source_path","name":"مسار حقل المصدر","required":true,"format":"text","example":"EXAMPLE-source-result-code"},{"id":"target_path","name":"حقل أو إجراء الوجهة المتحقق","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"transform_rule","name":"قاعدة التحويل والتحقق","required":true,"format":"text","example":"Approved code and unit mapping; preserve source value"},{"id":"required","name":"حقل إلزامي","required":true,"format":"true / false","example":"true"},{"id":"rejection_route","name":"معالجة البيانات غير الصالحة","required":true,"format":"text","example":"Quarantine; notify interface owner; no clinical write"},{"id":"approval_reference","name":"اعتماد المواءمة","required":true,"format":"text","example":"EXAMPLE-REF-001"}],"template":"/implementation/templates/message_mapping.csv","example":"/implementation/examples/message_mapping.csv"},{"id":"interface_tests","title":"اختبارات قبول الربط","purpose":"سجل تحضير اختبارات قبول الربط للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["message_mapping","endpoint_access"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"test_id","name":"معرف الاختبار","required":true,"format":"text","example":"IF-TEST-001"},{"id":"interface_id","name":"معرف الربط","required":true,"format":"text","example":"IFACE-001"},{"id":"scenario","name":"السيناريو","required":true,"format":"text","example":"Duplicate corrected laboratory result"},{"id":"fixture_reference","name":"مرجع بيانات الاختبار","required":true,"format":"text","example":"secure-test://EXAMPLE/corrected-result"},{"id":"expected","name":"السلوك المتوقع","required":true,"format":"text","example":"One corrected result; no duplicate charge; receipt logged"},{"id":"status","name":"حالة التنفيذ","required":true,"format":"not_run / passed / failed / blocked","example":"not_run"},{"id":"evidence_reference","name":"دليل الاختبار","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"owner_role","name":"مسؤول الاختبار","required":true,"format":"text","example":"Clinical and integration owners"}],"template":"/implementation/templates/interface_tests.csv","example":"/implementation/examples/interface_tests.csv"},{"id":"archive_retention","title":"الأرشفة والاحتفاظ والخروج","purpose":"سجل تحضير الأرشفة والاحتفاظ والخروج للترحيل أو الربط. يحدد النطاق والمتطلبات والأدلة دون نقل بيانات المرضى أو تفعيل اتصال تلقائياً.","route":"register","dependencies":["transition_scope","data_reconciliation"],"acceptance":"ارفع سجل التحضير في إعداد الحساب ← ملفات التنفيذ وأدلة القبول، ثم عاين وطبّق واحفظ. تحفظ الملفات السريرية وسجلات مطابقة الهوية في مساحة الترحيل الآمنة المعتمدة. سجّل مراجع الأدلة الفعلية بعد المراجعة؛ لا يشغّل السجل موصلاً ولا يستورد تاريخ المرضى.","columns":[{"id":"archive_id","name":"معرف الأرشيف","required":true,"format":"text","example":"ARCH-001"},{"id":"system_id","name":"معرف المصدر","required":true,"format":"text","example":"SRC-EPIC-001"},{"id":"scope_id","name":"معرف النطاق","required":true,"format":"text","example":"SCOPE-001"},{"id":"retention_rule","name":"قاعدة الاحتفاظ المعتمدة","required":true,"format":"text","example":"TO-CONFIRM by records/privacy owner"},{"id":"access_rule","name":"قاعدة الوصول للقراءة","required":true,"format":"text","example":"Approved care team access with audit"},{"id":"restore_test_reference","name":"اختبار استرجاع الأرشيف","required":true,"format":"text","example":"EXAMPLE-REF-001"},{"id":"exit_format","name":"تنسيق الخروج","required":true,"format":"text","example":"TO-CONFIRM"},{"id":"decommission_gate","name":"شرط إيقاف المصدر","required":true,"format":"text","example":"Acceptance, legal hold review and archive access approved"},{"id":"owner_role","name":"مسؤول الأرشيف","required":true,"format":"text","example":"Records and privacy owners"},{"id":"approval_reference","name":"اعتماد الأرشفة أو الخروج","required":true,"format":"text","example":"EXAMPLE-REF-002"}],"template":"/implementation/templates/archive_retention.csv","example":"/implementation/examples/archive_retention.csv"}]}}},{"slug":"/saudi","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/saudi","title":"NPHIES, ZATCA & Saudi billing compatibility | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Designed and refined in Al Diriyah, with Arabic/English experiences and precise NPHIES, ZATCA, SBS and DRG scope.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Designed and refined in Al Diriyah, with Arabic/English experiences and precise NPHIES, ZATCA, SBS and DRG scope.","description":"Explore NPHIES eligibility, authorization and claims, ZATCA e-invoicing, SBS service mapping and DRG scope. Review onboarding, release and activation requirements.","answers":[{"question":"Does mentioning NPHIES or ZATCA establish live certification?","answer":"No. Confirm the selected capability, release, licensed catalogue, credentials, onboarding and accepted production tests. NPHIES eligibility, authorization and claims, ZATCA e-invoicing, SBS mapping and DRG grouping each have their own scope and activation requirements.","href":"/resources/implementation"}],"overview":{"title":"Built here. Connected to Saudi healthcare.","summary":"National exchanges, invoicing and clinical standards, with clear scope.","areas":[{"name":"NPHIES","purpose":"Eligibility, authorizations and claims exchange.","functions":[],"details":"/integrations/nphies"},{"name":"ZATCA","purpose":"Electronic invoices connected to your billing flow.","functions":[],"details":"/integrations/zatca"},{"name":"HL7 FHIR","purpose":"Clinical resources and supported APIs for connected systems.","functions":[],"details":"/platform/integrations"},{"name":"SBS","purpose":"Service-code mapping and supported catalogue tooling.","functions":[],"details":"/platform/sbs-coding"},{"name":"DRG & casemix","purpose":"Coding workflows and defined grouper integration.","functions":[],"details":"/platform/drg"}]}},"ar":{"url":"https://mansoq.com/saudi?lang=ar","title":"نفيس وزاتكا والتوافق مع نظام الفوترة السعودي | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"صُمم وطُور في الدرعية، مع تجارب بالعربية والإنجليزية ونطاق دقيق لنفيس وزاتكا وSBS وDRG.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"صُمم وطُور في الدرعية، مع تجارب بالعربية والإنجليزية ونطاق دقيق لنفيس وزاتكا وSBS وDRG.","description":"استكشف أهلية نفيس والموافقات والمطالبات وفواتير زاتكا ومواءمة SBS ونطاق DRG، مع متطلبات التسجيل والإصدار والتفعيل.","answers":[{"question":"هل ذكر نفيس أو زاتكا يثبت اعتماد الاتصال الفعلي؟","answer":"لا. أكد القدرة والإصدار والكتالوج المرخص والاعتمادات والتسجيل واختبارات الإنتاج المقبولة. لأهلية نفيس والموافقات والمطالبات وفواتير زاتكا ومواءمة SBS وتجميع DRG نطاق ومتطلبات تفعيل مستقلة.","href":"/resources/implementation"}],"overview":{"title":"بُني هنا. متصل بالرعاية السعودية.","summary":"التبادل الوطني والفوترة والمعايير السريرية بنطاق واضح.","areas":[{"name":"نفيس","purpose":"تبادل الأهلية والموافقات والمطالبات.","functions":[],"details":"/integrations/nphies"},{"name":"زاتكا","purpose":"فواتير إلكترونية مرتبطة بمسار الفوترة.","functions":[],"details":"/integrations/zatca"},{"name":"HL7 FHIR","purpose":"موارد سريرية وواجهات مدعومة للأنظمة المترابطة.","functions":[],"details":"/platform/integrations"},{"name":"SBS","purpose":"مواءمة أكواد الخدمات وأدوات الكتالوج المدعوم.","functions":[],"details":"/platform/sbs-coding"},{"name":"DRG ومزيج الحالات","purpose":"مسارات الترميز وتكامل التجميع المحدد.","functions":[],"details":"/platform/drg"}]}}},{"slug":"/solutions","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions","title":"Hospital, clinic & specialist healthcare solutions | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Find a familiar care setting, then explore the people, workflow and product composition behind it.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Find a familiar care setting, then explore the people, workflow and product composition behind it.","description":"Explore MANSOQ for hospitals, clinics, polyclinics, medical cities, TeleICU and home and palliative care. Review coverage, complete cases and tailored packages.","answers":[],"overview":{"title":"Your care setting. Fully connected.","summary":"Explore the people, departments and workflows in your organization.","areas":[{"name":"Hospitals","purpose":"Admissions, wards and departments connected around each person.","functions":[],"details":"/solutions/hospitals"},{"name":"Clinics","purpose":"A clear outpatient journey from arrival to financial follow-up.","functions":[],"details":"/solutions/clinics"},{"name":"Polyclinics","purpose":"Connect specialties while keeping the shared patient and financial context.","functions":[],"details":"/solutions/polyclinics"},{"name":"Medical Cities","purpose":"A governed network composition with clear entity and record boundaries.","functions":[],"details":"/solutions/medical-city"},{"name":"TeleICU","purpose":"A defined remote critical-care composition around the local team.","functions":[],"details":"/solutions/teleicu"},{"name":"Home & Palliative Care","purpose":"Continuity across visits, care plans and multidisciplinary handovers.","functions":[],"details":"/solutions/home-palliative"}]}},"ar":{"url":"https://mansoq.com/solutions?lang=ar","title":"حلول المستشفيات والعيادات والرعاية التخصصية | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"حدد بيئة رعاية مألوفة ثم استكشف الأشخاص ومسار العمل وتكوين المنتجات خلفها.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"حدد بيئة رعاية مألوفة ثم استكشف الأشخاص ومسار العمل وتكوين المنتجات خلفها.","description":"استكشف منسوق للمستشفيات والعيادات والمجمعات والمدن الطبية والعناية عن بُعد والرعاية المنزلية والتلطيفية، مع التغطية والحالات والحزم.","answers":[],"overview":{"title":"بيئة رعايتك. مترابطة بالكامل.","summary":"استكشف الأشخاص والأقسام ومسارات العمل في منشأتك.","areas":[{"name":"المستشفيات","purpose":"التنويم والأجنحة والأقسام متصلة حول كل شخص.","functions":[],"details":"/solutions/hospitals"},{"name":"العيادات","purpose":"مسار واضح للعيادة من الوصول إلى المتابعة المالية.","functions":[],"details":"/solutions/clinics"},{"name":"المجمعات الطبية","purpose":"اربط التخصصات مع الحفاظ على سياق المريض والمالية المشترك.","functions":[],"details":"/solutions/polyclinics"},{"name":"المدن الطبية","purpose":"تكوين شبكة خاضع للحوكمة بحدود واضحة للكيانات والسجلات.","functions":[],"details":"/solutions/medical-city"},{"name":"العناية المركزة عن بُعد","purpose":"تهيئة محددة للعناية الحرجة عن بُعد حول الفريق المحلي.","functions":[],"details":"/solutions/teleicu"},{"name":"الرعاية المنزلية والتلطيفية","purpose":"استمرارية عبر الزيارات وخطط الرعاية وتسليم المسؤوليات بين التخصصات.","functions":[],"details":"/solutions/home-palliative"}]}}},{"slug":"/solutions/clinics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/clinics","title":"Clinics management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"A clear outpatient journey from arrival to financial follow-up.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A clear outpatient journey from arrival to financial follow-up.","description":"From the first appointment to follow-up and payment, bring the whole visit into one clinical and financial context. Appointments & arrival, Clinical consultation, Orders &…","answers":[{"question":"Which workflows does this solution connect?","answer":"Appointments & arrival: Connect scheduling, registration, queues and the encounter. Clinical consultation: Bring relevant history, documentation and care planning into the clinician’s workflow. Orders & medication: Keep orders, available results and prescriptions linked to the visit. Visit continuity: Keep follow-up documentation and the next encounter in the patient’s care context. Billing & payment: Connect visit activity to invoices, patient liability and payments. Insurance & collections: Follow coverage, authorizations, claims and reconciliation with clear responsibilities.","href":"/solutions/clinics"},{"question":"Where can I see complete operational scenarios?","answer":"The first visit: A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps. A follow-up with context: A returning patient has a follow-up consultation after earlier testing. The clinician needs the prior plan and available results beside today’s record. From order to review: During a consultation, a clinician requests a test and prescribes medication. Each request needs an owner and a return path to the visit. An insured visit, followed through: An insured patient attends a clinic. Reception verifies coverage, the revenue team follows the required approval and the claim is reconciled after the visit.","href":"/solutions/clinics#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=clinics#configuration"}],"solution":{"coverage":[{"name":"Appointments & arrival","description":"Connect scheduling, registration, queues and the encounter.","products":["outpatient","patient_access"]},{"name":"Clinical consultation","description":"Bring relevant history, documentation and care planning into the clinician’s workflow.","products":["outpatient","clinical_documentation"]},{"name":"Orders & medication","description":"Keep orders, available results and prescriptions linked to the visit.","products":["orders_medication"]},{"name":"Visit continuity","description":"Keep follow-up documentation and the next encounter in the patient’s care context.","products":["outpatient","clinical_documentation","core"]},{"name":"Billing & payment","description":"Connect visit activity to invoices, patient liability and payments.","products":["billing_finance"]},{"name":"Insurance & collections","description":"Follow coverage, authorizations, claims and reconciliation with clear responsibilities.","products":["revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"The first visit","scenario":"A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps.","challenge":"Reception, consultation and payment should describe the same visit.","stages":[{"title":"Arrange the appointment","action":"Connect the appointment to the selected service and patient identity.","owner":"Access & coordination","record":"Appointment · Service · Identity"},{"title":"Register the arrival","action":"Confirm the shared patient record and establish the outpatient encounter and financial context.","owner":"Access & coordination","record":"Patient record · Encounter · Payer"},{"title":"Document the consultation","action":"Review the available history and record the assessment and agreed care plan.","owner":"Treating clinician","record":"History · Clinical note · Care plan"},{"title":"Connect requests and medication","action":"Attach the clinician’s orders and prescriptions to the consultation context.","owner":"Treating clinician","record":"Orders · Prescription · Encounter"},{"title":"Complete visit billing","action":"Review recorded services, patient contribution and payment against the encounter.","owner":"Finance team","record":"Services · Invoice · Payment"},{"title":"Arrange the next visit","action":"Record the next appointment or follow-up responsibility with the consultation’s care context.","owner":"Access & coordination","record":"Follow-up · Responsible service"}],"exception":"If the patient already has a record, verify the identity before continuing so the new encounter follows the correct history.","completion":["A complete visit record from arrival to follow-up.","Orders remain linked to the consultation that created them.","The account reflects the documented visit activity."]},{"type":"Illustrative operational scenario","title":"A follow-up with context","scenario":"A returning patient has a follow-up consultation after earlier testing. The clinician needs the prior plan and available results beside today’s record.","challenge":"A follow-up should build on the previous visit instead of restarting the story.","stages":[{"title":"Identify the returning patient","action":"Confirm the patient and connect the new appointment to the existing record.","owner":"Access & coordination","record":"Identity · Appointment · Prior encounters"},{"title":"Review the earlier plan","action":"Review the prior consultation and its recorded follow-up reason.","owner":"Treating clinician","record":"Previous note · Follow-up reason"},{"title":"Review available results","action":"Review relevant available results and record their interpretation in today’s consultation.","owner":"Treating clinician","record":"Results · Review note"},{"title":"Update the care plan","action":"Document the current assessment and the clinician’s changes to orders or medication.","owner":"Treating clinician","record":"Assessment · Updated plan · Orders"},{"title":"Complete the encounter account","action":"Link today’s recorded service and payment responsibility to the follow-up encounter.","owner":"Finance team","record":"Follow-up service · Account"},{"title":"Set the next responsibility","action":"Record the next appointment, referral or documented follow-up action.","owner":"Access & coordination","record":"Next appointment · Referral · Owner"}],"exception":"When a result has not arrived, record the pending item and the responsible follow-up; do not present it as reviewed.","completion":["Previous and current consultations remain connected.","Result review has documented clinical responsibility.","The next care action is explicit."]},{"type":"Illustrative operational scenario","title":"From order to review","scenario":"During a consultation, a clinician requests a test and prescribes medication. Each request needs an owner and a return path to the visit.","challenge":"A request is useful when the result or medication step returns to the care context.","stages":[{"title":"Open the consultation context","action":"Review the patient record and the current consultation before creating a request.","owner":"Treating clinician","record":"Patient · Consultation"},{"title":"Record the diagnostic order","action":"Connect the requested service and documented clinical context to the encounter.","owner":"Treating clinician","record":"Order · Service · Clinical context"},{"title":"Record the prescription","action":"Document the clinician’s prescription and its encounter reference.","owner":"Treating clinician","record":"Prescription · Encounter reference"},{"title":"Route the departmental work","action":"Use the selected native department or agreed external connection to carry the request.","owner":"Department team","record":"Request · Department or interface"},{"title":"Review the returned information","action":"Review available results in the encounter and document the next clinical action.","owner":"Treating clinician","record":"Result · Review · Next action"},{"title":"Complete follow-up and billing","action":"Review delivered service charges while the care team records remaining follow-up responsibilities.","owner":"Finance team","record":"Charges · Pending work · Follow-up"}],"exception":"External diagnostics and dispensing require an agreed interface or documented handover; an order alone does not imply a native laboratory or pharmacy.","completion":["Requests can be traced back to their consultation.","Available results have an accountable review step.","Remaining work and charges stay in the same context."]},{"type":"Illustrative operational scenario","title":"An insured visit, followed through","scenario":"An insured patient attends a clinic. Reception verifies coverage, the revenue team follows the required approval and the claim is reconciled after the visit.","challenge":"Care activity, payer decisions and the patient’s contribution must remain traceable together.","stages":[{"title":"Verify eligibility","action":"Check coverage and retain the response with the patient and encounter context.","owner":"Access & coordination","record":"Coverage · Eligibility response"},{"title":"Follow the required approval","action":"Record the preauthorization request, payer response and next responsibility where required.","owner":"Revenue team","record":"Request · Approval status · Owner"},{"title":"Document the delivered consultation","action":"Record the consultation and services in the same outpatient encounter.","owner":"Treating clinician","record":"Clinical note · Service record"},{"title":"Review charge and contribution","action":"Apply the agreed contract and tariff context to reviewed charges and patient liability.","owner":"Revenue team","record":"Tariff · Charge · Patient contribution"},{"title":"Follow the claim response","action":"Review the claim work queue and payer response, assigning any correction to its owner.","owner":"Revenue team","record":"Claim · Response · Correction"},{"title":"Reconcile the financial response","action":"Match remittance and payments to the claim and encounter; identify unresolved differences.","owner":"Finance team","record":"Remittance · Allocation · Reconciliation"}],"exception":"A rejection remains a work item with its reason, correction and resubmission history. NPHIES exchange is used only in the selected, activated scope.","completion":["Coverage and approval are connected to the visit.","Payer responses have a documented next action.","The encounter’s financial position can be reviewed."]}]}},"ar":{"url":"https://mansoq.com/solutions/clinics?lang=ar","title":"العيادات | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"مسار واضح للعيادة من الوصول إلى المتابعة المالية.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"مسار واضح للعيادة من الوصول إلى المتابعة المالية.","description":"من الموعد الأول إلى المتابعة والدفع، اجمع الزيارة كاملة ضمن سياق سريري ومالي واحد. المواعيد والوصول، الاستشارة السريرية، الطلبات والأدوية، استمرارية الزيارة، الفوترة والدفع،…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"المواعيد والوصول: اربط الجدولة والتسجيل والطوابير والزيارة. الاستشارة السريرية: أدخل التاريخ ذي الصلة والتوثيق وتخطيط الرعاية في عمل الطبيب. الطلبات والأدوية: احتفظ بالطلبات والنتائج المتاحة والوصفات مرتبطة بالزيارة. استمرارية الزيارة: احتفظ بتوثيق المتابعة والزيارة التالية ضمن سياق رعاية المريض. الفوترة والدفع: اربط نشاط الزيارة بالفواتير والتزام المريض والمدفوعات. التأمين والتحصيل: تابع التغطية والموافقات والمطالبات والمطابقة بمسؤوليات واضحة.","href":"/solutions/clinics"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"الزيارة الأولى: يحجز مريض جديد استشارة ويصل إلى العيادة ويتلقى خطة رعاية موثقة ويكمل الخطوات المالية للزيارة. متابعة بسياق واضح: يعود مريض لاستشارة متابعة بعد فحوص سابقة. يحتاج الطبيب إلى الخطة السابقة والنتائج المتاحة بجانب سجل اليوم. من الطلب إلى المراجعة: يطلب طبيب فحصاً ويصف دواء أثناء الاستشارة. يحتاج كل طلب إلى مسؤول ومسار عودة إلى الزيارة. زيارة مؤمّنة بمتابعة كاملة: يحضر مريض مؤمّن إلى عيادة. يتحقق الاستقبال من التغطية ويتابع فريق الإيرادات الموافقة المطلوبة وتُطابق المطالبة بعد الزيارة.","href":"/solutions/clinics#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=clinics#configuration"}],"solution":{"coverage":[{"name":"المواعيد والوصول","description":"اربط الجدولة والتسجيل والطوابير والزيارة.","products":["outpatient","patient_access"]},{"name":"الاستشارة السريرية","description":"أدخل التاريخ ذي الصلة والتوثيق وتخطيط الرعاية في عمل الطبيب.","products":["outpatient","clinical_documentation"]},{"name":"الطلبات والأدوية","description":"احتفظ بالطلبات والنتائج المتاحة والوصفات مرتبطة بالزيارة.","products":["orders_medication"]},{"name":"استمرارية الزيارة","description":"احتفظ بتوثيق المتابعة والزيارة التالية ضمن سياق رعاية المريض.","products":["outpatient","clinical_documentation","core"]},{"name":"الفوترة والدفع","description":"اربط نشاط الزيارة بالفواتير والتزام المريض والمدفوعات.","products":["billing_finance"]},{"name":"التأمين والتحصيل","description":"تابع التغطية والموافقات والمطالبات والمطابقة بمسؤوليات واضحة.","products":["revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"الزيارة الأولى","scenario":"يحجز مريض جديد استشارة ويصل إلى العيادة ويتلقى خطة رعاية موثقة ويكمل الخطوات المالية للزيارة.","challenge":"يجب أن يصف الاستقبال والاستشارة والدفع الزيارة نفسها.","stages":[{"title":"تنظيم الموعد","action":"ربط الموعد بالخدمة المحددة وهوية المريض.","owner":"الاستقبال والتنسيق","record":"الموعد · الخدمة · الهوية"},{"title":"تسجيل الوصول","action":"تأكيد سجل المريض المشترك وتأسيس زيارة العيادة وسياقها المالي.","owner":"الاستقبال والتنسيق","record":"سجل المريض · الزيارة · الجهة الدافعة"},{"title":"توثيق الاستشارة","action":"مراجعة التاريخ المتاح وتسجيل التقييم وخطة الرعاية المتفق عليها.","owner":"الطبيب المعالج","record":"التاريخ · التوثيق السريري · خطة الرعاية"},{"title":"ربط الطلبات والأدوية","action":"إرفاق طلبات الطبيب ووصفاته بسياق الاستشارة.","owner":"الطبيب المعالج","record":"الطلبات · الوصفة · الزيارة"},{"title":"إنجاز فوترة الزيارة","action":"مراجعة الخدمات المسجلة ومساهمة المريض والدفع مقابل الزيارة.","owner":"الفريق المالي","record":"الخدمات · الفاتورة · الدفع"},{"title":"تنظيم الزيارة التالية","action":"تسجيل الموعد التالي أو مسؤولية المتابعة مع سياق رعاية الاستشارة.","owner":"الاستقبال والتنسيق","record":"المتابعة · الخدمة المسؤولة"}],"exception":"إذا كان للمريض سجل سابق، تُتحقق الهوية قبل المتابعة لتتبع الزيارة الجديدة التاريخ الصحيح.","completion":["سجل زيارة كامل من الوصول إلى المتابعة.","تظل الطلبات مرتبطة بالاستشارة التي أنشأتها.","يعكس الحساب نشاط الزيارة الموثق."]},{"type":"Illustrative operational scenario","title":"متابعة بسياق واضح","scenario":"يعود مريض لاستشارة متابعة بعد فحوص سابقة. يحتاج الطبيب إلى الخطة السابقة والنتائج المتاحة بجانب سجل اليوم.","challenge":"يجب أن تبني المتابعة على الزيارة السابقة بدلاً من بدء القصة من جديد.","stages":[{"title":"تحديد المريض العائد","action":"تأكيد المريض وربط الموعد الجديد بالسجل القائم.","owner":"الاستقبال والتنسيق","record":"الهوية · الموعد · الزيارات السابقة"},{"title":"مراجعة الخطة السابقة","action":"مراجعة الاستشارة السابقة وسبب المتابعة المسجل.","owner":"الطبيب المعالج","record":"التوثيق السابق · سبب المتابعة"},{"title":"مراجعة النتائج المتاحة","action":"مراجعة النتائج المتاحة ذات الصلة وتسجيل تفسيرها في استشارة اليوم.","owner":"الطبيب المعالج","record":"النتائج · ملاحظة المراجعة"},{"title":"تحديث خطة الرعاية","action":"توثيق التقييم الحالي وتعديلات الطبيب على الطلبات أو الأدوية.","owner":"الطبيب المعالج","record":"التقييم · الخطة المحدثة · الطلبات"},{"title":"إنجاز حساب الزيارة","action":"ربط خدمة اليوم المسجلة ومسؤولية الدفع بزيارة المتابعة.","owner":"الفريق المالي","record":"خدمة المتابعة · الحساب"},{"title":"تحديد المسؤولية التالية","action":"تسجيل الموعد التالي أو الإحالة أو إجراء المتابعة الموثق.","owner":"الاستقبال والتنسيق","record":"الموعد التالي · الإحالة · المسؤول"}],"exception":"عندما لا تصل نتيجة، يُسجل العنصر المعلق ومسؤول المتابعة ولا يُعرض على أنه تمت مراجعته.","completion":["تظل الاستشارة السابقة والحالية مترابطتين.","لمراجعة النتائج مسؤولية سريرية موثقة.","إجراء الرعاية التالي محدد بوضوح."]},{"type":"Illustrative operational scenario","title":"من الطلب إلى المراجعة","scenario":"يطلب طبيب فحصاً ويصف دواء أثناء الاستشارة. يحتاج كل طلب إلى مسؤول ومسار عودة إلى الزيارة.","challenge":"يكون الطلب مفيداً عندما تعود النتيجة أو خطوة الدواء إلى سياق الرعاية.","stages":[{"title":"فتح سياق الاستشارة","action":"مراجعة سجل المريض والاستشارة الحالية قبل إنشاء الطلب.","owner":"الطبيب المعالج","record":"المريض · الاستشارة"},{"title":"تسجيل طلب التشخيص","action":"ربط الخدمة المطلوبة والسياق السريري الموثق بالزيارة.","owner":"الطبيب المعالج","record":"الطلب · الخدمة · السياق السريري"},{"title":"تسجيل الوصفة","action":"توثيق وصفة الطبيب ومرجع زيارتها.","owner":"الطبيب المعالج","record":"الوصفة · مرجع الزيارة"},{"title":"توجيه عمل القسم","action":"استخدام القسم الداخلي المحدد أو الاتصال الخارجي المتفق عليه لنقل الطلب.","owner":"فريق القسم","record":"الطلب · القسم أو الاتصال"},{"title":"مراجعة المعلومات العائدة","action":"مراجعة النتائج المتاحة في الزيارة وتوثيق الإجراء السريري التالي.","owner":"الطبيب المعالج","record":"النتيجة · المراجعة · الإجراء التالي"},{"title":"إنجاز المتابعة والفوترة","action":"مراجعة رسوم الخدمات المنجزة بينما يسجل فريق الرعاية مسؤوليات المتابعة المتبقية.","owner":"الفريق المالي","record":"الرسوم · العمل المعلق · المتابعة"}],"exception":"يتطلب التشخيص والصرف الخارجيان اتصالاً متفقاً عليه أو تسليماً موثقاً؛ فالطلب وحده لا يعني وجود مختبر أو صيدلية داخليين.","completion":["يمكن تتبع الطلبات إلى استشارتها.","للنتائج المتاحة خطوة مراجعة بمسؤولية واضحة.","يبقى العمل المتبقي والرسوم في السياق نفسه."]},{"type":"Illustrative operational scenario","title":"زيارة مؤمّنة بمتابعة كاملة","scenario":"يحضر مريض مؤمّن إلى عيادة. يتحقق الاستقبال من التغطية ويتابع فريق الإيرادات الموافقة المطلوبة وتُطابق المطالبة بعد الزيارة.","challenge":"يجب أن تظل أنشطة الرعاية وقرارات الجهة الدافعة ومساهمة المريض قابلة للتتبع معاً.","stages":[{"title":"التحقق من الأهلية","action":"فحص التغطية وحفظ الرد مع سياق المريض والزيارة.","owner":"الاستقبال والتنسيق","record":"التغطية · رد الأهلية"},{"title":"متابعة الموافقة المطلوبة","action":"تسجيل طلب الموافقة المسبقة ورد الجهة الدافعة والمسؤولية التالية عند الحاجة.","owner":"فريق الإيرادات","record":"الطلب · حالة الموافقة · المسؤول"},{"title":"توثيق الاستشارة المنجزة","action":"تسجيل الاستشارة والخدمات في زيارة العيادة نفسها.","owner":"الطبيب المعالج","record":"التوثيق السريري · سجل الخدمة"},{"title":"مراجعة الرسم والمساهمة","action":"تطبيق سياق العقد والتعريفة المتفق عليه على الرسوم المراجعة والتزام المريض.","owner":"فريق الإيرادات","record":"التعريفة · الرسم · مساهمة المريض"},{"title":"متابعة رد المطالبة","action":"مراجعة قائمة عمل المطالبات ورد الجهة الدافعة وإسناد أي تصحيح إلى مسؤوله.","owner":"فريق الإيرادات","record":"المطالبة · الرد · التصحيح"},{"title":"مطابقة الرد المالي","action":"مطابقة إشعار السداد والمدفوعات بالمطالبة والزيارة وتحديد الفروقات غير المحسومة.","owner":"الفريق المالي","record":"إشعار السداد · التخصيص · المطابقة"}],"exception":"يبقى الرفض عنصراً في قائمة العمل مع سببه وتصحيحه وتاريخ إعادة الإرسال. يُستخدم تبادل نفيس ضمن النطاق المحدد والمفعّل فقط.","completion":["التغطية والموافقة مرتبطتان بالزيارة.","لردود الجهة الدافعة إجراء تالٍ موثق.","يمكن مراجعة الوضع المالي للزيارة."]}]}}},{"slug":"/solutions/home-palliative","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/home-palliative","title":"Home & Palliative Care management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Continuity across visits, care plans and multidisciplinary handovers.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Continuity across visits, care plans and multidisciplinary handovers.","description":"Connect home visits, palliative care plans, multidisciplinary teams and revenue around the person receiving care. Visit coordination, Palliative care plans, Multidisciplinary…","answers":[{"question":"Which workflows does this solution connect?","answer":"Visit coordination: Prepare visits and the care context needed by the responsible professional. Palliative care plans: Document agreed goals, observations and care-plan responsibilities. Multidisciplinary care: Bring relevant team documentation into the shared patient context. Orders & medication: Keep supported orders and medication context attached to the care plan. Visit-to-visit continuity: Carry observations, care notes and next responsibilities into the following visit. Revenue follow-through: Connect delivered services to billing, claims and payment follow-up.","href":"/solutions/home-palliative"},{"question":"Where can I see complete operational scenarios?","answer":"A home visit with continuity: A home-care team prepares a planned visit, documents the encounter and hands the next care responsibility to the continuing service. A palliative care-plan review: A palliative-care service reviews a patient’s documented goals and care plan over several visits, with input from different professionals. A multidisciplinary handover: A patient receives home-care input from nursing and a clinician. Each professional contributes to the same plan and hands remaining work to the next person. Delivered care to financial follow-up: A home-care service completes several visits under an agreed payer or self-pay arrangement. Revenue teams need to follow delivered services through settlement.","href":"/solutions/home-palliative#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=home_palliative#configuration"}],"solution":{"coverage":[{"name":"Visit coordination","description":"Prepare visits and the care context needed by the responsible professional.","products":["home_palliative"]},{"name":"Palliative care plans","description":"Document agreed goals, observations and care-plan responsibilities.","products":["home_palliative","clinical_documentation"]},{"name":"Multidisciplinary care","description":"Bring relevant team documentation into the shared patient context.","products":["clinical_documentation","home_palliative"]},{"name":"Orders & medication","description":"Keep supported orders and medication context attached to the care plan.","products":["orders_medication"]},{"name":"Visit-to-visit continuity","description":"Carry observations, care notes and next responsibilities into the following visit.","products":["core","home_palliative","clinical_documentation"]},{"name":"Revenue follow-through","description":"Connect delivered services to billing, claims and payment follow-up.","products":["billing_finance","revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"A home visit with continuity","scenario":"A home-care team prepares a planned visit, documents the encounter and hands the next care responsibility to the continuing service.","challenge":"Care delivered at home still needs one connected clinical and operational record.","stages":[{"title":"Arrange the visit","action":"Connect the patient, planned visit and responsible home-care service.","owner":"Access & coordination","record":"Patient · Visit · Service"},{"title":"Review the current plan","action":"Review the documented care plan and earlier visit context before the encounter.","owner":"Home-care professional","record":"Care plan · Previous visits"},{"title":"Document the home encounter","action":"Record observations and the care activity performed within the agreed service.","owner":"Home-care professional","record":"Visit note · Observations · Activity"},{"title":"Connect clinical requests","action":"Document any clinician-reviewed change, medication order or departmental request.","owner":"Treating clinician","record":"Reviewed plan · Orders · Medication"},{"title":"Hand over continuing care","action":"Record the next visit or care-team responsibility with the encounter context.","owner":"Home-care professional","record":"Next visit · Handover · Owner"},{"title":"Review delivered service billing","action":"Connect the documented visit services to the selected billing and revenue follow-up.","owner":"Finance team","record":"Visit service · Account · Follow-up"}],"exception":"If the visit is postponed, record the change and responsible follow-up. Mobile, offline and family messaging are separately agreed scope.","completion":["The home visit adds to the continuing care record.","The next visit has a documented purpose and owner.","Financial work refers to services actually recorded."]},{"type":"Illustrative operational scenario","title":"A palliative care-plan review","scenario":"A palliative-care service reviews a patient’s documented goals and care plan over several visits, with input from different professionals.","challenge":"A person’s goals should remain visible as care responsibilities change.","stages":[{"title":"Review the person’s context","action":"Review the existing record and documented palliative-care context.","owner":"Treating clinician","record":"Patient record · Care context"},{"title":"Document goals and the care plan","action":"Record the agreed goals and professional care plan within the supported palliative workflow.","owner":"Treating clinician","record":"Goals · Care plan · Clinician"},{"title":"Coordinate professional responsibilities","action":"Arrange the selected service visits and document the responsible professionals.","owner":"Access & coordination","record":"Visits · Professional roles"},{"title":"Document the visit review","action":"Record observations and professional contributions against the current care plan.","owner":"Home-care professional","record":"Observations · Visit notes · Plan"},{"title":"Review changes professionally","action":"Review documented changes and update the care plan through the responsible clinician.","owner":"Treating clinician","record":"Clinical review · Updated plan"},{"title":"Carry the plan into the next visit","action":"Document the continuing care handover and any outstanding responsibility.","owner":"Home-care professional","record":"Handover · Next visit · Pending work"}],"exception":"A change in goals or care needs is referred to the responsible professional for review; the platform records the decision rather than making clinical decisions.","completion":["The documented goals accompany each care review.","Professional contributions remain in one care context.","The next team can review the current plan and responsibilities."]},{"type":"Illustrative operational scenario","title":"A multidisciplinary handover","scenario":"A patient receives home-care input from nursing and a clinician. Each professional contributes to the same plan and hands remaining work to the next person.","challenge":"A multidisciplinary service needs shared context without blurred responsibility.","stages":[{"title":"Set the shared care plan","action":"Document the current care plan and the selected professional service responsibilities.","owner":"Treating clinician","record":"Care plan · Professional responsibilities"},{"title":"Coordinate service visits","action":"Arrange visits against the patient’s plan and responsible service.","owner":"Access & coordination","record":"Visit schedule · Service owner"},{"title":"Document nursing input","action":"Record the visit observations and nursing contribution in the patient’s context.","owner":"Nursing team","record":"Nursing note · Observations"},{"title":"Record clinician review","action":"Review the available visit documentation and record any care-plan update.","owner":"Treating clinician","record":"Review · Updated care plan"},{"title":"Connect medication and requests","action":"Link documented medication and department requests to the reviewed care plan.","owner":"Treating clinician","record":"Medication · Requests · Plan reference"},{"title":"Hand over the remaining work","action":"Record the next professional responsibility and outstanding items for the continuing service.","owner":"Home-care professional","record":"Handover · Pending items · Next owner"}],"exception":"Conflicting documentation is returned to the responsible professionals for review, with the care-plan update documented in the shared context.","completion":["Each contribution has a professional and visit reference.","Care-plan changes retain clinical review responsibility.","The next professional can see what remains to be done."]},{"type":"Illustrative operational scenario","title":"Delivered care to financial follow-up","scenario":"A home-care service completes several visits under an agreed payer or self-pay arrangement. Revenue teams need to follow delivered services through settlement.","challenge":"A visit schedule is not the same as a delivered service or a settled account.","stages":[{"title":"Confirm the financial arrangement","action":"Record the patient, payer or self-pay arrangement and agreed service context.","owner":"Access & coordination","record":"Patient · Payer · Service arrangement"},{"title":"Follow required approvals","action":"Document required coverage or authorization responses and responsible follow-up.","owner":"Revenue team","record":"Coverage · Approval · Owner"},{"title":"Document completed visits","action":"Record the care services delivered in each actual visit encounter.","owner":"Home-care professional","record":"Visit encounter · Delivered services"},{"title":"Review service charges","action":"Link reviewed charges to completed visit activity and the agreed tariff context.","owner":"Revenue team","record":"Visit activity · Tariff · Charge"},{"title":"Follow billing or claim work","action":"Review the selected invoice or claim workflow and retain response history.","owner":"Revenue team","record":"Invoice or claim · Response"},{"title":"Reconcile the settlement","action":"Allocate recorded payments or remittance and assign outstanding balances for follow-up.","owner":"Finance team","record":"Payment · Allocation · Outstanding balance"}],"exception":"A cancelled visit is reviewed separately from completed care activity; disputed charges return to the documented service record.","completion":["Charges refer to documented visit activity.","Payer and patient responsibilities remain visible.","Settlement differences have an accountable follow-up."]}]}},"ar":{"url":"https://mansoq.com/solutions/home-palliative?lang=ar","title":"الرعاية المنزلية والتلطيفية | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"استمرارية عبر الزيارات وخطط الرعاية وتسليم المسؤوليات بين التخصصات.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"استمرارية عبر الزيارات وخطط الرعاية وتسليم المسؤوليات بين التخصصات.","description":"اربط الزيارات المنزلية وخطط الرعاية التلطيفية والفرق متعددة التخصصات والإيرادات حول الشخص الذي يتلقى الرعاية. تنسيق الزيارات، خطط الرعاية التلطيفية، رعاية متعددة التخصصات،…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"تنسيق الزيارات: جهز الزيارات وسياق الرعاية الذي يحتاجه المختص المسؤول. خطط الرعاية التلطيفية: وثق الأهداف والملاحظات ومسؤوليات خطة الرعاية المتفق عليها. رعاية متعددة التخصصات: اجمع توثيق الفريق ذي الصلة ضمن سياق المريض المشترك. الطلبات والأدوية: احتفظ بالطلبات وسياق الأدوية المدعومين مرتبطين بخطة الرعاية. استمرارية بين الزيارات: انقل الملاحظات وتوثيق الرعاية والمسؤوليات التالية إلى الزيارة اللاحقة. استكمال متابعة الإيرادات: اربط الخدمات المقدمة بالفوترة والمطالبات ومتابعة الدفع.","href":"/solutions/home-palliative"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"زيارة منزلية باستمرارية: يجهز فريق رعاية منزلية زيارة مخططة ويوثق الزيارة ويسلم مسؤولية الرعاية التالية إلى الخدمة المستمرة. مراجعة خطة رعاية تلطيفية: تراجع خدمة رعاية تلطيفية أهداف مريض موثقة وخطة رعايته عبر زيارات متعددة بمشاركة ممارسين مختلفين. تسليم بين التخصصات: يتلقى مريض رعاية منزلية من التمريض وطبيب. يساهم كل ممارس في الخطة نفسها ويسلم العمل المتبقي إلى الشخص التالي. من الرعاية المقدمة إلى المتابعة المالية: تنجز خدمة رعاية منزلية عدة زيارات وفق ترتيب جهة دافعة أو دفع ذاتي متفق عليه. تحتاج فرق الإيرادات إلى متابعة الخدمات المنجزة حتى التسوية.","href":"/solutions/home-palliative#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=home_palliative#configuration"}],"solution":{"coverage":[{"name":"تنسيق الزيارات","description":"جهز الزيارات وسياق الرعاية الذي يحتاجه المختص المسؤول.","products":["home_palliative"]},{"name":"خطط الرعاية التلطيفية","description":"وثق الأهداف والملاحظات ومسؤوليات خطة الرعاية المتفق عليها.","products":["home_palliative","clinical_documentation"]},{"name":"رعاية متعددة التخصصات","description":"اجمع توثيق الفريق ذي الصلة ضمن سياق المريض المشترك.","products":["clinical_documentation","home_palliative"]},{"name":"الطلبات والأدوية","description":"احتفظ بالطلبات وسياق الأدوية المدعومين مرتبطين بخطة الرعاية.","products":["orders_medication"]},{"name":"استمرارية بين الزيارات","description":"انقل الملاحظات وتوثيق الرعاية والمسؤوليات التالية إلى الزيارة اللاحقة.","products":["core","home_palliative","clinical_documentation"]},{"name":"استكمال متابعة الإيرادات","description":"اربط الخدمات المقدمة بالفوترة والمطالبات ومتابعة الدفع.","products":["billing_finance","revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"زيارة منزلية باستمرارية","scenario":"يجهز فريق رعاية منزلية زيارة مخططة ويوثق الزيارة ويسلم مسؤولية الرعاية التالية إلى الخدمة المستمرة.","challenge":"تحتاج الرعاية المقدمة في المنزل إلى سجل سريري وتشغيلي مترابط واحد.","stages":[{"title":"تنظيم الزيارة","action":"ربط المريض والزيارة المخططة وخدمة الرعاية المنزلية المسؤولة.","owner":"الاستقبال والتنسيق","record":"المريض · الزيارة · الخدمة"},{"title":"مراجعة الخطة الحالية","action":"مراجعة خطة الرعاية الموثقة وسياق الزيارات السابقة قبل الزيارة.","owner":"ممارس الرعاية المنزلية","record":"خطة الرعاية · الزيارات السابقة"},{"title":"توثيق الزيارة المنزلية","action":"تسجيل الملاحظات ونشاط الرعاية المنفذ ضمن الخدمة المتفق عليها.","owner":"ممارس الرعاية المنزلية","record":"توثيق الزيارة · الملاحظات · النشاط"},{"title":"ربط الطلبات السريرية","action":"توثيق أي تغيير راجعه الطبيب أو طلب دواء أو طلب قسم.","owner":"الطبيب المعالج","record":"الخطة المراجعة · الطلبات · الأدوية"},{"title":"تسليم الرعاية المستمرة","action":"تسجيل الزيارة التالية أو مسؤولية فريق الرعاية مع سياق الزيارة.","owner":"ممارس الرعاية المنزلية","record":"الزيارة التالية · التسليم · المسؤول"},{"title":"مراجعة فوترة الخدمة المنجزة","action":"ربط خدمات الزيارة الموثقة بالفوترة والمتابعة الإيرادية المحددتين.","owner":"الفريق المالي","record":"خدمة الزيارة · الحساب · المتابعة"}],"exception":"إذا تأجلت الزيارة، يُسجل التغيير ومسؤول المتابعة. الجوال والعمل دون اتصال ورسائل الأسرة نطاقات متفق عليها بشكل مستقل.","completion":["تضيف الزيارة المنزلية إلى سجل الرعاية المستمرة.","للزيارة التالية غرض ومسؤول موثقان.","يرجع العمل المالي إلى الخدمات المسجلة فعلياً."]},{"type":"Illustrative operational scenario","title":"مراجعة خطة رعاية تلطيفية","scenario":"تراجع خدمة رعاية تلطيفية أهداف مريض موثقة وخطة رعايته عبر زيارات متعددة بمشاركة ممارسين مختلفين.","challenge":"يجب أن تظل أهداف الشخص واضحة عندما تتغير مسؤوليات الرعاية.","stages":[{"title":"مراجعة سياق الشخص","action":"مراجعة السجل القائم وسياق الرعاية التلطيفية الموثق.","owner":"الطبيب المعالج","record":"سجل المريض · سياق الرعاية"},{"title":"توثيق الأهداف وخطة الرعاية","action":"تسجيل الأهداف المتفق عليها وخطة الرعاية المهنية ضمن المسار التلطيفي المدعوم.","owner":"الطبيب المعالج","record":"الأهداف · خطة الرعاية · الطبيب"},{"title":"تنسيق مسؤوليات الممارسين","action":"تنظيم زيارات الخدمات المحددة وتوثيق الممارسين المسؤولين.","owner":"الاستقبال والتنسيق","record":"الزيارات · أدوار الممارسين"},{"title":"توثيق مراجعة الزيارة","action":"تسجيل الملاحظات ومساهمات الممارسين مقابل خطة الرعاية الحالية.","owner":"ممارس الرعاية المنزلية","record":"الملاحظات · توثيق الزيارة · الخطة"},{"title":"مراجعة التغييرات مهنياً","action":"مراجعة التغييرات الموثقة وتحديث خطة الرعاية بواسطة الطبيب المسؤول.","owner":"الطبيب المعالج","record":"المراجعة السريرية · الخطة المحدثة"},{"title":"نقل الخطة إلى الزيارة التالية","action":"توثيق تسليم الرعاية المستمرة وأي مسؤولية معلقة.","owner":"ممارس الرعاية المنزلية","record":"التسليم · الزيارة التالية · العمل المعلق"}],"exception":"يُحال تغير الأهداف أو احتياجات الرعاية إلى الممارس المسؤول للمراجعة؛ وتسجل المنصة القرار بدلاً من اتخاذ قرارات سريرية.","completion":["ترافق الأهداف الموثقة كل مراجعة للرعاية.","تبقى مساهمات الممارسين ضمن سياق رعاية واحد.","يمكن للفريق التالي مراجعة الخطة الحالية والمسؤوليات."]},{"type":"Illustrative operational scenario","title":"تسليم بين التخصصات","scenario":"يتلقى مريض رعاية منزلية من التمريض وطبيب. يساهم كل ممارس في الخطة نفسها ويسلم العمل المتبقي إلى الشخص التالي.","challenge":"تحتاج الخدمة متعددة التخصصات إلى سياق مشترك مع مسؤوليات واضحة.","stages":[{"title":"تحديد خطة الرعاية المشتركة","action":"توثيق خطة الرعاية الحالية ومسؤوليات خدمات الممارسين المحددة.","owner":"الطبيب المعالج","record":"خطة الرعاية · مسؤوليات الممارسين"},{"title":"تنسيق زيارات الخدمات","action":"تنظيم الزيارات مقابل خطة المريض والخدمة المسؤولة.","owner":"الاستقبال والتنسيق","record":"جدول الزيارات · مسؤول الخدمة"},{"title":"توثيق مساهمة التمريض","action":"تسجيل ملاحظات الزيارة ومساهمة التمريض ضمن سياق المريض.","owner":"فريق التمريض","record":"توثيق التمريض · الملاحظات"},{"title":"تسجيل مراجعة الطبيب","action":"مراجعة توثيق الزيارة المتاح وتسجيل أي تحديث لخطة الرعاية.","owner":"الطبيب المعالج","record":"المراجعة · خطة الرعاية المحدثة"},{"title":"ربط الأدوية والطلبات","action":"ربط الأدوية وطلبات الأقسام الموثقة بخطة الرعاية المراجعة.","owner":"الطبيب المعالج","record":"الأدوية · الطلبات · مرجع الخطة"},{"title":"تسليم العمل المتبقي","action":"تسجيل مسؤولية الممارس التالي والعناصر المعلقة للخدمة المستمرة.","owner":"ممارس الرعاية المنزلية","record":"التسليم · العناصر المعلقة · المسؤول التالي"}],"exception":"يُعاد التوثيق المتعارض إلى الممارسين المسؤولين للمراجعة، مع توثيق تحديث خطة الرعاية ضمن السياق المشترك.","completion":["لكل مساهمة مرجع ممارس وزيارة.","تحتفظ تغييرات خطة الرعاية بمسؤولية مراجعة سريرية.","يمكن للممارس التالي رؤية ما بقي لإنجازه."]},{"type":"Illustrative operational scenario","title":"من الرعاية المقدمة إلى المتابعة المالية","scenario":"تنجز خدمة رعاية منزلية عدة زيارات وفق ترتيب جهة دافعة أو دفع ذاتي متفق عليه. تحتاج فرق الإيرادات إلى متابعة الخدمات المنجزة حتى التسوية.","challenge":"جدول الزيارات ليس خدمة منجزة ولا حساباً تمت تسويته.","stages":[{"title":"تأكيد الترتيب المالي","action":"تسجيل المريض وترتيب الجهة الدافعة أو الدفع الذاتي وسياق الخدمة المتفق عليه.","owner":"الاستقبال والتنسيق","record":"المريض · الجهة الدافعة · ترتيب الخدمة"},{"title":"متابعة الموافقات المطلوبة","action":"توثيق ردود التغطية أو الموافقة المطلوبة ومسؤولية المتابعة.","owner":"فريق الإيرادات","record":"التغطية · الموافقة · المسؤول"},{"title":"توثيق الزيارات المنجزة","action":"تسجيل خدمات الرعاية المقدمة في كل زيارة فعلية.","owner":"ممارس الرعاية المنزلية","record":"الزيارة · الخدمات المقدمة"},{"title":"مراجعة رسوم الخدمات","action":"ربط الرسوم المراجعة بنشاط الزيارات المنجزة وسياق التعريفة المتفق عليه.","owner":"فريق الإيرادات","record":"نشاط الزيارة · التعريفة · الرسم"},{"title":"متابعة الفوترة أو المطالبة","action":"مراجعة مسار الفاتورة أو المطالبة المحدد وحفظ تاريخ الردود.","owner":"فريق الإيرادات","record":"الفاتورة أو المطالبة · الرد"},{"title":"مطابقة التسوية","action":"تخصيص المدفوعات أو إشعار السداد المسجل وإسناد الأرصدة المتبقية للمتابعة.","owner":"الفريق المالي","record":"الدفع · التخصيص · الرصيد المتبقي"}],"exception":"تُراجع الزيارة الملغاة بشكل منفصل عن نشاط الرعاية المنجز؛ وتعود الرسوم محل الاعتراض إلى سجل الخدمة الموثق.","completion":["ترجع الرسوم إلى نشاط زيارة موثق.","تظل مسؤوليات الجهة الدافعة والمريض واضحة.","للفروقات في التسوية متابعة بمسؤولية واضحة."]}]}}},{"slug":"/solutions/hospitals","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/hospitals","title":"Hospitals management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Admissions, wards and departments connected around each person.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Admissions, wards and departments connected around each person.","description":"Connect the front desk, wards, specialist departments and financial follow-up around every patient. Access & arrival, Ward & critical care, Specialist departments, Clinical…","answers":[{"question":"Which workflows does this solution connect?","answer":"Access & arrival: Keep appointments, emergency encounters and registration connected to the patient record. Ward & critical care: Carry nursing documentation, observations and care responsibilities through the stay. Specialist departments: Connect surgical cases, pharmacy, laboratory work and supplies. Add radiology to your scope when needed. Clinical continuity: Keep clinical notes, orders, results and medication with the same care context. Revenue cycle: Follow eligibility, approvals, charges, claims and reconciliation from one connected scope. Saudi connections: Bring insurance exchange, e-invoicing and supported coding into the agreed hospital scope.","href":"/solutions/hospitals"},{"question":"Where can I see complete operational scenarios?","answer":"Admission to discharge: A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge. Day surgery, end to end: A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected. Critical-care handover: An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together. Care delivered. Revenue followed.: A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.","href":"/solutions/hospitals#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=hospitals#configuration"}],"solution":{"coverage":[{"name":"Access & arrival","description":"Keep appointments, emergency encounters and registration connected to the patient record.","products":["outpatient","emergency","patient_access"]},{"name":"Ward & critical care","description":"Carry nursing documentation, observations and care responsibilities through the stay.","products":["inpatient","icu","clinical_documentation"]},{"name":"Specialist departments","description":"Connect surgical cases, pharmacy, laboratory work and supplies. Add radiology to your scope when needed.","products":["operating_room","laboratory","pharmacy","inventory","radiology"]},{"name":"Clinical continuity","description":"Keep clinical notes, orders, results and medication with the same care context.","products":["clinical_documentation","orders_medication"]},{"name":"Revenue cycle","description":"Follow eligibility, approvals, charges, claims and reconciliation from one connected scope.","products":["revenue_cycle","billing_finance"]},{"name":"Saudi connections","description":"Bring insurance exchange, e-invoicing and supported coding into the agreed hospital scope.","products":["nphies","zatca","sbs_full","drg"]}],"cases":[{"type":"Illustrative operational scenario","title":"Admission to discharge","scenario":"A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge.","challenge":"An admission is one journey, even when responsibility changes between several teams.","stages":[{"title":"Establish the encounter","action":"Confirm the patient identity, admission details and responsible service against the shared record.","owner":"Access & coordination","record":"Identity · Admission · Service"},{"title":"Receive the patient on the ward","action":"Document the ward handover, observations and care responsibilities for the incoming team.","owner":"Nursing team","record":"Ward · Observations · Responsible team"},{"title":"Document and request","action":"Record the assessment and connect medication and departmental requests to this inpatient encounter.","owner":"Treating clinician","record":"Clinical notes · Orders · Medication"},{"title":"Bring department work back","action":"Complete the selected laboratory or pharmacy work and return its documented result to the care context.","owner":"Department team","record":"Request · Department activity · Result"},{"title":"Prepare the next care step","action":"Record the discharge summary, medication plan and follow-up responsibility for the next team.","owner":"Treating clinician","record":"Discharge summary · Follow-up"},{"title":"Close the financial encounter","action":"Review encounter-linked charges, patient liability and payments; assign any outstanding balance for follow-up.","owner":"Finance team","record":"Charges · Invoice · Balance"}],"exception":"If a result or discharge task is outstanding, keep it attached to the encounter with a named owner; the clinical team decides the care action.","completion":["A discharge record carrying the documented care context.","A clear follow-up responsibility for the next care team.","Financial work traceable to the same admission."]},{"type":"Illustrative operational scenario","title":"Day surgery, end to end","scenario":"A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected.","challenge":"Theatre readiness and the recovery handover need more than a booking on a calendar.","stages":[{"title":"Book the surgical case","action":"Link the scheduled case, patient and responsible surgical service to the encounter.","owner":"Access & coordination","record":"Booking · Encounter · Service"},{"title":"Prepare the case","action":"Document the agreed preoperative assessment and preparation requirements for the surgical team.","owner":"Treating clinician","record":"Assessment · Preparation record"},{"title":"Coordinate theatre resources","action":"Connect the case to selected theatre resources and required consumables within the agreed operating-room scope.","owner":"Department team","record":"Theatre · Resources · Consumables"},{"title":"Document the procedure","action":"Record perioperative activity and the procedure against the patient’s case rather than a separate account.","owner":"Treating clinician","record":"Procedure · Perioperative notes"},{"title":"Hand over to recovery","action":"Carry the procedure record, observations and next responsibilities into recovery and discharge documentation.","owner":"Nursing team","record":"Recovery · Handover · Discharge"},{"title":"Review case-linked charges","action":"Reconcile recorded services and consumables with the case bill and assign financial follow-up.","owner":"Finance team","record":"Services · Consumables · Bill"}],"exception":"When a case is rescheduled, update the booking and resource responsibility while retaining the preparation record for review.","completion":["One case history from booking to recovery.","A recovery handover with the procedure context.","Services and consumables linked to financial review."]},{"type":"Illustrative operational scenario","title":"Critical-care handover","scenario":"An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together.","challenge":"A handover must transfer responsibility as well as information.","stages":[{"title":"Confirm the care context","action":"Open the correct inpatient encounter and confirm the current ICU team and location.","owner":"Nursing team","record":"Identity · Encounter · ICU location"},{"title":"Review documented observations","action":"Review recorded observations and clinical notes with their encounter context; assess care professionally.","owner":"Treating clinician","record":"Observations · Clinical notes"},{"title":"Carry medication context","action":"Bring the documented medication and order context into the handover for the responsible clinical team.","owner":"Nursing team","record":"Medication · Current orders"},{"title":"Review department follow-up","action":"Link available results and outstanding departmental work to the same encounter.","owner":"Department team","record":"Results · Pending requests"},{"title":"Record the shift handover","action":"Document the care handover and identify who takes responsibility for each next action.","owner":"Nursing team","record":"Handover note · Next owner"},{"title":"Continue or transfer care","action":"Update the next care plan or documented ward transfer while preserving the ICU encounter history.","owner":"Treating clinician","record":"Care plan · Transfer record"}],"exception":"If information is missing, identify its source and responsible team in the handover instead of treating an absent result as a completed task.","completion":["The incoming team can review one connected care record.","Pending work retains a documented owner.","The ICU history accompanies the next care setting."]},{"type":"Illustrative operational scenario","title":"Care delivered. Revenue followed.","scenario":"A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.","challenge":"Revenue follow-up starts with the services actually recorded in the encounter.","stages":[{"title":"Establish financial responsibility","action":"Record the patient, encounter and payer or self-pay context before financial follow-up.","owner":"Access & coordination","record":"Encounter · Payer · Patient account"},{"title":"Capture delivered activity","action":"Link recorded departmental and care services to accountable encounter charges.","owner":"Department team","record":"Service activity · Charge reference"},{"title":"Review prices and contribution","action":"Check the agreed tariffs and patient contribution against the recorded services and coverage.","owner":"Revenue team","record":"Tariff · Coverage · Contribution"},{"title":"Issue the invoice","action":"Review the invoice and use the selected ZATCA exchange scope where configured and activated.","owner":"Finance team","record":"Invoice · E-invoice response"},{"title":"Allocate payments","action":"Match recorded payments or payer financial responses to the relevant account and invoice.","owner":"Finance team","record":"Payment · Allocation · Balance"},{"title":"Resolve the remaining balance","action":"Assign unresolved differences for review and record the reconciliation decision and next action.","owner":"Revenue team","record":"Difference · Owner · Reconciliation"}],"exception":"A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.","completion":["Every reviewed charge has a care-activity reference.","Payments and outstanding balances have clear allocation.","Financial differences have a responsible next action."]}]}},"ar":{"url":"https://mansoq.com/solutions/hospitals?lang=ar","title":"المستشفيات | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"التنويم والأجنحة والأقسام متصلة حول كل شخص.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"التنويم والأجنحة والأقسام متصلة حول كل شخص.","description":"اربط الاستقبال والأجنحة والأقسام التخصصية والمتابعة المالية حول كل مريض. الوصول والاستقبال، الأجنحة والعناية الحرجة، الأقسام التخصصية، الاستمرارية السريرية، دورة الإيرادات،…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"الوصول والاستقبال: اربط المواعيد وزيارات الطوارئ والتسجيل بسجل المريض. الأجنحة والعناية الحرجة: انقل توثيق التمريض والملاحظات ومسؤوليات الرعاية عبر الإقامة. الأقسام التخصصية: اربط الحالات الجراحية والصيدلية وعمل المختبر والإمدادات. أضف الأشعة إلى نطاقك عند الحاجة. الاستمرارية السريرية: احتفظ بالتوثيق والطلبات والنتائج والأدوية ضمن سياق الرعاية نفسه. دورة الإيرادات: تابع الأهلية والموافقات والرسوم والمطالبات والمطابقة ضمن نطاق مترابط. الاتصالات السعودية: أدخل التبادل التأميني والفوترة الإلكترونية والترميز المدعوم ضمن نطاق المستشفى المتفق عليه.","href":"/solutions/hospitals"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"من الدخول إلى الخروج: يصل مريض لإقامة تنويم مخططة. يحتاج الاستقبال والجناح والتشخيص والمالية إلى العمل من سياق الزيارة نفسه حتى الخروج. الجراحة اليومية من البداية للنهاية: يحضر مريض لخدمة جراحة يومية مجدولة. يجب أن تظل الحجوزات وتجهيز العمليات والإجراء والتعافي والفوترة مترابطة. تسليم رعاية حرجة: تنتقل رعاية مريض في العناية المركزة من مناوبة إلى التالية. يحتاج الفريق المستلم إلى الملاحظات والأدوية والعمل المعلق الموثق معاً. رعاية مقدمة. إيرادات متابَعة.: تشمل زيارة مستشفى رعاية جناح وخدمات أقسام ومدفوعات المريض. تحتاج المالية إلى تفسير كل رسم وكل رصيد متبقٍ.","href":"/solutions/hospitals#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=hospitals#configuration"}],"solution":{"coverage":[{"name":"الوصول والاستقبال","description":"اربط المواعيد وزيارات الطوارئ والتسجيل بسجل المريض.","products":["outpatient","emergency","patient_access"]},{"name":"الأجنحة والعناية الحرجة","description":"انقل توثيق التمريض والملاحظات ومسؤوليات الرعاية عبر الإقامة.","products":["inpatient","icu","clinical_documentation"]},{"name":"الأقسام التخصصية","description":"اربط الحالات الجراحية والصيدلية وعمل المختبر والإمدادات. أضف الأشعة إلى نطاقك عند الحاجة.","products":["operating_room","laboratory","pharmacy","inventory","radiology"]},{"name":"الاستمرارية السريرية","description":"احتفظ بالتوثيق والطلبات والنتائج والأدوية ضمن سياق الرعاية نفسه.","products":["clinical_documentation","orders_medication"]},{"name":"دورة الإيرادات","description":"تابع الأهلية والموافقات والرسوم والمطالبات والمطابقة ضمن نطاق مترابط.","products":["revenue_cycle","billing_finance"]},{"name":"الاتصالات السعودية","description":"أدخل التبادل التأميني والفوترة الإلكترونية والترميز المدعوم ضمن نطاق المستشفى المتفق عليه.","products":["nphies","zatca","sbs_full","drg"]}],"cases":[{"type":"Illustrative operational scenario","title":"من الدخول إلى الخروج","scenario":"يصل مريض لإقامة تنويم مخططة. يحتاج الاستقبال والجناح والتشخيص والمالية إلى العمل من سياق الزيارة نفسه حتى الخروج.","challenge":"التنويم رحلة واحدة، حتى عندما تنتقل المسؤولية بين فرق متعددة.","stages":[{"title":"تأسيس الزيارة","action":"تأكيد هوية المريض وبيانات القبول والخدمة المسؤولة مقابل السجل المشترك.","owner":"الاستقبال والتنسيق","record":"الهوية · القبول · الخدمة"},{"title":"استقبال المريض في الجناح","action":"توثيق تسليم الجناح والملاحظات ومسؤوليات الرعاية للفريق المستلم.","owner":"فريق التمريض","record":"الجناح · الملاحظات · الفريق المسؤول"},{"title":"التوثيق والطلبات","action":"تسجيل التقييم وربط الأدوية وطلبات الأقسام بزيارة التنويم هذه.","owner":"الطبيب المعالج","record":"التوثيق السريري · الطلبات · الأدوية"},{"title":"إعادة عمل الأقسام إلى الرعاية","action":"إنجاز عمل المختبر أو الصيدلية المحدد وإعادة نتيجته الموثقة إلى سياق الرعاية.","owner":"فريق القسم","record":"الطلب · نشاط القسم · النتيجة"},{"title":"تجهيز خطوة الرعاية التالية","action":"تسجيل ملخص الخروج وخطة الأدوية ومسؤولية المتابعة للفريق التالي.","owner":"الطبيب المعالج","record":"ملخص الخروج · المتابعة"},{"title":"إقفال الزيارة مالياً","action":"مراجعة الرسوم المرتبطة بالزيارة والتزام المريض والمدفوعات وإسناد الرصيد المتبقي للمتابعة.","owner":"الفريق المالي","record":"الرسوم · الفاتورة · الرصيد"}],"exception":"إذا بقيت نتيجة أو مهمة خروج معلقة، ترتبط بالزيارة وبمسؤول محدد؛ ويقرر الفريق السريري إجراء الرعاية.","completion":["سجل خروج يحمل سياق الرعاية الموثق.","مسؤولية متابعة واضحة لفريق الرعاية التالي.","عمل مالي قابل للتتبع إلى التنويم نفسه."]},{"type":"Illustrative operational scenario","title":"الجراحة اليومية من البداية للنهاية","scenario":"يحضر مريض لخدمة جراحة يومية مجدولة. يجب أن تظل الحجوزات وتجهيز العمليات والإجراء والتعافي والفوترة مترابطة.","challenge":"جاهزية العمليات وتسليم التعافي يحتاجان إلى أكثر من حجز في التقويم.","stages":[{"title":"حجز الحالة الجراحية","action":"ربط الحالة المجدولة والمريض والخدمة الجراحية المسؤولة بالزيارة.","owner":"الاستقبال والتنسيق","record":"الحجز · الزيارة · الخدمة"},{"title":"تجهيز الحالة","action":"توثيق التقييم قبل الجراحة ومتطلبات التجهيز المتفق عليها للفريق الجراحي.","owner":"الطبيب المعالج","record":"التقييم · سجل التجهيز"},{"title":"تنسيق موارد العمليات","action":"ربط الحالة بموارد العمليات المحددة والمستهلكات المطلوبة ضمن نطاق غرفة العمليات المتفق عليه.","owner":"فريق القسم","record":"العمليات · الموارد · المستهلكات"},{"title":"توثيق الإجراء","action":"تسجيل النشاط المحيط بالجراحة والإجراء مقابل حالة المريض بدلاً من حساب منفصل.","owner":"الطبيب المعالج","record":"الإجراء · توثيق الرعاية المحيطة بالجراحة"},{"title":"التسليم إلى التعافي","action":"نقل سجل الإجراء والملاحظات والمسؤوليات التالية إلى توثيق التعافي والخروج.","owner":"فريق التمريض","record":"التعافي · التسليم · الخروج"},{"title":"مراجعة رسوم الحالة","action":"مطابقة الخدمات والمستهلكات المسجلة مع فاتورة الحالة وإسناد المتابعة المالية.","owner":"الفريق المالي","record":"الخدمات · المستهلكات · الفاتورة"}],"exception":"عند إعادة جدولة الحالة، يُحدّث الحجز ومسؤولية الموارد مع الاحتفاظ بسجل التجهيز للمراجعة.","completion":["تاريخ حالة واحد من الحجز إلى التعافي.","تسليم إلى التعافي يحمل سياق الإجراء.","خدمات ومستهلكات مرتبطة بالمراجعة المالية."]},{"type":"Illustrative operational scenario","title":"تسليم رعاية حرجة","scenario":"تنتقل رعاية مريض في العناية المركزة من مناوبة إلى التالية. يحتاج الفريق المستلم إلى الملاحظات والأدوية والعمل المعلق الموثق معاً.","challenge":"يجب أن ينقل تسليم الرعاية المسؤولية إلى جانب المعلومات.","stages":[{"title":"تأكيد سياق الرعاية","action":"فتح زيارة التنويم الصحيحة وتأكيد فريق العناية المركزة الحالي والموقع.","owner":"فريق التمريض","record":"الهوية · الزيارة · موقع العناية المركزة"},{"title":"مراجعة الملاحظات الموثقة","action":"مراجعة الملاحظات والتوثيق السريري المسجل بسياق الزيارة وتقييم الرعاية مهنياً.","owner":"الطبيب المعالج","record":"الملاحظات · التوثيق السريري"},{"title":"نقل سياق الأدوية","action":"إدراج سياق الأدوية والطلبات الموثق في التسليم للفريق السريري المسؤول.","owner":"فريق التمريض","record":"الأدوية · الطلبات الحالية"},{"title":"مراجعة متابعة الأقسام","action":"ربط النتائج المتاحة وعمل الأقسام المعلق بالزيارة نفسها.","owner":"فريق القسم","record":"النتائج · الطلبات المعلقة"},{"title":"تسجيل تسليم المناوبة","action":"توثيق تسليم الرعاية وتحديد من يتولى مسؤولية كل إجراء تالٍ.","owner":"فريق التمريض","record":"ملاحظة التسليم · المسؤول التالي"},{"title":"استمرار الرعاية أو نقلها","action":"تحديث خطة الرعاية التالية أو النقل الموثق إلى الجناح مع حفظ تاريخ زيارة العناية المركزة.","owner":"الطبيب المعالج","record":"خطة الرعاية · سجل النقل"}],"exception":"إذا نقصت معلومات، يُحدد مصدرها والفريق المسؤول في التسليم بدلاً من اعتبار النتيجة الغائبة مهمة منجزة.","completion":["يستطيع الفريق المستلم مراجعة سجل رعاية مترابط واحد.","يظل للعمل المعلق مسؤول موثق.","يرافق تاريخ العناية المركزة بيئة الرعاية التالية."]},{"type":"Illustrative operational scenario","title":"رعاية مقدمة. إيرادات متابَعة.","scenario":"تشمل زيارة مستشفى رعاية جناح وخدمات أقسام ومدفوعات المريض. تحتاج المالية إلى تفسير كل رسم وكل رصيد متبقٍ.","challenge":"تبدأ متابعة الإيرادات بالخدمات المسجلة فعلياً في الزيارة.","stages":[{"title":"تحديد المسؤولية المالية","action":"تسجيل المريض والزيارة وسياق الجهة الدافعة أو الدفع الذاتي قبل المتابعة المالية.","owner":"الاستقبال والتنسيق","record":"الزيارة · الجهة الدافعة · حساب المريض"},{"title":"التقاط النشاط المنجز","action":"ربط خدمات الأقسام والرعاية المسجلة برسوم زيارة قابلة للمساءلة.","owner":"فريق القسم","record":"نشاط الخدمة · مرجع الرسم"},{"title":"مراجعة الأسعار والمساهمة","action":"فحص التعريفات المتفق عليها ومساهمة المريض مقابل الخدمات والتغطية المسجلة.","owner":"فريق الإيرادات","record":"التعريفة · التغطية · المساهمة"},{"title":"إصدار الفاتورة","action":"مراجعة الفاتورة واستخدام نطاق تبادل زاتكا المحدد حيث تمت تهيئته وتفعيله.","owner":"الفريق المالي","record":"الفاتورة · رد الفاتورة الإلكترونية"},{"title":"تخصيص المدفوعات","action":"مطابقة المدفوعات المسجلة أو الردود المالية للجهة الدافعة بالحساب والفاتورة المعنيين.","owner":"الفريق المالي","record":"الدفع · التخصيص · الرصيد"},{"title":"معالجة الرصيد المتبقي","action":"إسناد الفروقات غير المحسومة للمراجعة وتسجيل قرار المطابقة والإجراء التالي.","owner":"فريق الإيرادات","record":"الفرق · المسؤول · المطابقة"}],"exception":"يعود الرسم محل الاعتراض إلى مرجع خدمته للمراجعة؛ ويحتفظ السجل المالي المصحح بتتبع الزيارة الأصلية.","completion":["لكل رسم تمت مراجعته مرجع نشاط رعاية.","للمدفوعات والأرصدة المتبقية تخصيص واضح.","للفروقات المالية إجراء تالٍ بمسؤولية محددة."]}]}}},{"slug":"/solutions/medical-city","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/medical-city","title":"Medical Cities management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"A governed network composition with clear entity and record boundaries.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A governed network composition with clear entity and record boundaries.","description":"Connect care across entities, departments and revenue while keeping record boundaries and access accountable. Network governance, Care across settings, Shared specialist work,…","answers":[{"question":"Which workflows does this solution connect?","answer":"Network governance: Define entities, record boundaries and accountable access across the agreed network. Care across settings: Connect outpatient, emergency and inpatient context in the network composition. Shared specialist work: Connect laboratory work, medication and departmental supply responsibilities. Connected systems: Agree the systems, interfaces and data exchanged across entities. Revenue operations: Connect clinical activity, payer follow-up and reconciliation within entity boundaries. Leadership insight: Review selected operational and revenue reports with clear source context.","href":"/solutions/medical-city"},{"question":"Where can I see complete operational scenarios?","answer":"Continuity across entities: A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries. Emergency into inpatient care: A medical-city outpatient service refers a patient for admission. The referral, receiving ward and financial encounter need connected responsibilities. Diagnostics and medication across teams: Several medical-city departments contribute to a patient’s care. The network needs to distinguish native operation from information exchanged with existing systems. A leadership view grounded in source data: Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.","href":"/solutions/medical-city#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=medical_cities#configuration"}],"solution":{"coverage":[{"name":"Network governance","description":"Define entities, record boundaries and accountable access across the agreed network.","products":["network_governance","core"]},{"name":"Care across settings","description":"Connect outpatient, emergency and inpatient context in the network composition.","products":["outpatient","emergency","inpatient"]},{"name":"Shared specialist work","description":"Connect laboratory work, medication and departmental supply responsibilities.","products":["laboratory","pharmacy","inventory"]},{"name":"Connected systems","description":"Agree the systems, interfaces and data exchanged across entities.","products":["interfaces"]},{"name":"Revenue operations","description":"Connect clinical activity, payer follow-up and reconciliation within entity boundaries.","products":["revenue_cycle","billing_finance"]},{"name":"Leadership insight","description":"Review selected operational and revenue reports with clear source context.","products":["analytics","rcm_reporting"]}],"cases":[{"type":"Illustrative operational scenario","title":"Continuity across entities","scenario":"A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries.","challenge":"Continuity across entities requires governed access, not unrestricted record sharing.","stages":[{"title":"Define the network boundary","action":"Agree the entities, identity scope and permitted record exchange for this composition.","owner":"Integration & IT team","record":"Entities · Identity boundary · Permissions"},{"title":"Record the source encounter","action":"Document the patient’s current encounter and reason for the next service.","owner":"Treating clinician","record":"Source encounter · Referral reason"},{"title":"Coordinate the receiving service","action":"Confirm the destination and responsible team for the referral or transfer.","owner":"Access & coordination","record":"Destination · Team · Transfer"},{"title":"Share the permitted context","action":"Carry the agreed information through the selected connection with source references.","owner":"Integration & IT team","record":"Interface · Source record · Shared context"},{"title":"Document receiving care","action":"Review permitted information and document the receiving entity’s encounter and responsibilities.","owner":"Treating clinician","record":"Receiving encounter · Care plan"},{"title":"Review continuity with governance","action":"Review supported network reporting within the agreed entity and access boundaries.","owner":"Service leadership","record":"Entity view · Access · Reporting"}],"exception":"If an identity cannot be matched or access is outside the agreed boundary, the responsible teams resolve it before exchanging additional records.","completion":["The receiving service has the permitted source context.","Source and receiving records retain their entity boundaries.","Network visibility follows the agreed governance model."]},{"type":"Illustrative operational scenario","title":"Emergency into inpatient care","scenario":"A medical-city outpatient service refers a patient for admission. The referral, receiving ward and financial encounter need connected responsibilities.","challenge":"Changing the care setting should not remove the reason the patient arrived.","stages":[{"title":"Document the referral","action":"Record the outpatient assessment and documented admission referral.","owner":"Treating clinician","record":"Outpatient encounter · Referral"},{"title":"Confirm the receiving entity","action":"Establish the destination service and the patient identity within the agreed network boundaries.","owner":"Access & coordination","record":"Destination · Identity · Entity"},{"title":"Create the admitted encounter","action":"Connect the admission and ward responsibility to the receiving entity’s record.","owner":"Access & coordination","record":"Admission · Ward · Encounter"},{"title":"Review the handover context","action":"Review available referral notes and record the receiving ward’s observations and responsibilities.","owner":"Nursing team","record":"Referral notes · Ward handover"},{"title":"Coordinate care and departments","action":"Document inpatient care and connect required department requests to the admitted encounter.","owner":"Treating clinician","record":"Care plan · Orders · Results"},{"title":"Complete care and financial follow-up","action":"Retain the discharge context and review each entity’s recorded charges and account responsibility.","owner":"Finance team","record":"Discharge · Entity charges · Account"}],"exception":"When the destination changes, update the responsible entity and transfer record; cross-entity sharing still follows the agreed permissions.","completion":["The admission retains the original referral context.","Ward and department responsibilities are explicit.","Care continuity respects separate entity accounts."]},{"type":"Illustrative operational scenario","title":"Diagnostics and medication across teams","scenario":"Several medical-city departments contribute to a patient’s care. The network needs to distinguish native operation from information exchanged with existing systems.","challenge":"Connected results and operating a department are different responsibilities.","stages":[{"title":"Define departmental ownership","action":"Agree which departments operate in MANSOQ and which retain an external system.","owner":"Service leadership","record":"Department · Operating mode · Owner"},{"title":"Create the encounter request","action":"Link each requested service to the correct patient, encounter and department.","owner":"Treating clinician","record":"Order · Encounter · Department"},{"title":"Perform the selected department work","action":"Document supported native activity or process the request in the retained source system.","owner":"Department team","record":"Department activity · Source reference"},{"title":"Return the agreed information","action":"Exchange the agreed results or status through the defined interface and identity mapping.","owner":"Integration & IT team","record":"Result · Interface · Identity mapping"},{"title":"Review in the care context","action":"Review available department information and document the next care responsibility.","owner":"Treating clinician","record":"Clinical review · Next action"},{"title":"Trace the service account","action":"Review selected charge linkage with the service’s native or external source reference.","owner":"Revenue team","record":"Service · Charge · Source"}],"exception":"If an interface fails, the agreed operational fallback and source owner handle the missing information; connected access does not replace departmental operation.","completion":["Each department has an explicit operating owner.","Returned information retains its source and encounter.","Department work and financial follow-up remain connected."]},{"type":"Illustrative operational scenario","title":"A leadership view grounded in source data","scenario":"Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.","challenge":"A network report is useful only when the included entities and definitions are clear.","stages":[{"title":"Agree the reporting view","action":"Define the operational question, selected entities and authorized audience.","owner":"Service leadership","record":"Question · Entities · Access"},{"title":"Identify the source activity","action":"Record the relevant care and departmental activity within its source entity.","owner":"Department team","record":"Activity · Entity · Encounter"},{"title":"Connect revenue context","action":"Review claims, financial responses and outstanding work within the selected reporting scope.","owner":"Revenue team","record":"Claims · Responses · Work items"},{"title":"Review the reporting boundaries","action":"Check included sources, entity permissions and the agreed operational definitions.","owner":"Integration & IT team","record":"Sources · Permissions · Definitions"},{"title":"Review the selected report","action":"Use supported operational and revenue views to identify work requiring attention.","owner":"Service leadership","record":"Report · Review · Work requiring action"},{"title":"Assign accountable follow-up","action":"Record the responsible team and return operational questions to the relevant source.","owner":"Service leadership","record":"Action · Owner · Source reference"}],"exception":"An incomplete source is identified in the review rather than silently treated as zero activity; the source owner resolves the reporting gap.","completion":["The reporting audience knows which entities are included.","Operational questions retain their source context.","Follow-up returns to the accountable team."]}]}},"ar":{"url":"https://mansoq.com/solutions/medical-city?lang=ar","title":"المدن الطبية | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تكوين شبكة خاضع للحوكمة بحدود واضحة للكيانات والسجلات.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تكوين شبكة خاضع للحوكمة بحدود واضحة للكيانات والسجلات.","description":"اربط الرعاية عبر الكيانات والأقسام والإيرادات مع وضوح حدود السجلات ومسؤوليات الوصول. حوكمة الشبكة، الرعاية عبر البيئات، العمل التخصصي المشترك، الأنظمة المترابطة، عمليات…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"حوكمة الشبكة: حدد الكيانات وحدود السجلات ومسؤوليات الوصول عبر الشبكة المتفق عليها. الرعاية عبر البيئات: اربط سياق العيادات والطوارئ والتنويم ضمن تكوين الشبكة. العمل التخصصي المشترك: اربط عمل المختبر والأدوية ومسؤوليات إمداد الأقسام. الأنظمة المترابطة: اتفق على الأنظمة والاتصالات والبيانات المتبادلة بين الكيانات. عمليات الإيرادات: اربط النشاط السريري ومتابعة الجهات الدافعة والمطابقة ضمن حدود الكيانات. رؤية القيادة: راجع التقارير التشغيلية والإيرادية المختارة بسياق مصادر واضح.","href":"/solutions/medical-city"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"استمرارية عبر الكيانات: ينتقل مريض بين خدمات شبكة مدينة طبية. يحتاج الكيان المستلم إلى سياق الرعاية المسموح مع احتفاظ كل منظمة بحدود بياناتها. من الطوارئ إلى التنويم: تحيل خدمة عيادات في مدينة طبية مريضاً للتنويم. تحتاج الإحالة والجناح المستلم والزيارة المالية إلى مسؤوليات مترابطة. التشخيص والأدوية بين الفرق: تساهم عدة أقسام في مدينة طبية في رعاية مريض. تحتاج الشبكة إلى التمييز بين التشغيل الداخلي والمعلومات المتبادلة مع الأنظمة القائمة. رؤية قيادية تستند إلى بيانات المصدر: يراجع قادة مدينة طبية النشاط التشغيلي والإيرادي عبر كيانات محددة. يحتاجون إلى عروض قابلة للمقارنة بمصدر وحدود تقارير واضحين.","href":"/solutions/medical-city#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=medical_cities#configuration"}],"solution":{"coverage":[{"name":"حوكمة الشبكة","description":"حدد الكيانات وحدود السجلات ومسؤوليات الوصول عبر الشبكة المتفق عليها.","products":["network_governance","core"]},{"name":"الرعاية عبر البيئات","description":"اربط سياق العيادات والطوارئ والتنويم ضمن تكوين الشبكة.","products":["outpatient","emergency","inpatient"]},{"name":"العمل التخصصي المشترك","description":"اربط عمل المختبر والأدوية ومسؤوليات إمداد الأقسام.","products":["laboratory","pharmacy","inventory"]},{"name":"الأنظمة المترابطة","description":"اتفق على الأنظمة والاتصالات والبيانات المتبادلة بين الكيانات.","products":["interfaces"]},{"name":"عمليات الإيرادات","description":"اربط النشاط السريري ومتابعة الجهات الدافعة والمطابقة ضمن حدود الكيانات.","products":["revenue_cycle","billing_finance"]},{"name":"رؤية القيادة","description":"راجع التقارير التشغيلية والإيرادية المختارة بسياق مصادر واضح.","products":["analytics","rcm_reporting"]}],"cases":[{"type":"Illustrative operational scenario","title":"استمرارية عبر الكيانات","scenario":"ينتقل مريض بين خدمات شبكة مدينة طبية. يحتاج الكيان المستلم إلى سياق الرعاية المسموح مع احتفاظ كل منظمة بحدود بياناتها.","challenge":"تتطلب الاستمرارية بين الكيانات وصولاً محكوماً، لا مشاركة سجلات بلا حدود.","stages":[{"title":"تحديد حدود الشبكة","action":"الاتفاق على الكيانات ونطاق الهوية وتبادل السجلات المسموح لهذا التكوين.","owner":"فريق التكامل وتقنية المعلومات","record":"الكيانات · حدود الهوية · الصلاحيات"},{"title":"تسجيل الزيارة المصدر","action":"توثيق زيارة المريض الحالية وسبب الخدمة التالية.","owner":"الطبيب المعالج","record":"الزيارة المصدر · سبب الإحالة"},{"title":"تنسيق الخدمة المستلمة","action":"تأكيد الجهة المستلمة والفريق المسؤول عن الإحالة أو النقل.","owner":"الاستقبال والتنسيق","record":"الوجهة · الفريق · النقل"},{"title":"مشاركة السياق المسموح","action":"نقل المعلومات المتفق عليها عبر الاتصال المحدد مع مراجع المصدر.","owner":"فريق التكامل وتقنية المعلومات","record":"الاتصال · السجل المصدر · السياق المشترك"},{"title":"توثيق الرعاية المستلمة","action":"مراجعة المعلومات المسموح بها وتوثيق زيارة الكيان المستلم ومسؤولياته.","owner":"الطبيب المعالج","record":"الزيارة المستلمة · خطة الرعاية"},{"title":"مراجعة الاستمرارية مع الحوكمة","action":"مراجعة تقارير الشبكة المدعومة ضمن حدود الكيانات والصلاحيات المتفق عليها.","owner":"قيادة الخدمة","record":"عرض الكيان · الصلاحيات · التقارير"}],"exception":"إذا تعذرت مطابقة الهوية أو تجاوز الوصول الحدود المتفق عليها، تعالج الفرق المسؤولة ذلك قبل تبادل سجلات إضافية.","completion":["تملك الخدمة المستلمة سياق المصدر المسموح.","تحتفظ سجلات المصدر والمستلم بحدود كياناتها.","تتبع رؤية الشبكة نموذج الحوكمة المتفق عليه."]},{"type":"Illustrative operational scenario","title":"من الطوارئ إلى التنويم","scenario":"تحيل خدمة عيادات في مدينة طبية مريضاً للتنويم. تحتاج الإحالة والجناح المستلم والزيارة المالية إلى مسؤوليات مترابطة.","challenge":"يجب ألا يُفقد تغيير بيئة الرعاية سبب وصول المريض.","stages":[{"title":"توثيق الإحالة","action":"تسجيل تقييم العيادة وإحالة التنويم الموثقة.","owner":"الطبيب المعالج","record":"زيارة العيادة · الإحالة"},{"title":"تأكيد الكيان المستلم","action":"تحديد الخدمة المستلمة وهوية المريض ضمن حدود الشبكة المتفق عليها.","owner":"الاستقبال والتنسيق","record":"الوجهة · الهوية · الكيان"},{"title":"إنشاء زيارة التنويم","action":"ربط القبول ومسؤولية الجناح بسجل الكيان المستلم.","owner":"الاستقبال والتنسيق","record":"القبول · الجناح · الزيارة"},{"title":"مراجعة سياق التسليم","action":"مراجعة توثيق الإحالة المتاح وتسجيل ملاحظات الجناح المستلم ومسؤولياته.","owner":"فريق التمريض","record":"توثيق الإحالة · تسليم الجناح"},{"title":"تنسيق الرعاية والأقسام","action":"توثيق رعاية التنويم وربط طلبات الأقسام المطلوبة بزيارة التنويم.","owner":"الطبيب المعالج","record":"خطة الرعاية · الطلبات · النتائج"},{"title":"إنجاز الرعاية والمتابعة المالية","action":"حفظ سياق الخروج ومراجعة الرسوم المسجلة لكل كيان ومسؤولية حسابه.","owner":"الفريق المالي","record":"الخروج · رسوم الكيان · الحساب"}],"exception":"عند تغير الوجهة، يُحدث الكيان المسؤول وسجل النقل؛ وتظل المشاركة بين الكيانات خاضعة للصلاحيات المتفق عليها.","completion":["يحتفظ التنويم بسياق الإحالة الأصلي.","مسؤوليات الجناح والأقسام محددة.","تراعي استمرارية الرعاية حسابات الكيانات المنفصلة."]},{"type":"Illustrative operational scenario","title":"التشخيص والأدوية بين الفرق","scenario":"تساهم عدة أقسام في مدينة طبية في رعاية مريض. تحتاج الشبكة إلى التمييز بين التشغيل الداخلي والمعلومات المتبادلة مع الأنظمة القائمة.","challenge":"ربط النتائج وتشغيل القسم مسؤوليتان مختلفتان.","stages":[{"title":"تحديد مسؤولية الأقسام","action":"الاتفاق على الأقسام التي تعمل في منسوق والتي تحتفظ بنظام خارجي.","owner":"قيادة الخدمة","record":"القسم · نمط التشغيل · المسؤول"},{"title":"إنشاء طلب الزيارة","action":"ربط كل خدمة مطلوبة بالمريض والزيارة والقسم الصحيحين.","owner":"الطبيب المعالج","record":"الطلب · الزيارة · القسم"},{"title":"تنفيذ عمل القسم المحدد","action":"توثيق النشاط الداخلي المدعوم أو معالجة الطلب في النظام المصدر المحتفظ به.","owner":"فريق القسم","record":"نشاط القسم · مرجع المصدر"},{"title":"إعادة المعلومات المتفق عليها","action":"تبادل النتائج أو الحالة المتفق عليها عبر الاتصال ومواءمة الهوية المحددين.","owner":"فريق التكامل وتقنية المعلومات","record":"النتيجة · الاتصال · مواءمة الهوية"},{"title":"المراجعة في سياق الرعاية","action":"مراجعة معلومات القسم المتاحة وتوثيق مسؤولية الرعاية التالية.","owner":"الطبيب المعالج","record":"المراجعة السريرية · الإجراء التالي"},{"title":"تتبع حساب الخدمة","action":"مراجعة ربط الرسوم المحدد بمرجع المصدر الداخلي أو الخارجي للخدمة.","owner":"فريق الإيرادات","record":"الخدمة · الرسم · المصدر"}],"exception":"إذا تعطل اتصال، تعالج آلية التشغيل البديلة المتفق عليها ومسؤول المصدر المعلومات الناقصة؛ ولا يحل الوصول المرتبط محل تشغيل القسم.","completion":["لكل قسم مسؤول تشغيل محدد.","تحتفظ المعلومات العائدة بمصدرها وزيارتها.","يظل عمل الأقسام والمتابعة المالية مترابطين."]},{"type":"Illustrative operational scenario","title":"رؤية قيادية تستند إلى بيانات المصدر","scenario":"يراجع قادة مدينة طبية النشاط التشغيلي والإيرادي عبر كيانات محددة. يحتاجون إلى عروض قابلة للمقارنة بمصدر وحدود تقارير واضحين.","challenge":"لا يكون تقرير الشبكة مفيداً إلا عندما تكون الكيانات المشمولة والتعريفات واضحة.","stages":[{"title":"الاتفاق على عرض التقارير","action":"تحديد السؤال التشغيلي والكيانات المختارة والجمهور المصرح له.","owner":"قيادة الخدمة","record":"السؤال · الكيانات · الصلاحيات"},{"title":"تحديد نشاط المصدر","action":"تسجيل نشاط الرعاية والأقسام المعني داخل الكيان المصدر.","owner":"فريق القسم","record":"النشاط · الكيان · الزيارة"},{"title":"ربط سياق الإيرادات","action":"مراجعة المطالبات والردود المالية والعمل المعلق ضمن نطاق التقارير المحدد.","owner":"فريق الإيرادات","record":"المطالبات · الردود · عناصر العمل"},{"title":"مراجعة حدود التقارير","action":"فحص المصادر المشمولة وصلاحيات الكيانات والتعريفات التشغيلية المتفق عليها.","owner":"فريق التكامل وتقنية المعلومات","record":"المصادر · الصلاحيات · التعريفات"},{"title":"مراجعة التقرير المحدد","action":"استخدام العروض التشغيلية والإيرادية المدعومة لتحديد العمل الذي يتطلب اهتماماً.","owner":"قيادة الخدمة","record":"التقرير · المراجعة · العمل المطلوب"},{"title":"إسناد متابعة بمسؤولية واضحة","action":"تسجيل الفريق المسؤول وإعادة الأسئلة التشغيلية إلى المصدر المعني.","owner":"قيادة الخدمة","record":"الإجراء · المسؤول · مرجع المصدر"}],"exception":"يُحدد المصدر غير المكتمل أثناء المراجعة بدلاً من اعتباره نشاطاً صفرياً دون توضيح؛ ويعالج مسؤول المصدر فجوة التقارير.","completion":["يعرف جمهور التقارير الكيانات المشمولة.","تحتفظ الأسئلة التشغيلية بسياق مصدرها.","تعود المتابعة إلى الفريق المسؤول."]}]}}},{"slug":"/solutions/polyclinics","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/polyclinics","title":"Polyclinics management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"Connect specialties while keeping the shared patient and financial context.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"Connect specialties while keeping the shared patient and financial context.","description":"Bring specialist visits, diagnostics, medication and revenue together without losing the patient’s context. Reception & scheduling, Specialist care, Diagnostic work, Pharmacy &…","answers":[{"question":"Which workflows does this solution connect?","answer":"Reception & scheduling: Keep each specialty visit connected to registration and encounter access. Specialist care: Carry documentation and referral context across the agreed specialty workflow. Diagnostic work: Link laboratory orders, specimens and results to the relevant encounter. Pharmacy & supply: Connect medication requests, dispensing and stock responsibilities. Visit finance: Keep invoices and payments connected to care activity across specialties. Payer follow-up: Follow eligibility, approvals, claims, denials and reconciliation.","href":"/solutions/polyclinics"},{"question":"Where can I see complete operational scenarios?","answer":"A specialty referral: A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results. Diagnostic work in the care journey: A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review. Medication, from request to dispensing: A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work. Eligibility to reconciliation: An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.","href":"/solutions/polyclinics#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=polyclinics#configuration"}],"solution":{"coverage":[{"name":"Reception & scheduling","description":"Keep each specialty visit connected to registration and encounter access.","products":["outpatient","patient_access"]},{"name":"Specialist care","description":"Carry documentation and referral context across the agreed specialty workflow.","products":["outpatient","clinical_documentation"]},{"name":"Diagnostic work","description":"Link laboratory orders, specimens and results to the relevant encounter.","products":["laboratory","orders_medication"]},{"name":"Pharmacy & supply","description":"Connect medication requests, dispensing and stock responsibilities.","products":["pharmacy","inventory","orders_medication"]},{"name":"Visit finance","description":"Keep invoices and payments connected to care activity across specialties.","products":["billing_finance"]},{"name":"Payer follow-up","description":"Follow eligibility, approvals, claims, denials and reconciliation.","products":["revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"A specialty referral","scenario":"A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.","challenge":"Different specialties should add to one patient story.","stages":[{"title":"Document the first consultation","action":"Record the assessment and the reason a specialist review is requested.","owner":"Treating clinician","record":"Assessment · Referral reason"},{"title":"Coordinate the referral","action":"Arrange the receiving specialty appointment against the existing patient identity.","owner":"Access & coordination","record":"Referral · Specialty · Appointment"},{"title":"Review the shared context","action":"Review the referring note and relevant available results before documenting the specialist encounter.","owner":"Treating clinician","record":"Referring note · Results · Encounter"},{"title":"Connect specialist requests","action":"Link the specialist’s orders and prescription to the receiving consultation.","owner":"Treating clinician","record":"Specialist note · Orders · Prescription"},{"title":"Return the care plan","action":"Document the specialist assessment and follow-up responsibility for the referring service.","owner":"Treating clinician","record":"Assessment · Plan · Next service"},{"title":"Review each service account","action":"Keep each encounter’s services and billing distinct while retaining the shared patient context.","owner":"Finance team","record":"Encounter charges · Patient account"}],"exception":"If the receiving service needs more information, record the missing referral context and return the task to the responsible service.","completion":["A referral with its clinical reason and receiving service.","Specialist work adds to the shared patient record.","Separate service accounts retain their encounter references."]},{"type":"Illustrative operational scenario","title":"Diagnostic work in the care journey","scenario":"A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review.","challenge":"The result must return to the patient and the consultation that requested it.","stages":[{"title":"Create the clinical request","action":"Record the requested laboratory service in the correct specialty encounter.","owner":"Treating clinician","record":"Order · Encounter · Requested service"},{"title":"Receive the laboratory work","action":"Confirm the patient, request and supported specimen workflow before processing.","owner":"Laboratory team","record":"Patient · Request · Specimen"},{"title":"Process and document","action":"Complete the selected native laboratory work or agreed LIS exchange.","owner":"Laboratory team","record":"Laboratory activity · Source system"},{"title":"Return the available result","action":"Attach the documented result to its request and patient encounter.","owner":"Laboratory team","record":"Result · Request reference"},{"title":"Record clinical review","action":"Review the result professionally and document the next care action.","owner":"Treating clinician","record":"Review note · Care action"},{"title":"Close the service loop","action":"Review the delivered service charge while retaining any remaining clinical follow-up.","owner":"Revenue team","record":"Service charge · Follow-up"}],"exception":"A rejected or incomplete specimen stays connected to the original request, with the laboratory’s documented reason and next responsibility.","completion":["The diagnostic request and result remain traceable.","The clinician’s review is part of the care record.","Laboratory activity connects to the relevant account."]},{"type":"Illustrative operational scenario","title":"Medication, from request to dispensing","scenario":"A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work.","challenge":"Prescribing, dispensing and stock movement need distinct responsibilities in one connected path.","stages":[{"title":"Document the prescription","action":"Record the clinician’s prescription against the specialty encounter.","owner":"Treating clinician","record":"Prescription · Clinician · Encounter"},{"title":"Receive the pharmacy work","action":"Verify the patient and prescription context within the selected pharmacy scope.","owner":"Pharmacy team","record":"Patient · Prescription reference"},{"title":"Review the medication request","action":"Document the pharmacist’s review and any clarification needed from the prescriber.","owner":"Pharmacy team","record":"Pharmacy review · Clarification"},{"title":"Record the dispensing step","action":"Record the agreed dispensing activity against the prescription and patient.","owner":"Pharmacy team","record":"Dispensing record · Prescription"},{"title":"Connect stock responsibility","action":"Link recorded dispensing to inventory responsibilities where inventory is included.","owner":"Department team","record":"Dispensing · Stock movement"},{"title":"Complete the account and follow-up","action":"Review medication charges and preserve documented follow-up for the care team.","owner":"Finance team","record":"Medication charge · Care follow-up"}],"exception":"An unavailable item or unclear prescription returns to the responsible pharmacist and prescriber; the software does not choose a substitute treatment.","completion":["Dispensing has a prescription and encounter reference.","Stock and pharmacy responsibilities remain distinct.","Medication activity is visible in financial follow-up."]},{"type":"Illustrative operational scenario","title":"Eligibility to reconciliation","scenario":"An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.","challenge":"Several departments can contribute to one claim without losing the origin of each service.","stages":[{"title":"Verify coverage","action":"Record eligibility and the relevant coverage context for the visit.","owner":"Access & coordination","record":"Eligibility · Coverage · Encounter"},{"title":"Follow service approvals","action":"Connect required preauthorization requests and payer decisions to the requested services.","owner":"Revenue team","record":"Service · Authorization · Response"},{"title":"Capture delivered services","action":"Record consultation, diagnostic and pharmacy activity with its encounter reference.","owner":"Department team","record":"Department activity · Charge reference"},{"title":"Review and submit the claim","action":"Review the claim work items and use the agreed, activated exchange channel.","owner":"Revenue team","record":"Claim · Submission · Exchange trace"},{"title":"Resolve payer responses","action":"Assign rejection reasons for correction, review and documented resubmission where needed.","owner":"Revenue team","record":"Response · Reason · Resubmission"},{"title":"Reconcile the remittance","action":"Match payer remittance to claim records and assign remaining financial differences.","owner":"Finance team","record":"Remittance · Claim · Difference"}],"exception":"A partially paid claim keeps the paid allocation and unresolved lines separate, with a documented reason and follow-up owner.","completion":["Every claim line retains its service context.","Corrections and resubmissions have a review history.","Paid and unresolved amounts have clear ownership."]}]}},"ar":{"url":"https://mansoq.com/solutions/polyclinics?lang=ar","title":"المجمعات الطبية | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"اربط التخصصات مع الحفاظ على سياق المريض والمالية المشترك.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"اربط التخصصات مع الحفاظ على سياق المريض والمالية المشترك.","description":"اجمع الزيارات التخصصية والتشخيص والأدوية والإيرادات دون فقد سياق المريض. الاستقبال والجدولة، الرعاية التخصصية، العمل التشخيصي، الصيدلية والإمداد، مالية الزيارة، متابعة الجهات…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"الاستقبال والجدولة: اربط زيارة كل تخصص بالتسجيل والوصول إلى الزيارة. الرعاية التخصصية: انقل التوثيق وسياق الإحالة عبر المسار التخصصي المتفق عليه. العمل التشخيصي: اربط طلبات المختبر والعينات والنتائج بالزيارة المناسبة. الصيدلية والإمداد: اربط طلبات الأدوية والصرف ومسؤوليات المخزون. مالية الزيارة: اربط الفواتير والمدفوعات بنشاط الرعاية عبر التخصصات. متابعة الجهات الدافعة: تابع الأهلية والموافقات والمطالبات والرفض والمطابقة.","href":"/solutions/polyclinics"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"إحالة تخصصية: يُحال مريض من تخصص إلى آخر داخل مجمع عيادات. يحتاج الطبيب المستلم إلى سبب الإحالة والتوثيق السابق والنتائج المتاحة. التشخيص ضمن رحلة الرعاية: تطلب عيادة تخصصية فحصاً مخبرياً. ينفذ المختبر العمل ويعيد النتيجة ويوثق الطبيب مراجعتها. الدواء من الطلب إلى الصرف: يغادر مريض استشارة مختص بوصفة. تراجع صيدلية مجمع العيادات عمل الدواء المحدد وتصرفه وتسجله. من الأهلية إلى المطابقة: تشمل زيارة تخصصية مؤمّنة فحوصاً وأدوية. يتابع فريق الإيرادات التغطية والموافقات والمطالبات وتخصيص السداد عبر تلك الخدمات.","href":"/solutions/polyclinics#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=polyclinics#configuration"}],"solution":{"coverage":[{"name":"الاستقبال والجدولة","description":"اربط زيارة كل تخصص بالتسجيل والوصول إلى الزيارة.","products":["outpatient","patient_access"]},{"name":"الرعاية التخصصية","description":"انقل التوثيق وسياق الإحالة عبر المسار التخصصي المتفق عليه.","products":["outpatient","clinical_documentation"]},{"name":"العمل التشخيصي","description":"اربط طلبات المختبر والعينات والنتائج بالزيارة المناسبة.","products":["laboratory","orders_medication"]},{"name":"الصيدلية والإمداد","description":"اربط طلبات الأدوية والصرف ومسؤوليات المخزون.","products":["pharmacy","inventory","orders_medication"]},{"name":"مالية الزيارة","description":"اربط الفواتير والمدفوعات بنشاط الرعاية عبر التخصصات.","products":["billing_finance"]},{"name":"متابعة الجهات الدافعة","description":"تابع الأهلية والموافقات والمطالبات والرفض والمطابقة.","products":["revenue_cycle"]}],"cases":[{"type":"Illustrative operational scenario","title":"إحالة تخصصية","scenario":"يُحال مريض من تخصص إلى آخر داخل مجمع عيادات. يحتاج الطبيب المستلم إلى سبب الإحالة والتوثيق السابق والنتائج المتاحة.","challenge":"يجب أن تضيف التخصصات المختلفة إلى قصة مريض واحدة.","stages":[{"title":"توثيق الاستشارة الأولى","action":"تسجيل التقييم وسبب طلب مراجعة المختص.","owner":"الطبيب المعالج","record":"التقييم · سبب الإحالة"},{"title":"تنسيق الإحالة","action":"تنظيم موعد التخصص المستلم مقابل هوية المريض القائمة.","owner":"الاستقبال والتنسيق","record":"الإحالة · التخصص · الموعد"},{"title":"مراجعة السياق المشترك","action":"مراجعة توثيق الطبيب المحيل والنتائج المتاحة ذات الصلة قبل توثيق زيارة المختص.","owner":"الطبيب المعالج","record":"توثيق الإحالة · النتائج · الزيارة"},{"title":"ربط طلبات المختص","action":"ربط طلبات المختص ووصفته بالاستشارة المستلمة.","owner":"الطبيب المعالج","record":"توثيق المختص · الطلبات · الوصفة"},{"title":"إعادة خطة الرعاية","action":"توثيق تقييم المختص ومسؤولية المتابعة للخدمة المحيلة.","owner":"الطبيب المعالج","record":"التقييم · الخطة · الخدمة التالية"},{"title":"مراجعة حساب كل خدمة","action":"إبقاء خدمات كل زيارة وفوترتها متميزة مع الاحتفاظ بسياق المريض المشترك.","owner":"الفريق المالي","record":"رسوم الزيارة · حساب المريض"}],"exception":"إذا احتاجت الخدمة المستلمة إلى معلومات إضافية، يُسجل سياق الإحالة الناقص وتُعاد المهمة إلى الخدمة المسؤولة.","completion":["إحالة تحمل سببها السريري والخدمة المستلمة.","يُضاف عمل المختص إلى سجل المريض المشترك.","تحتفظ حسابات الخدمات المنفصلة بمراجع زياراتها."]},{"type":"Illustrative operational scenario","title":"التشخيص ضمن رحلة الرعاية","scenario":"تطلب عيادة تخصصية فحصاً مخبرياً. ينفذ المختبر العمل ويعيد النتيجة ويوثق الطبيب مراجعتها.","challenge":"يجب أن تعود النتيجة إلى المريض والاستشارة التي طلبتها.","stages":[{"title":"إنشاء الطلب السريري","action":"تسجيل خدمة المختبر المطلوبة في زيارة التخصص الصحيحة.","owner":"الطبيب المعالج","record":"الطلب · الزيارة · الخدمة المطلوبة"},{"title":"استلام عمل المختبر","action":"تأكيد المريض والطلب ومسار العينات المدعوم قبل المعالجة.","owner":"فريق المختبر","record":"المريض · الطلب · العينة"},{"title":"المعالجة والتوثيق","action":"إنجاز عمل المختبر الداخلي المحدد أو تبادل نظام المختبر المتفق عليه.","owner":"فريق المختبر","record":"نشاط المختبر · النظام المصدر"},{"title":"إعادة النتيجة المتاحة","action":"إرفاق النتيجة الموثقة بطلبها وزيارة المريض.","owner":"فريق المختبر","record":"النتيجة · مرجع الطلب"},{"title":"تسجيل المراجعة السريرية","action":"مراجعة النتيجة مهنياً وتوثيق إجراء الرعاية التالي.","owner":"الطبيب المعالج","record":"ملاحظة المراجعة · إجراء الرعاية"},{"title":"إقفال مسار الخدمة","action":"مراجعة رسم الخدمة المنجزة مع الاحتفاظ بأي متابعة سريرية متبقية.","owner":"فريق الإيرادات","record":"رسم الخدمة · المتابعة"}],"exception":"تبقى العينة المرفوضة أو غير المكتملة مرتبطة بالطلب الأصلي، مع سبب المختبر الموثق والمسؤولية التالية.","completion":["يظل طلب التشخيص ونتيجته قابلين للتتبع.","مراجعة الطبيب جزء من سجل الرعاية.","يرتبط نشاط المختبر بالحساب المعني."]},{"type":"Illustrative operational scenario","title":"الدواء من الطلب إلى الصرف","scenario":"يغادر مريض استشارة مختص بوصفة. تراجع صيدلية مجمع العيادات عمل الدواء المحدد وتصرفه وتسجله.","challenge":"تحتاج الوصفة والصرف وحركة المخزون إلى مسؤوليات متميزة ضمن مسار مترابط واحد.","stages":[{"title":"توثيق الوصفة","action":"تسجيل وصفة الطبيب مقابل زيارة التخصص.","owner":"الطبيب المعالج","record":"الوصفة · الطبيب · الزيارة"},{"title":"استلام عمل الصيدلية","action":"التحقق من المريض وسياق الوصفة ضمن نطاق الصيدلية المحدد.","owner":"فريق الصيدلية","record":"المريض · مرجع الوصفة"},{"title":"مراجعة طلب الدواء","action":"توثيق مراجعة الصيدلي وأي توضيح مطلوب من الطبيب الواصف.","owner":"فريق الصيدلية","record":"مراجعة الصيدلية · التوضيح"},{"title":"تسجيل خطوة الصرف","action":"تسجيل نشاط الصرف المتفق عليه مقابل الوصفة والمريض.","owner":"فريق الصيدلية","record":"سجل الصرف · الوصفة"},{"title":"ربط مسؤولية المخزون","action":"ربط الصرف المسجل بمسؤوليات المخزون حيث يشمل النطاق المخزون.","owner":"فريق القسم","record":"الصرف · حركة المخزون"},{"title":"إنجاز الحساب والمتابعة","action":"مراجعة رسوم الدواء وحفظ المتابعة الموثقة لفريق الرعاية.","owner":"الفريق المالي","record":"رسم الدواء · متابعة الرعاية"}],"exception":"يعود الصنف غير المتاح أو الوصفة غير الواضحة إلى الصيدلي والطبيب المسؤولين؛ ولا تختار البرمجيات علاجاً بديلاً.","completion":["للصرف مرجع وصفة وزيارة.","تظل مسؤوليات المخزون والصيدلية متميزة.","يظهر نشاط الدواء في المتابعة المالية."]},{"type":"Illustrative operational scenario","title":"من الأهلية إلى المطابقة","scenario":"تشمل زيارة تخصصية مؤمّنة فحوصاً وأدوية. يتابع فريق الإيرادات التغطية والموافقات والمطالبات وتخصيص السداد عبر تلك الخدمات.","challenge":"يمكن لعدة أقسام المساهمة في مطالبة واحدة دون فقد مصدر كل خدمة.","stages":[{"title":"التحقق من التغطية","action":"تسجيل الأهلية وسياق التغطية المعني للزيارة.","owner":"الاستقبال والتنسيق","record":"الأهلية · التغطية · الزيارة"},{"title":"متابعة موافقات الخدمات","action":"ربط طلبات الموافقة المسبقة المطلوبة وقرارات الجهة الدافعة بالخدمات المطلوبة.","owner":"فريق الإيرادات","record":"الخدمة · الموافقة · الرد"},{"title":"التقاط الخدمات المنجزة","action":"تسجيل نشاط الاستشارة والتشخيص والصيدلية مع مرجع الزيارة.","owner":"فريق القسم","record":"نشاط القسم · مرجع الرسم"},{"title":"مراجعة المطالبة وإرسالها","action":"مراجعة عناصر عمل المطالبة واستخدام قناة التبادل المتفق عليها والمفعّلة.","owner":"فريق الإيرادات","record":"المطالبة · الإرسال · تتبع التبادل"},{"title":"معالجة ردود الجهة الدافعة","action":"إسناد أسباب الرفض للتصحيح والمراجعة وإعادة الإرسال الموثقة عند الحاجة.","owner":"فريق الإيرادات","record":"الرد · السبب · إعادة الإرسال"},{"title":"مطابقة إشعار السداد","action":"مطابقة إشعار سداد الجهة الدافعة بسجلات المطالبة وإسناد الفروقات المالية المتبقية.","owner":"الفريق المالي","record":"إشعار السداد · المطالبة · الفرق"}],"exception":"تُميز المطالبة المسددة جزئياً تخصيص المبلغ المسدد عن البنود غير المحسومة، مع سبب موثق ومسؤول متابعة.","completion":["يحتفظ كل بند مطالبة بسياق خدمته.","للتصحيحات وإعادة الإرسال تاريخ مراجعة.","للمبالغ المسددة وغير المحسومة مسؤولية واضحة."]}]}}},{"slug":"/solutions/teleicu","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/solutions/teleicu","title":"TeleICU management software | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"A defined remote critical-care composition around the local team.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A defined remote critical-care composition around the local team.","description":"Bring local critical-care context and remote specialist review together, with defined interfaces and clear clinical responsibility. Local care team, Remote specialist, Clinical…","answers":[{"question":"Which workflows does this solution connect?","answer":"Local care team: Prepare the supported case context for remote review. Remote specialist: Bring relevant clinical documentation into the agreed remote review workflow. Clinical information: Keep supported observations, orders, results and medication in context. Defined connections: Identify each source system, device or collaboration interface in the agreed scope. Team handover: Carry documented review context and the next responsibility back to the local team. Governed access: Keep identity, access and traceable actions on the shared foundation.","href":"/solutions/teleicu"},{"question":"Where can I see complete operational scenarios?","answer":"A remote critical-care review: A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team. A handover between care teams: A remote ICU specialist hands an ongoing review to the next specialist. The local team needs consistent context and explicit follow-up responsibility. Orders and results in the review: A TeleICU review needs notes and results held in a local source system. The teams agree exactly which information is available for the review. An interface with clear ownership: A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.","href":"/solutions/teleicu#solution-cases"},{"question":"How do I configure and price this solution?","answer":"Choose this care setting in the package builder, review included and optional products, then confirm implementation, interfaces and operating scope. Published care packages have no automatic trial; a demonstration or evaluation is arranged on request. Published workflow cases are illustrative; they do not claim named customer outcomes.","href":"/pricing?profile=teleicu#configuration"}],"solution":{"coverage":[{"name":"Local care team","description":"Prepare the supported case context for remote review.","products":["teleicu","clinical_documentation"]},{"name":"Remote specialist","description":"Bring relevant clinical documentation into the agreed remote review workflow.","products":["teleicu","clinical_documentation"]},{"name":"Clinical information","description":"Keep supported observations, orders, results and medication in context.","products":["clinical_documentation","orders_medication"]},{"name":"Defined connections","description":"Identify each source system, device or collaboration interface in the agreed scope.","products":["interfaces"]},{"name":"Team handover","description":"Carry documented review context and the next responsibility back to the local team.","products":["teleicu","clinical_documentation"]},{"name":"Governed access","description":"Keep identity, access and traceable actions on the shared foundation.","products":["core"]}],"cases":[{"type":"Illustrative operational scenario","title":"A remote critical-care review","scenario":"A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team.","challenge":"Remote expertise needs clinical context and a clear return path to the bedside.","stages":[{"title":"Prepare the local case","action":"Confirm the patient encounter and document the question for specialist review.","owner":"Local care team","record":"Encounter · Review question"},{"title":"Bring the supported context","action":"Make the agreed notes and observations available through the selected source-system connection.","owner":"Integration & IT team","record":"Source · Notes · Observations"},{"title":"Perform the remote review","action":"Review the available information and record the specialist’s assessment within the agreed service.","owner":"Remote specialist","record":"Review · Specialist note"},{"title":"Return documented recommendations","action":"Document recommendations and the points requiring local clinical review.","owner":"Remote specialist","record":"Recommendations · Local review"},{"title":"Record the bedside decision","action":"Review the specialist note and record the local clinician’s care decision and responsibilities.","owner":"Local care team","record":"Local decision · Care responsibility"},{"title":"Complete the review handover","action":"Document completed review work and any further specialist or bedside follow-up.","owner":"Local care team","record":"Review record · Follow-up owner"}],"exception":"Missing source information is referred back to the local team. Video, device data and live monitoring are separate connections, not assumed features of this scenario.","completion":["The remote review has a documented source and question.","Recommendations return to an accountable local clinician.","Bedside decisions and subsequent follow-up stay traceable."]},{"type":"Illustrative operational scenario","title":"A handover between care teams","scenario":"A remote ICU specialist hands an ongoing review to the next specialist. The local team needs consistent context and explicit follow-up responsibility.","challenge":"A change of specialist must not erase the review history.","stages":[{"title":"Identify active review work","action":"Confirm the patient case and the current documented specialist review.","owner":"Remote specialist","record":"Patient · Active review"},{"title":"Review the local update","action":"Provide the documented clinical update within the agreed information-sharing scope.","owner":"Local care team","record":"Local update · Source context"},{"title":"Record the specialist handover","action":"Document the previous review, open questions and next specialist responsibility.","owner":"Remote specialist","record":"Review history · Open questions · Owner"},{"title":"Review as the receiving specialist","action":"Read the prior context and document the receiving specialist’s assessment.","owner":"Remote specialist","record":"Receiving review · Assessment"},{"title":"Connect back to local care","action":"Review the updated recommendations and retain local clinical decision responsibility.","owner":"Local care team","record":"Recommendations · Local decision"},{"title":"Set the next review action","action":"Record whether further review is required and which service owns it.","owner":"Remote specialist","record":"Next review · Responsible service"}],"exception":"If local and remote records differ, identify the source and ask the responsible clinician to reconcile the information before relying on it.","completion":["The next specialist can review the earlier assessment.","Open questions have an explicit owner.","The local team retains a connected review history."]},{"type":"Illustrative operational scenario","title":"Orders and results in the review","scenario":"A TeleICU review needs notes and results held in a local source system. The teams agree exactly which information is available for the review.","challenge":"A remote record should show its source and permitted scope.","stages":[{"title":"Define the review dataset","action":"Identify the clinical notes, observations and results required for this service.","owner":"Local care team","record":"Required information · Review scope"},{"title":"Confirm source ownership","action":"Document the source system, identity mapping and team responsible for the connection.","owner":"Integration & IT team","record":"Source system · Mapping · Owner"},{"title":"Make agreed information available","action":"Carry supported source information through the selected, tested interface.","owner":"Integration & IT team","record":"Interface · Source references"},{"title":"Review the source context","action":"Check the available context and identify any missing information for local follow-up.","owner":"Remote specialist","record":"Available notes · Missing context"},{"title":"Document the professional review","action":"Record the review against the correct case and identify the information used.","owner":"Remote specialist","record":"Review note · Case · Source context"},{"title":"Return the next action","action":"Review the specialist record and document the local care or information follow-up.","owner":"Local care team","record":"Local response · Follow-up"}],"exception":"Unavailable data is made explicit in the review. An interface agreement determines what can be exchanged; no universal device compatibility is implied.","completion":["The review uses an identified source record.","Missing context has a responsible follow-up path.","The local response stays connected to the specialist note."]},{"type":"Illustrative operational scenario","title":"An interface with clear ownership","scenario":"A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.","challenge":"A usable connection joins technical delivery to a real clinical handover.","stages":[{"title":"Define the service boundary","action":"Agree the local and remote teams, systems and information needed for the review service.","owner":"Service leadership","record":"Teams · Systems · Information scope"},{"title":"Specify the interface","action":"Document the agreed protocol, identity mapping, licenses and delivery owners.","owner":"Integration & IT team","record":"Protocol · Mapping · Delivery owner"},{"title":"Rehearse a supported case","action":"Prepare an authorized demonstration case and confirm the intended source information.","owner":"Local care team","record":"Demonstration case · Source record"},{"title":"Verify the exchange and access","action":"Review the exchanged context, permitted access and agreed failure handling.","owner":"Integration & IT team","record":"Exchange trace · Access · Fallback"},{"title":"Rehearse the review handover","action":"Document the review and demonstrate its return to the responsible local clinician.","owner":"Remote specialist","record":"Specialist review · Local handover"},{"title":"Accept the operating scope","action":"Agree acceptance, support ownership and the activated service boundary.","owner":"Service leadership","record":"Acceptance · Support · Activation"}],"exception":"A failed test returns to the named interface owner. Activation follows agreed acceptance; connectivity does not grant unrestricted record access.","completion":["The interface has a defined technical and clinical purpose.","Review and fallback responsibilities are agreed.","The accepted service has a clear activation boundary."]}]}},"ar":{"url":"https://mansoq.com/solutions/teleicu?lang=ar","title":"العناية المركزة عن بُعد | حلول منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"تهيئة محددة للعناية الحرجة عن بُعد حول الفريق المحلي.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"تهيئة محددة للعناية الحرجة عن بُعد حول الفريق المحلي.","description":"اجمع سياق العناية الحرجة المحلي ومراجعة المختص عن بُعد باتصالات محددة ومسؤولية سريرية واضحة. فريق الرعاية المحلي، المختص عن بُعد، المعلومات السريرية، اتصالات محددة، تسليم…","answers":[{"question":"ما المسارات التي يربطها هذا الحل؟","answer":"فريق الرعاية المحلي: جهز سياق الحالة المدعوم للمراجعة عن بُعد. المختص عن بُعد: أدخل التوثيق السريري ذي الصلة في مسار المراجعة عن بُعد المتفق عليه. المعلومات السريرية: احتفظ بالملاحظات والطلبات والنتائج والأدوية المدعومة ضمن السياق. اتصالات محددة: حدد كل نظام مصدر أو جهاز أو اتصال تعاون ضمن النطاق المتفق عليه. تسليم المسؤولية: أعد سياق المراجعة الموثق والمسؤولية التالية إلى الفريق المحلي. وصول محكوم: احتفظ بالهوية والصلاحيات والإجراءات القابلة للتتبع ضمن الأساس المشترك.","href":"/solutions/teleicu"},{"question":"أين أرى سيناريوهات تشغيل متكاملة؟","answer":"مراجعة عناية حرجة عن بُعد: يطلب فريق عناية مركزة محلي مراجعة مختص عن بُعد. يحتاج المختص إلى السجل السريري المتفق عليه، بينما تبقى رعاية المريض بيد الفريق المحلي. تسليم بين فرق الرعاية: يسلم مختص عناية مركزة عن بُعد مراجعة مستمرة إلى المختص التالي. يحتاج الفريق المحلي إلى سياق متسق ومسؤولية متابعة صريحة. الطلبات والنتائج ضمن المراجعة: تحتاج مراجعة عناية مركزة عن بُعد إلى توثيق ونتائج محفوظة في نظام محلي. تتفق الفرق على المعلومات المتاحة للمراجعة بدقة. اتصال بمسؤولية واضحة: يضيف مستشفى اتصال عناية مركزة عن بُعد إلى جانب نظامه السريري القائم. تحتاج التقنية والأطباء وقيادة الخدمة إلى مسؤوليات تنفيذ وتشغيل واضحة.","href":"/solutions/teleicu#solution-cases"},{"question":"كيف أهيئ هذا الحل وأراجع سعره؟","answer":"اختر بيئة الرعاية في منشئ الحزمة وراجع المنتجات المشمولة والاختيارية ثم أكد التنفيذ والاتصالات والنطاق. لا تشمل باقات الرعاية المنشورة فترة تجريبية تلقائية؛ يرتب العرض التوضيحي أو التقييم عند الطلب. الحالات المنشورة توضيحية ولا تمثل نتائج لعملاء محددين.","href":"/pricing?profile=teleicu#configuration"}],"solution":{"coverage":[{"name":"فريق الرعاية المحلي","description":"جهز سياق الحالة المدعوم للمراجعة عن بُعد.","products":["teleicu","clinical_documentation"]},{"name":"المختص عن بُعد","description":"أدخل التوثيق السريري ذي الصلة في مسار المراجعة عن بُعد المتفق عليه.","products":["teleicu","clinical_documentation"]},{"name":"المعلومات السريرية","description":"احتفظ بالملاحظات والطلبات والنتائج والأدوية المدعومة ضمن السياق.","products":["clinical_documentation","orders_medication"]},{"name":"اتصالات محددة","description":"حدد كل نظام مصدر أو جهاز أو اتصال تعاون ضمن النطاق المتفق عليه.","products":["interfaces"]},{"name":"تسليم المسؤولية","description":"أعد سياق المراجعة الموثق والمسؤولية التالية إلى الفريق المحلي.","products":["teleicu","clinical_documentation"]},{"name":"وصول محكوم","description":"احتفظ بالهوية والصلاحيات والإجراءات القابلة للتتبع ضمن الأساس المشترك.","products":["core"]}],"cases":[{"type":"Illustrative operational scenario","title":"مراجعة عناية حرجة عن بُعد","scenario":"يطلب فريق عناية مركزة محلي مراجعة مختص عن بُعد. يحتاج المختص إلى السجل السريري المتفق عليه، بينما تبقى رعاية المريض بيد الفريق المحلي.","challenge":"تحتاج الخبرة عن بُعد إلى سياق سريري ومسار عودة واضح إلى سرير المريض.","stages":[{"title":"تجهيز الحالة المحلية","action":"تأكيد زيارة المريض وتوثيق السؤال المطلوب لمراجعة المختص.","owner":"فريق الرعاية المحلي","record":"الزيارة · سؤال المراجعة"},{"title":"إحضار السياق المدعوم","action":"إتاحة التوثيق والملاحظات المتفق عليها عبر اتصال النظام المصدر المحدد.","owner":"فريق التكامل وتقنية المعلومات","record":"المصدر · التوثيق · الملاحظات"},{"title":"تنفيذ المراجعة عن بُعد","action":"مراجعة المعلومات المتاحة وتسجيل تقييم المختص ضمن الخدمة المتفق عليها.","owner":"المختص عن بُعد","record":"المراجعة · توثيق المختص"},{"title":"إعادة التوصيات الموثقة","action":"توثيق التوصيات والنقاط التي تتطلب مراجعة سريرية محلية.","owner":"المختص عن بُعد","record":"التوصيات · المراجعة المحلية"},{"title":"تسجيل قرار الفريق المحلي","action":"مراجعة توثيق المختص وتسجيل قرار الطبيب المحلي ومسؤوليات الرعاية.","owner":"فريق الرعاية المحلي","record":"القرار المحلي · مسؤولية الرعاية"},{"title":"إنجاز تسليم المراجعة","action":"توثيق عمل المراجعة المنجز وأي متابعة إضافية للمختص أو الفريق المحلي.","owner":"فريق الرعاية المحلي","record":"سجل المراجعة · مسؤول المتابعة"}],"exception":"تُعاد معلومات المصدر الناقصة إلى الفريق المحلي. الفيديو وبيانات الأجهزة والمراقبة الحية اتصالات مستقلة وليست وظائف مفترضة في هذا المسار.","completion":["للمراجعة عن بُعد مصدر وسؤال موثقان.","تعود التوصيات إلى طبيب محلي مسؤول.","تظل قرارات الفريق المحلي والمتابعة اللاحقة قابلتين للتتبع."]},{"type":"Illustrative operational scenario","title":"تسليم بين فرق الرعاية","scenario":"يسلم مختص عناية مركزة عن بُعد مراجعة مستمرة إلى المختص التالي. يحتاج الفريق المحلي إلى سياق متسق ومسؤولية متابعة صريحة.","challenge":"يجب ألا يؤدي تغيير المختص إلى محو تاريخ المراجعة.","stages":[{"title":"تحديد عمل المراجعة الجاري","action":"تأكيد حالة المريض ومراجعة المختص الموثقة الحالية.","owner":"المختص عن بُعد","record":"المريض · المراجعة الجارية"},{"title":"مراجعة التحديث المحلي","action":"تقديم التحديث السريري الموثق ضمن نطاق مشاركة المعلومات المتفق عليه.","owner":"فريق الرعاية المحلي","record":"التحديث المحلي · سياق المصدر"},{"title":"تسجيل تسليم المختص","action":"توثيق المراجعة السابقة والأسئلة المفتوحة ومسؤولية المختص التالي.","owner":"المختص عن بُعد","record":"تاريخ المراجعة · الأسئلة المفتوحة · المسؤول"},{"title":"المراجعة بواسطة المختص المستلم","action":"قراءة السياق السابق وتوثيق تقييم المختص المستلم.","owner":"المختص عن بُعد","record":"المراجعة المستلمة · التقييم"},{"title":"إعادة الربط بالرعاية المحلية","action":"مراجعة التوصيات المحدثة والاحتفاظ بمسؤولية القرار السريري المحلي.","owner":"فريق الرعاية المحلي","record":"التوصيات · القرار المحلي"},{"title":"تحديد إجراء المراجعة التالي","action":"تسجيل الحاجة إلى مراجعة إضافية والخدمة المسؤولة عنها.","owner":"المختص عن بُعد","record":"المراجعة التالية · الخدمة المسؤولة"}],"exception":"إذا اختلف السجل المحلي عن البعيد، يُحدد المصدر ويُطلب من الطبيب المسؤول تسوية المعلومات قبل الاعتماد عليها.","completion":["يستطيع المختص التالي مراجعة التقييم السابق.","للأسئلة المفتوحة مسؤول صريح.","يحتفظ الفريق المحلي بتاريخ مراجعة مترابط."]},{"type":"Illustrative operational scenario","title":"الطلبات والنتائج ضمن المراجعة","scenario":"تحتاج مراجعة عناية مركزة عن بُعد إلى توثيق ونتائج محفوظة في نظام محلي. تتفق الفرق على المعلومات المتاحة للمراجعة بدقة.","challenge":"يجب أن يُظهر السجل عن بُعد مصدره ونطاقه المسموح.","stages":[{"title":"تحديد بيانات المراجعة","action":"تحديد التوثيق السريري والملاحظات والنتائج المطلوبة لهذه الخدمة.","owner":"فريق الرعاية المحلي","record":"المعلومات المطلوبة · نطاق المراجعة"},{"title":"تأكيد مسؤولية المصدر","action":"توثيق النظام المصدر ومواءمة الهوية والفريق المسؤول عن الاتصال.","owner":"فريق التكامل وتقنية المعلومات","record":"النظام المصدر · المواءمة · المسؤول"},{"title":"إتاحة المعلومات المتفق عليها","action":"نقل معلومات المصدر المدعومة عبر الاتصال المحدد والمختبر.","owner":"فريق التكامل وتقنية المعلومات","record":"الاتصال · مراجع المصدر"},{"title":"مراجعة سياق المصدر","action":"فحص السياق المتاح وتحديد أي معلومات ناقصة للمتابعة المحلية.","owner":"المختص عن بُعد","record":"التوثيق المتاح · السياق الناقص"},{"title":"توثيق المراجعة المهنية","action":"تسجيل المراجعة مقابل الحالة الصحيحة وتحديد المعلومات المستخدمة.","owner":"المختص عن بُعد","record":"توثيق المراجعة · الحالة · سياق المصدر"},{"title":"إعادة الإجراء التالي","action":"مراجعة سجل المختص وتوثيق متابعة الرعاية أو المعلومات محلياً.","owner":"فريق الرعاية المحلي","record":"الرد المحلي · المتابعة"}],"exception":"تُوضح البيانات غير المتاحة في المراجعة. تحدد اتفاقية الاتصال ما يمكن تبادله، ولا يُفترض توافق شامل مع الأجهزة.","completion":["تستخدم المراجعة سجلاً مصدرياً محدداً.","للسياق الناقص مسار متابعة مسؤول.","يبقى الرد المحلي مرتبطاً بتوثيق المختص."]},{"type":"Illustrative operational scenario","title":"اتصال بمسؤولية واضحة","scenario":"يضيف مستشفى اتصال عناية مركزة عن بُعد إلى جانب نظامه السريري القائم. تحتاج التقنية والأطباء وقيادة الخدمة إلى مسؤوليات تنفيذ وتشغيل واضحة.","challenge":"يربط الاتصال القابل للاستخدام التنفيذ التقني بتسليم رعاية فعلي.","stages":[{"title":"تحديد حدود الخدمة","action":"الاتفاق على الفرق المحلية والبعيدة والأنظمة والمعلومات اللازمة لخدمة المراجعة.","owner":"قيادة الخدمة","record":"الفرق · الأنظمة · نطاق المعلومات"},{"title":"تحديد الاتصال","action":"توثيق البروتوكول المتفق عليه ومواءمة الهوية والتراخيص ومسؤولي التنفيذ.","owner":"فريق التكامل وتقنية المعلومات","record":"البروتوكول · المواءمة · مسؤول التنفيذ"},{"title":"تجربة حالة مدعومة","action":"تجهيز حالة عرض مصرح بها وتأكيد معلومات المصدر المطلوبة.","owner":"فريق الرعاية المحلي","record":"حالة العرض · سجل المصدر"},{"title":"التحقق من التبادل والصلاحيات","action":"مراجعة السياق المتبادل والصلاحيات المسموح بها ومعالجة الإخفاق المتفق عليها.","owner":"فريق التكامل وتقنية المعلومات","record":"تتبع التبادل · الصلاحيات · البديل"},{"title":"تجربة تسليم المراجعة","action":"توثيق المراجعة وإظهار عودتها إلى الطبيب المحلي المسؤول.","owner":"المختص عن بُعد","record":"مراجعة المختص · التسليم المحلي"},{"title":"اعتماد نطاق التشغيل","action":"الاتفاق على الاعتماد ومسؤولية الدعم وحدود الخدمة المفعّلة.","owner":"قيادة الخدمة","record":"الاعتماد · الدعم · التفعيل"}],"exception":"يعود الاختبار غير الناجح إلى مسؤول الاتصال المحدد. يتبع التفعيل الاعتماد المتفق عليه؛ ولا يمنح الاتصال وصولاً غير مقيد للسجلات.","completion":["للاتصال غرض تقني وسريري محدد.","مسؤوليات المراجعة والبديل متفق عليها.","للخدمة المعتمدة حدود تفعيل واضحة."]}]}}},{"slug":"/terms","lastModified":"2026-10-08T11:56:50.711Z","en":{"url":"https://mansoq.com/terms","title":"Website Terms | MANSOQ","eyebrow":"MANSOQ Platform","summary":"The website explains MANSOQ capabilities and accepts business enquiries. It does not provide clinical advice or activate a paid service.","sections":[{"kind":"cards","intro":"","items":[{"text":"Capabilities depend on deployment scope, configuration and approvals. Confirm the agreed scope in your implementation proposal.","title":"Information and availability"},{"text":"Subscriptions, managed services, pricing and support obligations require a separately agreed contract. An enquiry is not a contract.","title":"Service agreements"},{"text":"MANSOQ branding identifies this platform. Included third-party components retain their own licences and notices.","title":"Names and licences"}],"title":"Using this website."}],"seoTitle":"Website Terms | MANSOQ","seoDescription":"The website explains MANSOQ capabilities and accepts business enquiries. It does not provide clinical advice or activate a paid service.","description":"The website explains MANSOQ capabilities and accepts business enquiries. It does not provide clinical advice or activate a paid service.","answers":[]},"ar":{"url":"https://mansoq.com/terms?lang=ar","title":"شروط الموقع | منسوق","eyebrow":"منصة منسوق","summary":"يشرح الموقع قدرات منسوق ويستقبل الاستفسارات التجارية. ولا يقدم مشورة سريرية أو يفعّل خدمة مدفوعة.","sections":[{"kind":"cards","intro":"","items":[{"text":"تعتمد القدرات على نطاق التطبيق والتهيئة والموافقات. أكد النطاق المتفق عليه في عرض التطبيق.","title":"المعلومات والتوافر"},{"text":"تتطلب الاشتراكات والخدمات المدارة والأسعار والتزامات الدعم عقدًا متفقًا عليه بصورة منفصلة. الاستفسار ليس عقدًا.","title":"اتفاقيات الخدمة"},{"text":"تعرّف هوية منسوق هذه المنصة. وتحتفظ مكونات الأطراف الثالثة بتراخيصها وإشعاراتها.","title":"الأسماء والتراخيص"}],"title":"استخدام الموقع."}],"seoTitle":"شروط الموقع | منسوق","seoDescription":"يشرح الموقع قدرات منسوق ويستقبل الاستفسارات التجارية. ولا يقدم مشورة سريرية أو يفعّل خدمة مدفوعة.","description":"يشرح الموقع قدرات منسوق ويستقبل الاستفسارات التجارية. ولا يقدم مشورة سريرية أو يفعّل خدمة مدفوعة.","answers":[]}},{"slug":"/","lastModified":"2026-10-18T19:22:00.000Z","en":{"url":"https://mansoq.com/","title":"Saudi healthcare, hospital management & RCM | MANSOQ","eyebrow":"Human-centered experiences. Connected across care.","summary":"One Saudi-built platform uniting clinical care and financial clarity.","ctaLabel":"Explore your scope","sections":[],"seoDescription":"A shared Saudi-built foundation for the people delivering care, with the clinical, departmental and revenue workflows your organization needs.","description":"Saudi-built healthcare platform connecting hospital and clinic care, laboratory, radiology, pharmacy, inventory and revenue cycle. Explore modules, plans and setup.","answers":[]},"ar":{"url":"https://mansoq.com/?lang=ar","title":"نظام المستشفيات والرعاية ودورة الإيرادات | منسوق","eyebrow":"تجارب تتمحور حول الإنسان. رعاية مترابطة.","summary":"منصة سعودية واحدة تجمع الرعاية السريرية والوضوح المالي.","ctaLabel":"استكشف نطاقك","sections":[],"seoDescription":"أساس مشترك بُني في السعودية لمقدمي الرعاية، مع المسارات السريرية والقسمية والإيرادية التي تحتاجها منشأتك.","description":"منصة سعودية تربط رعاية المستشفيات والعيادات بالمختبر والتصوير والصيدلية والمخزون ودورة الإيرادات. استكشف الوحدات والباقات والإعداد.","answers":[]}},{"slug":"/resources/migration-integration","lastModified":"2026-10-10T11:26:00.000Z","en":{"url":"https://mansoq.com/resources/migration-integration","title":"Epic, TrakCare & Oracle Health migration | MANSOQ","eyebrow":"Migration & integration reference","summary":"Plan exports, interfaces, validation and cutover with vendor-specific references and downloadable files.","seoTitle":"Epic, TrakCare & Oracle Health migration | MANSOQ","seoDescription":"Plan migration or integration with Epic, TrakCare, Oracle Health and other EHR, LIS, PACS and finance systems. Export files, mappings, tests and cutover.","sections":[],"description":"Plan migration or integration with Epic, TrakCare, Oracle Health and other EHR, LIS, PACS and finance systems. Export files, mappings, tests and cutover.","answers":[]},"ar":{"url":"https://mansoq.com/resources/migration-integration?lang=ar","title":"ترحيل وتكامل Epic وTrakCare وOracle Health | منسوق","eyebrow":"مرجع الترحيل والتكامل","summary":"خطط للاستخراج والاتصالات والتحقق والتحويل مع مراجع لكل نظام وملفات قابلة للتنزيل.","seoTitle":"ترحيل وتكامل Epic وTrakCare وOracle Health | منسوق","seoDescription":"دليل ترحيل وربط Epic وTrakCare وOracle Health وأنظمة المستشفيات والمختبر والتصوير والمالية: الملفات والمواءمة والاختبارات والتحويل.","sections":[],"description":"دليل ترحيل وربط Epic وTrakCare وOracle Health وأنظمة المستشفيات والمختبر والتصوير والمالية: الملفات والمواءمة والاختبارات والتحويل.","answers":[]}},{"slug":"/faq","lastModified":"2026-10-18T19:22:00.000Z","en":{"url":"https://mansoq.com/faq","title":"FAQs: healthcare software, setup, migration & pricing | MANSOQ","eyebrow":"MANSOQ support","summary":"Clear answers for every team. Explore MANSOQ products, clinical workflows, user roles, pricing, integrations, migration, IT, data protection and the path to go-live.","seoTitle":"FAQs: healthcare software, setup, migration & pricing | MANSOQ","seoDescription":"Search MANSOQ FAQs for clinical teams, IT, procurement and patients. Explore products, pricing, integrations, migration, security, setup and support.","sections":[],"description":"Search MANSOQ FAQs for clinical teams, IT, procurement and patients. Explore products, pricing, integrations, migration, security, setup and support.","answers":[{"id":"mansoq-overview","question":"What is MANSOQ?","answer":"MANSOQ brings healthcare software, connected clinical and operational workflows, and agreed revenue services into one product ecosystem. Start with the shared Core, select the care setting and departments you need, then confirm the available release, integrations and implementation scope with the team.","href":"/platform","url":"https://mansoq.com/faq#faq-mansoq-overview"},{"id":"which-organizations","question":"Which healthcare organizations can explore MANSOQ?","answer":"The website describes clinics, polyclinics, hospitals, medical groups, TeleICU and home or palliative care settings. Each setting needs its own workflow, capacity, clinical dependencies and delivery review; a public product page does not by itself establish that every capability is ready for your facility.","href":"/solutions","url":"https://mansoq.com/faq#faq-which-organizations"},{"id":"existing-software-coexistence","question":"Do we need to replace every existing hospital system?","answer":"No. You can plan replacement, a defined integration, a phased transition or a retained archive. Decide which system owns each record, how updates cross the boundary and how staff handle exceptions. Confirm source-vendor access and acceptance before committing to the transition.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-existing-software-coexistence"},{"id":"product-vs-service","question":"What is the difference between software, managed operations and RCM RaaS?","answer":"Software enables the selected workflows. Managed operations covers the agreed non-clinical work within the package allowance. RCM RaaS is an additional, accepted revenue service with its own worklists, authority and collection-fee basis. Neither service automatically supplies clinical staffing or transfers medical accountability.","href":"/services/raas","url":"https://mansoq.com/faq#faq-product-vs-service"},{"id":"request-a-demo","question":"How do I request a demonstration or a proposal?","answer":"Use the contact or demonstration request and describe your care setting, locations, users, current systems and the workflow you want to see. The team can review a relevant scenario, clarify dependencies and prepare an agreed scope. Use synthetic examples rather than sending patient records through a public enquiry.","href":"/demo","url":"https://mansoq.com/faq#faq-request-a-demo"},{"id":"english-arabic","question":"Can Arabic and English teams use the same planning resources?","answer":"Yes. The public product, FAQ and implementation guidance is available in Arabic and English, with language-specific links. During implementation, confirm the exact application language, translated terminology, right-to-left layouts, document templates and user training required for your selected release.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-english-arabic"},{"id":"which-user-roles","question":"Which user roles should we plan before setup?","answer":"Start with the people doing the work: registration, clinicians, nurses, departmental teams, pharmacy, revenue, finance, IT, managers and authorized support users. Map each role to its facilities, tasks and approval responsibilities. Product and release acceptance determine the exact permissions available.","href":"/platform/core","url":"https://mansoq.com/faq#faq-which-user-roles"},{"id":"multi-site-governance","question":"Can a group manage several facilities with different responsibilities?","answer":"Plan the legal-entity and facility hierarchy, local operating owners, cross-site access and consolidated reporting together. A group view must respect the accepted sharing boundary and financial ownership. Confirm the selected package, capacity and actual multi-entity capabilities before activation.","href":"/solutions/medical-cities","url":"https://mansoq.com/faq#faq-multi-site-governance"},{"id":"who-approves-clinical-records","question":"Who remains responsible for clinical documentation and decisions?","answer":"Your authorized clinical team remains responsible for patient care, record accuracy, orders and professional decisions. Define who drafts, reviews, signs and corrects records in the accepted workflow. Software assistance and operational support do not replace professional review or local clinical governance.","href":"/platform/core","url":"https://mansoq.com/faq#faq-who-approves-clinical-records"},{"id":"account-vs-clinical-access","question":"Does a website customer account give access to patient records?","answer":"A website account and a deployed clinical workspace serve different purposes. Commercial account access does not establish authorization to a patient record or prove that a clinical deployment is active. Your organization must complete its approved identity, role assignment, environment and activation process.","href":"/account","url":"https://mansoq.com/faq#faq-account-vs-clinical-access"},{"id":"clinical-workflow-coverage","question":"How do we confirm whether our clinical workflow is supported?","answer":"Review the relevant product handbook and demonstrate your real sequence of work using synthetic cases. Include normal care, handovers, corrections, escalation and downtime. Accept the supported release and configuration with clinical owners before using it in patient care.","href":"/platform/care-settings","url":"https://mansoq.com/faq#faq-clinical-workflow-coverage"},{"id":"department-vs-results","question":"Is viewing laboratory or radiology results the same as operating the department?","answer":"No. Results access, external-system integration and full departmental operation are distinct scopes. For laboratory or imaging operations, agree the required ordering, specimen or study handling, verification, reporting and exception workflows. Confirm analyzer, imaging, PACS and other interfaces separately.","href":"/platform/departments","url":"https://mansoq.com/faq#faq-department-vs-results"},{"id":"medication-safety-workflow","question":"What should pharmacy and medication teams validate?","answer":"Validate the selected prescribing, dispensing, administration and inventory handovers against your policies. Confirm the accepted formulary, units, permissions, review steps and correction process, including any external pharmacy connection. Do not assume that every clinical alert or medication safety function is available without release-specific validation.","href":"/platform/pharmacy","url":"https://mansoq.com/faq#faq-medication-safety-workflow"},{"id":"ai-clinical-review","question":"Can AI make clinical decisions or finalize a medical note automatically?","answer":"Assistive AI must remain within the accepted intended use and human approval process. An authorized clinician reviews and corrects any generated draft before accepting it. Agree consent, data handling, supplier involvement and validation; generated content can be incomplete or incorrect and does not replace clinical judgement.","href":"/platform/ai","url":"https://mansoq.com/faq#faq-ai-clinical-review"},{"id":"teleicu-responsibilities","question":"Does TeleICU include bedside staff or transfer clinical responsibility?","answer":"The software scope and clinical service arrangement must be agreed separately. Confirm the bedside team, remote clinical coverage, licensing, escalation route, equipment and connectivity. A TeleICU package does not by itself provide clinical staffing, emergency response or transfer responsibility for patient care.","href":"/solutions/teleicu","url":"https://mansoq.com/faq#faq-teleicu-responsibilities"},{"id":"clinical-downtime","question":"How should clinical teams prepare for downtime?","answer":"Approve a local downtime process covering patient identification, urgent communication, medications, orders and documentation. Rehearse who declares downtime, how work continues and how records are reconciled after recovery. Agree technical recovery arrangements and clinical acceptance before go-live.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-clinical-downtime"},{"id":"migration-source-systems","question":"Can we migrate from Epic, Oracle Health, TrakCare or another HIS?","answer":"Use the source-system migration reference to plan the route for your installed product and version. Access rights, extraction formats, vendor contracts, mapping and data quality determine the actual scope. A listed vendor is a planning reference, not a promise of a ready connector, partnership or guaranteed migration.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-migration-source-systems"},{"id":"migration-data-domains","question":"Which information should be included in a migration scope?","answer":"Inventory patient identifiers, demographics, active encounters, clinical records, attachments, appointments, financial balances and reference catalogues as applicable. For each domain, agree whether to import, integrate, archive or exclude it, together with the owner, retention needs and acceptance checks. Historical data is not automatically included in a setup allowance.","href":"/resources/implementation#existing-systems","url":"https://mansoq.com/faq#faq-migration-data-domains"},{"id":"migration-patient-matching","question":"How do we reduce duplicate patients and incorrect record matching?","answer":"Preserve source identifiers and define matching rules before import. Profile duplicates, missing identifiers and conflicting demographics, then route uncertain matches to an authorized reviewer. Reconcile accepted records and record any correction; do not silently merge ambiguous patients.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-migration-patient-matching"},{"id":"migration-rehearsal","question":"What happens before the final migration and go-live?","answer":"Run an agreed rehearsal with representative data, mapping checks and clinical and financial reconciliation. Record rejected rows, counts, attachments, ownership and sign-off. Agree the extraction freeze, final changes, cutover window, rollback criteria and retained-system access before the final transfer.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-migration-rehearsal"},{"id":"migration-no-downtime","question":"Can we guarantee zero downtime or a fixed migration date?","answer":"Timing depends on source access, data quality, external vendors, testing, training and acceptance. Define a delivery plan with dependencies and a cutover rehearsal rather than assuming zero downtime. The accepted statement of work determines milestones, responsibilities and any agreed service commitments.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-migration-no-downtime"},{"id":"historical-archive","question":"Can we keep the old system as a read-only archive?","answer":"A retained archive can be part of an agreed transition. Confirm licensing, retention, access, patient matching, audit and the process for retrieving older records. Define which system owns new transactions and ensure staff know when to consult the archive.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-historical-archive"},{"id":"integration-standards","question":"Does mentioning FHIR, HL7 or DICOM mean a system will connect immediately?","answer":"No. A standard is only part of an integration. Agree the installed versions, supported resources or messages, identifiers, authentication, mapping, error handling and acceptance tests. Confirm the actual adapter, source-vendor rights and commissioning scope before relying on live exchange.","href":"/platform/integrations","url":"https://mansoq.com/faq#faq-integration-standards"},{"id":"integration-scope-checklist","question":"What information does IT need to scope an interface?","answer":"Provide the sending and receiving systems, versions, owner, use case, fields, message frequency, environment and security requirements. Include sample synthetic payloads, test credentials through an approved channel and vendor dependencies. Agree monitoring, reconciliation, retries and who owns failed transactions.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-integration-scope-checklist"},{"id":"national-activation","question":"Are NPHIES and ZATCA live as soon as we subscribe?","answer":"Required NPHIES and ZATCA workflows are included in every plan, but live transmission needs your organization’s credentials and external acceptance. Agree enrolment, supported transactions, test evidence, reconciliation and incident ownership. A subscription alone does not grant national-platform approval.","href":"/saudi","url":"https://mansoq.com/faq#faq-national-activation"},{"id":"identity-sso","question":"Can our organization use SSO or an existing identity provider?","answer":"Discuss company sign-in with the MANSOQ team during technical discovery. Availability depends on the selected product, identity provider and accepted deployment scope. Configuration and account administration are handled within your authorized account experience.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-identity-sso"},{"id":"devices-network","question":"What hardware, browsers and network capacity do we need?","answer":"Build a readiness list for your accepted workflows, including workstations, mobile use, printers, scanners, medical devices and telepresence where needed. Confirm supported browsers, versions, connectivity, bandwidth and fallback arrangements with implementation owners. Hardware supply and device interfaces require explicit scope.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-devices-network"},{"id":"deployment-hosting-options","question":"Can we request dedicated hosting or a different deployment model?","answer":"Discuss architecture, data location, isolation, operations and recovery needs in an Enterprise proposal. A customer-owned database or a storage choice does not establish dedicated deployment of every application component. Confirm the complete infrastructure and responsibility boundary in the accepted design.","href":"/pricing#care-packages","url":"https://mansoq.com/faq#faq-deployment-hosting-options"},{"id":"integration-change-management","question":"Who maintains an interface after a vendor changes its API?","answer":"Agree the maintained version, monitoring owner, support boundary and change process when commissioning the connection. A vendor upgrade may need mapping changes, retesting or a separate build. Record release notices and avoid upgrading a dependent system before impact review and acceptance.","href":"/platform/integrations","url":"https://mansoq.com/faq#faq-integration-change-management"},{"id":"security-evidence","question":"What security and compliance evidence should we review?","answer":"Request the controls and evidence relevant to your selected service, deployment and data flows. Review access, audit, encryption, incident handling, suppliers, retention and recovery together with your security and legal teams. Confirm the scope and validity of any evidence; a website description does not establish a certification or legal conclusion.","href":"/company/trust","url":"https://mansoq.com/faq#faq-security-evidence"},{"id":"data-ownership-access","question":"Who controls clinical data and who may access it?","answer":"Your agreement must define the organization’s authority over its records and the permitted processing roles. Assign access only to authorized people and approved service activities, with the accepted audit and support process. A storage choice alone does not define all access, data flows or legal responsibilities.","href":"/privacy","url":"https://mansoq.com/faq#faq-data-ownership-access"},{"id":"data-location-subprocessors","question":"How do we confirm where data is stored and which suppliers process it?","answer":"Review the complete data-flow map for the accepted environment, including application databases, files, logs, backups, support systems and external AI or communication providers. Agree locations, subprocessors, transfer controls and permitted use in the relevant documents before activation.","href":"/company/trust","url":"https://mansoq.com/faq#faq-data-location-subprocessors"},{"id":"backup-recovery-evidence","question":"Are backup and disaster recovery targets guaranteed for every plan?","answer":"Recovery arrangements depend on the accepted deployment and service scope. Confirm backup ownership, frequency, retention, encryption, restore tests and any agreed recovery time or recovery point objectives. A database option or product description alone is not evidence of a tested recovery commitment.","href":"/company/trust","url":"https://mansoq.com/faq#faq-backup-recovery-evidence"},{"id":"privacy-requests","question":"How should patients request access to or correction of their information?","answer":"Patients should contact the healthcare provider responsible for their record through its approved privacy or records channel. The provider verifies identity, reviews the request and applies its obligations and clinical correction policy. Do not submit medical records, identity documents or sensitive details through the public marketing enquiry.","href":"/privacy","url":"https://mansoq.com/faq#faq-privacy-requests"},{"id":"safe-support-information","question":"What can we safely include in a support or sales enquiry?","answer":"For a public enquiry, describe the workflow, organization and issue without patient-identifiable details, passwords, API keys or production files. Use synthetic examples where possible. Your support owner should provide the approved secure channel and authorization when sensitive evidence is necessary.","href":"/contact","url":"https://mansoq.com/faq#faq-safe-support-information"},{"id":"implementation-start-checklist","question":"What do we need before implementation begins?","answer":"Name an executive sponsor, delivery owner, clinical and financial approvers, IT contacts and data owners. Prepare the facility structure, role matrix, product scope, source-system inventory and required integrations. Agree the statement of work, dependencies, acceptance evidence and planned operating model before scheduling activation.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-implementation-start-checklist"},{"id":"implementation-timeline","question":"How long will setup and implementation take?","answer":"There is no universal timeline. The schedule follows the accepted scope, source-data readiness, interface access, configuration, training and external approvals. Use milestones with named owners and readiness gates; confirm dates after discovery rather than treating a package purchase as a go-live commitment.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-implementation-timeline"},{"id":"training-by-role","question":"How should training be organized for each role?","answer":"Train each team on its accepted tasks, permissions, handovers and exceptions using synthetic scenarios. Include registration, clinical, departmental, financial and administrative owners as relevant, and record attendance and competency checks. Agree delivery format, materials, train-the-trainer support and any onsite training separately.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-training-by-role"},{"id":"go-live-acceptance","question":"Who signs off go-live readiness?","answer":"Your designated business, clinical, financial and technical owners should accept the areas they control. Review configuration, role tests, migration reconciliation, interfaces, training, downtime and support readiness. Document open issues, their impact and the authorized go/no-go decision before activating live workflows.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-go-live-acceptance"},{"id":"support-hours-sla","question":"Is 24/7 support or a response-time SLA included automatically?","answer":"Support coverage, severity definitions, response targets, channels and escalation follow the accepted service agreement. Confirm the named contacts and incident ownership for software, hosting, devices, vendors and clinical operations. A public FAQ does not create an unagreed 24/7 coverage or resolution guarantee.","href":"/contact","url":"https://mansoq.com/faq#faq-support-hours-sla"},{"id":"report-a-problem","question":"How should our team report a problem after go-live?","answer":"Use the support route agreed with your organization and include the environment, time, affected workflow, impact and safe reproduction steps. Separate urgent clinical escalation from the software ticket according to your local policy. Send sensitive evidence only through the approved secure channel and keep the incident owner informed.","href":"/contact","url":"https://mansoq.com/faq#faq-report-a-problem"},{"id":"new-site-module","question":"What changes when we add a site, department or product later?","answer":"Review capacity, licensing, workflow dependencies, permissions, data sharing, interfaces and support impact before activation. Update the accepted configuration and commercial scope, then test and train the affected roles. More care capacity does not automatically increase managed hours or interface allowances.","href":"/pricing#configuration","url":"https://mansoq.com/faq#faq-new-site-module"},{"id":"procurement-information","question":"What should procurement include in an RFP or evaluation?","answer":"State your care settings, sites, capacity, roles, required workflows, current systems, data volumes and integration needs. Add security evidence, hosting, recovery, support, training and acceptance requirements. Separate mandatory requirements from optional requests so the proposal can show gaps, dependencies and costs clearly.","href":"/contact?request=consultation","url":"https://mansoq.com/faq#faq-procurement-information"},{"id":"quotation-total-cost","question":"What should we include when comparing total cost?","answer":"Compare the accepted recurring software and managed-service charges, setup and migration, additional capacity, RCM RaaS where selected, tax and third-party costs. Include hardware, messaging, bespoke interfaces, dedicated infrastructure and optional services when needed. Use the accepted quotation rather than adding assumptions to a published package price.","href":"/pricing","url":"https://mansoq.com/faq#faq-quotation-total-cost"},{"id":"contract-before-activation","question":"Which documents should be agreed before live activation?","answer":"Agree the product and service scope, quotation, statement of work, responsibilities, data-processing terms and acceptance criteria relevant to your deployment. Confirm support, billing, renewals, changes, termination and data-exit arrangements in the applicable contract. Website guidance helps evaluation but does not replace accepted agreements.","href":"/terms","url":"https://mansoq.com/faq#faq-contract-before-activation"},{"id":"roi-guarantees","question":"Are operational savings or collection improvements guaranteed?","answer":"Expected benefits depend on the starting process, selected scope, data quality, adoption and operating responsibilities. Agree baseline measures and review actual results with your team. Illustrative scenarios and workflow examples are not audited customer outcomes or a guarantee of revenue, savings or clinical results.","href":"/case-studies","url":"https://mansoq.com/faq#faq-roi-guarantees"},{"id":"partner-implementation","question":"Can an implementation partner or integrator work with us?","answer":"Discuss the proposed partner role and agree the delivery boundary, technical access, training, change ownership and acceptance responsibilities. A partner must work within the approved security and data-processing arrangements. Being named in a migration reference does not establish a commercial partnership.","href":"/company/partners","url":"https://mansoq.com/faq#faq-partner-implementation"},{"id":"data-exit-portability","question":"What happens to our data if we leave or change systems?","answer":"Agree export formats, included records and attachments, authorized recipients, timing, costs, retention and deletion before signing. Confirm how the destination will interpret the data and how remaining legal or clinical record obligations are handled. A storage connection alone does not guarantee complete application portability.","href":"/privacy","url":"https://mansoq.com/faq#faq-data-exit-portability"},{"id":"patient-medical-advice","question":"Can I get medical advice or emergency care through this website?","answer":"The public MANSOQ website provides product and service information. Contact your healthcare provider for medical advice, appointments and care-related questions. For an emergency, use your local emergency service or your provider’s urgent-care route; a marketing enquiry is not monitored as a clinical emergency channel.","href":"/contact","url":"https://mansoq.com/faq#faq-patient-medical-advice"},{"id":"patient-portal-access","question":"How do I access my appointments, results or patient portal?","answer":"Your healthcare provider confirms whether a patient-facing workflow is active and supplies the correct access route. Verify the provider’s identity and contact its registration or support team for account recovery. The public MANSOQ website does not provide a universal portal for every healthcare organization.","href":"/contact","url":"https://mansoq.com/faq#faq-patient-portal-access"},{"id":"family-proxy-consent","question":"Can family members view a patient’s information?","answer":"Family or representative access must follow the healthcare provider’s identity, consent, guardianship and authorization policy. Confirm the supported proxy workflow and its limits with the provider. A family relationship alone does not establish permission to view a record or receive clinical updates.","href":"/privacy","url":"https://mansoq.com/faq#faq-family-proxy-consent"},{"id":"patient-billing-insurance","question":"Who can answer a question about my bill or insurance claim?","answer":"Contact the healthcare provider’s billing or insurance team using the details on your bill or care documents. They can verify your identity and review the relevant account. MANSOQ’s public product team cannot determine an individual claim decision or disclose patient-account details through a sales enquiry.","href":"/contact","url":"https://mansoq.com/faq#faq-patient-billing-insurance"},{"id":"module-core","question":"What is the MANSOQ Core workflow and what should we validate?","answer":"Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary.\n\n1. Identify: Register the person with the identifiers your organization uses. Review a possible duplicate before creating another patient; preserve the original identifiers when a source system is retained.\n\n2. Organize: Define legal organizations, facilities, departments and locations. Assign each operational record to its facility and keep cross-site sharing within the approved boundary.\n\n3. Authorize: Assign named users to roles and facilities, then verify their read, create and update permissions. Test a restricted user as well as an administrator before accepting the setup.\n\n4. Connect context: Link encounters, notes, observations, requests and attachments to the correct person. Departmental and revenue modules use this context through their selected capabilities and permissions.\n\n5. Review & maintain: Review record changes and responsible users, maintain shared configuration and confirm release-specific retention, backup and support arrangements. Re-test affected permissions when adding a site or module.\n\nCore supplies shared identity and context. Cross-tenant data exchange, external patient matching and enterprise sharing require a separately accepted interface and governance scope.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/core","url":"https://mansoq.com/faq#faq-module-core"},{"id":"module-outpatient","question":"What is the Outpatient Care workflow and what should we validate?","answer":"Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope.\n\n1. Book & arrive: Configure clinic services, practitioner resources, sessions and visit types. Book into the intended slot, record arrival and route the visit to the appropriate clinical team.\n\n2. Consult: Open the encounter, review relevant history and allergies, capture observations and document the assessment. Use approved forms and keep the author and encounter attached to the record.\n\n3. Order & act: Create service and medication requests with their clinical context. Route them to the selected laboratory, radiology or pharmacy workflow; review completed results before determining the next action.\n\n4. Close & follow up: Document the care plan and follow-up responsibility, complete the encounter and link performed services to billing. Insurance verification, claims and electronic invoices depend on the selected revenue extensions.\n\nScheduling and encounters form the visit pathway. Department operation, results exchange, medication and insurance processing are configured through their own modules.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/outpatient","url":"https://mansoq.com/faq#faq-module-outpatient"},{"id":"module-inpatient","question":"What is the Inpatient Care workflow and what should we validate?","answer":"Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow.\n\n1. Admit & locate: Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context.\n\n2. Coordinate care: Record assessments and observations, maintain the care plan and track service requests. Keep clinical notes, results and outstanding actions available to authorized ward staff.\n\n3. Medication & transfers: Connect medication requests, administration records and pharmacy dispensing. On a ward or team transfer, review the current plan, location and unresolved tasks with the receiving team.\n\n4. Discharge & reconcile: Complete the discharge record, medication instructions and follow-up responsibility. Review documented service activity and open financial items through billing and the selected revenue-cycle workflow.\n\nAn inpatient encounter brings the stay together. ICU, surgery, pharmacy and departmental interfaces retain their own configuration, access and acceptance requirements.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/inpatient","url":"https://mansoq.com/faq#faq-module-inpatient"},{"id":"module-emergency","question":"What is the Emergency Care workflow and what should we validate?","answer":"Emergency encounter context, observations and accountable care handovers according to verified operational scope.\n\n1. Receive: Record the arrival and establish identity using the locally approved process, including the temporary-identity route where required. Open the emergency encounter and assign the location and team.\n\n2. Assess & prioritize: Capture the presenting concern and observations. Configure your approved triage categories and escalation responsibilities; clinical priority remains the care team’s decision.\n\n3. Treat & observe: Document care, medication and urgent requests. Keep results and repeat observations attached to the encounter and identify who owns each outstanding action during observation.\n\n4. Determine destination: Document discharge, admission or transfer with the receiving team, current treatment and pending requests. Billing and insurance tasks follow their authorized workflow without replacing clinical disposition.\n\nEmergency documentation connects to selected diagnostic, inpatient and critical-care services. Triage rules, escalation thresholds and emergency policies must be approved locally.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/emergency","url":"https://mansoq.com/faq#faq-module-emergency"},{"id":"module-teleicu","question":"What is the TeleICU workflow and what should we validate?","answer":"A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately.\n\n1. Establish hub & spoke: Identify participating facilities, critical-care beds and specialist coverage. Agree which organization owns care, which records remote staff may access and the escalation contacts for each site.\n\n2. Prepare the case: Link the person and encounter to the shared review context. Confirm available observations, notes and imaging sources; commission camera or device connections only within the agreed scope.\n\n3. Review remotely: Let the authorized specialist review the case and document the assessment and recommendations. Name the bedside owner who receives and acts on the plan; remote advice does not silently transfer clinical responsibility.\n\n4. Follow & escalate: Track the next review and handover responsibilities. Maintain contact and downtime procedures for unavailable video, incomplete source information or a case requiring direct escalation.\n\nSpecialist workflow, video, cameras and clinical/device exchange have distinct delivery boundaries. Confirm each facility’s network, equipment and supported integrations before commissioning.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/teleicu","url":"https://mansoq.com/faq#faq-module-teleicu"},{"id":"module-home-palliative","question":"What is the Home & Palliative Care workflow and what should we validate?","answer":"Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope.\n\n1. Enroll & plan: Establish the person’s care context, consent and caregiver contacts. Define the service zone, multidisciplinary team and approved home or palliative-care plan with escalation responsibilities.\n\n2. Schedule the visit: Assign the practitioner and visit time, accounting for service area and travel constraints. Confirm required equipment, medication and the information the visiting team needs.\n\n3. Deliver & document: Record the encounter, observations, symptom review and delivered care. Keep medication and service requests with the current plan and document the caregiver discussion and next responsibilities.\n\n4. Continue care: Plan the next visit or referral and hand over unresolved needs to the multidisciplinary team. Reconcile supplied items and delivered services through inventory and billing where selected.\n\nHome-care documentation, scheduling, stock and remote support are selected separately. Offline work, remote devices and route optimization must be explicitly confirmed for the chosen deployment.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/home-palliative","url":"https://mansoq.com/faq#faq-module-home-palliative"},{"id":"module-operating-room","question":"What is the Operating Room workflow and what should we validate?","answer":"Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope.\n\n1. Plan the procedure: Connect the procedure request to the patient and encounter. Configure theatres, practitioners, sessions, equipment and service codes; confirm the responsible surgeon, anesthesia team and receiving ward.\n\n2. Prepare & verify: Record preparation, consent references and the locally approved safety checklist. Review the relevant record, medication and required investigations before moving to the procedure.\n\n3. Document the procedure: Keep clinical documentation, observations, medication and used supplies with the encounter. Link performed services and consumables to the relevant stock and charge records where those modules are selected.\n\n4. Recover & hand over: Record recovery status and the next care plan. Transfer the current treatment, pending requests and responsibilities to the ward or discharge team, then reconcile documented service activity.\n\nTheatre scheduling and clinical records are composed with inpatient, medication, inventory and billing capabilities. Anesthesia-device capture and external theatre systems need separate interface acceptance.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/operating-room","url":"https://mansoq.com/faq#faq-module-operating-room"},{"id":"module-icu","question":"What is the Intensive Care workflow and what should we validate?","answer":"Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified.\n\n1. Receive into the unit: Link the admitted patient to the critical-care location and responsible team. Review the referral, current treatments and outstanding investigations at the initial handover.\n\n2. Observe & document: Keep observations, assessments and care documentation in the encounter. Agree measurement units, recording frequency and local escalation responsibility; automated device feeds require an accepted device connection.\n\n3. Coordinate treatment: Connect orders, medication administration and diagnostic reports to the current plan. Reconcile changes with the bedside team and document the owner of each pending action.\n\n4. Handover & transfer: Review the current record and outstanding responsibilities at each shift or unit transfer. TeleICU review can be added with separately defined remote access, response ownership and device scope.\n\nICU clinical records do not imply every monitor, ventilator or alarm is integrated. Specify device models, supported protocols, responsible clinicians and downtime procedures in the selected scope.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/icu","url":"https://mansoq.com/faq#faq-module-icu"},{"id":"module-pharmacy","question":"What is the Pharmacy workflow and what should we validate?","answer":"Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list.\n\n1. Prescribe: Create the medication request with the encounter, product, dose, route, frequency and duration. Keep allergy and current medication context available for professional review.\n\n2. Verify & prepare: Review the prescription in the pharmacy queue, confirm the item and quantity and choose the appropriate stock lot. Record any substitution through the authorized process rather than silently changing the prescription.\n\n3. Dispense & hand over: Record prepared and handed-over medication, quantity, days supply and instructions. Link the dispense record to the patient, location, authorizing request and applicable charge.\n\n4. Track & reconcile: Review outstanding prescriptions, completed dispensing and inventory movements. Handle returns and corrections through the approved stock and finance processes; inpatient administration remains a separate clinical record.\n\nPrescribing, dispensing, administration and stock are linked but separate records. Formulary rules, unit conversions, payer coverage and external dispensers need their own accepted configuration.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/pharmacy","url":"https://mansoq.com/faq#faq-module-pharmacy"},{"id":"module-laboratory","question":"What is the Laboratory workflow and what should we validate?","answer":"Lab orders, specimen and result workflows with native operation distinct from external LIS integration.\n\n1. Request: Select the test from the service catalogue and link it to the patient, encounter and ordering clinician. Include the clinical question, priority and required specimen information.\n\n2. Collect & receive: Record specimen type, collection information, accession identifier, received time and condition. Keep processing notes and the original request linked so recollection can be traced.\n\n3. Record & review: Keep observations and diagnostic reports with the request and specimen. Configure the approved test definitions, units and result interpretation; name the result reviewer and critical-result communication route.\n\n4. Release & follow up: Make the approved report available in the clinical encounter. Preserve amendment reasons, reviewer responsibility and communication evidence; the ordering team owns the clinical follow-up.\n\nNative requests, specimens, observations and reports are distinct from an external LIS or analyzer connection. Device protocols, code mappings, acknowledgements and downtime recovery require interface testing for the chosen release.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/laboratory","url":"https://mansoq.com/faq#faq-module-laboratory"},{"id":"module-radiology","question":"What is the Radiology workflow and what should we validate?","answer":"Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope.\n\n1. Refer & schedule: Create the imaging request with the clinical question, patient, encounter and requested procedure. Confirm modality, department availability and required preparation before the scheduled examination.\n\n2. Acquire & identify: Connect departmental work to the request and accession information. When PACS is selected, verify patient, study and encounter identifiers before accepting the linked imaging study.\n\n3. Interpret & report: Attach the diagnostic report to the correct clinical request. Confirm author, report status and clinical communication responsibility; agree the external reporting workflow if interpretation occurs in another system.\n\n4. Communicate & amend: Return the report to the authorized care team, document critical findings through the approved pathway and retain addenda with their reason and owner. Track outstanding reports at handover.\n\nRadiology request and report context is separate from image storage, viewing, acquisition hardware and RIS/PACS integration. Agree each included component and test DICOM study linkage and report exchange where selected.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/radiology","url":"https://mansoq.com/faq#faq-module-radiology"},{"id":"module-inventory","question":"What is the Inventory workflow and what should we validate?","answer":"Stock, stores and departmental supply operation within the agreed supported scope.\n\n1. Define stock: Configure products, stores, units and supplier references. Import opening quantities by lot and location with cost and expiry information; reconcile the opening file to an approved stock count.\n\n2. Request & receive: Create supply requests and delivery records, confirm the supplying and receiving locations and inspect actual received quantities. Retain references to the original request and supplier.\n\n3. Issue & transfer: Select the item and lot for departmental use, dispensing or transfer. Confirm source, destination and quantity so physical movement can be reconciled with the correct inventory record.\n\n4. Count & reconcile: Review on-hand stock, expiry and pending deliveries. Investigate count variances and record authorized adjustments and returns with a reason; agree the finance export when external accounting is used.\n\nStock and supply records support departmental activity. Procurement approvals, accounting exports, barcode devices and external warehouse systems require explicit scope and testing.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/inventory","url":"https://mansoq.com/faq#faq-module-inventory"},{"id":"module-clinical-documentation","question":"What is the Clinical Documentation & Care Planning workflow and what should we validate?","answer":"Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow.\n\n1. Prepare forms: Configure approved questionnaires, clinical forms and author permissions for the care setting. Define required fields, terminology and review responsibility before use.\n\n2. Document the encounter: Capture the assessment, observations, conditions and clinical narrative against the correct encounter. Keep structured responses and attachments linked to the patient and responsible author.\n\n3. Review & complete: Review required information and the care plan. Apply the approved completion and signature process for the selected release, then make the relevant record available to authorized receiving teams.\n\n4. Amend & retain: Handle corrections with an identified author and reason. Agree retention and record access, and preserve relevant versions and audit evidence when documentation is used for coding or external exchange.\n\nDocumentation supplies clinical context to orders, handovers and coding. External document exchange, signatures and retention policies must match the accepted release and organization rules.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/clinical-documentation","url":"https://mansoq.com/faq#faq-module-clinical-documentation"},{"id":"module-orders-medication","question":"What is the Orders, Results & Medication workflow and what should we validate?","answer":"Required order/result and medication scope for the chosen workflow, separate from native departmental operation.\n\n1. Define destinations: Configure requestable services, medication catalogues and departmental destinations. Agree order statuses, required information and which roles may create, change or cancel requests.\n\n2. Place the request: Link the order to the patient and encounter with the requested item, quantity and clinical context. For medication, record the dosage instructions and authorizing prescriber.\n\n3. Fulfil & track: Route work to the selected department or pharmacy. Track request status and linked specimen, diagnostic report, dispense or administration records without treating these distinct events as one completion.\n\n4. Review & reconcile: Review completed results and medication activity, document cancellations or changes and resolve outstanding requests at handover. Charge capture follows the performed service and selected billing configuration.\n\nOrder management coordinates requests. Laboratory processing, imaging systems, dispensing and administration need the corresponding operational modules; an interface alone does not supply departmental operation.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/orders-medication","url":"https://mansoq.com/faq#faq-module-orders-medication"},{"id":"module-patient-access","question":"What is the Patient Access workflow and what should we validate?","answer":"Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified.\n\n1. Publish availability: Configure practitioner or location resources, session dates, opening hours and slot rules. Link services and approved booking permissions to the resource.\n\n2. Register & book: Identify the patient, review contact and identifier information and book the intended service. Preserve referral and payer details where the selected care and revenue workflow requires them.\n\n3. Arrive & route: Record arrival and queue information, open or link the encounter and direct the person to the responsible clinic or department. Confirm the next responsibility rather than leaving a booking without a care destination.\n\n4. Reschedule & follow up: Record completion, cancellation or missed attendance, then arrange an appropriate follow-up. Apply the configured revisit and charging policy using the selected billing workflow.\n\nAccess links a person to a care service. Public booking channels, patient communications and external identity or insurance services require selected and accepted connections.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/patient-access","url":"https://mansoq.com/faq#faq-module-patient-access"},{"id":"module-billing-finance","question":"What is the Billing & Finance workflow and what should we validate?","answer":"Invoices, payments and financial records linked to care activity, with accounting connections defined separately.\n\n1. Define charges: Configure service charge definitions, currency and the applicable tax treatment. Confirm account ownership, gross prices and authorized billing roles; contracted payer prices belong to the selected revenue-cycle configuration.\n\n2. Capture activity: Link charges to the encounter and performed service with quantity and supporting context. Review unbilled medication and departmental services, and resolve missing or duplicate items before invoice preparation.\n\n3. Invoice & collect: Review account charges, invoice ownership and the permitted patient or payer liability. Record payments against their reference and invoice; insurance estimates and submission approval remain separate decisions.\n\n4. Reconcile & correct: Reconcile invoices and payments to accepted control totals. Handle refunds, reversals and adjustments with reasons and approval; agree accounting exports when required. ZATCA e-invoicing is included and transmits live after your ZATCA credentials and external acceptance.\n\nBilling records service activity and money movements. Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. External accounting integration is agreed separately.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/billing-finance","url":"https://mansoq.com/faq#faq-module-billing-finance"},{"id":"module-revenue-cycle","question":"What is the Revenue Cycle Management workflow and what should we validate?","answer":"A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation.\n\n1. Establish the rules: Configure legal organizations, administration agreements, provider contracts, products, issued policies and member classes in dependency order. Keep source evidence, effective dates and approval with each configuration version.\n\n2. Verify coverage: Resolve member eligibility, provider network, benefit rules, exclusions, limits and tariff applicability for the requested service. An unknown fact creates a named review item; it must not silently become an assumed price or patient liability.\n\n3. Authorize & prepare: Prepare required authorization and supporting evidence. Keep requested and approved services, quantities and validity separate. Review the provisional estimate, unresolved facts and expiry before accepting financial preparation.\n\n4. Capture & submit: Attest performed activity, reconcile charges and assemble the claim with coding and attachments. Validate the payload and submission identity; production transmission requires approved credentials, endpoints, exchange package and activation evidence.\n\n5. Resolve responses: Distinguish transport validation, payer business errors and adjudicated denials. Route corrections, evidence requests, contract disputes and clinical appeals to the right owner with the original business references and applicable deadlines.\n\n6. Settle & explain: Link remittance advice to claims, distinguish adjudication from cash settlement and reconcile partial payments, deductions and unmatched cash. Review ageing, exceptions and decision traces without converting unresolved balances into patient charges.\n\nRequired NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. Catalogue reference data is not certified production configuration; payer credentials, terminology rights and external finance connections are each accepted before use.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/revenue-cycle","url":"https://mansoq.com/faq#faq-module-revenue-cycle"},{"id":"module-sbs-specific","question":"What is the SBS Specific Mapping Tooling workflow and what should we validate?","answer":"Specific supported service-code mapping and update scope. Required clinical/claim codes are not removed to create a price upgrade.\n\n1. Select the edition: Identify the supported Saudi Billing System catalogue release and usage rights. Agree whether the selected scope uses specified service codes or the full licensed catalogue.\n\n2. Map local services: Connect each provider service to the approved code and effective period. Preserve local service identifiers, descriptions and mapping evidence; resolve unmatched services through coding review.\n\n3. Validate use: Check required codes, inactive entries, duplicates and mapping completeness. Review representative service activity through the selected charge and claim workflow before accepting the mapping.\n\n4. Maintain versions: Review edition changes and effective dates with the catalogue owner. Preserve earlier mappings for historical records and test affected downstream pricing and claims before activation.\n\nSBS mapping is distinct from catalogue licensing and from NPHIES exchange acceptance. A mapping file does not grant catalogue rights or certify a claim.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/sbs-coding","url":"https://mansoq.com/faq#faq-module-sbs-specific"},{"id":"module-sbs-full","question":"What is the Full Supported SBS Catalogue Tooling workflow and what should we validate?","answer":"Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed.\n\n1. Select the edition: Identify the supported Saudi Billing System catalogue release and usage rights. Agree whether the selected scope uses specified service codes or the full licensed catalogue.\n\n2. Map local services: Connect each provider service to the approved code and effective period. Preserve local service identifiers, descriptions and mapping evidence; resolve unmatched services through coding review.\n\n3. Validate use: Check required codes, inactive entries, duplicates and mapping completeness. Review representative service activity through the selected charge and claim workflow before accepting the mapping.\n\n4. Maintain versions: Review edition changes and effective dates with the catalogue owner. Preserve earlier mappings for historical records and test affected downstream pricing and claims before activation.\n\nSBS mapping is distinct from catalogue licensing and from NPHIES exchange acceptance. A mapping file does not grant catalogue rights or certify a claim.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/sbs-coding","url":"https://mansoq.com/faq#faq-module-sbs-full"},{"id":"module-drg","question":"What is the DRG / Casemix / Grouper Integration workflow and what should we validate?","answer":"Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license.\n\n1. Prepare coded episode: Identify the encounter and approved coding inputs required by the selected grouper. Review diagnosis, procedure and episode completeness with the coding owner before grouping.\n\n2. Agree the grouper: Confirm the grouper release, licence, supported input format and delivery route. Establish whether processing is external or supplied in the accepted deployment; test representative coded cases.\n\n3. Review grouping output: Keep the returned grouping result with its episode, input version and review responsibility. Validate errors and unexpected group assignments before using the result in casemix analysis.\n\n4. Correct & compare: Preserve previous results when coding is corrected or a grouper version changes. Agree financial use and reporting definitions separately, then re-test representative episodes after changes.\n\nDRG capability requires an agreed licensed grouper and supported integration. No particular grouper, national reimbursement rule or automatic financial outcome is implied.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/drg","url":"https://mansoq.com/faq#faq-module-drg"},{"id":"module-nphies","question":"What is the NPHIES workflow and what should we validate?","answer":"Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly.\n\n1. Prepare provider identity: Confirm provider and payer identifiers, the supported exchange package and the responsible organization. Record onboarding evidence and agreed sandbox and production endpoints before connection testing.\n\n2. Check eligibility & authorization: Prepare member, policy and service context for supported eligibility and authorization exchanges. Validate the request and preserve payer responses, validity and unresolved coverage information.\n\n3. Exchange claims: Assemble supported claims and attachments, apply package validation and keep message and claim identities traceable. Transmission is permitted only after the production activation gates and required evidence are accepted.\n\n4. Follow responses & reconcile: Track supported responses, polling and payment advice. Distinguish platform errors from payer decisions and reconcile returned business references under the accepted retry and correction rules.\n\nNPHIES capability is subject to package support, onboarding, credentials and certification evidence. Built exchange code and sample reference data do not establish certified production readiness.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/integrations/nphies","url":"https://mansoq.com/faq#faq-module-nphies"},{"id":"module-zatca","question":"What is the ZATCA E-invoicing workflow and what should we validate?","answer":"Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated.\n\n1. Define taxpayer & phase: Confirm the legal taxpayer, VAT identifier, applicable invoicing phase and invoice type. Assign the invoicing owner and record the approved tax and document identity rules.\n\n2. Onboard the connection: Prepare the selected invoice unit, endpoint and securely managed credential references. Complete required onboarding and testing evidence; sample credentials or sandbox success do not authorize live submission.\n\n3. Prepare & validate invoice: Link the supported invoice to billing activity, document identity and tax treatment. Verify required invoice data and the selected reporting or clearance route before transmission.\n\n4. Submit & retain evidence: Keep the supported response and trace with the invoice. Follow approved rejection, retry, credit-note and credential-renewal procedures and reconcile submitted documents to the billing ledger.\n\nE-invoice scope, phase, document types and production onboarding are explicitly agreed. This module description is not a certification or compliance claim.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/integrations/zatca","url":"https://mansoq.com/faq#faq-module-zatca"},{"id":"module-analytics","question":"What is the Advanced Analytics workflow and what should we validate?","answer":"Selected operational, departmental and revenue reports, separate from standard Core reporting.\n\n1. Choose sources: Identify the operational source, owner and reporting boundary. Agree which facilities, encounters and financial records can contribute to each view and how data completeness will be checked.\n\n2. Define measures: Specify the unit of analysis, numerator, denominator, exclusions and reporting period. Reconcile financial and activity totals before treating a dashboard as an accepted measure.\n\n3. Publish a view: Configure the selected dashboard provider and view for its facility context. Verify role access, refresh behaviour, filters and the meaning of each displayed value with the intended users.\n\n4. Monitor & maintain: Review source freshness and changes to definitions or mappings. Agree export controls and retain acceptance evidence when a view is used for operational or financial decisions.\n\nThe analytics connector supplies provider-based dashboard access. Specific dashboards, metrics, warehouse design and external finance feeds require a defined reporting scope and acceptance.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/analytics","url":"https://mansoq.com/faq#faq-module-analytics"},{"id":"module-ai","question":"What is the Reviewed AI Assistance workflow and what should we validate?","answer":"Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made.\n\n1. Approve the task: Define the text or image assistance use case, permitted data, model provider and responsible reviewer. Agree consent, data handling, evaluation criteria and a manual fallback before activation.\n\n2. Provide context: Supply only the approved record context and inputs. Configure allowed models and usage limits; confirm image size, input boundaries and access for the selected feature.\n\n3. Generate assistance: Use the configured provider to produce assistance for the approved task. Treat the output as proposed content with possible omissions or errors; the model does not replace professional judgment.\n\n4. Review & retain: Have the responsible professional verify and edit the proposed content before saving or acting on it. Monitor approved evaluation results, access and provider failures under the agreed governance procedure.\n\nThe plugin supports configured text and image assistance. Autonomous diagnosis, prescribing or clinical action is not implied; each deployed use case and provider must be approved and evaluated.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/ai","url":"https://mansoq.com/faq#faq-module-ai"},{"id":"module-interfaces","question":"What is the System & Device Interfaces workflow and what should we validate?","answer":"Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually.\n\n1. Define the exchange: Name source and target systems, message types, direction, protocol and version. Agree whether the connection carries identity, encounters, orders, results, devices or financial activity and identify its owners.\n\n2. Map identifiers & data: Map patient, facility, practitioner and encounter identifiers alongside service codes, units, timestamps and statuses. Define required fields, transformations and the treatment of unsupported values.\n\n3. Test & accept: Use the agreed test environment, credentials and endpoint. Verify valid, invalid, duplicate and delayed messages, acknowledgements, ordering and reconciliation before approving production access.\n\n4. Operate & recover: Monitor failed and pending exchanges and assign support responsibility. Follow approved retry and duplicate rules, then reconcile records after downtime, credential rotation or interface version changes.\n\nAvailable protocols and adapters are release-specific. A third-party system name or standards logo is not proof of an active connector; accept the exact data, direction, license and support scope.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/integrations","url":"https://mansoq.com/faq#faq-module-interfaces"},{"id":"module-network-governance","question":"What is the Network Governance workflow and what should we validate?","answer":"Defined entity, tenant and record boundaries, accountable access and governed network composition.\n\n1. Map the network: Identify legal organizations, facilities, departments and their administrative owners. Define which catalogues and patient contexts are shared and which remain isolated.\n\n2. Delegate access: Assign cross-site and local responsibilities to named roles. Test access within a site, across accepted sharing boundaries and against restricted records.\n\n3. Coordinate continuity: Agree referral, record and responsibility handovers across participating services. Specify identifier mapping and the systems retaining ownership when an external facility is connected.\n\n4. Review boundaries: Maintain governance and acceptance evidence as sites, roles or releases change. Re-test sharing, restricted access and interface recovery before extending the network.\n\nShared facilities in one deployment and exchange between separate tenants are different scopes. The agreed governance and integration design determines record sharing.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/solutions/medical-city","url":"https://mansoq.com/faq#faq-module-network-governance"},{"id":"module-managed-revenue","question":"What is the Managed Revenue People Services workflow and what should we validate?","answer":"Qualified people, authorized access and an accepted operating scope, separate from RCM software.\n\n1. Agree responsibilities: Specify delegated revenue tasks, authorized users, provider and payer boundaries and service coverage. Name the organization that retains each clinical, contractual and financial decision.\n\n2. Prepare the work: Establish source access, work queues and the documents needed for eligibility, coding, authorization or claim tasks. Approve handover rules and quality checks before processing live work.\n\n3. Process & escalate: Perform only the agreed tasks through authorized workflows. Route missing clinical evidence, contracting questions and payer disputes to the retained owner and keep submission authority explicit.\n\n4. Review service delivery: Reconcile completed work, remittance and outstanding exceptions with the provider. Review agreed measures, support coverage and change requests against the service terms without promising unsupported financial outcomes.\n\nPeople services are distinct from software licensing and integration activation. Agree staffing, delegated authority, hours, deliverables and support terms in the service proposal.\n\nAccept the release, configuration, permissions, dependencies and tests with the workflow owner before activation. Public visibility alone does not establish clinical readiness.","href":"/platform/managed-revenue","url":"https://mansoq.com/faq#faq-module-managed-revenue"},{"id":"what-is-mansoq","question":"What is MANSOQ and what problem does it solve?","answer":"MANSOQ connects the patient record, care workflow, billing and agreed non-clinical operations. Your team works from a shared care context instead of repeatedly reconstructing what happened across separate queues. Choose a care product and plan, then agree the modules, connections, responsibilities and launch scope that fit your organisation.","href":"/platform","url":"https://mansoq.com/faq#faq-what-is-mansoq"},{"id":"software-and-services","question":"Am I buying software, managed services or both?","answer":"These care packages combine software with a defined monthly allowance of managed non-clinical work. Software supports the workflow; managed services help with agreed configuration, specialist review and operational queues. The proposal separates the two fees so you can see what you are buying. Licensed clinical staffing is supplied by the customer.","url":"https://mansoq.com/faq#faq-software-and-services"},{"id":"four-care-products","question":"How do I choose between Clinics, Polyclinics, TeleICU and Home & Palliative Care?","answer":"Choose Clinics for appointment-led outpatient care; Polyclinics for connected specialties, pharmacy, laboratory and stock; TeleICU for remote ICU consultation and handover; and Home & Palliative Care for visits, continuity, care plans and authorised family communication. Choose by the workflow you need to operate, not only by the facility name.","href":"/solutions","url":"https://mansoq.com/faq#faq-four-care-products"},{"id":"essential-fit","question":"Who is Essential best for?","answer":"Essential suits teams that can own their daily operations and need the complete contracted care workflow with baseline security, support and required national foundations. It provides a smaller managed-hours allowance. For example, your own reception and billing teams perform the daily work while MANSOQ helps with agreed setup and review tasks.","url":"https://mansoq.com/faq#faq-essential-fit"},{"id":"premium-fit","question":"When should I choose Premium?","answer":"Choose Premium when repeated tasks, disconnected handoffs or growing activity are making daily work harder. It adds workflow automation, operational dashboards, more care capacity, more managed hours and the published maintained-interface allowance. Its benefit is helping your team see and handle exceptions sooner; your team still owns the operational decisions and follow-through.","url":"https://mansoq.com/faq#faq-premium-fit"},{"id":"diamond-fit","question":"What makes Diamond meaningfully different from Premium?","answer":"Diamond includes Premium and adds a named owner for agreed operational queues, a monthly performance and capacity review, larger service allowances and the option to use your own clinical database and file storage. For example, an agreed unresolved billing or visit task has an identified MANSOQ contact coordinating the next action within the contracted hours.","url":"https://mansoq.com/faq#faq-diamond-fit"},{"id":"enterprise-fit","question":"When does Enterprise become the right choice?","answer":"Enterprise suits groups with multiple legal entities, complex integrations, dedicated deployment or an operating scope that needs a tailored agreement. It adds agreed group governance, permissions, consolidated reporting and a coordinated implementation programme. Sales defines the actual capacity, interfaces, managed scope, infrastructure responsibilities and service targets in the proposal.","url":"https://mansoq.com/faq#faq-enterprise-fit"},{"id":"same-safety-foundation","question":"Do I need a higher plan to get basic security or required national workflows?","answer":"The baseline includes role-based access, an audit trail, consent, backup and export, plus Saudi insurance and coding foundations for the contracted workflow. Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. Higher plans add capacity, automation, managed follow-through and governance.","url":"https://mansoq.com/faq#faq-same-safety-foundation"},{"id":"choose-by-benefit","question":"How do I decide whether the extra cost is worth it?","answer":"Compare the actual constraint you want to remove: care capacity, repeated work, interfaces, operational follow-through or group governance. Then compare the included hours and connections with your workload. An illustrative measure is the number of overdue tasks or repeated data-entry steps before and after rollout. MANSOQ does not promise a fixed saving or revenue increase without your baseline and agreed measurement.","url":"https://mansoq.com/faq#faq-choose-by-benefit"},{"id":"mixed-care-group","question":"Can one organisation combine several care products?","answer":"Yes, a mixed care scope can be discussed in one composition proposal. For example, a group may need outpatient clinics, remote ICU consultation and home-care follow-up. Agree each workflow, capacity measure, data boundary and responsible team. Do not simply add public card prices and assume that this covers shared infrastructure or separate legal entities.","url":"https://mansoq.com/faq#faq-mixed-care-group"},{"id":"all-plan-foundation","question":"What is included in every care plan?","answer":"Patient record, scheduling, documentation, orders, medication and billing for the contracted care workflow.\n\nRole-based access, audit trail, consent, backup and export; required Saudi insurance, coding, NPHIES and ZATCA workflows where applicable.\n\nPatient / family access, baseline product support, onboarding and agreed migration specification.\n\nCustomer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.","url":"https://mansoq.com/faq#faq-all-plan-foundation"},{"id":"feature-rcm-raas","question":"How does \"RCM RaaS · 18% of collections\" work and what is the benefit?","answer":"What it means: A managed revenue-cycle service for your approved billing and payer worklists, priced on the money actually collected within the agreed scope.\n\nHow it works: Agree the revenue-service scope, customer responsibilities and eligible collection definition with the team. The service supports the accepted eligibility, claims and reconciliation workflows. Collection fees follow the accepted agreement and reviewed financial evidence.\n\nOne example: On SAR 100,000 of approved eligible collections, the RaaS fee is SAR 18,000, plus applicable VAT. The package subscription is charged separately.\n\nYour benefit & expected result: An accountable team follows revenue exceptions through to reconciliation, with a transparent fee tied to eligible collections. Payer approval and collection outcomes depend on the actual evidence and payer decisions.\n\nIncluded scope: Agreed eligibility and authorisation follow-up, claim preparation and submission, rejection and denial worklists, payer follow-up and remittance reconciliation. Customer retains clinical decisions, source permissions and approval of refunds, write-offs and bank changes. Fees are additional to the package subscription, on eligible cleared collections after agreed refunds and exclusions; implementation and service acceptance are required. Activate only after signed scope and implementation/service acceptance. No annual discount applies to collection fees.","url":"https://mansoq.com/faq#faq-feature-rcm-raas"},{"id":"feature-patient-access","question":"How does \"Patient access & secure team roles\" work and what is the benefit?","answer":"What it means: Patients and authorised family members can access the agreed patient-facing information. Staff access is based on their job and care responsibilities.\n\nHow it works: Assign roles such as clinician, reception and billing, then approve patient or family access. Permissions control available actions and records; the audit trail records activity.\n\nOne example: A receptionist manages an appointment while the treating clinician updates clinical notes. An authorised family member sees only the information approved for them.\n\nYour benefit & expected result: People can do their work and follow care with appropriate access, while you retain visibility of who used the system.\n\nIncluded scope: Access depends on configured permissions, consent and the agreed patient/family workflow.","url":"https://mansoq.com/faq#faq-feature-patient-access"},{"id":"feature-dashboards","question":"How does \"Operational dashboards & insights\" work and what is the benefit?","answer":"What it means: A current view of agreed operational measures, such as activity, outstanding work and capacity usage.\n\nHow it works: The dashboards summarise recorded system activity. Authorised managers can review the agreed measures and investigate the underlying work.\n\nOne example: A clinic manager reviews completed visits and outstanding billing tasks, then assigns the backlog to the appropriate team.\n\nYour benefit & expected result: A clearer view of where work is building up, so managers can prioritise action using recorded data.\n\nIncluded scope: Measures and refresh frequency depend on the accepted scope and the completeness of source data.","url":"https://mansoq.com/faq#faq-feature-dashboards"},{"id":"feature-monthly-review","question":"How does \"Monthly performance & capacity review\" work and what is the benefit?","answer":"What it means: A scheduled review of agreed operational results, outstanding issues and how much of your package capacity you are using.\n\nHow it works: The named owner prepares the agreed measures, reviews them with you and records actions, responsible people and any capacity changes you approve. Preparation and review use managed hours.\n\nOne example: You review clinician-capacity usage and the billing backlog, then agree the next month’s operational priorities.\n\nYour benefit & expected result: An agreed action plan and fewer surprises about capacity. Outcomes depend on the recorded data and follow-through by both teams.","url":"https://mansoq.com/faq#faq-feature-monthly-review"},{"id":"feature-entity-governance","question":"How does \"Multi-entity governance & permissions\" work and what is the benefit?","answer":"What it means: An agreed access and governance structure for a group with multiple facilities or legal entities.\n\nHow it works: Map the entities, data boundaries and responsible roles with sales and implementation. Approve who can work within each entity and who can see permitted group-level information, then test those permissions before launch.\n\nOne example: A branch manager sees the records they are authorised to manage at their branch; a group director sees the approved group-level reports.\n\nYour benefit & expected result: Clearer accountability across the group and access that follows your agreed organisational boundaries.\n\nIncluded scope: Separate legal entities and patient-record sharing require an agreed data and deployment scope.","url":"https://mansoq.com/faq#faq-feature-entity-governance"},{"id":"feature-group-reporting","question":"How does \"Consolidated group reporting\" work and what is the benefit?","answer":"What it means: Bring agreed measures from multiple facilities into a group view for authorised leadership.\n\nHow it works: Agree the facilities, measures, definitions and reporting frequency. The group view consolidates the accepted data while respecting the approved permissions and data boundaries.\n\nOne example: A director compares monthly care activity and outstanding operational work across three branches using the same agreed definitions.\n\nYour benefit & expected result: Easier comparison across locations and a clearer basis for assigning resources and investigating differences.\n\nIncluded scope: Included sources, reporting frequency and any custom report development are agreed in the Enterprise proposal.","url":"https://mansoq.com/faq#faq-feature-group-reporting"},{"id":"feature-custom-integrations","question":"How does \"Custom integrations & service agreement\" work and what is the benefit?","answer":"What it means: A separately defined integration and support scope designed around your organisation’s systems and operating needs.\n\nHow it works: Sales and delivery agree the systems, exchanged data, acceptance tests, service hours, response targets and responsibilities. Each connection is commissioned before use; the signed agreement sets the support commitment.\n\nOne example: A group needs its existing finance system connected to accepted billing data. The proposal defines the mapping, tests and support arrangements for that connection.\n\nYour benefit & expected result: A clear scope for your more complex setup and measurable service commitments once agreed.\n\nIncluded scope: Connections, vendor charges, service targets and price are determined in the sales quotation. Enterprise does not imply unlimited integrations or automatic 24/7 coverage.","url":"https://mansoq.com/faq#faq-feature-custom-integrations"},{"id":"feature-implementation","question":"How does \"A dedicated implementation programme\" work and what is the benefit?","answer":"What it means: A coordinated launch plan for your agreed facilities, migration, integrations, training and acceptance.\n\nHow it works: Agree milestones, owners and acceptance criteria. Prepare and reconcile the migration, test access and connections, train the agreed users, and review readiness before a planned cutover.\n\nOne example: Three branches launch in stages: a pilot branch first, migration reconciliation and training next, then the other branches after their acceptance checks.\n\nYour benefit & expected result: A clearer launch sequence, visible responsibilities and agreed evidence for each readiness decision.\n\nIncluded scope: Delivery dates, migration work, on-site attendance and price are defined in the signed implementation scope.","url":"https://mansoq.com/faq#faq-feature-implementation"},{"id":"feature-national-workflows","question":"How does \"Core national workflows where required\" work and what is the benefit?","answer":"What it means: The Saudi insurance, coding and electronic-invoicing workflows that apply to your contracted care service.\n\nHow it works: During setup, agree which workflows apply, such as NPHIES insurance exchange, Saudi billing codes and ZATCA invoicing. Activate and test the relevant connections with your organisation’s required credentials and approvals.\n\nOne example: An insured clinic needs NPHIES eligibility checks and electronic invoices. Those applicable workflows are included in the foundation and accepted before use.\n\nYour benefit & expected result: Your applicable national workflows are part of the care foundation, with required information and connection status easier to follow.\n\nIncluded scope: Organisational approvals, payer/vendor access and connection acceptance are required. National foundation connectors do not use the separate external-interface allowance.","url":"https://mansoq.com/faq#faq-feature-national-workflows"},{"id":"feature-customer-storage","question":"How does \"Your own database & file storage\" work and what is the benefit?","answer":"What it means: An optional deployment choice: keep the primary clinical database and private clinical, facility and report files in infrastructure you control.\n\nHow it works: Provide a dedicated PostgreSQL database and private S3-compatible storage, such as AWS S3, DigitalOcean Spaces or MinIO on your server. After credentials, network, backup and recovery are accepted, the live app, imports, reports and background workers use that destination.\n\nOne example: Your organisation owns a PostgreSQL database and a private Spaces bucket. A new clinical record is saved in your database, and a patient attachment is saved in your bucket.\n\nYour benefit & expected result: More control over the primary clinical data location, infrastructure access and recovery policy. The clinical runtime has no automatic fallback to a MANSOQ database or bucket.\n\nIncluded scope: Available in Diamond and Enterprise after connection acceptance. Infrastructure and connection/migration work are scoped separately. The full data-processing and retention scope is defined in the accepted agreement. Changing an existing live destination requires an agreed migration.","url":"https://mansoq.com/faq#faq-feature-customer-storage"},{"id":"package-price","question":"How is a MANSOQ package priced?","answer":"The recurring base combines the published software fee and managed-services fee. Additional care capacity, sites and approved managed hours are added at the selected plan rates. Setup, migration, bespoke work, customer infrastructure and applicable third-party usage are scoped separately. Review the itemised proposal, tax and commercial term before accepting it.","href":"/pricing#configuration","url":"https://mansoq.com/faq#faq-package-price"},{"id":"currency-tax","question":"Which currency is used and is VAT included?","answer":"The care-package card prices are in Saudi riyals (SAR) before VAT. Applicable tax is shown separately in the proposal. Check the billed currency and tax treatment on the final quotation, especially for an organisation outside Saudi Arabia. A displayed monthly amount should be compared with the complete invoice, not treated as a tax-inclusive total.","url":"https://mansoq.com/faq#faq-currency-tax"},{"id":"enterprise-price-hidden","question":"Why is there no public Enterprise price?","answer":"Enterprise depends on your entities, scale, integration work, deployment, migration and agreed operating responsibilities. A public fixed price could hide material work or imply commitments that have not been scoped. Use Request a sales call; the selected care product and Enterprise package are included in the request so the team can prepare the right quotation.","url":"https://mansoq.com/faq#faq-enterprise-price-hidden"},{"id":"annual-discount","question":"How does annual prepayment change the price?","answer":"Annual prepayment applies the published discount to the base software fee only. Managed services, additional care capacity, sites, hours, setup and third-party charges are not reduced by that discount. The package builder shows the selected billing basis. The signed proposal determines payment dates and the actual invoicing arrangement.","url":"https://mansoq.com/faq#faq-annual-discount"},{"id":"setup-separate","question":"Why are setup and migration separate from the monthly price?","answer":"These are launch projects whose effort depends on source data, record quality, interfaces, training, sites and cutover work. The monthly package describes recurring use and the agreed ongoing service allowance. A small clean import and a complex multi-system migration need different launch scopes. Any displayed setup range is a planning budget, with the final scope agreed in writing.","url":"https://mansoq.com/faq#faq-setup-separate"},{"id":"third-party-costs","question":"Which third-party costs should I budget for?","answer":"Depending on your selection, budget for messaging, video, network carriers, hardware, external-system licences or interface fees, and customer-owned infrastructure. Agree the supplier, payer, usage limit and consent requirements before activation. An included workflow or maintained interface does not mean the supplier provides its equipment or traffic free of charge.","url":"https://mansoq.com/faq#faq-third-party-costs"},{"id":"avoid-surprise-fees","question":"How can I avoid surprise charges?","answer":"Have the proposal list base capacity, additional-unit and site rates, included hours, approved extra hours, interfaces, setup, infrastructure and third-party usage. Agree who can approve extra work and how usage is reported. Routine service terms call for notifications at 80% and 100% of the managed-hours allowance and approval before additional work.","url":"https://mansoq.com/faq#faq-avoid-surprise-fees"},{"id":"monthly-contract","question":"Does a monthly price automatically mean a month-to-month contract?","answer":"No contract duration should be inferred from the card price. The quotation and signed agreement define the term, payment schedule, renewal, notice and cancellation rules. Ask the sales team to state those terms explicitly before signing, including how an annual prepayment or staged implementation affects your commitment.","url":"https://mansoq.com/faq#faq-monthly-contract"},{"id":"request-no-payment","question":"Do I need to pay to build a plan or request a proposal?","answer":"The builder lets you review a proposed scope and request help without making a payment. Sending a proposal request does not activate a clinical service or accept a contract. Review the itemised commercial and implementation scope, then use the agreed acceptance and payment process if you decide to proceed.","url":"https://mansoq.com/faq#faq-request-no-payment"},{"id":"regional-pricing","question":"Can customers outside Saudi Arabia request a package?","answer":"Discuss the country, care workflow, billing rules, data location, hosting and required local connections with sales. The Saudi catalogue is a starting point for scope, not an automatic promise of every country-specific integration or tax arrangement. A regional proposal should state the applicable currency, local requirements, deployment and support window.","url":"https://mansoq.com/faq#faq-regional-pricing"},{"id":"clinics-extra-rates","question":"What do extra Clinics capacity, sites and managed hours cost?","answer":"Essential: SAR 150.00 per additional care unit per month; SAR 400.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nPremium: SAR 200.00 per additional care unit per month; SAR 600.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nDiamond: SAR 250.00 per additional care unit per month; SAR 900.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nThese rates are before VAT and do not increase other included allowances. Enterprise additions are scoped in its sales quotation. Bespoke work, infrastructure and vendor charges are separate.","url":"https://mansoq.com/faq#faq-clinics-extra-rates"},{"id":"polyclinics-extra-rates","question":"What do extra Polyclinics capacity, sites and managed hours cost?","answer":"Essential: SAR 150.00 per additional care unit per month; SAR 1,500.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nPremium: SAR 200.00 per additional care unit per month; SAR 2,000.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nDiamond: SAR 250.00 per additional care unit per month; SAR 3,000.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nThese rates are before VAT and do not increase other included allowances. Enterprise additions are scoped in its sales quotation. Bespoke work, infrastructure and vendor charges are separate.","url":"https://mansoq.com/faq#faq-polyclinics-extra-rates"},{"id":"teleicu-extra-rates","question":"What do extra TeleICU capacity, sites and managed hours cost?","answer":"Essential: SAR 200.00 per additional care unit per month; SAR 1,500.00 per additional site per month; SAR 280.00 per approved extra managed hour.\n\nPremium: SAR 350.00 per additional care unit per month; SAR 2,500.00 per additional site per month; SAR 280.00 per approved extra managed hour.\n\nDiamond: SAR 500.00 per additional care unit per month; SAR 4,000.00 per additional site per month; SAR 280.00 per approved extra managed hour.\n\nThese rates are before VAT and do not increase other included allowances. Enterprise additions are scoped in its sales quotation. Bespoke work, infrastructure and vendor charges are separate.","url":"https://mansoq.com/faq#faq-teleicu-extra-rates"},{"id":"home_palliative-extra-rates","question":"What do extra Home & Palliative Care capacity, sites and managed hours cost?","answer":"Essential: SAR 20.00 per additional care unit per month; SAR 750.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nPremium: SAR 35.00 per additional care unit per month; SAR 1,250.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nDiamond: SAR 50.00 per additional care unit per month; SAR 2,000.00 per additional site per month; SAR 180.00 per approved extra managed hour.\n\nThese rates are before VAT and do not increase other included allowances. Enterprise additions are scoped in its sales quotation. Bespoke work, infrastructure and vendor charges are separate.","url":"https://mansoq.com/faq#faq-home_palliative-extra-rates"},{"id":"annual-price-worked-example","question":"Can you show a worked annual-prepayment example?","answer":"Illustrative example using the published Clinics Premium rate: SAR 1,090.00 base software + SAR 900.00 managed services = SAR 1,990.00 per month before VAT.\n\nWith annual software prepayment, the base monthly-equivalent total is SAR 1,881.00 and the recurring-year equivalent is SAR 22,572.00. Only software receives the published discount. Approved extras, setup, tax and supplier fees are additional, and invoice timing follows the contract.","url":"https://mansoq.com/faq#faq-annual-price-worked-example"},{"id":"extra-capacity-worked-example","question":"Can you show how extra capacity, a second site and extra hours are calculated?","answer":"Illustrative Clinics Premium configuration: 152 clinician units, two sites and one approved extra managed hour.\n\nBase SAR 1,990.00 + two extra care units SAR 400.00 + one extra site SAR 600.00 + one extra hour SAR 180.00 = SAR 3,170.00 per month before VAT, setup and third-party costs.\n\nThe care-unit increase does not add hours or interfaces. Actual changes require approval and the accepted quotation.","url":"https://mansoq.com/faq#faq-extra-capacity-worked-example"},{"id":"capacity-measures","question":"Why do products use different capacity measures?","answer":"Clinics and Polyclinics count named independent clinicians; TeleICU counts commissioned ICU beds; Home & Palliative Care counts unique active patients during the month. These measures reflect the workload of each care setting. A care unit is not a visit, a software login or a shift unless your accepted contract explicitly defines it that way.","url":"https://mansoq.com/faq#faq-capacity-measures"},{"id":"clinician-counting","question":"Do nurses, receptionists and administrators use clinician capacity?","answer":"The clinician measure counts named independent clinicians delivering care. Assisting nursing, administration and support accounts do not add a clinician fee under that definition. For example, 20 independent clinicians and five reception accounts use 20 clinician units. Agree named clinician identities and role access; this definition does not promise unlimited accounts or infrastructure resources.","url":"https://mansoq.com/faq#faq-clinician-counting"},{"id":"icu-counting","question":"Are TeleICU beds billed only when occupied?","answer":"The measure is a commissioned, enabled ICU bed under the contract. It is not the daily number of occupied beds. For example, 50 commissioned beds use 50 units even if occupancy changes. Agree which sites and beds are accepted, enabled and later decommissioned so the contracted count stays clear.","url":"https://mansoq.com/faq#faq-icu-counting"},{"id":"home-patient-counting","question":"Does every home visit count as another patient?","answer":"No. A unique patient with a completed contracted visit or active remote episode is counted once during the month across contracted branches. Four visits for the same patient still count as one active patient. Archived or deceased patients do not remain billable under the published definition; agree reconciliation and activity records before billing.","url":"https://mansoq.com/faq#faq-home-patient-counting"},{"id":"capacity-not-hours","question":"Will adding more patients, clinicians or beds add managed hours too?","answer":"Additional care units and sites do not automatically increase managed hours or maintained interfaces. These are separate allowances. For example, more home-care patients may require both additional patient capacity and extra agreed dispatch support; the second part needs its own managed-hours scope. The proposal should show each change separately.","url":"https://mansoq.com/faq#faq-capacity-not-hours"},{"id":"sites-definition","question":"What does one included site mean?","answer":"The non-Enterprise packages include one facility or branch in the contracted data boundary. Additional sites are priced separately and require agreed access, capacity and setup. A separate legal entity or a requirement to segregate patient data may need an Enterprise proposal rather than a simple extra-site fee.","url":"https://mansoq.com/faq#faq-sites-definition"},{"id":"growth-planning","question":"What should I do when we approach the package capacity?","answer":"Review actual care usage, managed workload and interface needs together. Compare approved extra capacity with the next plan instead of looking at the unit price alone. Agree the capacity change, effective date and resulting fees before use. Clinical continuity, access and billing reconciliation should be part of the change plan.","url":"https://mansoq.com/faq#faq-growth-planning"},{"id":"enterprise-reference-capacity","question":"Does the Enterprise capacity reference mean unlimited usage?","answer":"The plus sign indicates a larger deployment to be scoped with sales. It is not an unlimited allowance or an automatic minimum purchase requirement. The quotation specifies actual care units, sites, users, interfaces, managed operations and infrastructure limits. Use the reference as an invitation to size your organisation accurately.","url":"https://mansoq.com/faq#faq-enterprise-reference-capacity"},{"id":"current-capacity-ladder","question":"How much care capacity does each plan include?","answer":"Clinics: Essential 50 active clinicians; Premium 150 active clinicians; Diamond 250 active clinicians; Enterprise 550+ active clinicians\n\nPolyclinics: Essential 50 active clinicians; Premium 150 active clinicians; Diamond 250 active clinicians; Enterprise 550+ active clinicians\n\nTeleICU: Essential 50 commissioned ICU beds; Premium 150 commissioned ICU beds; Diamond 250 commissioned ICU beds; Enterprise 550+ commissioned ICU beds\n\nHome & Palliative Care: Essential 50 active patients / month; Premium 150 active patients / month; Diamond 250 active patients / month; Enterprise 550+ active patients / month\n\nThe non-Enterprise packages include one site. Enterprise is a sizing reference; sales agrees actual limits. Use the product’s counting definition and reconcile the accepted capacity before billing.","url":"https://mansoq.com/faq#faq-current-capacity-ladder"},{"id":"clinic-day","question":"How does a normal clinic visit run from beginning to end?","answer":"Within the accepted workflow, reception schedules and registers the patient, the clinician documents the consultation and orders, and the authorised team prepares the cash or insurance billing and follow-up. The shared patient and encounter context connects those steps. Example: a missing insurance detail remains a visible operational task rather than being lost after the consultation.","url":"https://mansoq.com/faq#faq-clinic-day"},{"id":"clinic-cash-insurance","question":"Can Clinics support both cash patients and insurance workflows?","answer":"The contracted outpatient scope includes cash and insurance workflows. Agree your services, tariffs, payers, authorisation requirements and applicable national connections during setup. The platform helps connect documented care with billing and payer follow-up; payer approval and collection still depend on correct evidence, eligibility, contracts and the payer response.","url":"https://mansoq.com/faq#faq-clinic-cash-insurance"},{"id":"clinic-reminders","question":"How do recall and reminder workflows benefit a clinic?","answer":"Premium and above add agreed recall and reminder automation. Define which follow-ups need a task or message, who owns the queue and how consent and contact details are handled. For example, an agreed follow-up list helps reception see whom to contact next. Message delivery, attendance and clinical follow-up are not guaranteed; provider usage is scoped separately.","url":"https://mansoq.com/faq#faq-clinic-reminders"},{"id":"clinic-departments","question":"Can a clinic add a laboratory, pharmacy or other departments later?","answer":"Use the tailored builder or discuss an expansion with sales. Additional departments require their accepted module scope, required companions, setup, access roles and any external connections. A clinic package should not be assumed to include every hospital department. If several specialties and departmental workflows are central to your operation, compare the Polyclinics scope.","href":"/pricing/capabilities","url":"https://mansoq.com/faq#faq-clinic-departments"},{"id":"clinics-rcm-raas","question":"How is RCM RaaS priced for Clinics?","answer":"Essential: 18%; Premium: 15%; Diamond: 10%; Enterprise: 4.5%–7.5%. These percentages apply to approved eligible cleared collections, additional to the package subscription. Enterprise needs an approved exact rate within the range and an accepted scope. Actual fees are calculated from reviewed financial evidence after agreed refunds and exclusions; estimated collections in the builder do not create an invoice.","url":"https://mansoq.com/faq#faq-clinics-rcm-raas"},{"id":"clinics-prices","question":"What are the published Clinics prices?","answer":"Essential: SAR 990.00 per month, comprising SAR 690.00 software + SAR 300.00 managed services. Includes 50 active clinicians and one site.\n\nPremium: SAR 1,990.00 per month, comprising SAR 1,090.00 software + SAR 900.00 managed services. Includes 150 active clinicians and one site.\n\nDiamond: SAR 3,490.00 per month, comprising SAR 1,690.00 software + SAR 1,800.00 managed services. Includes 250 active clinicians and one site.\n\nEnterprise: Price and actual operating scope are determined by the sales quotation.\n\nAll public amounts are before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Additions and third-party costs are separately scoped. An unapproved price is not a public offer.","href":"/pricing#care-packages","url":"https://mansoq.com/faq#faq-clinics-prices"},{"id":"clinics-tier-benefits","question":"What changes between the Clinics plans?","answer":"Essential: Complete the care workflow. Appointment, consultation, referral and cash / insurance workflow with basic operating reports.\n\nPremium: Reduce repeat work and find exceptions sooner. Appointment, consultation, referral and cash / insurance workflow with basic operating reports. Recall and reminder automation, eligibility / authorization worklists, denial analytics and monthly specialist optimization.\n\nDiamond: Give agreed operational queues an accountable owner. Appointment, consultation, referral and cash / insurance workflow with basic operating reports. Recall and reminder automation, eligibility / authorization worklists, denial analytics and monthly specialist optimization. Named owner for agreed claims / recall queues, exception follow-up and a monthly recovery and performance review. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nEnterprise: Govern care and operations across the organization. Appointment, consultation, referral and cash / insurance workflow with basic operating reports. Recall and reminder automation, eligibility / authorization worklists, denial analytics and monthly specialist optimization. Named owner for agreed claims / recall queues, exception follow-up and a monthly recovery and performance review. Group governance, entity-specific permissions, consolidated reporting, agreed integrations and dedicated operating scope. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nHigher tiers retain the contracted care foundation. Capacity, managed-hour and interface allowances are separate; the accepted proposal determines the live scope.","url":"https://mansoq.com/faq#faq-clinics-tier-benefits"},{"id":"clinics-care-workflow-example","question":"Clinics: How does the core care workflow work, and what is the benefit?","answer":"What it means: The daily care workflow in one system: appointments, the patient record, clinical documentation, orders and billing.\n\nHow it works: Reception books the visit, the clinician documents care, and authorised billing staff use the recorded services to prepare the invoice or insurance workflow.\n\nOne example: A patient books a consultation. The doctor records the visit and orders a test; billing staff prepare the agreed charges from that visit.\n\nYour benefit & expected result: Less repeated entry and an easier way to trace the appointment, care record and charges together.","url":"https://mansoq.com/faq#faq-clinics-care-workflow-example"},{"id":"clinics-automation-example","question":"Clinics: How does automation work in this care setting?","answer":"What it means: Routine steps follow agreed rules, while items needing human attention appear in a shared work list.\n\nHow it works: Agree the trigger, next step and responsible role. When a required item is missing or a task cannot move forward, it is routed to the appropriate team for review.\n\nOne example: A visit is ready for billing but an insurance detail is missing. The case goes to the billing team’s follow-up queue instead of being lost among completed visits.\n\nYour benefit & expected result: Fewer forgotten tasks and less time searching for the next action. Your team reviews and resolves exceptions.\n\nIncluded scope: Automation rules are configured for your accepted workflow; insurer approval and payment are not guaranteed.","url":"https://mansoq.com/faq#faq-clinics-automation-example"},{"id":"clinics-named-owner-example","question":"Clinics: What does the named owner do in this care setting?","answer":"What it means: A named MANSOQ operations contact is accountable for following through on your agreed non-clinical work queues.\n\nHow it works: Agree the queue, actions and escalation route. The owner reviews outstanding work, coordinates with your team and records progress within the included managed-hours allowance.\n\nOne example: A billing task is missing documentation. The owner coordinates with your billing team, records the next action and follows its progress.\n\nYour benefit & expected result: Clearer responsibility and fewer hand-offs between contacts, with a visible record of follow-up.\n\nIncluded scope: The owner operates within the agreed service window and hours. Full outsourced billing, unlimited queue work and clinical staffing require their own scope.","url":"https://mansoq.com/faq#faq-clinics-named-owner-example"},{"id":"polyclinic-clinic-difference","question":"How is Polyclinics different from Clinics?","answer":"Polyclinics adds shared outpatient records and cross-specialty referrals with the contracted pharmacy, laboratory, inventory and departmental billing scope. Its operational focus is the handoff between teams. Example: a clinician requests an accepted laboratory service, the result stays linked to the patient and the documented service supports the authorised billing workflow.","url":"https://mansoq.com/faq#faq-polyclinic-clinic-difference"},{"id":"cross-specialty-access","question":"Can specialists share a patient record without giving everyone unrestricted access?","answer":"Shared care context is governed by approved roles, facilities and data boundaries. Agree which clinicians and departmental teams may read or update each relevant part, then test their permissions before launch. The benefit is a more connected referral or handover while preserving accountability. Separate legal entities require an agreed sharing and deployment scope.","url":"https://mansoq.com/faq#faq-cross-specialty-access"},{"id":"polyclinic-stock","question":"What is the benefit of connecting pharmacy, laboratory and inventory?","answer":"Accepted departmental workflows connect service requests, results or medication activity with the patient and the relevant stock and charge evidence. This helps teams follow what was requested, performed and recorded. Premium adds agreed handoff automation, stock and expiry alerts and contribution reporting. Exact data, catalogue setup and device connections are accepted during implementation.","url":"https://mansoq.com/faq#faq-polyclinic-stock"},{"id":"polyclinic-charge-leakage","question":"How does Diamond help with cross-department exceptions and missed charges?","answer":"Agree specific exception or revenue-cycle queues with the named operations owner. The owner coordinates outstanding documentation, handoffs or charge-evidence issues and records progress within the included hours. The monthly review helps identify repeated causes and assign actions. It is a defined follow-through service, not a guarantee that every possible lost charge will be recovered.","url":"https://mansoq.com/faq#faq-polyclinic-charge-leakage"},{"id":"polyclinics-rcm-raas","question":"How is RCM RaaS priced for Polyclinics?","answer":"Essential: 18%; Premium: 15%; Diamond: 10%; Enterprise: 4.5%–7.5%. These percentages apply to approved eligible cleared collections, additional to the package subscription. Enterprise needs an approved exact rate within the range and an accepted scope. Actual fees are calculated from reviewed financial evidence after agreed refunds and exclusions; estimated collections in the builder do not create an invoice.","url":"https://mansoq.com/faq#faq-polyclinics-rcm-raas"},{"id":"polyclinics-prices","question":"What are the published Polyclinics prices?","answer":"Essential: SAR 2,490.00 per month, comprising SAR 1,490.00 software + SAR 1,000.00 managed services. Includes 50 active clinicians and one site.\n\nPremium: SAR 4,990.00 per month, comprising SAR 2,790.00 software + SAR 2,200.00 managed services. Includes 150 active clinicians and one site.\n\nDiamond: SAR 8,990.00 per month, comprising SAR 4,490.00 software + SAR 4,500.00 managed services. Includes 250 active clinicians and one site.\n\nEnterprise: Price and actual operating scope are determined by the sales quotation.\n\nAll public amounts are before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Additions and third-party costs are separately scoped. An unapproved price is not a public offer.","href":"/pricing#care-packages","url":"https://mansoq.com/faq#faq-polyclinics-prices"},{"id":"polyclinics-tier-benefits","question":"What changes between the Polyclinics plans?","answer":"Essential: Complete the care workflow. Shared outpatient records, cross-specialty referrals, pharmacy, laboratory, stock and departmental billing.\n\nPremium: Reduce repeat work and find exceptions sooner. Shared outpatient records, cross-specialty referrals, pharmacy, laboratory, stock and departmental billing. Department handoff automation, tariff / denial review, stock and expiry alerts and service contribution reporting.\n\nDiamond: Give agreed operational queues an accountable owner. Shared outpatient records, cross-specialty referrals, pharmacy, laboratory, stock and departmental billing. Department handoff automation, tariff / denial review, stock and expiry alerts and service contribution reporting. Named operations owner for cross-department exceptions, charge leakage and agreed RCM queues; monthly management review. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nEnterprise: Govern care and operations across the organization. Shared outpatient records, cross-specialty referrals, pharmacy, laboratory, stock and departmental billing. Department handoff automation, tariff / denial review, stock and expiry alerts and service contribution reporting. Named operations owner for cross-department exceptions, charge leakage and agreed RCM queues; monthly management review. Group governance, entity-specific permissions, consolidated reporting, agreed integrations and dedicated operating scope. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nHigher tiers retain the contracted care foundation. Capacity, managed-hour and interface allowances are separate; the accepted proposal determines the live scope.","url":"https://mansoq.com/faq#faq-polyclinics-tier-benefits"},{"id":"polyclinics-care-workflow-example","question":"Polyclinics: How does the core care workflow work, and what is the benefit?","answer":"What it means: The daily care workflow in one system: appointments, the patient record, clinical documentation, orders and billing.\n\nHow it works: Reception books the visit, the clinician documents care, and authorised billing staff use the recorded services to prepare the invoice or insurance workflow.\n\nOne example: A patient books a consultation. The doctor records the visit and orders a test; billing staff prepare the agreed charges from that visit.\n\nYour benefit & expected result: Less repeated entry and an easier way to trace the appointment, care record and charges together.","url":"https://mansoq.com/faq#faq-polyclinics-care-workflow-example"},{"id":"polyclinics-automation-example","question":"Polyclinics: How does automation work in this care setting?","answer":"What it means: Routine steps follow agreed rules, while items needing human attention appear in a shared work list.\n\nHow it works: Agree the trigger, next step and responsible role. When a required item is missing or a task cannot move forward, it is routed to the appropriate team for review.\n\nOne example: A visit is ready for billing but an insurance detail is missing. The case goes to the billing team’s follow-up queue instead of being lost among completed visits.\n\nYour benefit & expected result: Fewer forgotten tasks and less time searching for the next action. Your team reviews and resolves exceptions.\n\nIncluded scope: Automation rules are configured for your accepted workflow; insurer approval and payment are not guaranteed.","url":"https://mansoq.com/faq#faq-polyclinics-automation-example"},{"id":"polyclinics-named-owner-example","question":"Polyclinics: What does the named owner do in this care setting?","answer":"What it means: A named MANSOQ operations contact is accountable for following through on your agreed non-clinical work queues.\n\nHow it works: Agree the queue, actions and escalation route. The owner reviews outstanding work, coordinates with your team and records progress within the included managed-hours allowance.\n\nOne example: A billing task is missing documentation. The owner coordinates with your billing team, records the next action and follows its progress.\n\nYour benefit & expected result: Clearer responsibility and fewer hand-offs between contacts, with a visible record of follow-up.\n\nIncluded scope: The owner operates within the agreed service window and hours. Full outsourced billing, unlimited queue work and clinical staffing require their own scope.","url":"https://mansoq.com/faq#faq-polyclinics-named-owner-example"},{"id":"teleicu-team-model","question":"Does TeleICU include intensivists or bedside nurses?","answer":"The customer supplies the licensed remote and bedside clinicians, clinical decisions, escalation coverage and medical governance. MANSOQ supplies the contracted technology and non-clinical operating support. Commissioned bed capacity does not purchase clinician shifts, continuous clinical alarm surveillance or emergency response staffing.","url":"https://mansoq.com/faq#faq-teleicu-team-model"},{"id":"teleicu-essential-data","question":"Can Essential TeleICU work before automated device feeds are connected?","answer":"The Essential scope is consultation-led with secure consultation, manually entered or charted data, handover, escalation and downtime procedures. Agree the information your clinicians require, who enters it and how they verify its time and source. A clinical record containing manually entered data should not be presented as a live monitor feed.","url":"https://mansoq.com/faq#faq-teleicu-essential-data"},{"id":"teleicu-interface-examples","question":"Which TeleICU systems could be connected?","answer":"Examples include an admission or EHR feed, monitors, ventilators and laboratory results, within the selected maintained-interface allowance. Each feed needs an authorised source, supported format, agreed mapping, patient and bed matching, freshness checks and accepted tests. A plan allowance is a scope limit; it does not mean every vendor device is already commissioned.","url":"https://mansoq.com/faq#faq-teleicu-interface-examples"},{"id":"teleicu-stale-data","question":"How should stale or disconnected ICU data be handled?","answer":"Freshness and disconnect controls are part of the accepted connected workflow. Agree how the team recognises an unavailable or old feed, verifies current information and uses the downtime procedure. The clinical team must not rely on an outdated value as current. Escalation, fallback documentation and ownership are rehearsed before clinical launch.","url":"https://mansoq.com/faq#faq-teleicu-stale-data"},{"id":"teleicu-alert-responsibility","question":"Who responds to ICU alarms or urgent clinical deterioration?","answer":"Your licensed clinical organisation defines and provides that response. Agree the bedside and remote escalation chain, response coverage and emergency pathway under your medical governance. Managed operational hours and a named technical workflow owner do not replace clinical alarm surveillance or an emergency care team.","url":"https://mansoq.com/faq#faq-teleicu-alert-responsibility"},{"id":"teleicu-equipment","question":"Are cameras, monitors, telepresence devices and connectivity included?","answer":"Equipment, telepresence and connectivity are customer-owned or separately quoted. Assess compatible devices, permissions, bandwidth, maintenance, power and recovery with your technical and clinical teams. The package describes a technology and operating scope; the proposal must identify the hardware and carrier responsibilities needed to run it.","url":"https://mansoq.com/faq#faq-teleicu-equipment"},{"id":"teleicu-value","question":"What practical benefit should a TeleICU team expect?","answer":"The intended benefit is clearer consultation documentation, more consistent handover and a visible agreed follow-up path. Accepted connected feeds can reduce repeated information collection; named operational follow-through can make unresolved technical tasks easier to track. Measure these changes against your own baseline. Clinical outcomes depend on your clinicians, protocols, data quality and delivery context.","url":"https://mansoq.com/faq#faq-teleicu-value"},{"id":"teleicu-rcm-raas","question":"How is RCM RaaS priced for TeleICU?","answer":"Essential: 18%; Premium: 15%; Diamond: 10%; Enterprise: 4.5%–7.5%. These percentages apply to approved eligible cleared collections, additional to the package subscription. Enterprise needs an approved exact rate within the range and an accepted scope. Actual fees are calculated from reviewed financial evidence after agreed refunds and exclusions; estimated collections in the builder do not create an invoice.","url":"https://mansoq.com/faq#faq-teleicu-rcm-raas"},{"id":"teleicu-prices","question":"What are the published TeleICU prices?","answer":"Essential: SAR 6,500.00 per month, comprising SAR 4,500.00 software + SAR 2,000.00 managed services. Includes 50 commissioned ICU beds and one site.\n\nPremium: SAR 12,500.00 per month, comprising SAR 8,500.00 software + SAR 4,000.00 managed services. Includes 150 commissioned ICU beds and one site.\n\nDiamond: SAR 22,000.00 per month, comprising SAR 14,000.00 software + SAR 8,000.00 managed services. Includes 250 commissioned ICU beds and one site.\n\nEnterprise: Price and actual operating scope are determined by the sales quotation.\n\nAll public amounts are before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Additions and third-party costs are separately scoped. An unapproved price is not a public offer.","href":"/pricing#care-packages","url":"https://mansoq.com/faq#faq-teleicu-prices"},{"id":"teleicu-tier-benefits","question":"What changes between the TeleICU plans?","answer":"Essential: Complete the care workflow. Consult-led remote ICU workflow: secure consultation, manual/charted data, handoff, escalation and downtime procedures.\n\nPremium: Reduce repeat work and find exceptions sooner. Consult-led remote ICU workflow: secure consultation, manual/charted data, handoff, escalation and downtime procedures. Two accepted data interfaces, such as ADT/EHR and monitor feeds; freshness / disconnect controls and specialist workflow optimization.\n\nDiamond: Give agreed operational queues an accountable owner. Consult-led remote ICU workflow: secure consultation, manual/charted data, handoff, escalation and downtime procedures. Two accepted data interfaces, such as ADT/EHR and monitor feeds; freshness / disconnect controls and specialist workflow optimization. Four accepted interfaces, such as ADT, monitor, ventilator and laboratory; named technical workflow owner and review of exceptions. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nEnterprise: Govern care and operations across the organization. Consult-led remote ICU workflow: secure consultation, manual/charted data, handoff, escalation and downtime procedures. Two accepted data interfaces, such as ADT/EHR and monitor feeds; freshness / disconnect controls and specialist workflow optimization. Four accepted interfaces, such as ADT, monitor, ventilator and laboratory; named technical workflow owner and review of exceptions. Group governance, entity-specific permissions, consolidated reporting, agreed integrations and dedicated operating scope. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nHigher tiers retain the contracted care foundation. Capacity, managed-hour and interface allowances are separate; the accepted proposal determines the live scope.","url":"https://mansoq.com/faq#faq-teleicu-tier-benefits"},{"id":"teleicu-care-workflow-example","question":"TeleICU: How does the core care workflow work, and what is the benefit?","answer":"What it means: A shared record for your remote ICU consultations, care plans and clinical handovers.\n\nHow it works: Your licensed team records the consultation, documents decisions and assigns follow-up to the responsible clinician. Authorised colleagues can see the same care record.\n\nOne example: A remote intensivist documents a consultation for a patient in bed 12. The bedside team reads the plan and records the agreed follow-up.\n\nYour benefit & expected result: A clearer handover and less searching for the latest plan. Your clinicians remain responsible for treatment and escalation.","url":"https://mansoq.com/faq#faq-teleicu-care-workflow-example"},{"id":"teleicu-automation-example","question":"TeleICU: How does automation work in this care setting?","answer":"What it means: Bring agreed ICU data sources into the care workflow so authorised teams can review information together.\n\nHow it works: Agree the source system and data fields, connect and test the interface, and define who follows up when information is missing or a connection needs attention.\n\nOne example: An accepted hospital interface sends lab results into the ICU workflow. A missing result appears in an agreed follow-up queue for the responsible team.\n\nYour benefit & expected result: Less manual transfer and clearer visibility of missing information. Clinical interpretation and escalation stay with your licensed team.\n\nIncluded scope: Sources, devices and refresh frequency require interface acceptance. This feature does not supply continuous clinical alarm surveillance.","url":"https://mansoq.com/faq#faq-teleicu-automation-example"},{"id":"teleicu-named-owner-example","question":"TeleICU: What does the named owner do in this care setting?","answer":"What it means: A named MANSOQ operations contact is accountable for following through on your agreed non-clinical work queues.\n\nHow it works: Agree the queue, actions and escalation route. The owner reviews outstanding work, coordinates with your team and records progress within the included managed-hours allowance.\n\nOne example: An agreed ICU documentation task is still incomplete. The owner follows up with the responsible team and records its status; your clinicians make the clinical decisions.\n\nYour benefit & expected result: Clearer responsibility and fewer hand-offs between contacts, with a visible record of follow-up.\n\nIncluded scope: The owner operates within the agreed service window and hours. Full outsourced billing, unlimited queue work and clinical staffing require their own scope.","url":"https://mansoq.com/faq#faq-teleicu-named-owner-example"},{"id":"home-day","question":"How does the home-care workflow run from referral to follow-up?","answer":"Within the accepted scope, your team registers the patient, creates the agreed care plan, schedules visits, documents observations and medication information, and records follow-up and authorised family communication. Each visiting team can review the current plan and prior notes. The customer supplies the licensed clinicians and the clinical approval of that plan.","url":"https://mansoq.com/faq#faq-home-day"},{"id":"home-routing","question":"How do visit automation, rosters and route planning help?","answer":"Premium and above add agreed recurring-visit automation and route or roster optimisation. Define visit frequency, locations, team availability and exceptions. For example, a rescheduled visit remains visible in the work queue so the dispatcher can coordinate the next action. Actual travel, staffing availability and clinical priorities still need human judgement.","url":"https://mansoq.com/faq#faq-home-routing"},{"id":"family-access","question":"Can family members and caregivers see updates?","answer":"Patient and family access follows agreed identity, consent and role permissions. Define who is authorised, what information they may see and who manages access changes. Example: an approved caregiver can receive the agreed visit update, while other records remain restricted. External messages and branded apps may require separately scoped services and provider usage.","url":"https://mansoq.com/faq#faq-family-access"},{"id":"palliative-records","question":"What does the palliative-care scope cover?","answer":"The contracted workflow covers care plans, symptom and medication documentation, caregiver communication and family or bereavement-support records. It helps authorised teams keep the care context and follow-up together. The clinical organisation defines treatment, symptom management, escalation and family support delivery; the software does not prescribe care or replace licensed staff.","url":"https://mansoq.com/faq#faq-palliative-records"},{"id":"home-monitoring","question":"Is remote patient monitoring automatically included?","answer":"Connected monitoring workflows are optional and require an accepted device and interface scope. Agree what is measured, who reviews the information, its timing, clinical escalation and supplier costs. A patient record or video workflow alone is not continuous monitoring, and managed operational support does not supply a clinician to watch the feed.","url":"https://mansoq.com/faq#faq-home-monitoring"},{"id":"missed-home-visits","question":"How does Diamond help when visits or documentation need follow-up?","answer":"The named owner follows agreed dispatch, visit-exception and documentation queues within the managed-hours allowance. The owner coordinates with your dispatcher or clinical team, records outstanding actions and reviews continuity and capacity monthly. For example, an unfinished visit note can be assigned back to its responsible team instead of being left in an unowned backlog.","url":"https://mansoq.com/faq#faq-missed-home-visits"},{"id":"home-emergencies","question":"Who handles emergencies during a home or palliative-care episode?","answer":"The customer supplies the licensed clinical coverage and emergency or escalation pathway. Agree patient and caregiver instructions through your clinical governance and rehearse the escalation process. Messaging, reminders and non-clinical managed queues should not be treated as an emergency-response service.","url":"https://mansoq.com/faq#faq-home-emergencies"},{"id":"home_palliative-rcm-raas","question":"How is RCM RaaS priced for Home & Palliative Care?","answer":"Essential: 18%; Premium: 15%; Diamond: 10%; Enterprise: 4.5%–7.5%. These percentages apply to approved eligible cleared collections, additional to the package subscription. Enterprise needs an approved exact rate within the range and an accepted scope. Actual fees are calculated from reviewed financial evidence after agreed refunds and exclusions; estimated collections in the builder do not create an invoice.","url":"https://mansoq.com/faq#faq-home_palliative-rcm-raas"},{"id":"home_palliative-prices","question":"What are the published Home & Palliative Care prices?","answer":"Essential: SAR 1,990.00 per month, comprising SAR 990.00 software + SAR 1,000.00 managed services. Includes 50 active patients / month and one site.\n\nPremium: SAR 3,990.00 per month, comprising SAR 1,790.00 software + SAR 2,200.00 managed services. Includes 150 active patients / month and one site.\n\nDiamond: SAR 6,990.00 per month, comprising SAR 2,490.00 software + SAR 4,500.00 managed services. Includes 250 active patients / month and one site.\n\nEnterprise: Price and actual operating scope are determined by the sales quotation.\n\nAll public amounts are before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Additions and third-party costs are separately scoped. An unapproved price is not a public offer.","href":"/pricing#care-packages","url":"https://mansoq.com/faq#faq-home_palliative-prices"},{"id":"home_palliative-tier-benefits","question":"What changes between the Home & Palliative Care plans?","answer":"Essential: Complete the care workflow. Visits, care plans, symptom / medication documentation, caregiver communication and family / bereavement support records.\n\nPremium: Reduce repeat work and find exceptions sooner. Visits, care plans, symptom / medication documentation, caregiver communication and family / bereavement support records. Route and roster optimization, recurring visit automation, family updates and optional connected monitoring workflows.\n\nDiamond: Give agreed operational queues an accountable owner. Visits, care plans, symptom / medication documentation, caregiver communication and family / bereavement support records. Route and roster optimization, recurring visit automation, family updates and optional connected monitoring workflows. Named owner for dispatch and visit exceptions, documentation follow-up and monthly continuity / capacity review. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nEnterprise: Govern care and operations across the organization. Visits, care plans, symptom / medication documentation, caregiver communication and family / bereavement support records. Route and roster optimization, recurring visit automation, family updates and optional connected monitoring workflows. Named owner for dispatch and visit exceptions, documentation follow-up and monthly continuity / capacity review. Group governance, entity-specific permissions, consolidated reporting, agreed integrations and dedicated operating scope. Use your own PostgreSQL database and private S3-compatible storage, including customer cloud, Spaces or server-hosted storage. Migrations, clinical files, reports and background jobs use the accepted customer destination; credentials, network, backups and recovery are commissioned before go-live.\n\nHigher tiers retain the contracted care foundation. Capacity, managed-hour and interface allowances are separate; the accepted proposal determines the live scope.","url":"https://mansoq.com/faq#faq-home_palliative-tier-benefits"},{"id":"home_palliative-care-workflow-example","question":"Home & Palliative Care: How does the core care workflow work, and what is the benefit?","answer":"What it means: One care record for home visits, the agreed care plan, symptom and medication notes, and authorised family communication.\n\nHow it works: Your team schedules a visit, records what happened and updates the care plan. Family communication and follow-up are kept with the patient record, under the agreed access permissions.\n\nOne example: After a home visit, a nurse records symptom observations and the clinician updates the care plan. The next visiting team can review both before attending.\n\nYour benefit & expected result: Better continuity between visits and a clear record of what the care team and family have agreed.","url":"https://mansoq.com/faq#faq-home_palliative-care-workflow-example"},{"id":"home_palliative-automation-example","question":"Home & Palliative Care: How does automation work in this care setting?","answer":"What it means: Organise recurring visits and help dispatchers plan team schedules and travel routes.\n\nHow it works: Set the clinician-approved visit frequency, team availability and service area. The workflow prepares recurring visits and routing information for your dispatcher to review and confirm.\n\nOne example: A patient needs two visits each week. The recurring schedule creates those visits and the dispatcher groups nearby visits into an appropriate route.\n\nYour benefit & expected result: Less repeated scheduling and a clearer daily plan. Your team confirms clinical priority, staffing and the final route.","url":"https://mansoq.com/faq#faq-home_palliative-automation-example"},{"id":"home_palliative-named-owner-example","question":"Home & Palliative Care: What does the named owner do in this care setting?","answer":"What it means: A named MANSOQ operations contact is accountable for following through on your agreed non-clinical work queues.\n\nHow it works: Agree the queue, actions and escalation route. The owner reviews outstanding work, coordinates with your team and records progress within the included managed-hours allowance.\n\nOne example: A home visit needs rescheduling. The owner follows up with your dispatcher and tracks the agreed action until its operational status is clear.\n\nYour benefit & expected result: Clearer responsibility and fewer hand-offs between contacts, with a visible record of follow-up.\n\nIncluded scope: The owner operates within the agreed service window and hours. Full outsourced billing, unlimited queue work and clinical staffing require their own scope.","url":"https://mansoq.com/faq#faq-home_palliative-named-owner-example"},{"id":"managed-hours-definition","question":"What are managed hours actually used for?","answer":"They cover agreed configuration, specialist review and operational queue work. For example, a specialist may review an agreed exception list, adjust an accepted workflow and document the next actions. Define the queue, allowed actions, access, owner and expected output before work starts. Managed hours are not clinician shifts or unlimited outsourcing.","url":"https://mansoq.com/faq#faq-managed-hours-definition"},{"id":"managed-hours-tracking","question":"How are managed hours recorded?","answer":"The routine service terms record work in 15-minute increments. Preparation for a review counts as well as the review itself. Agree the task record and usage report so your organisation can understand what was done and what remains. Example: preparing an exception review and discussing its actions both use the agreed allowance.","url":"https://mansoq.com/faq#faq-managed-hours-tracking"},{"id":"unused-hours","question":"Do unused managed hours roll into the next month?","answer":"The published routine service terms provide no rollover unless separately agreed. Plan priorities and review dates with the responsible team so the monthly allowance is used for useful work. If your workload is seasonal, ask for a written arrangement; do not assume unused hours create an unlimited future balance.","url":"https://mansoq.com/faq#faq-unused-hours"},{"id":"extra-hour-approval","question":"What happens when the managed-hours allowance is nearly used?","answer":"Routine terms call for notifications at 80% and 100% of the allowance and approval before extra work. Decide whether to reprioritise, add approved hours or change the service scope. Clinical and critical support responsibilities follow their own accepted arrangements; care-unit capacity and interface allowances do not increase just because extra hours are purchased.","url":"https://mansoq.com/faq#faq-extra-hour-approval"},{"id":"service-window","question":"When are routine managed operations available?","answer":"The published routine window is Sunday to Thursday, 08:00–18:00 Arabia Standard Time, excluding agreed holidays. Agree scheduling, contacts and any special coverage in the proposal. This operational window is distinct from application availability, your clinical coverage and separately commissioned critical technical incident cover.","url":"https://mansoq.com/faq#faq-service-window"},{"id":"support-vs-managed","question":"What is the difference between product support and managed operations?","answer":"Product support addresses the accepted product and technical incidents. Managed operations are the agreed ongoing configuration, review and queue work. The routine package terms state that product defects and critical support do not consume the managed-hours allowance. Contact routes, severity, coverage and response commitments must be defined in the accepted support agreement.","url":"https://mansoq.com/faq#faq-support-vs-managed"},{"id":"named-owner-accountability","question":"Does a named operations owner do all our work for us?","answer":"The owner is accountable for follow-through on the agreed queues within the accepted hours, permissions and service window. Your team still supplies the required evidence, approvals and clinical decisions. Full outsourced billing or a larger operational team requires a separate scope. The benefit is clearer responsibility and recorded next actions for the work you have agreed.","url":"https://mansoq.com/faq#faq-named-owner-accountability"},{"id":"queue-ownership-example","question":"What does an operational exception queue look like in practice?","answer":"It is a visible list of work needing attention, with an owner, reason, next action and status. Example: a visit is complete but billing documentation is missing. The responsible team receives a follow-up task and records progress. Automation helps identify the exception; it does not invent missing evidence or approve a payer decision.","url":"https://mansoq.com/faq#faq-queue-ownership-example"},{"id":"monthly-review-results","question":"What should a monthly performance and capacity review produce?","answer":"Agree the measures in advance: capacity use, overdue work, repeated exceptions and any relevant care or revenue-cycle measures. The owner reviews the accepted data with your team and records priorities, actions, responsible people and approved capacity changes. Preparation uses managed hours. The useful result is an actionable follow-up plan, not a guaranteed improvement percentage.","url":"https://mansoq.com/faq#faq-monthly-review-results"},{"id":"clinical-staffing-responsibility","question":"Who remains responsible for treatment, prescriptions and clinical decisions?","answer":"The customer supplies licensed clinicians, treatment decisions, clinical escalation and medical governance. MANSOQ supplies the contracted technology and non-clinical operations. An automated task, dashboard or operations owner can support coordination but cannot substitute for your clinician approval, clinical protocol or staffing arrangement.","url":"https://mansoq.com/faq#faq-clinical-staffing-responsibility"},{"id":"current-managed-hour-allowances","question":"How many managed hours are included for every product and plan?","answer":"Clinics: Essential 2 hours/month; Premium 6 hours/month; Diamond 12 hours/month; Enterprise agreed with sales\n\nPolyclinics: Essential 4 hours/month; Premium 12 hours/month; Diamond 24 hours/month; Enterprise agreed with sales\n\nTeleICU: Essential 4 hours/month; Premium 12 hours/month; Diamond 24 hours/month; Enterprise agreed with sales\n\nHome & Palliative Care: Essential 4 hours/month; Premium 12 hours/month; Diamond 24 hours/month; Enterprise agreed with sales\n\nThe allowance is for agreed non-clinical work, not staffing shifts. Review preparation counts; additional care units and sites do not increase hours.","url":"https://mansoq.com/faq#faq-current-managed-hour-allowances"},{"id":"rcm-raas-benefit","question":"What does RCM RaaS do for our team?","answer":"RCM RaaS assigns the agreed non-clinical revenue queues to an accountable operating team: eligibility and authorisation follow-up, claim preparation and submission, rejected claims, denial follow-up and remittance reconciliation. Agree the supported payers, entities, volumes, service window and approvals. Your clinicians remain responsible for clinical evidence and decisions; your finance team retains approval of sensitive financial changes.","url":"https://mansoq.com/faq#faq-rcm-raas-benefit"},{"id":"rcm-raas-additional","question":"Is the RaaS percentage additional to the subscription?","answer":"Yes. The approved collection fee is additional to the package’s software and managed-operations subscription. The proposal separates fixed subscription fees from collection-based fees. Define which work belongs to the package’s included hours and which belongs to the RaaS scope. Selecting RaaS requests the service; it does not authorise automatic charges or establish an accepted operating scope.","url":"https://mansoq.com/faq#faq-rcm-raas-additional"},{"id":"rcm-raas-collection-basis","question":"What collection amount is used for the RaaS fee?","answer":"Actual billing uses eligible bank-cleared collections for the agreed period, less documented refunds and agreed exclusions or adjustments. It does not use the face value of submitted claims, unpaid invoices or a customer-entered planning estimate. Reconcile remittances and financial evidence with your finance sponsor, record the excluded amount and obtain independent fee review. The contract defines which entities, payers and receipts are eligible.","url":"https://mansoq.com/faq#faq-rcm-raas-collection-basis"},{"id":"rcm-raas-yearly","question":"Does yearly prepayment discount the RaaS collection fee?","answer":"No. The annual software discount applies only to the eligible base software subscription. The collection fee is calculated separately for the agreed collection period using the approved contract rate. The builder’s RaaS estimate remains separate from the fixed monthly and annual subscription amounts; it is neither a prepaid collection fee nor a guaranteed invoice.","url":"https://mansoq.com/faq#faq-rcm-raas-yearly"},{"id":"rcm-raas-outcomes","question":"Does RCM RaaS guarantee payment, unlimited workload or clinical staffing?","answer":"The service provides defined operational responsibility and transparent collection-based billing. Agree workload, staffing, coverage, queue ownership, approvals and performance reporting in the signed scope. Payer payment and denial outcomes depend on evidence and payer decisions. Customer clinicians supply care decisions and clinical documentation. A published fee percentage alone does not commission unrestricted volumes, staffing or 24/7 coverage.","url":"https://mansoq.com/faq#faq-rcm-raas-outcomes"},{"id":"interface-meaning","question":"What is a maintained external interface?","answer":"It is an agreed connection exchanging specified data with a named external system, within the published plan allowance. Define the source, destination, format, mapping, timing, permissions, tests and maintenance responsibility. Example: an accepted admission feed updates the agreed patient or bed context. Building a bespoke connector and paying the supplier are separately scoped.","url":"https://mansoq.com/faq#faq-interface-meaning"},{"id":"interface-counting","question":"How is an interface counted and what if one system sends several feeds?","answer":"The accepted interface specification determines the count. A single supplier name does not automatically make all its feeds one interface, and one feed should not be split into arbitrary charges without a defined scope. Agree each data domain, direction, endpoint, acceptance test and maintenance obligation before approving the proposal.","url":"https://mansoq.com/faq#faq-interface-counting"},{"id":"national-connectors","question":"Do NPHIES and ZATCA consume the standard external-interface allowance?","answer":"The published service terms exclude applicable national foundation connectors from the standard maintained external-interface allowance. Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance. Bespoke additions, external vendor work and charges are separately reviewed.","url":"https://mansoq.com/faq#faq-national-connectors"},{"id":"nphies-live-readiness","question":"Does a package label mean NPHIES is immediately ready to use?","answer":"A named capability is not proof of an accepted production connection. Confirm the exact release, facility and payer scope, authorised credentials, onboarding, mappings and accepted tests. Eligibility, authorisation, claims and payer responses are separate workflow steps. Your team supplies the relevant source permissions and correct clinical and billing evidence.","href":"/saudi","url":"https://mansoq.com/faq#faq-nphies-live-readiness"},{"id":"zatca-coding","question":"What should we confirm for ZATCA, SBS and other coding requirements?","answer":"Agree the applicable invoicing and coding scope, current licensed catalogues, service mapping, authorised credentials and production acceptance. National e-invoicing, insurance service mapping and any grouping requirements have distinct setup needs. Review the Saudi and implementation references with your responsible finance and technical teams; do not infer certification from a marketing name.","href":"/saudi","url":"https://mansoq.com/faq#faq-zatca-coding"},{"id":"keep-existing-system","question":"Can we keep our existing EHR or finance system?","answer":"Discuss an add-to-existing-system model, a full migration or a phased transition. Define which system owns each record and how accepted data passes between them. Existing-system permissions, exports, vendor cooperation and tested mappings are needed. A FHIR clinical extract alone may not include schedules, claims, balances or attachments.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-keep-existing-system"},{"id":"integration-failure","question":"What happens when an external system or connection fails?","answer":"The accepted connection scope should define detection, ownership, retry or reconciliation rules, downtime work and escalation. Record failed or delayed exchanges so the responsible team can verify what reached the destination. Example: a delayed laboratory feed is investigated and reconciled rather than treated as a complete result transfer. Supplier incidents follow the agreed responsibility boundary.","url":"https://mansoq.com/faq#faq-integration-failure"},{"id":"all-vendors","question":"Can we assume that every device or third-party system is already supported?","answer":"Confirm the exact vendor, product and installed release against the accepted connection scope. A generic integration capability is not an already commissioned adapter for every model. Supply interface documentation and authorised access, agree the mapping and test cohort, and accept both successful and failed exchange scenarios before live use.","url":"https://mansoq.com/faq#faq-all-vendors"},{"id":"current-interface-allowances","question":"How many maintained interfaces are included in each plan?","answer":"Clinics: Essential 0 interfaces; Premium 1 interfaces; Diamond 2 interfaces; Enterprise agreed with sales\n\nPolyclinics: Essential 0 interfaces; Premium 2 interfaces; Diamond 4 interfaces; Enterprise agreed with sales\n\nTeleICU: Essential device interfaces scoped in the proposal; Premium 2 interfaces; Diamond 4 interfaces; Enterprise agreed with sales\n\nHome & Palliative Care: Essential 0 interfaces; Premium 1 interfaces; Diamond 3 interfaces; Enterprise agreed with sales\n\nThese are agreed standard external connections. Applicable national foundation connectors are separate. Each connection must be commissioned; vendor fees and bespoke build work are separately scoped.","url":"https://mansoq.com/faq#faq-current-interface-allowances"},{"id":"own-storage-plans","question":"Which plans let us use our own database and file storage?","answer":"Diamond and Enterprise offer this optional deployment choice. Your organisation provides an accepted dedicated PostgreSQL database and private S3-compatible file storage. Infrastructure, connection work and any migration are scoped separately. Essential and Premium do not include this deployment option in the published care-package scope.","url":"https://mansoq.com/faq#faq-own-storage-plans"},{"id":"storage-included-optional","question":"Do Diamond and Enterprise require us to host the data ourselves?","answer":"Customer-owned storage is an option, not a mandatory purchase. Choose the accepted MANSOQ-managed deployment or propose your own destination, then confirm the hosting and recovery terms. Your own infrastructure can provide more direct control over location and access, but it also needs agreed administration, monitoring, backup and incident responsibilities.","url":"https://mansoq.com/faq#faq-storage-included-optional"},{"id":"supported-storage-types","question":"Can we use our cloud, DigitalOcean Spaces or a server in our facility?","answer":"The supported customer destination is a dedicated PostgreSQL database plus private S3-compatible object storage, such as AWS S3, DigitalOcean Spaces or MinIO on a customer server. A plain shared folder or an arbitrary database type is not interchangeable with that accepted interface. Confirm your region, connectivity, certificates, permissions and backup design before commissioning.","url":"https://mansoq.com/faq#faq-supported-storage-types"},{"id":"storage-live-app","question":"Does customer-owned storage apply only during setup or also to the live system?","answer":"After the connection is accepted, the clinical runtime uses the approved customer database and private file destination. The scope includes native database migrations, clinical files, facility and report files, clinical imports, reports and background jobs that use that runtime. The selected destination is an operating deployment choice, not just a configuration label.","url":"https://mansoq.com/faq#faq-storage-live-app"},{"id":"storage-connection-acceptance","question":"What must happen before our own database and storage can go live?","answer":"Provide the authorised destination and scoped service credentials, then accept network access, certificate validation, database and file operations, migration readiness, backups and recovery. Agree owners and incident contacts. A selected checkbox or submitted address does not establish a live accepted connection; commissioning verifies the destination before clinical use.","url":"https://mansoq.com/faq#faq-storage-connection-acceptance"},{"id":"storage-unavailable","question":"What happens if our customer-owned database or storage is unavailable?","answer":"The clinical runtime does not automatically fall back to a MANSOQ database or bucket. An affected operation reports a connection or storage problem rather than silently placing clinical data elsewhere. Use the accepted downtime and escalation process, restore the destination and reconcile affected work. Agree recovery and clinical continuity responsibilities before launch.","url":"https://mansoq.com/faq#faq-storage-unavailable"},{"id":"storage-infrastructure-cost","question":"Who pays for and administers our cloud or server?","answer":"Customer infrastructure and its connection or migration work are separately scoped. The agreement should name who pays the provider and who manages database maintenance, storage, capacity, certificates, networking, backups and monitoring. Owning the account alone does not transfer those operating responsibilities to MANSOQ or make the infrastructure charge part of the card price.","url":"https://mansoq.com/faq#faq-storage-infrastructure-cost"},{"id":"storage-move-later","question":"Can we move an existing live system to our own storage later?","answer":"Treat the move as an agreed migration, not a live checkbox change. Inventory the database and files, prepare the new destination, map and reconcile records, rehearse cutover and recovery, and accept the final switch. Agree downtime, ownership and rollback so the move does not split the live clinical record between unapproved destinations.","url":"https://mansoq.com/faq#faq-storage-move-later"},{"id":"data-location","question":"Can we require a particular country or region for hosting?","answer":"State the required location in the proposal and data agreement. Confirm the agreed data domains, files, backups and external provider flows separately. Your own destination gives direct control over its location; it does not by itself confirm the location of every connected service. The accepted deployment and data terms should describe the complete boundary.","url":"https://mansoq.com/faq#faq-data-location"},{"id":"security-certification","question":"Do these packages automatically establish security certification or regulatory approval?","answer":"Package names and security features are not certification evidence. Review the actual release, controls, data agreement, deployment, supplier responsibilities and accepted tests with your organisation. Any certification or approval claim needs its own current evidence for the relevant scope. The proposal should identify required assurance documents rather than assume them from the tier.","url":"https://mansoq.com/faq#faq-security-certification"},{"id":"backup-recovery-objectives","question":"Are backups enough, and what do recovery time and recovery point mean?","answer":"A backup must be restorable and accepted for your deployment. A recovery-time objective describes the target time to restore service; a recovery-point objective describes how much recent data loss the agreed design aims to limit. Agree the targets, schedule, retention, owners and restore tests. The public cards do not promise a universal recovery time or zero data loss.","url":"https://mansoq.com/faq#faq-backup-recovery-objectives"},{"id":"data-contract-retention","question":"Who owns the records and decides retention or deletion?","answer":"The data agreement must define the organisation’s rights and responsibilities, authorised processing, access, export, retention and deletion. Customer-owned infrastructure adds control over the accepted destination; it does not replace those terms. Ask for the agreed clinical and service-data retention boundaries before onboarding real records.","url":"https://mansoq.com/faq#faq-data-contract-retention"},{"id":"launch-sequence","question":"What is the complete implementation sequence?","answer":"Agree the products, release, facilities, data boundary and responsibilities. Prepare account and foundation setup, product configuration and authorised imports. Accept interfaces, reconcile migration records and balances, train users, rehearse normal and failed workflows, and approve downtime, recovery and cutover. Then hand over monitoring and the accepted support arrangements.","href":"/resources/implementation","url":"https://mansoq.com/faq#faq-launch-sequence"},{"id":"launch-timeline","question":"How long does implementation take?","answer":"The delivery plan depends on the source data, interfaces, sites, infrastructure, training and acceptance work. Sales and delivery agree milestones and owners after scoping those inputs. A card price does not promise a fixed launch date. A phased rollout can start with an agreed pilot site and expand after its readiness checks are accepted.","url":"https://mansoq.com/faq#faq-launch-timeline"},{"id":"customer-launch-inputs","question":"What do we need to provide before setup starts?","answer":"Provide the responsible project and clinical owners, facilities and roles, service and tariff catalogues, clinician schedules, authorised source-system extracts and interface information. If using your storage, also provide the agreed infrastructure and scoped service access. Keep real credentials out of public enquiries; use the agreed secure commissioning process.","url":"https://mansoq.com/faq#faq-customer-launch-inputs"},{"id":"imports-templates","question":"What can we import and how are imports checked?","answer":"The implementation guide provides templates, examples and field dictionaries for selected foundation and product data, including departments, users, roles, services, doctors, schedules, assets and stock. Validate field formats and references, preview errors, and reconcile accepted records before committing an import. Not every spreadsheet is a ready-to-load migration file.","href":"/resources/implementation#templates","url":"https://mansoq.com/faq#faq-imports-templates"},{"id":"migration-quality","question":"How do we know a migration is complete and correct?","answer":"Accept the data domains and mappings before transfer, preserve source identifiers, and reconcile records, financial balances, attachments and relationships separately. Use an agreed test cohort and investigate exceptions. A successful upload alone is not acceptance of a complete clinical and financial migration; the authorised owners sign off the agreed evidence.","url":"https://mansoq.com/faq#faq-migration-quality"},{"id":"legacy-history","question":"Can we keep old records as an archive instead of migrating every field?","answer":"A governed history archive can be considered as part of the transition scope. Agree which history must be active, which remains in an authorised archive and how users locate and access it. Preserve provenance and identifiers. The proposal must define retention, search or access needs and responsibility; an archive is not automatically a fully editable live patient record.","href":"/resources/migration-integration","url":"https://mansoq.com/faq#faq-legacy-history"},{"id":"training","question":"What training and onboarding should we agree?","answer":"Agree user groups, workflows, trainers, materials and evidence that the responsible users can complete their accepted duties. Baseline onboarding and an agreed migration specification are part of the package foundation; delivery days, travel and on-site training are separately scoped. Training should include exceptions, access limits and downtime procedures as well as normal screens.","url":"https://mansoq.com/faq#faq-training"},{"id":"production-readiness","question":"Does choosing a package mean we can immediately use it for real patients?","answer":"A commercial selection is not clinical go-live acceptance. Confirm the deployed release and accepted capabilities, roles, migration, interfaces, training, clinical governance and support. Rehearse downtime and escalation, then approve the launch evidence. Planned capabilities or uncommissioned connections must not be assumed operational merely because they appear in a proposal.","url":"https://mansoq.com/faq#faq-production-readiness"},{"id":"pilot-and-phases","question":"Can we launch one branch or workflow first?","answer":"A staged implementation can reduce the amount of change your teams handle at once. Agree the pilot scope, data boundary, measures, acceptance gate and expansion plan. Example: accept the first branch’s access, migration and billing workflow before adding other branches. The schedule and cost of staged work are defined in the implementation proposal.","url":"https://mansoq.com/faq#faq-pilot-and-phases"},{"id":"cutover-and-rollback","question":"What is cutover and why should we rehearse rollback?","answer":"Cutover is the agreed switch from the old operating arrangement to the accepted new one. Rehearse the final data changes, reconciliation, permissions, downtime communications and recovery path before the date. A rollback plan defines how the authorised team responds if acceptance fails. This gives your organisation a clearer continuity decision at launch.","url":"https://mansoq.com/faq#faq-cutover-and-rollback"},{"id":"current-setup-budgets","question":"What setup and migration budgets are shown for each product?","answer":"Clinics: Essential SAR 1,500.00–SAR 3,000.00; Premium SAR 2,500.00–SAR 5,000.00; Diamond SAR 4,000.00–SAR 8,000.00; Enterprise agreed with sales\n\nPolyclinics: Essential SAR 5,000.00–SAR 10,000.00; Premium SAR 8,000.00–SAR 18,000.00; Diamond SAR 15,000.00–SAR 30,000.00; Enterprise agreed with sales\n\nTeleICU: Essential SAR 10,000.00–SAR 20,000.00; Premium SAR 20,000.00–SAR 50,000.00; Diamond SAR 40,000.00–SAR 100,000.00; Enterprise agreed with sales\n\nHome & Palliative Care: Essential SAR 3,000.00–SAR 6,000.00; Premium SAR 5,000.00–SAR 10,000.00; Diamond SAR 8,000.00–SAR 20,000.00; Enterprise agreed with sales\n\nThese ranges are before VAT and separate from the recurring total. The setup and migration budget range is indicative; the final price follows the statement of work.","url":"https://mansoq.com/faq#faq-current-setup-budgets"},{"id":"optional-vs-required","question":"What is required in every package and what is optional?","answer":"The contracted care workflow and required companions form the package foundation: patient context, documentation, orders and medication, billing, secure access, audit, backup and applicable national workflows. Optional services such as AI assistance, branding, equipment, extra interfaces and full outsourced RCM are selected and scoped separately. Your signed composition states what is actually included.","url":"https://mansoq.com/faq#faq-optional-vs-required"},{"id":"addon-checkbox-activation","question":"Does ticking an optional addition activate it or settle its price?","answer":"A selection records your interest in the proposed scope. It does not commission a device, create an accepted integration, approve a supplier or finalise bespoke pricing. The team reviews compatibility, dependencies, responsibilities and usage, then quotes and accepts the service. Only the accepted deployment and entitlements determine what goes live.","url":"https://mansoq.com/faq#faq-addon-checkbox-activation"},{"id":"package_ai_scribe-benefit","question":"How does the \"AI documentation assistant\" addition work?","answer":"Opt-in; clinician review, consent, intended-use and supplier review required.\n\nAn accepted documentation assistant can help prepare text for clinician review. Define intended use, consent, supplier handling and the human approval step; it does not replace clinical judgement or make every generated statement correct.\n\nOne example: A clinician reviews and corrects an assisted draft before accepting the note.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_ai_scribe-benefit"},{"id":"package_branded_app-benefit","question":"How does the \"Branded patient / family app\" addition work?","answer":"Branding, distribution and app maintenance scoped separately.\n\nAn agreed branded patient or family experience can make the service easier to recognise and access. Define supported workflows, identity and access, distribution, maintenance and ownership in the separate scope.\n\nOne example: Authorised users see the organisation’s agreed branding when accessing the accepted patient workflow.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_branded_app-benefit"},{"id":"package_bespoke_interfaces-benefit","question":"How does the \"Additional or bespoke interfaces\" addition work?","answer":"Each connector has an acceptance specification and supplier cost.\n\nConnect a needed external workflow beyond the standard allowance or connector scope. Agree source data, mapping, testing, maintenance, dependencies and vendor fees before development or commissioning.\n\nOne example: A finance-system exchange is defined with its required fields and reconciliation tests.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_bespoke_interfaces-benefit"},{"id":"package_equipment-benefit","question":"How does the \"Devices, telepresence & connectivity\" addition work?","answer":"Customer-owned devices or separately quoted hardware, carrier and vendor fees.\n\nThe right accepted equipment and connectivity support the selected workflow. Confirm compatibility, supply, installation, network capacity, maintenance and incident ownership rather than assuming the subscription includes hardware.\n\nOne example: A remote ICU workflow uses customer-provided telepresence equipment accepted during setup.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_equipment-benefit"},{"id":"package_onsite_training-benefit","question":"How does the \"On-site training\" addition work?","answer":"Travel, delivery days and attendance agreed in advance.\n\nHands-on role training can help users practise the accepted workflow with an instructor present. Agree delivery days, attendance, travel, materials and competence checks before scheduling.\n\nOne example: Reception and billing users rehearse registration, billing exceptions and the agreed downtime process.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_onsite_training-benefit"},{"id":"package_dedicated_hosting-benefit","question":"How does the \"Dedicated hosting & continuity design\" addition work?","answer":"Architecture, recovery objectives and infrastructure require an Enterprise proposal.\n\nA separately designed deployment and continuity arrangement can address organisational architecture and recovery needs. It requires an Enterprise proposal defining application infrastructure, operations and recovery objectives. Diamond’s own-database option alone does not establish a dedicated deployment of every application component.\n\nOne example: An Enterprise group agrees its application deployment, incident coverage and tested recovery targets.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_dedicated_hosting-benefit"},{"id":"package_full_rcm-benefit","question":"How does the \"RCM RaaS managed revenue service\" addition work?","answer":"The selected plan’s configured percentage of eligible cleared collections, additional to the package subscription. Enterprise requires an approved exact rate within its configured range and an accepted operating scope.\n\nRCM RaaS takes the agreed operational responsibility for revenue worklists beyond the package’s managed-hours allowance. Its plan-specific percentage is additional to the subscription, on reviewed eligible cleared collections after agreed refunds and exclusions. Approve the queues, authority, evidence and reporting before activation. Enterprise needs an approved exact rate within the configured range.\n\nOne example: A defined claims follow-up service reports agreed actions and collections under the accepted contract.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_full_rcm-benefit"},{"id":"package_messages-benefit","question":"How does the \"Messaging & video usage\" addition work?","answer":"Third-party usage budget and consent agreed; no unlimited carrier charges.\n\nAccepted external messaging and video can support reminders, consultations and authorised updates. Agree the supplier, patient consent, data flow, usage budget and charges. A software communication workflow does not include unlimited carrier or video-provider usage.\n\nOne example: Agreed appointment reminders use an approved provider within the accepted message budget.\n\nSelection expresses a request; price, compatibility and acceptance are confirmed in the proposal.","url":"https://mansoq.com/faq#faq-package_messages-benefit"},{"id":"builder-open","question":"How do I open the tailored platform builder?","answer":"Select Build your tailored platform beside the package heading or in the page introduction. The packages hide and the builder appears on the same page. Choose a facility, care and services, review the plan and enter your request details. This keeps the package comparison and the detailed configuration as two clear views.","url":"https://mansoq.com/faq#faq-builder-open"},{"id":"builder-back","question":"Can I return to packages without losing my builder progress?","answer":"Use Back to packages. The builder hides and the packages return. Reopening the builder in the same page session preserves its current choices and step. Browser Back and Forward also follow the view switch. Changing the selected starting package intentionally loads that package’s scope, so review your capacity and additions after a new package choice.","url":"https://mansoq.com/faq#faq-builder-back"},{"id":"choose-package-entry","question":"What happens when I select Choose Essential, Premium or Diamond?","answer":"The selected care product and starting package open in the builder so you can review their included services, capacity and optional additions. You can keep the package or tailor the proposed scope. Enterprise’s Request a sales call instead starts a proposal enquiry with its product and package context; it does not expose an unscoped public price.","url":"https://mansoq.com/faq#faq-choose-package-entry"},{"id":"builder-four-steps","question":"What happens in each of the four builder steps?","answer":"Your facility identifies the care setting. Care & services selects the operating model, package or own plan, modules and required scale. Review your plan shows the proposed composition and commercial breakdown. Your details captures the request and consent. Review every step before submitting; a quote request is not a live clinical deployment.","url":"https://mansoq.com/faq#faq-builder-four-steps"},{"id":"native-or-augment","question":"What is the difference between a complete care system and adding to my existing system?","answer":"A complete care system runs the accepted care and operations scope on MANSOQ. Adding to an existing system keeps the current system and connects the selected services through an accepted integration scope. Decide which system owns each record and what must be exchanged. The operating model can affect eligibility, interfaces, setup and final pricing.","url":"https://mansoq.com/faq#faq-native-or-augment"},{"id":"required-companions","question":"Why are some modules automatically selected or not removable?","answer":"Some services depend on shared patient identity, clinical documentation, orders, billing, access or other required companions. The builder includes those dependencies so the proposed workflow can be reviewed as a complete scope. An automatically included dependency is not an arbitrary extra; review the itemised scope and accepted operating model if it is unclear.","url":"https://mansoq.com/faq#faq-required-companions"},{"id":"saved-plan-device","question":"Can I save or compare a proposed plan?","answer":"Where offered in the review flow, saving stores the proposed scope on the current browser or device so you can compare it later. It is not the same as submitting a request or reserving a price. Avoid putting patient data in a saved commercial scope. If the catalogue changes, review the updated scope and fees before relying on an older saved selection.","url":"https://mansoq.com/faq#faq-saved-plan-device"},{"id":"proposal-contents","question":"What should the final proposal contain?","answer":"It should state the care products, operating model, release, included modules, capacity, sites, recurring software and managed fees, setup and migration, interfaces, optional work, tax and third-party charges. It should also define responsibilities, data terms, milestones, acceptance, support commitments, payment and contract conditions. Enterprise needs a sales-defined price for that complete scope.","url":"https://mansoq.com/faq#faq-proposal-contents"},{"id":"trial-activation","question":"If a trial is available, when does it actually start?","answer":"A published duration is not activation. Trial eligibility and timing are confirmed with your team for the selected products and agreed evaluation scope before activation. The accepted activation and expiry dates govern the actual evaluation period.","url":"https://mansoq.com/faq#faq-trial-activation"},{"id":"demo-real-data","question":"Should we use real patient records in a demonstration or evaluation?","answer":"The guided evaluation acceptance process uses a synthetic-data scenario. Agree the test users, workflow, support and success criteria. Real-patient operation needs its own accepted data, clinical, security and launch arrangements. A demo can show a workflow and help validate fit without treating a preview or unaccepted connection as clinical production.","url":"https://mansoq.com/faq#faq-demo-real-data"},{"id":"current-trial-policy","question":"Do all MANSOQ plans have the same trial?","answer":"The currently published care packages do not include an automatic trial period. You can request a demonstration and discuss a separately accepted evaluation with the team. Do not assume a universal 14-day trial from another plan or an own-plan configuration. Any evaluation depends on scope, readiness, policy, synthetic data and an accepted activation date.","href":"/pricing#configuration","url":"https://mansoq.com/faq#faq-current-trial-policy"},{"id":"upgrades","question":"Can we upgrade when our organisation grows?","answer":"Discuss the new capacity, interfaces, managed workload, sites and data requirements with sales. Agree the effective date, revised fees, entitlements and any migration or setup work before changing the live scope. The builder helps compare a proposed starting package; it does not amend an existing customer contract by itself.","url":"https://mansoq.com/faq#faq-upgrades"},{"id":"downgrades","question":"What should we check before downgrading a plan?","answer":"Check whether the smaller plan can support your actual care capacity, maintained connections and operational work. Review any functions or deployment options that depend on Diamond or Enterprise. If you use customer-owned storage, do not assume a lower tier can keep that option; agree a supported deployment and migration plan. Contract timing and price changes follow the signed terms.","url":"https://mansoq.com/faq#faq-downgrades"},{"id":"change-products","question":"Can we add or remove products after launch?","answer":"Treat the change as a reviewed operating-scope update. Confirm dependencies, affected users and records, interfaces, care continuity and commercial impact. Adding a department can require configuration, training and acceptance; removing one can require a record-access or archive plan. Agree the change before altering live workflows.","url":"https://mansoq.com/faq#faq-change-products"},{"id":"renewal-cancellation-refund","question":"What are the renewal, cancellation and refund rules?","answer":"The signed quotation and agreement define those rules; the public package cards do not publish a universal notice period, refund entitlement or automatic renewal policy. Ask the team to specify term, notice, outstanding charges, annual prepayment treatment and any early-exit conditions before signing. Apply the accepted terms to your organisation’s case.","url":"https://mansoq.com/faq#faq-renewal-cancellation-refund"},{"id":"export-and-exit","question":"Can we obtain our records when leaving MANSOQ?","answer":"Backup and export are part of the package foundation, while the exit agreement defines the authorised export domains, format, files, timing, recipients and responsibilities. Agree clinical records, attachments, financial history and the agreed service records separately. Verify completeness and access before decommissioning the old service.","url":"https://mansoq.com/faq#faq-export-and-exit"},{"id":"exit-with-own-storage","question":"Does owning the database make exit or application migration automatic?","answer":"Owning the accepted infrastructure gives direct control over that destination. You still need an orderly application and data transition: supported exports, record and file relationships, identifiers, access, backup and any schema or interface mapping for the receiving system. Retention and service decommissioning follow the agreed data and exit terms.","url":"https://mansoq.com/faq#faq-exit-with-own-storage"},{"id":"scope-change-approval","question":"How should custom requests and scope changes be approved?","answer":"Describe the business need, affected workflow, owner, expected output and acceptance test. The proposal or change record should state delivery effort, price, responsibilities, dependencies and effect on the release or support scope. Do not treat a verbal idea or an optional checkbox as an accepted custom development commitment.","url":"https://mansoq.com/faq#faq-scope-change-approval"},{"id":"success-measurement","question":"How do we measure whether the platform is delivering value?","answer":"Agree a baseline and a small set of workflow measures before rollout, such as overdue operational tasks, handoff completeness, repeat entry, documentation completion and capacity use. Use consistent definitions and compare periods after users are trained. Track actions from the monthly review. Distinguish observed improvement from an illustrative benefit or an unverified revenue claim.","url":"https://mansoq.com/faq#faq-success-measurement"}],"faqTopics":[{"id":"start-here","title":"Start here","summary":"Understand the platform, who it serves and the next step.","answers":["https://mansoq.com/faq#faq-mansoq-overview","https://mansoq.com/faq#faq-which-organizations","https://mansoq.com/faq#faq-existing-software-coexistence","https://mansoq.com/faq#faq-product-vs-service","https://mansoq.com/faq#faq-request-a-demo","https://mansoq.com/faq#faq-english-arabic"]},{"id":"roles-access","title":"People, roles & access","summary":"Give every team the right access and clear responsibilities.","answers":["https://mansoq.com/faq#faq-which-user-roles","https://mansoq.com/faq#faq-multi-site-governance","https://mansoq.com/faq#faq-who-approves-clinical-records","https://mansoq.com/faq#faq-account-vs-clinical-access"]},{"id":"clinical-governance","title":"Clinical workflows & safe use","summary":"Understand workflow boundaries, human review and departmental scope.","answers":["https://mansoq.com/faq#faq-clinical-workflow-coverage","https://mansoq.com/faq#faq-department-vs-results","https://mansoq.com/faq#faq-medication-safety-workflow","https://mansoq.com/faq#faq-ai-clinical-review","https://mansoq.com/faq#faq-teleicu-responsibilities","https://mansoq.com/faq#faq-clinical-downtime"]},{"id":"migration-planning","title":"Migration & existing systems","summary":"Move or connect data with ownership, reconciliation and a clear cutover.","answers":["https://mansoq.com/faq#faq-migration-source-systems","https://mansoq.com/faq#faq-migration-data-domains","https://mansoq.com/faq#faq-migration-patient-matching","https://mansoq.com/faq#faq-migration-rehearsal","https://mansoq.com/faq#faq-migration-no-downtime","https://mansoq.com/faq#faq-historical-archive"]},{"id":"it-integrations","title":"IT, interfaces & technical setup","summary":"Plan technical dependencies and test the actual connection.","answers":["https://mansoq.com/faq#faq-integration-standards","https://mansoq.com/faq#faq-integration-scope-checklist","https://mansoq.com/faq#faq-national-activation","https://mansoq.com/faq#faq-identity-sso","https://mansoq.com/faq#faq-devices-network","https://mansoq.com/faq#faq-deployment-hosting-options","https://mansoq.com/faq#faq-integration-change-management"]},{"id":"privacy-governance","title":"Privacy, security & governance","summary":"Confirm controls, evidence and the responsibility for each data flow.","answers":["https://mansoq.com/faq#faq-security-evidence","https://mansoq.com/faq#faq-data-ownership-access","https://mansoq.com/faq#faq-data-location-subprocessors","https://mansoq.com/faq#faq-backup-recovery-evidence","https://mansoq.com/faq#faq-privacy-requests","https://mansoq.com/faq#faq-safe-support-information"]},{"id":"delivery-support","title":"Implementation, training & support","summary":"Prepare your team, accept the workflow and agree ongoing support.","answers":["https://mansoq.com/faq#faq-implementation-start-checklist","https://mansoq.com/faq#faq-implementation-timeline","https://mansoq.com/faq#faq-training-by-role","https://mansoq.com/faq#faq-go-live-acceptance","https://mansoq.com/faq#faq-support-hours-sla","https://mansoq.com/faq#faq-report-a-problem","https://mansoq.com/faq#faq-new-site-module"]},{"id":"procurement-partners","title":"Buying, procurement & partnerships","summary":"Build a reviewable scope and a clear commercial decision.","answers":["https://mansoq.com/faq#faq-procurement-information","https://mansoq.com/faq#faq-quotation-total-cost","https://mansoq.com/faq#faq-contract-before-activation","https://mansoq.com/faq#faq-roi-guarantees","https://mansoq.com/faq#faq-partner-implementation","https://mansoq.com/faq#faq-data-exit-portability"]},{"id":"patient-family-guide","title":"Patients, families & public enquiries","summary":"Find the right route for care, records and access questions.","answers":["https://mansoq.com/faq#faq-patient-medical-advice","https://mansoq.com/faq#faq-patient-portal-access","https://mansoq.com/faq#faq-family-proxy-consent","https://mansoq.com/faq#faq-patient-billing-insurance"]},{"id":"product-workflows","title":"Product & department workflow guide","summary":"Answers from published product handbooks covering tasks, handovers, connections and acceptance.","answers":["https://mansoq.com/faq#faq-module-core","https://mansoq.com/faq#faq-module-outpatient","https://mansoq.com/faq#faq-module-inpatient","https://mansoq.com/faq#faq-module-emergency","https://mansoq.com/faq#faq-module-teleicu","https://mansoq.com/faq#faq-module-home-palliative","https://mansoq.com/faq#faq-module-operating-room","https://mansoq.com/faq#faq-module-icu","https://mansoq.com/faq#faq-module-pharmacy","https://mansoq.com/faq#faq-module-laboratory","https://mansoq.com/faq#faq-module-radiology","https://mansoq.com/faq#faq-module-inventory","https://mansoq.com/faq#faq-module-clinical-documentation","https://mansoq.com/faq#faq-module-orders-medication","https://mansoq.com/faq#faq-module-patient-access","https://mansoq.com/faq#faq-module-billing-finance","https://mansoq.com/faq#faq-module-revenue-cycle","https://mansoq.com/faq#faq-module-sbs-specific","https://mansoq.com/faq#faq-module-sbs-full","https://mansoq.com/faq#faq-module-drg","https://mansoq.com/faq#faq-module-nphies","https://mansoq.com/faq#faq-module-zatca","https://mansoq.com/faq#faq-module-analytics","https://mansoq.com/faq#faq-module-ai","https://mansoq.com/faq#faq-module-interfaces","https://mansoq.com/faq#faq-module-network-governance","https://mansoq.com/faq#faq-module-managed-revenue"]},{"id":"choosing","title":"Choosing your platform & plan","summary":"Start with your care setting, team and operational needs.","answers":["https://mansoq.com/faq#faq-what-is-mansoq","https://mansoq.com/faq#faq-software-and-services","https://mansoq.com/faq#faq-four-care-products","https://mansoq.com/faq#faq-essential-fit","https://mansoq.com/faq#faq-premium-fit","https://mansoq.com/faq#faq-diamond-fit","https://mansoq.com/faq#faq-enterprise-fit","https://mansoq.com/faq#faq-same-safety-foundation","https://mansoq.com/faq#faq-choose-by-benefit","https://mansoq.com/faq#faq-mixed-care-group","https://mansoq.com/faq#faq-all-plan-foundation"]},{"id":"benefits","title":"Feature benefits, explained","summary":"Meaning, workflow, a concrete example and the expected result.","answers":["https://mansoq.com/faq#faq-feature-rcm-raas","https://mansoq.com/faq#faq-feature-patient-access","https://mansoq.com/faq#faq-feature-dashboards","https://mansoq.com/faq#faq-feature-monthly-review","https://mansoq.com/faq#faq-feature-entity-governance","https://mansoq.com/faq#faq-feature-group-reporting","https://mansoq.com/faq#faq-feature-custom-integrations","https://mansoq.com/faq#faq-feature-implementation","https://mansoq.com/faq#faq-feature-national-workflows","https://mansoq.com/faq#faq-feature-customer-storage"]},{"id":"pricing","title":"Prices, fees & purchasing","summary":"Understand the recurring price and the work quoted separately.","answers":["https://mansoq.com/faq#faq-package-price","https://mansoq.com/faq#faq-currency-tax","https://mansoq.com/faq#faq-enterprise-price-hidden","https://mansoq.com/faq#faq-annual-discount","https://mansoq.com/faq#faq-setup-separate","https://mansoq.com/faq#faq-third-party-costs","https://mansoq.com/faq#faq-avoid-surprise-fees","https://mansoq.com/faq#faq-monthly-contract","https://mansoq.com/faq#faq-request-no-payment","https://mansoq.com/faq#faq-regional-pricing","https://mansoq.com/faq#faq-clinics-extra-rates","https://mansoq.com/faq#faq-polyclinics-extra-rates","https://mansoq.com/faq#faq-teleicu-extra-rates","https://mansoq.com/faq#faq-home_palliative-extra-rates","https://mansoq.com/faq#faq-annual-price-worked-example","https://mansoq.com/faq#faq-extra-capacity-worked-example"]},{"id":"capacity","title":"Capacity, users & growth","summary":"Know what is counted and what changes as you grow.","answers":["https://mansoq.com/faq#faq-capacity-measures","https://mansoq.com/faq#faq-clinician-counting","https://mansoq.com/faq#faq-icu-counting","https://mansoq.com/faq#faq-home-patient-counting","https://mansoq.com/faq#faq-capacity-not-hours","https://mansoq.com/faq#faq-sites-definition","https://mansoq.com/faq#faq-growth-planning","https://mansoq.com/faq#faq-enterprise-reference-capacity","https://mansoq.com/faq#faq-current-capacity-ladder"]},{"id":"clinics","title":"Clinics: daily outpatient care","summary":"From appointments and consultation to billing and follow-up.","answers":["https://mansoq.com/faq#faq-clinic-day","https://mansoq.com/faq#faq-clinic-cash-insurance","https://mansoq.com/faq#faq-clinic-reminders","https://mansoq.com/faq#faq-clinic-departments","https://mansoq.com/faq#faq-clinics-rcm-raas","https://mansoq.com/faq#faq-clinics-prices","https://mansoq.com/faq#faq-clinics-tier-benefits","https://mansoq.com/faq#faq-clinics-care-workflow-example","https://mansoq.com/faq#faq-clinics-automation-example","https://mansoq.com/faq#faq-clinics-named-owner-example"]},{"id":"polyclinics","title":"Polyclinics: connected specialties","summary":"Coordinate departments around the same patient and service evidence.","answers":["https://mansoq.com/faq#faq-polyclinic-clinic-difference","https://mansoq.com/faq#faq-cross-specialty-access","https://mansoq.com/faq#faq-polyclinic-stock","https://mansoq.com/faq#faq-polyclinic-charge-leakage","https://mansoq.com/faq#faq-polyclinics-rcm-raas","https://mansoq.com/faq#faq-polyclinics-prices","https://mansoq.com/faq#faq-polyclinics-tier-benefits","https://mansoq.com/faq#faq-polyclinics-care-workflow-example","https://mansoq.com/faq#faq-polyclinics-automation-example","https://mansoq.com/faq#faq-polyclinics-named-owner-example"]},{"id":"teleicu","title":"TeleICU: remote critical-care workflows","summary":"Understand consultation, data connections and clinical responsibility.","answers":["https://mansoq.com/faq#faq-teleicu-team-model","https://mansoq.com/faq#faq-teleicu-essential-data","https://mansoq.com/faq#faq-teleicu-interface-examples","https://mansoq.com/faq#faq-teleicu-stale-data","https://mansoq.com/faq#faq-teleicu-alert-responsibility","https://mansoq.com/faq#faq-teleicu-equipment","https://mansoq.com/faq#faq-teleicu-value","https://mansoq.com/faq#faq-teleicu-rcm-raas","https://mansoq.com/faq#faq-teleicu-prices","https://mansoq.com/faq#faq-teleicu-tier-benefits","https://mansoq.com/faq#faq-teleicu-care-workflow-example","https://mansoq.com/faq#faq-teleicu-automation-example","https://mansoq.com/faq#faq-teleicu-named-owner-example"]},{"id":"home","title":"Home & Palliative Care: continuity","summary":"Coordinate visits, care plans and authorised family follow-up.","answers":["https://mansoq.com/faq#faq-home-day","https://mansoq.com/faq#faq-home-routing","https://mansoq.com/faq#faq-family-access","https://mansoq.com/faq#faq-palliative-records","https://mansoq.com/faq#faq-home-monitoring","https://mansoq.com/faq#faq-missed-home-visits","https://mansoq.com/faq#faq-home-emergencies","https://mansoq.com/faq#faq-home_palliative-rcm-raas","https://mansoq.com/faq#faq-home_palliative-prices","https://mansoq.com/faq#faq-home_palliative-tier-benefits","https://mansoq.com/faq#faq-home_palliative-care-workflow-example","https://mansoq.com/faq#faq-home_palliative-automation-example","https://mansoq.com/faq#faq-home_palliative-named-owner-example"]},{"id":"operations","title":"Managed operations & support","summary":"See who does the work, how hours are used and what support means.","answers":["https://mansoq.com/faq#faq-managed-hours-definition","https://mansoq.com/faq#faq-managed-hours-tracking","https://mansoq.com/faq#faq-unused-hours","https://mansoq.com/faq#faq-extra-hour-approval","https://mansoq.com/faq#faq-service-window","https://mansoq.com/faq#faq-support-vs-managed","https://mansoq.com/faq#faq-named-owner-accountability","https://mansoq.com/faq#faq-queue-ownership-example","https://mansoq.com/faq#faq-monthly-review-results","https://mansoq.com/faq#faq-clinical-staffing-responsibility","https://mansoq.com/faq#faq-current-managed-hour-allowances"]},{"id":"rcm-raas","title":"RCM RaaS: service & collection fees","summary":"Understand the managed revenue service, its fee base and approved billing.","answers":["https://mansoq.com/faq#faq-rcm-raas-benefit","https://mansoq.com/faq#faq-rcm-raas-additional","https://mansoq.com/faq#faq-rcm-raas-collection-basis","https://mansoq.com/faq#faq-rcm-raas-yearly","https://mansoq.com/faq#faq-rcm-raas-outcomes"]},{"id":"connections","title":"Integrations & national workflows","summary":"Distinguish an included workflow from an accepted live connection.","answers":["https://mansoq.com/faq#faq-interface-meaning","https://mansoq.com/faq#faq-interface-counting","https://mansoq.com/faq#faq-national-connectors","https://mansoq.com/faq#faq-nphies-live-readiness","https://mansoq.com/faq#faq-zatca-coding","https://mansoq.com/faq#faq-keep-existing-system","https://mansoq.com/faq#faq-integration-failure","https://mansoq.com/faq#faq-all-vendors","https://mansoq.com/faq#faq-current-interface-allowances"]},{"id":"storage","title":"Data protection, storage & recovery","summary":"Understand your storage choice and the responsibilities behind it.","answers":["https://mansoq.com/faq#faq-own-storage-plans","https://mansoq.com/faq#faq-storage-included-optional","https://mansoq.com/faq#faq-supported-storage-types","https://mansoq.com/faq#faq-storage-live-app","https://mansoq.com/faq#faq-storage-connection-acceptance","https://mansoq.com/faq#faq-storage-unavailable","https://mansoq.com/faq#faq-storage-infrastructure-cost","https://mansoq.com/faq#faq-storage-move-later","https://mansoq.com/faq#faq-data-location","https://mansoq.com/faq#faq-security-certification","https://mansoq.com/faq#faq-backup-recovery-objectives","https://mansoq.com/faq#faq-data-contract-retention"]},{"id":"implementation","title":"Setup, migration & go-live","summary":"Follow the path from agreed scope to an accepted operating service.","answers":["https://mansoq.com/faq#faq-launch-sequence","https://mansoq.com/faq#faq-launch-timeline","https://mansoq.com/faq#faq-customer-launch-inputs","https://mansoq.com/faq#faq-imports-templates","https://mansoq.com/faq#faq-migration-quality","https://mansoq.com/faq#faq-legacy-history","https://mansoq.com/faq#faq-training","https://mansoq.com/faq#faq-production-readiness","https://mansoq.com/faq#faq-pilot-and-phases","https://mansoq.com/faq#faq-cutover-and-rollback","https://mansoq.com/faq#faq-current-setup-budgets"]},{"id":"additions","title":"Optional additions & specialised services","summary":"Know why you might add a service and how its scope is agreed.","answers":["https://mansoq.com/faq#faq-optional-vs-required","https://mansoq.com/faq#faq-addon-checkbox-activation","https://mansoq.com/faq#faq-package_ai_scribe-benefit","https://mansoq.com/faq#faq-package_branded_app-benefit","https://mansoq.com/faq#faq-package_bespoke_interfaces-benefit","https://mansoq.com/faq#faq-package_equipment-benefit","https://mansoq.com/faq#faq-package_onsite_training-benefit","https://mansoq.com/faq#faq-package_dedicated_hosting-benefit","https://mansoq.com/faq#faq-package_full_rcm-benefit","https://mansoq.com/faq#faq-package_messages-benefit"]},{"id":"builder","title":"Builder, proposals & evaluation","summary":"Tailor the scope, review your choices and understand activation.","answers":["https://mansoq.com/faq#faq-builder-open","https://mansoq.com/faq#faq-builder-back","https://mansoq.com/faq#faq-choose-package-entry","https://mansoq.com/faq#faq-builder-four-steps","https://mansoq.com/faq#faq-native-or-augment","https://mansoq.com/faq#faq-required-companions","https://mansoq.com/faq#faq-saved-plan-device","https://mansoq.com/faq#faq-proposal-contents","https://mansoq.com/faq#faq-trial-activation","https://mansoq.com/faq#faq-demo-real-data","https://mansoq.com/faq#faq-current-trial-policy"]},{"id":"changes","title":"Changes, agreements & leaving","summary":"Plan growth, service changes and an orderly exit.","answers":["https://mansoq.com/faq#faq-upgrades","https://mansoq.com/faq#faq-downgrades","https://mansoq.com/faq#faq-change-products","https://mansoq.com/faq#faq-renewal-cancellation-refund","https://mansoq.com/faq#faq-export-and-exit","https://mansoq.com/faq#faq-exit-with-own-storage","https://mansoq.com/faq#faq-scope-change-approval","https://mansoq.com/faq#faq-success-measurement"]}]},"ar":{"url":"https://mansoq.com/faq?lang=ar","title":"الأسئلة الشائعة: الرعاية والتقنية والترحيل والأسعار | منسوق","eyebrow":"دعم منسوق","summary":"إجابات واضحة لكل فريق. استكشف منتجات منسوق والمسارات السريرية وأدوار المستخدمين والأسعار والتكامل والترحيل والتقنية وحماية البيانات ومسار الإطلاق.","seoTitle":"الأسئلة الشائعة: الرعاية والتقنية والترحيل والأسعار | منسوق","seoDescription":"إجابات لفرق الرعاية والتقنية والمشتريات والمرضى عن منتجات منسوق والأدوار والأسعار والتكامل والترحيل والأمن والإعداد والدعم.","sections":[],"description":"إجابات لفرق الرعاية والتقنية والمشتريات والمرضى عن منتجات منسوق والأدوار والأسعار والتكامل والترحيل والأمن والإعداد والدعم.","answers":[{"id":"mansoq-overview","question":"ما هي منسوق؟","answer":"تجمع منسوق برمجيات الرعاية الصحية والمسارات السريرية والتشغيلية المترابطة وخدمات الإيرادات المتفق عليها في منظومة منتجات واحدة. ابدأ بكور المشترك واختر بيئة الرعاية والأقسام المطلوبة، ثم أكد الإصدار المتاح والتكاملات ونطاق التنفيذ مع الفريق.","href":"/platform","url":"https://mansoq.com/faq?lang=ar#faq-mansoq-overview"},{"id":"which-organizations","question":"ما المنشآت الصحية التي يمكنها استكشاف منسوق؟","answer":"يعرض الموقع العيادات والمجمعات والمستشفيات والمجموعات الطبية والعناية المركزة عن بُعد والرعاية المنزلية أو التلطيفية. تحتاج كل بيئة إلى مراجعة مساراتها وسعتها ومتطلباتها السريرية والتنفيذية؛ ولا تثبت صفحة المنتج وحدها جاهزية كل قدرة لمنشأتك.","href":"/solutions","url":"https://mansoq.com/faq?lang=ar#faq-which-organizations"},{"id":"existing-software-coexistence","question":"هل يلزم استبدال جميع أنظمة المستشفى الحالية؟","answer":"لا. يمكن تخطيط الاستبدال أو تكامل محدد أو انتقال مرحلي أو أرشيف مستمر. حدد النظام المسؤول عن كل سجل وكيف تنتقل التحديثات وكيف يعالج الموظفون الاستثناءات. أكد صلاحيات مورّد المصدر ومعايير القبول قبل الالتزام بالانتقال.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-existing-software-coexistence"},{"id":"product-vs-service","question":"ما الفرق بين البرنامج والتشغيل المدار وRCM RaaS؟","answer":"يمكّن البرنامج المسارات المختارة. يغطي التشغيل المدار العمل غير السريري المتفق عليه ضمن رصيد الباقة. وتمثل RCM RaaS خدمة إيرادات إضافية مقبولة بقوائم عمل وصلاحيات وأساس لرسوم التحصيل مستقل. لا توفر أي من الخدمتين تلقائياً كادراً سريرياً ولا تنقل المسؤولية الطبية.","href":"/services/raas","url":"https://mansoq.com/faq?lang=ar#faq-product-vs-service"},{"id":"request-a-demo","question":"كيف أطلب عرضاً توضيحياً أو عرض سعر؟","answer":"استخدم طلب التواصل أو العرض التوضيحي واذكر بيئة الرعاية والمواقع والمستخدمين والأنظمة الحالية والمسار المطلوب. يستطيع الفريق مراجعة سيناريو مناسب وتوضيح المتطلبات وإعداد نطاق متفق عليه. استخدم أمثلة اصطناعية بدلاً من إرسال سجلات المرضى عبر الاستفسار العام.","href":"/demo","url":"https://mansoq.com/faq?lang=ar#faq-request-a-demo"},{"id":"english-arabic","question":"هل تستطيع الفرق العربية والإنجليزية استخدام موارد التخطيط نفسها؟","answer":"نعم. يتوفر دليل المنتجات والأسئلة الشائعة والتنفيذ العام بالعربية والإنجليزية بروابط حسب اللغة. أكد أثناء التنفيذ لغة التطبيق الفعلية والمصطلحات المترجمة واتجاه الواجهات وقوالب المستندات وتدريب المستخدمين المطلوبة للإصدار المختار.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-english-arabic"},{"id":"which-user-roles","question":"ما أدوار المستخدمين التي نخطط لها قبل الإعداد؟","answer":"ابدأ بمن ينفذ العمل: التسجيل والممارسون والتمريض وفرق الأقسام والصيدلية والإيرادات والمالية والتقنية والمديرون والدعم المخول. اربط كل دور بمنشآته ومهامه ومسؤوليات الاعتماد. يحدد قبول المنتج والإصدار الصلاحيات الفعلية المتاحة.","href":"/platform/core","url":"https://mansoq.com/faq?lang=ar#faq-which-user-roles"},{"id":"multi-site-governance","question":"هل تستطيع المجموعة إدارة منشآت متعددة بمسؤوليات مختلفة؟","answer":"خطط لتسلسل الكيانات والمنشآت ومسؤولي التشغيل المحلي والوصول بين المواقع والتقارير المجمعة معاً. يجب أن يحترم عرض المجموعة حدود المشاركة والمسؤولية المالية المعتمدة. أكد الباقة والسعة وقدرات تعدد الكيانات الفعلية قبل التفعيل.","href":"/solutions/medical-cities","url":"https://mansoq.com/faq?lang=ar#faq-multi-site-governance"},{"id":"who-approves-clinical-records","question":"من يتحمل مسؤولية التوثيق والقرارات السريرية؟","answer":"يبقى فريقك السريري المخول مسؤولاً عن رعاية المريض ودقة السجل والأوامر والقرارات المهنية. حدد من يعد السجل ويراجعه ويعتمده ويصححه في المسار المقبول. لا تستبدل مساعدة البرنامج أو الدعم التشغيلي المراجعة المهنية والحوكمة السريرية المحلية.","href":"/platform/core","url":"https://mansoq.com/faq?lang=ar#faq-who-approves-clinical-records"},{"id":"account-vs-clinical-access","question":"هل يمنح حساب العميل في الموقع وصولاً لسجلات المرضى؟","answer":"يخدم حساب الموقع وبيئة العمل السريرية المنشورة غرضين مختلفين. لا يثبت الوصول التجاري صلاحية لسجل مريض أو تفعيل بيئة سريرية. يجب أن تستكمل المؤسسة إجراءات الهوية وتعيين الأدوار والبيئة والتفعيل المعتمدة.","href":"/account","url":"https://mansoq.com/faq?lang=ar#faq-account-vs-clinical-access"},{"id":"clinical-workflow-coverage","question":"كيف نتحقق من دعم مسارنا السريري؟","answer":"راجع دليل المنتج المناسب واعرض تسلسل عملك الفعلي باستخدام حالات اصطناعية. ضمّن الرعاية المعتادة والتسليم والتصحيح والتصعيد والتوقف. اعتمد الإصدار والتهيئة المدعومين مع المسؤولين السريريين قبل الاستخدام لرعاية المرضى.","href":"/platform/care-settings","url":"https://mansoq.com/faq?lang=ar#faq-clinical-workflow-coverage"},{"id":"department-vs-results","question":"هل عرض نتائج المختبر أو الأشعة يساوي تشغيل القسم؟","answer":"لا. عرض النتائج والتكامل مع نظام خارجي وتشغيل القسم بالكامل نطاقات مختلفة. لتشغيل المختبر أو التصوير، اعتمد مسارات الطلب والتعامل مع العينة أو الدراسة والتحقق والتقرير والاستثناءات. أكد واجهات المحللات والتصوير وPACS وغيرها بصورة مستقلة.","href":"/platform/departments","url":"https://mansoq.com/faq?lang=ar#faq-department-vs-results"},{"id":"medication-safety-workflow","question":"ماذا تتحقق منه فرق الصيدلية والأدوية؟","answer":"تحقق من تسليم الوصف والصرف والإعطاء والمخزون المختار وفق سياساتك. أكد دليل الأدوية والوحدات والصلاحيات وخطوات المراجعة والتصحيح وأي اتصال بصيدلية خارجية. لا تفترض توفر كل تنبيه سريري أو وظيفة سلامة دوائية دون تحقق خاص بالإصدار.","href":"/platform/pharmacy","url":"https://mansoq.com/faq?lang=ar#faq-medication-safety-workflow"},{"id":"ai-clinical-review","question":"هل يتخذ الذكاء الاصطناعي قرارات سريرية أو يعتمد الملاحظة الطبية تلقائياً؟","answer":"يجب أن يبقى الذكاء الاصطناعي المساعد ضمن الاستخدام المقصود ومسار الاعتماد البشري المقبولين. يراجع الممارس المخول أي مسودة مولدة ويصححها قبل اعتمادها. اعتمد الموافقة ومعالجة البيانات ودور المورّد والتحقق؛ فقد يكون المحتوى المولد ناقصاً أو خاطئاً ولا يستبدل الحكم السريري.","href":"/platform/ai","url":"https://mansoq.com/faq?lang=ar#faq-ai-clinical-review"},{"id":"teleicu-responsibilities","question":"هل تشمل العناية عن بُعد كادر السرير أو تنقل المسؤولية السريرية؟","answer":"يجب اعتماد نطاق البرنامج وترتيب الخدمة السريرية بشكل مستقل. أكد فريق السرير والتغطية السريرية عن بُعد والتراخيص والتصعيد والأجهزة والاتصال. لا توفر باقة العناية عن بُعد بذاتها كادراً سريرياً أو استجابة طوارئ ولا تنقل مسؤولية رعاية المريض.","href":"/solutions/teleicu","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-responsibilities"},{"id":"clinical-downtime","question":"كيف تستعد الفرق السريرية لتوقف النظام؟","answer":"اعتمد إجراء توقف محلياً يغطي تعريف المريض والتواصل العاجل والأدوية والأوامر والتوثيق. تدرب على مسؤول إعلان التوقف واستمرار العمل وتسوية السجلات بعد الاستعادة. اعتمد ترتيبات التعافي التقني والقبول السريري قبل الإطلاق.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-clinical-downtime"},{"id":"migration-source-systems","question":"هل يمكن الترحيل من Epic أو Oracle Health أو TrakCare أو نظام آخر؟","answer":"استخدم مرجع ترحيل الأنظمة لتخطيط المسار وفق المنتج والإصدار المثبتين لديك. تحدد صلاحيات الوصول وصيغ الاستخراج وعقود المورّد وربط الحقول وجودة البيانات النطاق الفعلي. يمثل إدراج المورّد مرجعاً للتخطيط ولا يعد بوصل جاهز أو شراكة أو ترحيل مضمون.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-migration-source-systems"},{"id":"migration-data-domains","question":"ما المعلومات التي ينبغي تضمينها في نطاق الترحيل؟","answer":"احصر معرّفات المرضى وبياناتهم والزيارات النشطة والسجلات السريرية والمرفقات والمواعيد والأرصدة المالية والأدلة المرجعية حسب الحاجة. اعتمد لكل مجال الاستيراد أو التكامل أو الأرشفة أو الاستبعاد ومسؤوله ومتطلبات الاحتفاظ وفحوص القبول. لا تشمل ميزانية الإعداد كل البيانات التاريخية تلقائياً.","href":"/resources/implementation#existing-systems","url":"https://mansoq.com/faq?lang=ar#faq-migration-data-domains"},{"id":"migration-patient-matching","question":"كيف نحد من تكرار المرضى وربط السجلات بالشخص الخطأ؟","answer":"احتفظ بمعرّفات المصدر وحدد قواعد المطابقة قبل الاستيراد. افحص التكرار والمعرّفات المفقودة والبيانات المتعارضة، ثم أحل التطابقات غير المؤكدة لمراجع مخول. طابق السجلات المقبولة وسجل التصحيح؛ ولا تدمج مرضى غير مؤكدي الهوية دون مراجعة.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-migration-patient-matching"},{"id":"migration-rehearsal","question":"ماذا يحدث قبل الترحيل النهائي والإطلاق؟","answer":"نفذ تجربة متفقاً عليها ببيانات ممثلة وفحوص ربط الحقول والتسوية السريرية والمالية. سجل الصفوف المرفوضة والأعداد والمرفقات والمسؤوليات والاعتماد. اعتمد تجميد الاستخراج والتغييرات النهائية ونافذة الانتقال ومعايير التراجع والوصول للنظام السابق قبل النقل النهائي.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-migration-rehearsal"},{"id":"migration-no-downtime","question":"هل يمكن ضمان عدم التوقف أو تاريخ ترحيل ثابت؟","answer":"يعتمد التوقيت على صلاحيات المصدر وجودة البيانات والمورّدين والاختبار والتدريب والقبول. ضع خطة تنفيذ بمتطلباتها وتجربة للانتقال بدلاً من افتراض انعدام التوقف. يحدد بيان العمل المقبول المراحل والمسؤوليات وأي التزامات خدمة متفق عليها.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-migration-no-downtime"},{"id":"historical-archive","question":"هل يمكن إبقاء النظام السابق أرشيفاً للقراءة فقط؟","answer":"يمكن أن يكون الأرشيف المستمر جزءاً من انتقال متفق عليه. أكد الترخيص والاحتفاظ والوصول ومطابقة المرضى والتدقيق وإجراء استرجاع السجلات القديمة. حدد النظام المسؤول عن المعاملات الجديدة ودرب الموظفين على وقت الرجوع للأرشيف.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-historical-archive"},{"id":"integration-standards","question":"هل تعني الإشارة إلى FHIR أو HL7 أو DICOM اتصال النظام فوراً؟","answer":"لا. يمثل المعيار جزءاً من التكامل فقط. اعتمد الإصدارات والموارد أو الرسائل المدعومة والمعرّفات والمصادقة وربط الحقول ومعالجة الأخطاء واختبارات القبول. أكد المحول الفعلي وصلاحيات مورّد المصدر ونطاق التفعيل قبل الاعتماد على التبادل المباشر.","href":"/platform/integrations","url":"https://mansoq.com/faq?lang=ar#faq-integration-standards"},{"id":"integration-scope-checklist","question":"ما المعلومات التي تحتاجها التقنية لتحديد نطاق الواجهة؟","answer":"قدم النظامين المرسل والمستقبل والإصدارات والمسؤول والاستخدام والحقول وتواتر الرسائل والبيئة ومتطلبات الأمن. ضمّن عينات اصطناعية واعتمادات اختبار عبر قناة معتمدة ومتطلبات المورّد. اعتمد المراقبة والتسوية وإعادة المحاولة ومسؤولية المعاملات الفاشلة.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-integration-scope-checklist"},{"id":"national-activation","question":"هل يعمل نفيس وزاتكا مباشرة بمجرد الاشتراك؟","answer":"مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة، لكن الإرسال المباشر يحتاج اعتمادات منشأتك والقبول الخارجي. اعتمد التسجيل والمعاملات المدعومة وأدلة الاختبار والتسوية ومسؤولية الحوادث. لا يمنح الاشتراك وحده اعتماد المنصات الوطنية.","href":"/saudi","url":"https://mansoq.com/faq?lang=ar#faq-national-activation"},{"id":"identity-sso","question":"هل يمكن استخدام الدخول الموحد أو مزود الهوية الحالي؟","answer":"ناقش تسجيل دخول الشركة مع فريق منسوق أثناء الاستكشاف التقني. يعتمد توفره على المنتج المختار ومزود الهوية ونطاق النشر المقبول. تعالج التهيئة وإدارة الحساب داخل تجربة الحساب المخولة.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-identity-sso"},{"id":"devices-network","question":"ما الأجهزة والمتصفحات وسعة الشبكة المطلوبة؟","answer":"أعد قائمة جاهزية للمسارات المقبولة تشمل محطات العمل والجوال والطابعات والماسحات والأجهزة الطبية والحضور عن بُعد عند الحاجة. أكد المتصفحات والإصدارات والاتصال والسعة وترتيبات البديل مع مسؤولي التنفيذ. يحتاج توريد الأجهزة وواجهاتها إلى نطاق صريح.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-devices-network"},{"id":"deployment-hosting-options","question":"هل يمكن طلب استضافة مخصصة أو نموذج نشر مختلف؟","answer":"ناقش البنية وموقع البيانات والعزل والتشغيل والتعافي في عرض المؤسسات. لا تثبت قاعدة يملكها العميل أو خيار التخزين نشراً مخصصاً لكل مكونات التطبيق. أكد البنية الكاملة وحدود المسؤولية في التصميم المقبول.","href":"/pricing#care-packages","url":"https://mansoq.com/faq?lang=ar#faq-deployment-hosting-options"},{"id":"integration-change-management","question":"من يصون الواجهة عندما يغير المورّد واجهته البرمجية؟","answer":"اعتمد الإصدار المصان ومسؤول المراقبة وحدود الدعم وإجراء التغيير عند تفعيل الاتصال. قد تحتاج ترقية المورّد إلى تعديل الربط أو إعادة الاختبار أو بناء مستقل. سجل إشعارات الإصدارات ولا ترقِّ نظاماً معتمداً قبل مراجعة الأثر والقبول.","href":"/platform/integrations","url":"https://mansoq.com/faq?lang=ar#faq-integration-change-management"},{"id":"security-evidence","question":"ما أدلة الأمن والامتثال التي ينبغي مراجعتها؟","answer":"اطلب الضوابط والأدلة المتعلقة بالخدمة والنشر وتدفقات البيانات المختارة. راجع الوصول والتدقيق والتشفير والحوادث والمورّدين والاحتفاظ والتعافي مع فريقي الأمن والشؤون القانونية. تحقق من نطاق الأدلة وصلاحيتها؛ ولا يثبت وصف الموقع شهادة أو حكماً قانونياً.","href":"/company/trust","url":"https://mansoq.com/faq?lang=ar#faq-security-evidence"},{"id":"data-ownership-access","question":"من يتحكم بالبيانات السريرية ومن يحق له الوصول إليها؟","answer":"يجب أن يحدد الاتفاق سلطة المؤسسة على سجلاتها وأدوار المعالجة المسموحة. امنح الوصول للأشخاص المخولين وأنشطة الخدمة المعتمدة فقط وفق إجراءات التدقيق والدعم المقبولة. لا يحدد خيار التخزين وحده كل الصلاحيات والتدفقات والمسؤوليات القانونية.","href":"/privacy","url":"https://mansoq.com/faq?lang=ar#faq-data-ownership-access"},{"id":"data-location-subprocessors","question":"كيف نتحقق من موقع تخزين البيانات والمورّدين الذين يعالجونها؟","answer":"راجع خريطة تدفق البيانات الكاملة للبيئة المقبولة، بما فيها قواعد التطبيق والملفات والسجلات والنسخ الاحتياطية وأنظمة الدعم ومورّدو الذكاء الاصطناعي أو التواصل الخارجيون. اعتمد المواقع والمعالجين الفرعيين وضوابط النقل والاستخدام المسموح في الوثائق ذات الصلة قبل التفعيل.","href":"/company/trust","url":"https://mansoq.com/faq?lang=ar#faq-data-location-subprocessors"},{"id":"backup-recovery-evidence","question":"هل أهداف النسخ الاحتياطي والتعافي مضمونة لكل باقة؟","answer":"تعتمد ترتيبات التعافي على النشر ونطاق الخدمة المقبولين. أكد مسؤولية النسخ وتواتره والاحتفاظ والتشفير واختبارات الاستعادة وأهداف زمن الاستعادة ونقطة الاستعادة المتفق عليها. لا يعد خيار قاعدة البيانات أو وصف المنتج دليلاً على التزام تعافٍ مختبر.","href":"/company/trust","url":"https://mansoq.com/faq?lang=ar#faq-backup-recovery-evidence"},{"id":"privacy-requests","question":"كيف يطلب المريض الاطلاع على معلوماته أو تصحيحها؟","answer":"يتواصل المريض مع مقدم الرعاية المسؤول عن سجله عبر قناة الخصوصية أو السجلات المعتمدة لديه. يتحقق مقدم الرعاية من الهوية ويراجع الطلب ويطبق التزاماته وسياسة تصحيح السجلات السريرية. لا ترسل سجلات طبية أو وثائق هوية أو تفاصيل حساسة عبر استفسار التسويق العام.","href":"/privacy","url":"https://mansoq.com/faq?lang=ar#faq-privacy-requests"},{"id":"safe-support-information","question":"ما المعلومات المناسبة في استفسار الدعم أو المبيعات؟","answer":"صف المسار والمؤسسة والمشكلة في الاستفسار العام دون بيانات تعريف المريض أو كلمات المرور أو مفاتيح API أو ملفات الإنتاج. استخدم أمثلة اصطناعية متى أمكن. يحدد مسؤول الدعم القناة الآمنة المعتمدة والتفويض عندما تتطلب المعالجة أدلة حساسة.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-safe-support-information"},{"id":"implementation-start-checklist","question":"ماذا نحتاج قبل بدء التنفيذ؟","answer":"سمِّ راعياً تنفيذياً ومسؤول تنفيذ ومعتمدي الجوانب السريرية والمالية وجهات التقنية وملاك البيانات. جهز هيكل المنشآت ومصفوفة الأدوار ونطاق المنتجات وحصر أنظمة المصدر والتكاملات المطلوبة. اعتمد بيان العمل والمتطلبات وأدلة القبول ونموذج التشغيل قبل جدولة التفعيل.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-implementation-start-checklist"},{"id":"implementation-timeline","question":"كم يستغرق الإعداد والتنفيذ؟","answer":"لا توجد مدة موحدة. تتبع الجدولة النطاق المقبول وجاهزية بيانات المصدر والوصول للواجهات والتهيئة والتدريب والموافقات الخارجية. استخدم مراحل بمسؤولين وبوابات جاهزية، وأكد التواريخ بعد الاستكشاف بدلاً من اعتبار شراء الباقة التزاماً بالإطلاق.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-implementation-timeline"},{"id":"training-by-role","question":"كيف ينظم التدريب لكل دور؟","answer":"درّب كل فريق على مهامه وصلاحياته والتسليم والاستثناءات المقبولة باستخدام سيناريوهات اصطناعية. أشرك مسؤولي التسجيل والرعاية والأقسام والمالية والإدارة حسب الحاجة وسجل الحضور وفحوص الكفاءة. اعتمد أسلوب التنفيذ والمواد وتدريب المدربين وأي تدريب حضوري بشكل مستقل.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-training-by-role"},{"id":"go-live-acceptance","question":"من يعتمد الجاهزية للإطلاق؟","answer":"يعتمد مسؤولو الأعمال والرعاية والمالية والتقنية المعينون المجالات الواقعة ضمن مسؤوليتهم. راجع التهيئة واختبارات الأدوار وتسوية الترحيل والواجهات والتدريب والتوقف وجاهزية الدعم. وثق المشكلات المفتوحة وأثرها وقرار الإطلاق أو التأجيل المخول قبل تفعيل المسارات الحية.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-go-live-acceptance"},{"id":"support-hours-sla","question":"هل يشمل الاشتراك تلقائياً دعماً على مدار الساعة أو زمناً مضموناً للاستجابة؟","answer":"تتبع تغطية الدعم وتعريفات الخطورة وأهداف الاستجابة والقنوات والتصعيد اتفاق الخدمة المقبول. أكد جهات التواصل ومسؤولية الحوادث للبرنامج والاستضافة والأجهزة والمورّدين والتشغيل السريري. لا ينشئ دليل الأسئلة تغطية غير متفق عليها على مدار الساعة أو ضماناً للحل.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-support-hours-sla"},{"id":"report-a-problem","question":"كيف يبلغ فريقنا عن مشكلة بعد الإطلاق؟","answer":"استخدم مسار الدعم المتفق عليه مع مؤسستك واذكر البيئة والوقت والمسار المتأثر والأثر وخطوات إعادة المشكلة الآمنة. افصل التصعيد السريري العاجل عن تذكرة البرنامج وفق السياسة المحلية. أرسل الأدلة الحساسة عبر القناة الآمنة المعتمدة وأطلع مسؤول الحادث.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-report-a-problem"},{"id":"new-site-module","question":"ماذا يتغير عند إضافة موقع أو قسم أو منتج لاحقاً؟","answer":"راجع السعة والترخيص ومتطلبات المسار والصلاحيات ومشاركة البيانات والواجهات وأثر الدعم قبل التفعيل. حدّث التهيئة والنطاق التجاري المقبولين ثم اختبر الأدوار المتأثرة ودربها. لا تزيد سعة الرعاية الإضافية تلقائياً ساعات التشغيل أو رصيد الواجهات.","href":"/pricing#configuration","url":"https://mansoq.com/faq?lang=ar#faq-new-site-module"},{"id":"procurement-information","question":"ماذا تتضمن طلبات العروض أو التقييم لدى المشتريات؟","answer":"حدد بيئات الرعاية والمواقع والسعة والأدوار والمسارات المطلوبة والأنظمة الحالية وحجم البيانات والتكاملات. أضف متطلبات أدلة الأمن والاستضافة والتعافي والدعم والتدريب والقبول. ميّز المتطلبات الإلزامية عن الخيارات ليعرض المقترح الفجوات والمتطلبات والتكاليف بوضوح.","href":"/contact?request=consultation","url":"https://mansoq.com/faq?lang=ar#faq-procurement-information"},{"id":"quotation-total-cost","question":"ما الذي ندرجه عند مقارنة التكلفة الإجمالية؟","answer":"قارن رسوم البرنامج والتشغيل المتكررة المقبولة والإعداد والترحيل والسعة الإضافية وRCM RaaS عند اختيارها والضريبة وتكاليف الأطراف الأخرى. أدرج الأجهزة والرسائل والواجهات المخصصة والبنية المخصصة والخدمات الاختيارية عند الحاجة. اعتمد العرض المقبول بدلاً من إضافة افتراضات لسعر الباقة المنشور.","href":"/pricing","url":"https://mansoq.com/faq?lang=ar#faq-quotation-total-cost"},{"id":"contract-before-activation","question":"ما الوثائق التي ينبغي اعتمادها قبل التفعيل المباشر؟","answer":"اعتمد نطاق المنتج والخدمة والعرض وبيان العمل والمسؤوليات وشروط معالجة البيانات ومعايير القبول المناسبة للنشر. أكد الدعم والفوترة والتجديد والتغييرات والإنهاء وخروج البيانات في العقد المعمول به. يساعد دليل الموقع على التقييم ولا يستبدل الاتفاقات المقبولة.","href":"/terms","url":"https://mansoq.com/faq?lang=ar#faq-contract-before-activation"},{"id":"roi-guarantees","question":"هل تحسن التحصيل أو الوفورات التشغيلية مضمونة؟","answer":"تعتمد الفوائد المتوقعة على الوضع الحالي والنطاق المختار وجودة البيانات والتبني والمسؤوليات التشغيلية. اعتمد مقاييس خط أساس وراجع النتائج الفعلية مع فريقك. لا تمثل السيناريوهات والأمثلة التوضيحية نتائج عملاء مدققة أو ضماناً للإيراد أو الوفورات أو النتائج السريرية.","href":"/case-studies","url":"https://mansoq.com/faq?lang=ar#faq-roi-guarantees"},{"id":"partner-implementation","question":"هل يمكن لشريك تنفيذ أو تكامل العمل معنا؟","answer":"ناقش دور الشريك المقترح واعتمد حدود التنفيذ والوصول التقني والتدريب ومسؤولية التغيير والقبول. يجب أن يعمل الشريك ضمن ترتيبات الأمن ومعالجة البيانات المعتمدة. لا يثبت إدراج جهة في مرجع الترحيل وجود شراكة تجارية.","href":"/company/partners","url":"https://mansoq.com/faq?lang=ar#faq-partner-implementation"},{"id":"data-exit-portability","question":"ماذا يحدث لبياناتنا عند المغادرة أو تغيير النظام؟","answer":"اعتمد صيغ التصدير والسجلات والمرفقات المشمولة والمستلمين المخولين والتوقيت والتكاليف والاحتفاظ والحذف قبل التوقيع. أكد كيفية تفسير النظام الوجهة للبيانات ومعالجة التزامات الاحتفاظ القانونية أو السريرية. لا يضمن اتصال التخزين وحده قابلية نقل التطبيق بالكامل.","href":"/privacy","url":"https://mansoq.com/faq?lang=ar#faq-data-exit-portability"},{"id":"patient-medical-advice","question":"هل أستطيع الحصول على استشارة طبية أو رعاية طارئة من هذا الموقع؟","answer":"يوفر موقع منسوق العام معلومات المنتجات والخدمات. تواصل مع مقدم رعايتك للاستشارة الطبية والمواعيد والأسئلة المتعلقة بالعلاج. للطوارئ استخدم خدمة الطوارئ المحلية أو مسار الرعاية العاجلة لدى مقدم الخدمة؛ فلا يُراقب استفسار التسويق بوصفه قناة طوارئ سريرية.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-patient-medical-advice"},{"id":"patient-portal-access","question":"كيف أصل لمواعيدي أو نتائجي أو بوابة المريض؟","answer":"يؤكد مقدم الرعاية تفعيل مسار المريض ويزودك برابط الوصول الصحيح. تحقق من هوية مقدم الرعاية وتواصل مع فريق التسجيل أو الدعم لديه لاستعادة الحساب. لا يوفر موقع منسوق العام بوابة موحدة لكل المنشآت الصحية.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-patient-portal-access"},{"id":"family-proxy-consent","question":"هل يمكن لأفراد الأسرة الاطلاع على معلومات المريض؟","answer":"يتبع وصول الأسرة أو الممثل سياسة مقدم الرعاية للتحقق من الهوية والموافقة والولاية والتفويض. أكد مع مقدم الرعاية مسار التمثيل المدعوم وحدوده. لا تثبت صلة القرابة وحدها صلاحية الاطلاع على السجل أو تلقي التحديثات السريرية.","href":"/privacy","url":"https://mansoq.com/faq?lang=ar#faq-family-proxy-consent"},{"id":"patient-billing-insurance","question":"من يجيب عن سؤال بخصوص فاتورتي أو مطالبتي التأمينية؟","answer":"تواصل مع فريق الفوترة أو التأمين لدى مقدم الرعاية عبر البيانات الواردة في الفاتورة أو وثائق الرعاية. يستطيع الفريق التحقق من هويتك ومراجعة الحساب المعني. لا يستطيع فريق المنتجات العام في منسوق تقرير مطالبة فردية أو كشف بيانات حساب مريض عبر استفسار مبيعات.","href":"/contact","url":"https://mansoq.com/faq?lang=ar#faq-patient-billing-insurance"},{"id":"module-core","question":"ما مسار عمل «منسوق كور» وما الذي نعتمده قبل استخدامه؟","answer":"هوية المريض وسجله المشترك وسياق الرعاية والإدارة والصلاحيات والتدقيق والتهيئة ضمن حدود بيانات متفق عليها.\n\n1. التعريف: سجّل الشخص بمعرّفات مؤسستك. راجع احتمال التكرار قبل إنشاء مريض آخر واحتفظ بمعرّفات المصدر عند استمرار استخدام نظام سابق.\n\n2. التنظيم: عرّف المؤسسات القانونية والمنشآت والأقسام والمواقع. اربط كل سجل تشغيلي بمنشأته واجعل المشاركة بين المواقع ضمن الحدود المعتمدة.\n\n3. الصلاحيات: اربط المستخدمين بأدوارهم ومنشآتهم وتحقق من صلاحيات القراءة والإنشاء والتعديل. اختبر مستخدماً محدود الصلاحيات ومديراً قبل اعتماد الإعداد.\n\n4. ربط السياق: اربط الزيارات والملاحظات والقياسات والطلبات والمرفقات بالشخص الصحيح. تستخدم الأقسام والإيرادات هذا السياق وفق القدرات والصلاحيات المختارة.\n\n5. المراجعة والصيانة: راجع تغييرات السجلات والمستخدم المسؤول وحدّث التهيئة المشتركة وأكد ترتيبات الاحتفاظ والنسخ الاحتياطي والدعم للإصدار المختار. أعد اختبار الصلاحيات عند إضافة موقع أو وحدة.\n\nيوفر كور الهوية والسياق المشتركين. يتطلب التبادل بين الحسابات ومطابقة المرضى خارجياً والمشاركة المؤسسية نطاق ربط وحوكمة معتمداً.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/core","url":"https://mansoq.com/faq?lang=ar#faq-module-core"},{"id":"module-outpatient","question":"ما مسار عمل «رعاية العيادات الخارجية» وما الذي نعتمده قبل استخدامه؟","answer":"التسجيل والمواعيد وقوائم الزيارات والاستشارات والمتابعة مع النطاق السريري والفوترة المطلوبين.\n\n1. الحجز والوصول: هيئ خدمات العيادة والأطباء والجلسات وأنواع الزيارات. احجز في الفترة المناسبة وسجّل الوصول ووجّه الزيارة للفريق السريري.\n\n2. الاستشارة: افتح الزيارة وراجع التاريخ المرضي والحساسيات وسجّل القياسات والتقييم. استخدم النماذج المعتمدة واحتفظ بارتباط المؤلف والزيارة بالسجل.\n\n3. الطلبات والتنفيذ: أنشئ طلبات الخدمات والأدوية بسياقها السريري. وجّهها للمختبر أو الأشعة أو الصيدلية المختارة وراجع النتائج المكتملة قبل تحديد الخطوة التالية.\n\n4. الإغلاق والمتابعة: وثق خطة الرعاية ومسؤولية المتابعة وأكمل الزيارة واربط الخدمات المنفذة بالفوترة. يعتمد التأمين والمطالبات والفواتير الإلكترونية على إضافات الإيرادات المختارة.\n\nتشكل المواعيد والزيارات مسار الزيارة. يهيأ تشغيل الأقسام وتبادل النتائج والأدوية والتأمين عبر وحداتها.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/outpatient","url":"https://mansoq.com/faq?lang=ar#faq-module-outpatient"},{"id":"module-inpatient","question":"ما مسار عمل «رعاية التنويم» وما الذي نعتمده قبل استخدامه؟","answer":"الدخول والنقل والخروج والأجنحة والأسرة والتمريض والطلبات والأدوية ضمن مسار تنويم متكامل.\n\n1. التنويم وتحديد الموقع: أنشئ زيارة التنويم وحدد الجناح والسرير المناسبين. أكد الفريق المسؤول واحتفظ بسياق الإحالة أو الطوارئ.\n\n2. تنسيق الرعاية: سجّل التقييمات والقياسات وحدّث خطة الرعاية وتابع طلبات الخدمات. أتح الملاحظات والنتائج والإجراءات المعلقة لفريق الجناح المخوّل.\n\n3. الأدوية والنقل: اربط طلبات الأدوية وسجلات إعطائها وصرفها. راجع الخطة الحالية والموقع والمهام غير المكتملة مع الفريق المستلم عند النقل.\n\n4. الخروج والمطابقة: أكمل سجل الخروج وتعليمات الأدوية ومسؤولية المتابعة. راجع الخدمات الموثقة والبنود المالية المفتوحة عبر الفوترة ومسار الإيرادات المختار.\n\nتجمع زيارة التنويم تفاصيل الإقامة. للعناية المركزة والجراحة والصيدلية واتصالات الأقسام متطلبات تهيئة وصلاحيات وقبول مستقلة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/inpatient","url":"https://mansoq.com/faq?lang=ar#faq-module-inpatient"},{"id":"module-emergency","question":"ما مسار عمل «رعاية الطوارئ» وما الذي نعتمده قبل استخدامه؟","answer":"سياق زيارة الطوارئ والملاحظات وتسليم مسؤوليات الرعاية وفق النطاق التشغيلي المتحقق منه.\n\n1. الاستقبال: سجّل الوصول وحدد الهوية وفق الإجراء المحلي المعتمد بما في ذلك مسار الهوية المؤقتة عند الحاجة. افتح زيارة الطوارئ وحدد الموقع والفريق.\n\n2. التقييم وتحديد الأولوية: سجّل الشكوى والقياسات. هيئ فئات الفرز ومسؤوليات التصعيد المعتمدة؛ تبقى الأولوية السريرية قرار فريق الرعاية.\n\n3. العلاج والملاحظة: وثق الرعاية والأدوية والطلبات العاجلة. اربط النتائج والقياسات المتكررة بالزيارة وحدد مسؤول كل إجراء معلق أثناء الملاحظة.\n\n4. تحديد الوجهة: وثق الخروج أو التنويم أو النقل مع الفريق المستلم والعلاج الحالي والطلبات المعلقة. تتبع الفوترة والتأمين مسارهما المخوّل دون استبدال قرار الرعاية.\n\nيرتبط توثيق الطوارئ بالتشخيص والتنويم والعناية الحرجة المختارة. يجب اعتماد قواعد الفرز وحدود التصعيد وسياسات الطوارئ محلياً.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/emergency","url":"https://mansoq.com/faq?lang=ar#faq-module-emergency"},{"id":"module-teleicu","question":"ما مسار عمل «العناية المركزة عن بُعد» وما الذي نعتمده قبل استخدامه؟","answer":"تهيئة محددة لتنسيق العناية الحرجة عن بُعد مع تحديد نطاق اتصالات النظام المحلي والفيديو والأجهزة المدعومة بشكل مستقل.\n\n1. إنشاء المركز والمواقع: حدد المنشآت المشاركة وأسرة العناية وتغطية المختصين. اتفق على الجهة المسؤولة عن الرعاية والسجلات المتاحة للفريق البعيد وجهات التصعيد بكل موقع.\n\n2. تحضير الحالة: اربط الشخص والزيارة بسياق المراجعة المشترك. أكد مصادر القياسات والملاحظات والصور وشغّل اتصالات الكاميرات والأجهزة ضمن النطاق المتفق عليه.\n\n3. المراجعة عن بُعد: يُراجع المختص المخوّل الحالة ويوثق التقييم والتوصيات. حدد مسؤول السرير الذي يستقبل الخطة وينفذها؛ لا تنقل المشورة المسؤولية السريرية ضمنياً.\n\n4. المتابعة والتصعيد: تابع المراجعة التالية ومسؤوليات التسليم. حافظ على إجراءات التواصل والتعطل عند غياب الفيديو أو نقص المعلومات أو الحاجة لتصعيد مباشر.\n\nلمسار المختص والفيديو والكاميرات والتبادل السريري والأجهزة حدود تنفيذ مستقلة. أكد شبكة كل منشأة وأجهزتها والاتصالات المدعومة قبل التشغيل.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/teleicu","url":"https://mansoq.com/faq?lang=ar#faq-module-teleicu"},{"id":"module-home-palliative","question":"ما مسار عمل «الرعاية المنزلية والتلطيفية» وما الذي نعتمده قبل استخدامه؟","answer":"الزيارات وخطط الرعاية والتوثيق متعدد التخصصات مع مسارات تلطيفية متحقق منها. ويحدد نطاق الجوال والعمل دون اتصال وقنوات الأسرة بشكل مستقل.\n\n1. التسجيل والتخطيط: حدد سياق الرعاية والموافقة ووسائل التواصل مع مقدم الرعاية. عرّف منطقة الخدمة والفريق والخطة المنزلية أو التلطيفية المعتمدة ومسؤوليات التصعيد.\n\n2. جدولة الزيارة: حدد الممارس ووقت الزيارة مع مراعاة المنطقة والتنقل. أكد الأجهزة والأدوية والمعلومات المطلوبة للفريق الزائر.\n\n3. التقديم والتوثيق: سجّل الزيارة والقياسات ومراجعة الأعراض والرعاية المقدمة. اربط الأدوية والخدمات بالخطة ووثق نقاش مقدم الرعاية والمسؤوليات التالية.\n\n4. استمرار الرعاية: خطط للزيارة التالية أو الإحالة وسلّم الاحتياجات غير المحسومة للفريق المتعدد التخصصات. طابق المستلزمات والخدمات عبر المخزون والفوترة عند اختيارهما.\n\nيُختار توثيق الرعاية المنزلية والمواعيد والمخزون والدعم البعيد بصورة مستقلة. يجب تأكيد العمل دون اتصال والأجهزة البعيدة وتحسين المسارات للنشر المختار.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/home-palliative","url":"https://mansoq.com/faq?lang=ar#faq-module-home-palliative"},{"id":"module-operating-room","question":"ما مسار عمل «غرفة العمليات» وما الذي نعتمده قبل استخدامه؟","answer":"نطاق متحقق منه لحجز الحالات والتحضير والتوثيق المحيط بالجراحة والموارد والمستهلكات وتسليم الرعاية بعد العملية.\n\n1. تخطيط الإجراء: اربط طلب الإجراء بالمريض والزيارة. هيئ غرف العمليات والأطباء والجلسات والأجهزة ورموز الخدمات وأكد الجراح وفريق التخدير والجناح المستلم.\n\n2. التحضير والتحقق: سجّل التحضير ومراجع الموافقة وقائمة السلامة المحلية المعتمدة. راجع السجل والأدوية والفحوص المطلوبة قبل الإجراء.\n\n3. توثيق الإجراء: احفظ التوثيق السريري والقياسات والأدوية والمستلزمات المستخدمة مع الزيارة. اربط الخدمات والمستهلكات بالمخزون والرسوم عند اختيار وحداتها.\n\n4. الإفاقة والتسليم: سجّل حالة الإفاقة وخطة الرعاية التالية. سلّم العلاج الحالي والطلبات المعلقة والمسؤوليات للجناح أو فريق الخروج ثم طابق نشاط الخدمات الموثق.\n\nتُجمع جدولة العمليات والسجلات السريرية مع التنويم والأدوية والمخزون والفوترة. يتطلب التقاط بيانات أجهزة التخدير والأنظمة الخارجية اعتماد ربط مستقلاً.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/operating-room","url":"https://mansoq.com/faq?lang=ar#faq-module-operating-room"},{"id":"module-icu","question":"ما مسار عمل «العناية المركزة» وما الذي نعتمده قبل استخدامه؟","answer":"نطاق متحقق منه لسجل العناية الحرجة والملاحظات والأدوية واتصالات الأجهزة. ويلزم التحقق الصريح من وظائف المراقبة والإنذار.\n\n1. الاستقبال في الوحدة: اربط المريض المنوّم بموقع العناية الحرجة والفريق المسؤول. راجع الإحالة والعلاجات الحالية والفحوص المعلقة عند التسليم الأول.\n\n2. المراقبة والتوثيق: احفظ القياسات والتقييمات وتوثيق الرعاية في الزيارة. حدد الوحدات وتكرار التسجيل ومسؤولية التصعيد المحلية؛ تتطلب التغذية الآلية ربط جهاز معتمداً.\n\n3. تنسيق العلاج: اربط الطلبات وإعطاء الأدوية والتقارير بالخطة الحالية. طابق التغييرات مع فريق السرير ووثق مسؤول كل إجراء معلق.\n\n4. التسليم والنقل: راجع السجل والمسؤوليات المعلقة عند تغيير المناوبة أو الوحدة. يمكن إضافة المراجعة عن بُعد مع تعريف مستقل للوصول والمسؤوليات ونطاق الأجهزة.\n\nلا يعني توفر سجل العناية ربط كل شاشة أو جهاز تنفس أو إنذار. حدد طرازات الأجهزة والبروتوكولات والأطباء المسؤولين وإجراءات التعطل ضمن النطاق المختار.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/icu","url":"https://mansoq.com/faq?lang=ar#faq-module-icu"},{"id":"module-pharmacy","question":"ما مسار عمل «الصيدلية» وما الذي نعتمده قبل استخدامه؟","answer":"طلبات الأدوية والصرف وتشغيل المخزون بما يتجاوز وصف الدواء أو عرض قائمته.\n\n1. الوصف: أنشئ طلب الدواء بالزيارة والمنتج والجرعة وطريقة الإعطاء والتكرار والمدة. أتح سياق الحساسيات والأدوية الحالية للمراجعة المهنية.\n\n2. التحقق والتحضير: راجع الوصفة في قائمة الصيدلية وأكد الصنف والكمية واختر التشغيلة المناسبة. سجّل أي استبدال عبر الإجراء المخوّل دون تغيير الوصفة ضمنياً.\n\n3. الصرف والتسليم: سجّل تحضير الدواء وتسليمه والكمية وأيام التغطية والتعليمات. اربط الصرف بالمريض والموقع والطلب المخوّل والرسوم المنطبقة.\n\n4. التتبع والمطابقة: راجع الوصفات المعلقة والصرف المكتمل وحركات المخزون. عالج المرتجعات والتصحيحات عبر إجراءات المخزون والمالية المعتمدة؛ يبقى إعطاء الدواء للمنوّم سجلاً سريرياً مستقلاً.\n\nالوصف والصرف والإعطاء والمخزون سجلات مترابطة ومستقلة. تحتاج قواعد قائمة الأدوية وتحويل الوحدات والتغطية والصرف الخارجي تهيئة معتمدة لكل منها.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/pharmacy","url":"https://mansoq.com/faq?lang=ar#faq-module-pharmacy"},{"id":"module-laboratory","question":"ما مسار عمل «المختبر» وما الذي نعتمده قبل استخدامه؟","answer":"مسارات طلبات المختبر والعينات والنتائج مع فصل التشغيل الداخلي عن ربط نظام المختبر الخارجي.\n\n1. الطلب: اختر الفحص من كتالوج الخدمات واربطه بالمريض والزيارة والطبيب الطالب. أضف السؤال السريري والأولوية ومعلومات العينة المطلوبة.\n\n2. الجمع والاستلام: سجّل نوع العينة ومعلومات الجمع ومعرّف التسجيل ووقت الاستلام والحالة. اربط ملاحظات المعالجة بالطلب الأصلي لتتبع إعادة الجمع.\n\n3. التسجيل والمراجعة: اربط القياسات والتقارير التشخيصية بالطلب والعينة. هيئ تعريفات الفحوص والوحدات وتفسير النتائج المعتمد وحدد مراجع النتيجة ومسار إبلاغ النتائج الحرجة.\n\n4. الإصدار والمتابعة: أتح التقرير المعتمد في الزيارة السريرية. احتفظ بأسباب التعديل ومسؤولية المراجع ودليل الإبلاغ؛ يتولى الفريق الطالب المتابعة السريرية.\n\nتختلف الطلبات والعينات والقياسات والتقارير الداخلية عن ربط نظام مختبر أو محلل خارجي. تتطلب بروتوكولات الأجهزة ومواءمة الرموز والإقرارات والتعافي اختبار اتصال للإصدار المختار.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/laboratory","url":"https://mansoq.com/faq?lang=ar#faq-module-laboratory"},{"id":"module-radiology","question":"ما مسار عمل «الأشعة» وما الذي نعتمده قبل استخدامه؟","answer":"طلبات الأشعة وتشغيل القسم والتقارير المتحقق منها، مع نطاق تنفيذ مستقل لاتصالات أنظمة الأشعة والأرشفة.\n\n1. الإحالة والجدولة: أنشئ طلب التصوير بالسؤال السريري والمريض والزيارة والإجراء المطلوب. أكد نوع التصوير وتوافر القسم والتحضير المطلوب قبل الفحص المجدول.\n\n2. التصوير والتعريف: اربط عمل القسم بالطلب ومعلومات التسجيل. عند اختيار الأرشفة الطبية تحقق من معرّفات المريض والدراسة والزيارة قبل قبول الدراسة المرتبطة.\n\n3. التفسير والتقرير: اربط التقرير التشخيصي بالطلب السريري الصحيح. أكد المؤلف وحالة التقرير ومسؤولية الإبلاغ واتفق على مسار التقارير الخارجي إذا جرى التفسير في نظام آخر.\n\n4. الإبلاغ والتعديل: أعد التقرير لفريق الرعاية المخوّل ووثق النتائج الحرجة عبر المسار المعتمد واحتفظ بالإضافات وأسبابها ومسؤوليها. تابع التقارير المعلقة عند التسليم.\n\nسياق طلبات الأشعة وتقاريرها مستقل عن حفظ الصور وعرضها وأجهزة التصوير وربط أنظمة الأشعة والأرشفة. حدد المكونات المشمولة واختبر ارتباط الدراسات وتبادل التقارير عند اختيارهما.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/radiology","url":"https://mansoq.com/faq?lang=ar#faq-module-radiology"},{"id":"module-inventory","question":"ما مسار عمل «المخزون» وما الذي نعتمده قبل استخدامه؟","answer":"تشغيل المخزون والمستودعات وتزويد الأقسام ضمن النطاق المدعوم المتفق عليه.\n\n1. تعريف المخزون: هيئ المنتجات والمستودعات والوحدات ومراجع الموردين. استورد الكميات الافتتاحية حسب التشغيلة والموقع والتكلفة والصلاحية وطابق الملف مع جرد معتمد.\n\n2. الطلب والاستلام: أنشئ طلبات التوريد وسجلات التسليم وأكد مواقع التوريد والاستلام وافحص الكميات المستلمة فعلياً. احتفظ بمراجع الطلب الأصلي والمورد.\n\n3. الصرف والتحويل: اختر الصنف والتشغيلة للاستخدام في القسم أو الصرف أو التحويل. أكد المصدر والوجهة والكمية لمطابقة الحركة الفعلية بسجل المخزون الصحيح.\n\n4. الجرد والمطابقة: راجع المخزون المتوفر والصلاحية والتسليمات المعلقة. حقق في فروق الجرد وسجّل التسويات والمرتجعات المخولة وأسبابها واتفق على التصدير المالي عند استخدام محاسبة خارجية.\n\nتدعم سجلات المخزون والتوريد نشاط الأقسام. تتطلب موافقات المشتريات والتصدير المحاسبي وأجهزة الرموز والمستودعات الخارجية نطاقاً واختبارات محددة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/inventory","url":"https://mansoq.com/faq?lang=ar#faq-module-inventory"},{"id":"module-clinical-documentation","question":"ما مسار عمل «التوثيق السريري وتخطيط الرعاية» وما الذي نعتمده قبل استخدامه؟","answer":"التوثيق المطلوب للأطباء والتمريض والملاحظات والنماذج وخطط الرعاية والتسليم وفق مسار الرعاية المختار.\n\n1. تحضير النماذج: هيئ الاستبيانات والنماذج السريرية وصلاحيات المؤلفين لبيئة الرعاية. حدد الحقول المطلوبة والمصطلحات ومسؤولية المراجعة قبل الاستخدام.\n\n2. توثيق الزيارة: سجّل التقييم والقياسات والتشخيصات والسرد السريري للزيارة الصحيحة. اربط الإجابات المنظمة والمرفقات بالمريض والمؤلف المسؤول.\n\n3. المراجعة والإكمال: راجع المعلومات المطلوبة وخطة الرعاية. طبّق إجراء الإكمال والتوقيع المعتمد للإصدار المختار وأتح السجل المناسب للفرق المخوّلة المستلمة.\n\n4. التعديل والاحتفاظ: عالج التصحيحات بمؤلف وسبب محددين. اتفق على الاحتفاظ والوصول واحفظ الإصدارات وأدلة التدقيق عند استخدام التوثيق للترميز أو التبادل الخارجي.\n\nيوفر التوثيق السياق للطلبات والتسليم والترميز. يجب أن تتوافق وثائق التبادل والتوقيعات والاحتفاظ مع الإصدار المعتمد وقواعد المؤسسة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/clinical-documentation","url":"https://mansoq.com/faq?lang=ar#faq-module-clinical-documentation"},{"id":"module-orders-medication","question":"ما مسار عمل «الطلبات والنتائج والأدوية» وما الذي نعتمده قبل استخدامه؟","answer":"نطاق الطلبات والنتائج والأدوية المطلوب للمسار المختار، مع فصله عن التشغيل الداخلي للأقسام.\n\n1. تعريف الوجهات: هيئ الخدمات القابلة للطلب وكتالوجات الأدوية ووجهات الأقسام. اتفق على حالات الطلب والمعلومات المطلوبة وأدوار الإنشاء والتغيير والإلغاء.\n\n2. إنشاء الطلب: اربط الطلب بالمريض والزيارة والصنف والكمية والسياق السريري. سجّل تعليمات الجرعة والطبيب المخوّل للأدوية.\n\n3. التنفيذ والتتبع: وجّه العمل للقسم أو الصيدلية المختارة. تابع حالة الطلب والعينة والتقرير والصرف أو الإعطاء المرتبطين دون اعتبار هذه الأحداث المختلفة إكمالاً واحداً.\n\n4. المراجعة والمطابقة: راجع النتائج ونشاط الأدوية ووثق الإلغاء والتغييرات وأكمل الطلبات المعلقة عند التسليم. يتبع التقاط الرسوم الخدمة المنفذة وتهيئة الفوترة المختارة.\n\nتنسق إدارة الطلبات الطلبات. تحتاج معالجة المختبر والأشعة والصرف والإعطاء وحداتها التشغيلية؛ لا يوفر الاتصال وحده تشغيل القسم.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/orders-medication","url":"https://mansoq.com/faq?lang=ar#faq-module-orders-medication"},{"id":"module-patient-access","question":"ما مسار عمل «وصول المريض إلى الرعاية» وما الذي نعتمده قبل استخدامه؟","answer":"التسجيل والجدولة والوصول إلى الزيارات وقوائم الانتظار، مع تحقق مستقل من نطاق بوابة المريض والتواصل مع الأسرة.\n\n1. تحديد التوافر: هيئ موارد الأطباء أو المواقع وتواريخ الجلسات وساعات العمل وقواعد الفترات. اربط الخدمات وصلاحيات الحجز المعتمدة بالمورد.\n\n2. التسجيل والحجز: حدد المريض وراجع التواصل والمعرّفات واحجز الخدمة المطلوبة. احفظ تفاصيل الإحالة والدافع عند طلبها من مسار الرعاية والإيرادات المختار.\n\n3. الوصول والتوجيه: سجّل الوصول ومعلومات قائمة الانتظار وافتح الزيارة أو اربطها ووجّه الشخص للعيادة أو القسم المسؤول. أكد المسؤولية التالية للحجز.\n\n4. إعادة الجدولة والمتابعة: سجّل الإكمال أو الإلغاء أو عدم الحضور ونظّم المتابعة المناسبة. طبّق سياسة إعادة الزيارة والرسوم عبر مسار الفوترة المختار.\n\nيربط الاستقبال الشخص بخدمة رعاية. تحتاج قنوات الحجز العامة والتواصل والهوية أو التأمين الخارجي اتصالات مختارة ومعتمدة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/patient-access","url":"https://mansoq.com/faq?lang=ar#faq-module-patient-access"},{"id":"module-billing-finance","question":"ما مسار عمل «الفوترة والمالية» وما الذي نعتمده قبل استخدامه؟","answer":"الفواتير والمدفوعات والسجلات المالية المرتبطة بنشاط الرعاية، مع تحديد نطاق ربط المحاسبة بشكل مستقل.\n\n1. تعريف الرسوم: هيئ تعريفات رسوم الخدمات والعملة والمعالجة الضريبية المنطبقة. أكد مسؤولية الحساب والأسعار والصلاحيات؛ تتبع أسعار الدافعين التعاقدية تهيئة الإيرادات المختارة.\n\n2. التقاط النشاط: اربط الرسوم بالزيارة والخدمة المنفذة والكمية والسياق الداعم. راجع الأدوية وخدمات الأقسام غير المفوترة وعالج البنود المفقودة أو المكررة قبل إعداد الفاتورة.\n\n3. الفوترة والتحصيل: راجع رسوم الحساب ومالك الفاتورة ومسؤولية المريض أو الدافع المسموحة. سجّل الدفعات بمراجعها وفواتيرها؛ تبقى تقديرات التأمين واعتماد الإرسال قرارات مستقلة.\n\n4. المطابقة والتصحيح: طابق الفواتير والدفعات مع الإجماليات المعتمدة. عالج الاسترداد والعكس والتسويات بأسباب وموافقات واتفق على التصدير المحاسبي عند الحاجة. الفوترة الإلكترونية لزاتكا مشمولة ويبدأ إرسالها المباشر بعد اعتمادات زاتكا والقبول الخارجي.\n\nتسجل الفوترة نشاط الخدمات والحركات المالية. مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. يُتفق على الربط المحاسبي الخارجي بشكل مستقل.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/billing-finance","url":"https://mansoq.com/faq?lang=ar#faq-module-billing-finance"},{"id":"module-revenue-cycle","question":"ما مسار عمل «إدارة دورة الإيراد» وما الذي نعتمده قبل استخدامه؟","answer":"مسار إيرادات متكامل ومترابط بوحدات تفصيلية للأهلية والموافقات وإعداد الجهات الدافعة والرسوم والمطالبات والرفض والمطابقة.\n\n1. تأسيس القواعد: هيئ المؤسسات القانونية واتفاقات الإدارة وعقود المزود والمنتجات والوثائق المصدرة وفئات الأعضاء بترتيب الاعتماد. احفظ الأدلة والتواريخ والموافقة مع كل إصدار.\n\n2. التحقق من التغطية: حدد أهلية العضو والشبكة والمنافع والاستثناءات والحدود والتعرفة للخدمة. تنتج المعلومة المجهولة بند مراجعة محدداً دون افتراض سعر أو مسؤولية للمريض.\n\n3. الموافقة والتحضير: جهز الموافقة المطلوبة والأدلة. افصل الخدمات والكميات والفترات المطلوبة عن المعتمدة وراجع التقدير المؤقت والمعلومات غير المحسومة والصلاحية قبل قبول التحضير المالي.\n\n4. الالتقاط والإرسال: اعتمد النشاط المنفذ وطابق الرسوم واجمع المطالبة والترميز والمرفقات. تحقق من البيانات وهوية الإرسال؛ يتطلب الإرسال الفعلي بيانات اتصال وحزمة تبادل وأدلة تفعيل معتمدة.\n\n5. معالجة الردود: ميّز تحقق النقل وأخطاء الدافع والرفض بعد التقييم. وجّه التصحيحات وطلبات الأدلة ونزاعات العقود والاعتراضات السريرية للمسؤول المناسب بمراجعها الأصلية ومواعيدها.\n\n6. التسوية والتفسير: اربط إشعارات السداد بالمطالبات وافصل التقييم عن تسوية النقد وطابق الدفعات الجزئية والخصومات والنقد غير المطابق. راجع الأعمار والاستثناءات والتتبع دون تحويل الأرصدة غير المحسومة لرسوم على المريض.\n\nمسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. البيانات المرجعية ليست تهيئة إنتاج معتمدة؛ تُعتمد بيانات الدافع وحقوق المصطلحات والاتصالات المالية كلٌ على حدة قبل الاستخدام.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/revenue-cycle","url":"https://mansoq.com/faq?lang=ar#faq-module-revenue-cycle"},{"id":"module-sbs-specific","question":"ما مسار عمل «أدوات مواءمة أكواد SBS المحددة» وما الذي نعتمده قبل استخدامه؟","answer":"نطاق مواءمة وتحديث محدد لأكواد الخدمات المدعومة، دون حذف الأكواد السريرية أو أكواد المطالبات المطلوبة لفرض ترقية سعرية.\n\n1. اختيار الإصدار: حدد إصدار نظام الفوترة السعودي المدعوم وحقوق استخدامه. اتفق على رموز محددة أو الكتالوج المرخّص الكامل.\n\n2. مواءمة الخدمات المحلية: اربط خدمة المزود بالرمز والفترة المعتمدين. احفظ المعرّفات والأوصاف المحلية وأدلة المواءمة وعالج الخدمات غير المطابقة بمراجعة الترميز.\n\n3. التحقق من الاستخدام: تحقق من الرموز المطلوبة والمعطلة والتكرار واكتمال المواءمة. راجع نشاط خدمات نموذجي عبر الرسوم والمطالبات المختارة قبل الاعتماد.\n\n4. إدارة الإصدارات: راجع تغييرات الإصدار والتواريخ مع المسؤول. احفظ المواءمات السابقة للسجلات التاريخية واختبر الأسعار والمطالبات المتأثرة قبل التفعيل.\n\nمواءمة SBS مستقلة عن ترخيص الكتالوج وقبول تبادل نفيس. لا يمنح ملف المواءمة حقوق الكتالوج أو اعتماد المطالبة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/sbs-coding","url":"https://mansoq.com/faq?lang=ar#faq-module-sbs-specific"},{"id":"module-sbs-full","question":"ما مسار عمل «أدوات كتالوج SBS المدعوم الكامل» وما الذي نعتمده قبل استخدامه؟","answer":"أدوات استيراد ومواءمة وتحديث الكتالوج المدعوم الكامل، مع الاتفاق على الإصدار والنطاق وصلاحيات الاستخدام الفعلية.\n\n1. اختيار الإصدار: حدد إصدار نظام الفوترة السعودي المدعوم وحقوق استخدامه. اتفق على رموز محددة أو الكتالوج المرخّص الكامل.\n\n2. مواءمة الخدمات المحلية: اربط خدمة المزود بالرمز والفترة المعتمدين. احفظ المعرّفات والأوصاف المحلية وأدلة المواءمة وعالج الخدمات غير المطابقة بمراجعة الترميز.\n\n3. التحقق من الاستخدام: تحقق من الرموز المطلوبة والمعطلة والتكرار واكتمال المواءمة. راجع نشاط خدمات نموذجي عبر الرسوم والمطالبات المختارة قبل الاعتماد.\n\n4. إدارة الإصدارات: راجع تغييرات الإصدار والتواريخ مع المسؤول. احفظ المواءمات السابقة للسجلات التاريخية واختبر الأسعار والمطالبات المتأثرة قبل التفعيل.\n\nمواءمة SBS مستقلة عن ترخيص الكتالوج وقبول تبادل نفيس. لا يمنح ملف المواءمة حقوق الكتالوج أو اعتماد المطالبة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/sbs-coding","url":"https://mansoq.com/faq?lang=ar#faq-module-sbs-full"},{"id":"module-drg","question":"ما مسار عمل «تكامل DRG ومزيج الحالات والتجميع» وما الذي نعتمده قبل استخدامه؟","answer":"مسار محدد للترميز ومزيج الحالات وإصدار التجميع المدعوم وتراخيصه واتصالاته، ولا يعني الوصول للكتالوج وجود ترخيص تجميع مفعل.\n\n1. تحضير الحالة المرمزة: حدد الزيارة ومدخلات الترميز المطلوبة لأداة التجميع المختارة. راجع اكتمال التشخيص والإجراء والحالة مع مسؤول الترميز قبل التجميع.\n\n2. تحديد أداة التجميع: أكد إصدار الأداة وترخيصها وصيغة المدخلات وطريقة التنفيذ. حدد المعالجة الخارجية أو المشمولة واختبر حالات مرمزة نموذجية.\n\n3. مراجعة ناتج التجميع: احفظ نتيجة التجميع والحالة وإصدار المدخلات ومسؤولية المراجعة. تحقق من الأخطاء والمجموعات غير المتوقعة قبل تحليل مزيج الحالات.\n\n4. التصحيح والمقارنة: احفظ النتائج السابقة عند تصحيح الترميز أو تغيير إصدار الأداة. اتفق على الاستخدام المالي وتعريفات التقارير وأعد اختبار حالات نموذجية بعد التغيير.\n\nتتطلب قدرة DRG أداة تجميع مرخّصة متفقاً عليها وربطاً مدعوماً. لا يفترض ذلك أداة معينة أو قاعدة سداد وطنية أو نتيجة مالية تلقائية.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/drg","url":"https://mansoq.com/faq?lang=ar#faq-module-drg"},{"id":"module-nphies","question":"ما مسار عمل «نفيس» وما الذي نعتمده قبل استخدامه؟","answer":"تبادل الأهلية والموافقات والمطالبات المدعوم، مع اتفاق صريح على التسجيل وبيانات الاتصال والإصدارات والتفعيل.\n\n1. تحضير هوية المزود: أكد معرّفات المزود والدافع وحزمة التبادل المدعومة والجهة المسؤولة. سجّل أدلة التسجيل ووجهات الاختبار والإنتاج قبل الاختبار.\n\n2. فحص الأهلية والموافقة: جهز العضو والوثيقة والخدمة لتبادل الأهلية والموافقة المدعوم. تحقق من الطلب واحفظ ردود الدافع والصلاحية والمعلومات غير المحسومة.\n\n3. تبادل المطالبات: اجمع المطالبات والمرفقات المدعومة وطبّق تحقق الحزمة وتتبع معرّفات الرسالة والمطالبة. يسمح بالإرسال بعد اعتماد شروط الإنتاج والأدلة المطلوبة.\n\n4. متابعة الردود والمطابقة: تابع الردود والاستعلامات وإشعارات السداد المدعومة. ميّز أخطاء المنصة من قرارات الدافع وطابق المراجع وفق قواعد الإعادة والتصحيح المعتمدة.\n\nتخضع قدرة نفيس لدعم الحزمة والتسجيل وبيانات الاتصال وأدلة الاعتماد. لا يثبت الكود أو البيانات المرجعية جاهزية إنتاج معتمدة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/integrations/nphies","url":"https://mansoq.com/faq?lang=ar#faq-module-nphies"},{"id":"module-zatca","question":"ما مسار عمل «الفوترة الإلكترونية مع زاتكا» وما الذي نعتمده قبل استخدامه؟","answer":"تكامل الفواتير الإلكترونية والتسجيل المدعوم، مع توضيح المرحلة المعنية والتهيئة والمسؤوليات التشغيلية.\n\n1. تعريف المكلف والمرحلة: أكد المكلف القانوني ومعرّف الضريبة ومرحلة الفوترة ونوع الفاتورة. حدد المسؤول وسجّل قواعد الضريبة وهوية المستند المعتمدة.\n\n2. تسجيل الاتصال: جهز وحدة الفوترة والوجهة ومراجع بيانات الاتصال الآمنة. أكمل التسجيل وأدلة الاختبار؛ لا تخوّل البيانات التجريبية أو نجاح الاختبار الإرسال الفعلي.\n\n3. إعداد الفاتورة والتحقق: اربط الفاتورة المدعومة بنشاط الفوترة وهوية المستند والضريبة. تحقق من البيانات المطلوبة ومسار الإبلاغ أو التخليص المختار قبل الإرسال.\n\n4. الإرسال وحفظ الأدلة: احفظ الرد والتتبع مع الفاتورة. اتبع إجراءات الرفض والإعادة والإشعار الدائن وتجديد بيانات الاتصال وطابق المستندات مع دفتر الفوترة.\n\nيُتفق صراحة على نطاق الفاتورة والمرحلة وأنواع المستندات وتسجيل الإنتاج. لا يُعد وصف الوحدة ادعاء اعتماد أو امتثال.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/integrations/zatca","url":"https://mansoq.com/faq?lang=ar#faq-module-zatca"},{"id":"module-analytics","question":"ما مسار عمل «التحليلات المتقدمة» وما الذي نعتمده قبل استخدامه؟","answer":"تقارير تشغيلية وقسمية وإيرادية مختارة، منفصلة عن التقارير الأساسية لكور.\n\n1. اختيار المصادر: حدد المصدر التشغيلي والمسؤول وحدود التقارير. اتفق على المنشآت والزيارات والسجلات المالية المشاركة وكيفية التحقق من اكتمال البيانات.\n\n2. تعريف المقاييس: حدد مستوى التحليل والبسط والمقام والاستثناءات والفترة. طابق الإجماليات المالية والنشاط قبل اعتماد لوحة المعلومات مقياساً.\n\n3. نشر الرؤية: هيئ مزود اللوحات المختار والرؤية لسياق المنشأة. تحقق من الصلاحيات والتحديث والمرشحات ومعنى القيم مع المستخدمين.\n\n4. المراقبة والصيانة: راجع حداثة المصدر وتغييرات التعريفات والمواءمة. حدد ضوابط التصدير واحفظ أدلة القبول للرؤى المستخدمة في قرارات التشغيل أو المال.\n\nيوفر موصل التحليلات وصولاً للوحات حسب المزود. تتطلب اللوحات والمقاييس وتصميم مستودع البيانات والتغذية المالية نطاق تقارير واعتماداً محددين.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/analytics","url":"https://mansoq.com/faq?lang=ar#faq-module-analytics"},{"id":"module-ai","question":"ما مسار عمل «مساندة الذكاء الاصطناعي الخاضعة للمراجعة» وما الذي نعتمده قبل استخدامه؟","answer":"تقتصر الإتاحة على المهام المساعدة المتحقق منها وحدود البيانات المحددة والمراجعة البشرية المسؤولة، دون ادعاء تشخيص مستقل.\n\n1. اعتماد المهمة: حدد مهمة المساعدة النصية أو الصورية والبيانات المسموحة والمزود والمراجع. اتفق على الموافقة والتعامل مع البيانات والتقييم والبديل اليدوي قبل التفعيل.\n\n2. توفير السياق: قدم السياق والمدخلات المعتمدة فقط. هيئ النماذج المسموحة وحدود الاستخدام وأكد حجم الصور وحدود المدخلات والوصول للميزة.\n\n3. توليد المساعدة: استخدم المزود المهيأ للمهمة المعتمدة. تعامل مع الناتج كمحتوى مقترح قد يتضمن نقصاً أو أخطاء؛ لا يستبدل النموذج الحكم المهني.\n\n4. المراجعة والاحتفاظ: يتحقق المهني المسؤول من المحتوى ويعدله قبل الحفظ أو التصرف. تابع نتائج التقييم والوصول وأعطال المزود وفق الحوكمة المعتمدة.\n\nيدعم الملحق المساعدة النصية والصورية المهيأة. لا يفترض التشخيص أو الوصف أو التصرف السريري المستقل؛ يجب اعتماد وتقييم كل مهمة ومزود.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/ai","url":"https://mansoq.com/faq?lang=ar#faq-module-ai"},{"id":"module-interfaces","question":"ما مسار عمل «اتصالات الأنظمة والأجهزة» وما الذي نعتمده قبل استخدامه؟","answer":"تحديد كل اتصال فعلي مع أنظمة المستشفيات والمختبر والأشعة والأرشفة والهوية والأجهزة والواجهات وبروتوكولاته وتراخيصه ونطاق تنفيذه.\n\n1. تعريف التبادل: حدد المصدر والوجهة وأنواع الرسائل والاتجاه والبروتوكول والإصدار. حدد الهوية أو الزيارات أو الطلبات أو النتائج أو الأجهزة أو النشاط المالي والمسؤولين.\n\n2. مواءمة المعرّفات والبيانات: واءم معرّفات المريض والمنشأة والممارس والزيارة ورموز الخدمات والوحدات والأوقات والحالات. حدد الحقول المطلوبة والتحويلات والقيم غير المدعومة.\n\n3. الاختبار والقبول: استخدم بيئة الاختبار وبيانات الاتصال والوجهة المتفق عليها. تحقق من الرسائل الصحيحة والخاطئة والمكررة والمتأخرة والإقرارات والترتيب والمطابقة قبل اعتماد الإنتاج.\n\n4. التشغيل والتعافي: راقب التبادلات الفاشلة والمعلقة وحدد مسؤول الدعم. اتبع قواعد الإعادة والتكرار وطابق السجلات بعد التعطل أو تغيير بيانات الاتصال أو إصدار الربط.\n\nالبروتوكولات والأدوات المتاحة مرتبطة بالإصدار. لا يثبت اسم نظام خارجي أو شعار معيار وجود ربط فعّال؛ اعتمد البيانات والاتجاه والترخيص والدعم المحددين.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/integrations","url":"https://mansoq.com/faq?lang=ar#faq-module-interfaces"},{"id":"module-network-governance","question":"ما مسار عمل «حوكمة الشبكة» وما الذي نعتمده قبل استخدامه؟","answer":"حدود محددة للكيانات والبيئات والسجلات وصلاحيات ذات مسؤولية وتكوين شبكة خاضعة للحوكمة.\n\n1. تعريف الشبكة: حدد المؤسسات والمنشآت والأقسام والمسؤولين. عرّف الكتالوجات وسياقات المرضى المشتركة والمنفصلة.\n\n2. تفويض الوصول: اربط المسؤوليات المحلية والمشتركة بأدوار محددة. اختبر الوصول داخل الموقع وعبر حدود المشاركة المعتمدة وللسجلات المقيدة.\n\n3. تنسيق الاستمرارية: اتفق على تسليم الإحالات والسجلات والمسؤوليات بين الخدمات. حدد مواءمة المعرّفات والأنظمة المالكة عند ربط منشأة خارجية.\n\n4. مراجعة الحدود: حدّث الحوكمة وأدلة القبول عند تغير المواقع والأدوار والإصدارات. أعد اختبار المشاركة والوصول المقيد وتعافي الربط قبل توسيع الشبكة.\n\nتختلف المنشآت المشتركة في نشر واحد عن التبادل بين حسابات مستقلة. يحدد تصميم الحوكمة والربط المتفق عليه مشاركة السجلات.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/solutions/medical-city","url":"https://mansoq.com/faq?lang=ar#faq-module-network-governance"},{"id":"module-managed-revenue","question":"ما مسار عمل «خدمات فريق إدارة الإيرادات» وما الذي نعتمده قبل استخدامه؟","answer":"أفراد مؤهلون وصلاحيات مفوضة ونطاق تشغيل معتمد، بشكل منفصل عن برمجيات إدارة دورة الإيراد.\n\n1. تحديد المسؤوليات: حدد مهام الإيرادات المفوضة والمستخدمين وحدود المزود والدافع وتغطية الخدمة. حدد الجهة التي تحتفظ بالقرار السريري والتعاقدي والمالي.\n\n2. تحضير العمل: جهز الوصول للمصادر وقوائم العمل والوثائق اللازمة للأهلية والترميز والموافقة والمطالبة. اعتمد التسليم وفحوص الجودة قبل العمل الفعلي.\n\n3. المعالجة والتصعيد: نفذ المهام المتفق عليها فقط عبر المسارات المخولة. أحل الأدلة السريرية الناقصة ومسائل العقود ونزاعات الدافع للمسؤول وحدد صلاحية الإرسال.\n\n4. مراجعة تقديم الخدمة: طابق العمل المكتمل والسداد والاستثناءات مع المزود. راجع المقاييس والتغطية والتغييرات وفق الشروط دون وعد بنتائج مالية غير مدعومة.\n\nخدمات الفرق مستقلة عن ترخيص البرمجيات وتفعيل الربط. اتفق على الكوادر والتفويض والساعات والمخرجات والدعم في عرض الخدمة.\n\nاعتمد الإصدار والتهيئة والصلاحيات والمتطلبات والاختبارات مع مسؤول المسار قبل التفعيل. لا يثبت النشر العام وحده الجاهزية السريرية.","href":"/platform/managed-revenue","url":"https://mansoq.com/faq?lang=ar#faq-module-managed-revenue"},{"id":"what-is-mansoq","question":"ما هي منسوق وما المشكلة التي تعالجها؟","answer":"تربط منسوق سجل المريض ومسار الرعاية والفوترة والتشغيل غير السريري المتفق عليه. يعمل فريقك من سياق رعاية مشترك بدلاً من إعادة جمع تفاصيل ما حدث من قوائم منفصلة. اختر منتج الرعاية والباقة ثم اتفق على الوحدات والاتصالات والمسؤوليات ونطاق الإطلاق المناسب لمؤسستك.","href":"/platform","url":"https://mansoq.com/faq?lang=ar#faq-what-is-mansoq"},{"id":"software-and-services","question":"هل أشتري برنامجاً أم خدمات تشغيل مدارة أم كليهما؟","answer":"تجمع باقات الرعاية البرنامج مع رصيد شهري محدد من العمل غير السريري المدار. يدعم البرنامج المسار، وتساعد الخدمات المدارة في الإعداد والمراجعة المتخصصة وقوائم التشغيل المتفق عليها. يفصل العرض الرسمين لتعرف ما تشتريه. يوفر العميل الكادر السريري المرخص.","url":"https://mansoq.com/faq?lang=ar#faq-software-and-services"},{"id":"four-care-products","question":"كيف أختار بين العيادات والمجمعات والعناية عن بُعد والرعاية المنزلية والتلطيفية؟","answer":"اختر العيادات للرعاية الخارجية المرتبطة بالمواعيد، والمجمعات لربط التخصصات والصيدلية والمختبر والمخزون، والعناية عن بُعد للاستشارة والتسليم في العناية المركزة، والرعاية المنزلية والتلطيفية للزيارات واستمرارية الرعاية والخطط والتواصل المصرح به مع الأسرة. اختر حسب المسار الذي تريد تشغيله، وليس اسم المنشأة وحده.","href":"/solutions","url":"https://mansoq.com/faq?lang=ar#faq-four-care-products"},{"id":"essential-fit","question":"لمن تناسب الباقة الأساسية؟","answer":"تناسب الأساسية الفرق القادرة على إدارة عملياتها اليومية والتي تحتاج مسار الرعاية المتعاقد عليه كاملاً مع أساسيات الأمان والدعم والمتطلبات الوطنية. يتوفر فيها رصيد أصغر من ساعات التشغيل. مثلاً، ينفذ فريق الاستقبال والفوترة لديك العمل اليومي وتساعد منسوق في مهام الإعداد والمراجعة المتفق عليها.","url":"https://mansoq.com/faq?lang=ar#faq-essential-fit"},{"id":"premium-fit","question":"متى أختار بريميوم؟","answer":"اختر بريميوم عندما تزيد صعوبة العمل اليومي بسبب المهام المتكررة أو التسليم غير المترابط أو نمو النشاط. تضيف أتمتة المسارات ولوحات التشغيل وسعة رعاية أكبر وساعات تشغيل أكثر ورصيد الواجهات المنشور. تساعد فريقك على رؤية الاستثناءات ومعالجتها مبكراً، مع بقاء القرارات والمتابعة التشغيلية لدى فريقك.","url":"https://mansoq.com/faq?lang=ar#faq-premium-fit"},{"id":"diamond-fit","question":"ما الفرق العملي بين الماسية وبريميوم؟","answer":"تشمل الماسية مزايا بريميوم وتضيف مسؤولاً محدداً عن قوائم التشغيل المتفق عليها ومراجعة شهرية للأداء والسعة وأرصدة خدمات أكبر وخيار استخدام قاعدة البيانات والتخزين السريري الخاص بك. مثلاً، تكون لمهمة فوترة أو زيارة معلقة ومتفق عليها جهة اتصال محددة في منسوق تنسق الإجراء التالي ضمن الساعات المتعاقد عليها.","url":"https://mansoq.com/faq?lang=ar#faq-diamond-fit"},{"id":"enterprise-fit","question":"متى تصبح باقة المؤسسات هي الاختيار المناسب؟","answer":"تناسب المؤسسات المجموعات ذات الكيانات القانونية المتعددة أو التكاملات المعقدة أو النشر المخصص أو نطاق التشغيل الذي يحتاج اتفاقاً مفصلاً. تضيف حوكمة المجموعة والصلاحيات والتقارير الموحدة وبرنامج تنفيذ منسقاً حسب الاتفاق. تحدد المبيعات السعة الفعلية والواجهات ونطاق التشغيل ومسؤوليات البنية وأهداف الخدمة في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-enterprise-fit"},{"id":"same-safety-foundation","question":"هل أحتاج باقة أعلى للحصول على الأمان الأساسي أو المسارات الوطنية المطلوبة؟","answer":"يشمل الأساس صلاحيات حسب الدور وسجل تدقيق وموافقة ونسخاً احتياطياً وتصديراً، مع أساسيات التأمين والترميز للمسار المتعاقد عليه. مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. تضيف الباقات الأعلى السعة والأتمتة والمتابعة المدارة والحوكمة.","url":"https://mansoq.com/faq?lang=ar#faq-same-safety-foundation"},{"id":"choose-by-benefit","question":"كيف أقرر إن كانت تكلفة الباقة الأعلى تستحق؟","answer":"قارن القيد الذي تريد معالجته: سعة الرعاية أو العمل المتكرر أو الواجهات أو المتابعة التشغيلية أو حوكمة المجموعة. ثم قارن الساعات والاتصالات المشمولة بحجم عملك. من مؤشرات القياس التوضيحية عدد المهام المتأخرة أو خطوات الإدخال المتكررة قبل الإطلاق وبعده. لا تعد منسوق بتوفير ثابت أو زيادة إيرادات دون خط أساس لديك وقياس متفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-choose-by-benefit"},{"id":"mixed-care-group","question":"هل تستطيع المؤسسة الجمع بين عدة منتجات رعاية؟","answer":"نعم، يمكن مناقشة نطاق رعاية متعدد في عرض تركيب واحد. مثلاً، قد تحتاج مجموعة إلى عيادات واستشارات عناية عن بُعد ومتابعة منزلية. اتفق على كل مسار ومقياس سعة وحدود بيانات وفريق مسؤول. لا تفترض أن جمع أسعار البطاقات العامة يغطي البنية المشتركة أو الكيانات القانونية المستقلة.","url":"https://mansoq.com/faq?lang=ar#faq-mixed-care-group"},{"id":"all-plan-foundation","question":"ما المشمول في كل باقة رعاية؟","answer":"سجل المريض والمواعيد والتوثيق والطلبات والأدوية والفوترة لمسار الرعاية المتعاقد عليه.\n\nصلاحيات حسب الدور وسجل تدقيق وموافقة ونسخ احتياطي وتصدير؛ ومسارات التأمين والترميز ونفيس وفاتورة السعودية عند انطباقها.\n\nوصول المريض والأسرة ودعم المنتج الأساسي والتأهيل ومواصفات ترحيل البيانات المتفق عليها.\n\nيوفر العميل الكادر المرخص والقرارات السريرية وتغطية التصعيد والحوكمة الطبية وصلاحيات أنظمة المصدر. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه.","url":"https://mansoq.com/faq?lang=ar#faq-all-plan-foundation"},{"id":"feature-rcm-raas","question":"كيف تعمل ميزة «إدارة الإيرادات RaaS · ١٨٪ من التحصيل» وما فائدتها؟","answer":"المعنى: خدمة مدارة لدورة الإيرادات لقوائم الفوترة والجهات الدافعة المعتمدة، تسعّر حسب الأموال المحصلة فعلياً ضمن النطاق المتفق عليه.\n\nطريقة العمل: اعتمد نطاق خدمة الإيرادات ومسؤوليات العميل وتعريف التحصيل المؤهل مع الفريق. تدعم الخدمة مسارات الأهلية والمطالبات والتسوية المقبولة. تتبع رسوم التحصيل الاتفاق المقبول والأدلة المالية المراجعة.\n\nمثال: عند تحصيل ١٠٠٬٠٠٠ ريال مؤهلة ومعتمدة، تكون رسوم RaaS ‏١٨٬٠٠٠ ر.س.‏، مع الضريبة عند انطباقها. يسدد اشتراك الباقة بشكل مستقل.\n\nالفائدة والنتيجة المتوقعة: يتابع فريق مسؤول استثناءات الإيرادات حتى التسوية برسوم واضحة ترتبط بالتحصيل المؤهل. تعتمد الموافقة والتحصيل على الأدلة الفعلية وقرارات الجهات الدافعة.\n\nالنطاق: متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها وقوائم الرفض والإنكار ومتابعة الجهات الدافعة ومطابقة التسويات وفق النطاق المتفق عليه. يحتفظ العميل بالقرارات السريرية وصلاحيات المصادر واعتماد المبالغ المستردة والشطب وتغييرات الحسابات البنكية. تضاف الرسوم إلى الاشتراك وتحتسب على التحصيل الفعلي المؤهل بعد المبالغ المستردة والاستبعادات المتفق عليها؛ يلزم قبول التنفيذ والخدمة. تفعل الخدمة بعد توقيع النطاق وقبول التنفيذ والخدمة. لا يطبق الخصم السنوي على رسوم التحصيل.","url":"https://mansoq.com/faq?lang=ar#faq-feature-rcm-raas"},{"id":"feature-patient-access","question":"كيف تعمل ميزة «وصول المرضى وصلاحيات فريق آمنة» وما فائدتها؟","answer":"المعنى: يصل المرضى وأفراد الأسرة المصرح لهم إلى المعلومات المخصصة لهم. وتحدد صلاحيات الموظفين بحسب أدوارهم ومسؤوليات الرعاية.\n\nطريقة العمل: تحدد أدواراً مثل الممارس والاستقبال والفوترة، ثم تعتمد وصول المريض أو الأسرة. تتحكم الصلاحيات في الإجراءات والسجلات المتاحة، ويسجل سجل التدقيق النشاط.\n\nمثال: يدير موظف الاستقبال موعداً، ويحدث الممارس المعالج الملاحظات السريرية. ويطلع فرد الأسرة المصرح له على المعلومات المعتمدة له فقط.\n\nالفائدة والنتيجة المتوقعة: ينجز الجميع أعمالهم ويتابعون الرعاية بالصلاحيات المناسبة، مع قدرتك على معرفة من استخدم النظام.\n\nالنطاق: يعتمد الوصول على الصلاحيات المضبوطة والموافقة ومسار المريض والأسرة المتفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-feature-patient-access"},{"id":"feature-dashboards","question":"كيف تعمل ميزة «لوحات تشغيل وتحليلات» وما فائدتها؟","answer":"المعنى: عرض لمؤشرات التشغيل المتفق عليها، مثل النشاط والعمل المعلق واستخدام السعة.\n\nطريقة العمل: تلخص اللوحات النشاط المسجل في النظام. يراجع المديرون المصرح لهم المؤشرات المتفق عليها ويتابعون الأعمال المرتبطة بها.\n\nمثال: يراجع مدير العيادة الزيارات المكتملة ومهام الفوترة المعلقة، ثم يسند المتأخرات إلى الفريق المناسب.\n\nالفائدة والنتيجة المتوقعة: رؤية أوضح لمواضع تراكم العمل، تساعد المديرين على تحديد الأولويات باستخدام البيانات المسجلة.\n\nالنطاق: تعتمد المؤشرات وتواتر تحديثها على النطاق المعتمد واكتمال بيانات المصدر.","url":"https://mansoq.com/faq?lang=ar#faq-feature-dashboards"},{"id":"feature-monthly-review","question":"كيف تعمل ميزة «مراجعة شهرية للأداء والسعة» وما فائدتها؟","answer":"المعنى: مراجعة مجدولة لنتائج التشغيل المتفق عليها والمشكلات المعلقة ومدى استخدام سعة باقتك.\n\nطريقة العمل: يعد المسؤول المؤشرات المتفق عليها ويراجعها معك ويسجل الإجراءات والمسؤولين وأي تغيير في السعة توافق عليه. يستهلك التحضير والمراجعة من ساعات التشغيل.\n\nمثال: تراجع استخدام سعة الممارسين ومتأخرات الفوترة، ثم تتفق على أولويات التشغيل للشهر التالي.\n\nالفائدة والنتيجة المتوقعة: خطة عمل متفق عليها ووضوح أكبر بشأن السعة. تعتمد النتائج على البيانات المسجلة ومتابعة الفريقين.","url":"https://mansoq.com/faq?lang=ar#faq-feature-monthly-review"},{"id":"feature-entity-governance","question":"كيف تعمل ميزة «حوكمة وصلاحيات متعددة الكيانات» وما فائدتها؟","answer":"المعنى: هيكل متفق عليه للصلاحيات والحوكمة لمجموعة تضم منشآت أو كيانات قانونية متعددة.\n\nطريقة العمل: تحدد الكيانات وحدود البيانات والأدوار المسؤولة مع المبيعات والتنفيذ. تعتمد من يعمل في كل كيان ومن يرى المعلومات المسموح بها على مستوى المجموعة، ثم تختبر الصلاحيات قبل الإطلاق.\n\nمثال: يرى مدير الفرع السجلات المصرح له بإدارتها في فرعه، ويرى مدير المجموعة التقارير المعتمدة على مستوى المجموعة.\n\nالفائدة والنتيجة المتوقعة: مسؤوليات أوضح عبر المجموعة ووصول يتبع حدود مؤسستك المتفق عليها.\n\nالنطاق: تحتاج الكيانات القانونية المستقلة ومشاركة سجلات المرضى إلى نطاق بيانات ونشر متفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-feature-entity-governance"},{"id":"feature-group-reporting","question":"كيف تعمل ميزة «تقارير موحدة للمجموعة» وما فائدتها؟","answer":"المعنى: جمع مؤشرات متفق عليها من منشآت متعددة في عرض للمجموعة مخصص للقيادة المصرح لها.\n\nطريقة العمل: تحدد المنشآت والمؤشرات وتعريفاتها وتواتر التقارير. يجمع عرض المجموعة البيانات المعتمدة مع الالتزام بالصلاحيات وحدود البيانات المقررة.\n\nمثال: يقارن مدير نشاط الرعاية الشهري والعمل التشغيلي المعلق بين ثلاثة فروع باستخدام تعريفات موحدة متفق عليها.\n\nالفائدة والنتيجة المتوقعة: مقارنة أسهل بين المواقع وأساس أوضح لتوزيع الموارد ومراجعة الاختلافات.\n\nالنطاق: تتفق المصادر المشمولة وتواتر التقارير وأي تطوير لتقارير مخصصة في عرض المؤسسات.","url":"https://mansoq.com/faq?lang=ar#faq-feature-group-reporting"},{"id":"feature-custom-integrations","question":"كيف تعمل ميزة «تكاملات واتفاق خدمة مخصص» وما فائدتها؟","answer":"المعنى: نطاق تكامل ودعم يحدد خصيصاً لأنظمة مؤسستك واحتياجات تشغيلها.\n\nطريقة العمل: تتفق المبيعات والتنفيذ على الأنظمة والبيانات المتبادلة واختبارات القبول وساعات الخدمة وأهداف الاستجابة والمسؤوليات. يعتمد كل اتصال قبل الاستخدام، ويحدد الاتفاق الموقع التزام الدعم.\n\nمثال: تحتاج مجموعة إلى ربط نظامها المالي الحالي ببيانات الفوترة المعتمدة. يحدد العرض ربط الحقول والاختبارات وترتيبات دعم ذلك الاتصال.\n\nالفائدة والنتيجة المتوقعة: نطاق واضح لإعدادك الأكثر تعقيداً والتزامات خدمة قابلة للقياس بعد الاتفاق عليها.\n\nالنطاق: تحدد الاتصالات ورسوم المورد وأهداف الخدمة والسعر في عرض المبيعات. لا تعني باقة المؤسسات تكاملات غير محدودة أو تغطية تلقائية على مدار الساعة.","url":"https://mansoq.com/faq?lang=ar#faq-feature-custom-integrations"},{"id":"feature-implementation","question":"كيف تعمل ميزة «برنامج تنفيذ مخصص» وما فائدتها؟","answer":"المعنى: خطة إطلاق منسقة لمنشآتك المتفق عليها والترحيل والتكاملات والتدريب والقبول.\n\nطريقة العمل: تحدد المراحل والمسؤولين ومعايير القبول. تعد بيانات الترحيل وتطابقها، وتختبر الصلاحيات والاتصالات، وتدرب المستخدمين المتفق عليهم، وتراجع الجاهزية قبل الانتقال المخطط.\n\nمثال: تطلق ثلاثة فروع على مراحل: فرع تجريبي أولاً، ثم مطابقة الترحيل والتدريب، وبعدها الفروع الأخرى بعد استكمال فحوص قبولها.\n\nالفائدة والنتيجة المتوقعة: تسلسل إطلاق أوضح ومسؤوليات ظاهرة وأدلة متفق عليها لكل قرار جاهزية.\n\nالنطاق: تحدد مواعيد التنفيذ وعمل الترحيل والحضور في الموقع والسعر في نطاق التنفيذ الموقع.","url":"https://mansoq.com/faq?lang=ar#faq-feature-implementation"},{"id":"feature-national-workflows","question":"كيف تعمل ميزة «المسارات الوطنية الأساسية عند الحاجة» وما فائدتها؟","answer":"المعنى: مسارات التأمين والترميز والفوترة الإلكترونية السعودية التي تنطبق على خدمة الرعاية المتعاقد عليها.\n\nطريقة العمل: يحدد أثناء الإعداد ما ينطبق عليك، مثل تبادل التأمين عبر نفيس والترميز السعودي وفوترة هيئة الزكاة والضريبة والجمارك. تفعل الاتصالات المعنية وتختبر باستخدام صلاحيات مؤسستك واعتماداتها المطلوبة.\n\nمثال: تحتاج عيادة تقدم خدمات مؤمنة إلى التحقق من الأهلية عبر نفيس والفواتير الإلكترونية. تدخل المسارات المنطبقة ضمن الأساس وتعتمد قبل الاستخدام.\n\nالفائدة والنتيجة المتوقعة: تكون المسارات الوطنية المنطبقة جزءاً من أساس الرعاية، مع سهولة متابعة المعلومات المطلوبة وحالة الاتصال.\n\nالنطاق: تلزم اعتمادات المؤسسة ووصول الجهات الدافعة والموردين وقبول الاتصال. لا تستهلك موصلات الأساس الوطنية رصيد الواجهات الخارجية المنفصل.","url":"https://mansoq.com/faq?lang=ar#faq-feature-national-workflows"},{"id":"feature-customer-storage","question":"كيف تعمل ميزة «قاعدة البيانات والتخزين الخاص بك» وما فائدتها؟","answer":"المعنى: خيار نشر اختياري: حفظ قاعدة البيانات السريرية الأساسية والملفات السريرية وملفات المنشأة والتقارير الخاصة في بنية تحتية تتحكم بها.\n\nطريقة العمل: توفر قاعدة PostgreSQL مخصصة وتخزيناً خاصاً متوافقاً مع S3، مثل AWS S3 أو DigitalOcean Spaces أو MinIO على خادمك. بعد اعتماد الصلاحيات والشبكة والنسخ والاستعادة، يستخدم التطبيق الحي والاستيراد والتقارير والمهام الخلفية تلك الوجهة.\n\nمثال: تملك مؤسستك قاعدة PostgreSQL وحاوية Spaces خاصة. يحفظ السجل السريري الجديد في قاعدتك، ويحفظ مرفق المريض في حاويتك.\n\nالفائدة والنتيجة المتوقعة: تحكم أكبر في موقع البيانات السريرية الأساسية والوصول إلى البنية وسياسة الاستعادة. لا يتحول التشغيل السريري تلقائياً إلى قاعدة أو حاوية لدى منسوق.\n\nالنطاق: متاح في الماسية والمؤسسات بعد اعتماد الاتصال. تحدد البنية وعمل الربط والترحيل مستقلاً. يحدد الاتفاق المقبول النطاق الكامل لمعالجة البيانات والاحتفاظ بها. يتطلب تغيير وجهة حية قائمة ترحيلاً متفقاً عليه.","url":"https://mansoq.com/faq?lang=ar#faq-feature-customer-storage"},{"id":"package-price","question":"كيف يحدد سعر حزمة منسوق؟","answer":"يجمع الأساس المتكرر رسم البرنامج ورسم الخدمات المدارة المنشورين. تضاف سعة الرعاية والمواقع وساعات التشغيل الإضافية المعتمدة بأسعار الباقة المختارة. يحدد الإعداد والترحيل والعمل المخصص وبنية العميل واستخدام المورّد بشكل مستقل. راجع العرض المفصل والضريبة والمدة التجارية قبل قبوله.","href":"/pricing#configuration","url":"https://mansoq.com/faq?lang=ar#faq-package-price"},{"id":"currency-tax","question":"ما العملة المستخدمة وهل تشمل الأسعار ضريبة القيمة المضافة؟","answer":"أسعار بطاقات الرعاية بالريال السعودي قبل ضريبة القيمة المضافة. تظهر الضريبة المنطبقة بشكل مستقل في العرض. راجع عملة الفوترة والمعالجة الضريبية في العرض النهائي، خصوصاً للمؤسسات خارج السعودية. قارن المبلغ الشهري الظاهر بالفاتورة كاملة ولا تعتبره إجمالياً شاملاً للضريبة.","url":"https://mansoq.com/faq?lang=ar#faq-currency-tax"},{"id":"enterprise-price-hidden","question":"لماذا لا يظهر سعر عام لباقة المؤسسات؟","answer":"يعتمد سعر المؤسسات على الكيانات والحجم وعمل التكامل والنشر والترحيل ومسؤوليات التشغيل المتفق عليها. قد يخفي السعر العام الثابت عملاً مهماً أو يوحي بالتزامات لم يحدد نطاقها. استخدم «اطلب تواصل المبيعات»؛ يتضمن الطلب منتج الرعاية وباقة المؤسسات المختارين ليعد الفريق العرض المناسب.","url":"https://mansoq.com/faq?lang=ar#faq-enterprise-price-hidden"},{"id":"annual-discount","question":"كيف يغير السداد السنوي المسبق السعر؟","answer":"يطبق السداد السنوي المسبق الخصم المنشور على رسم البرنامج الأساسي فقط. لا يشمل الخصم الخدمات المدارة أو سعة الرعاية أو المواقع أو الساعات الإضافية أو الإعداد أو رسوم المورّد. يوضح المنشئ أساس الفوترة المختار، ويحدد العرض الموقع تواريخ الدفع وترتيب إصدار الفواتير.","url":"https://mansoq.com/faq?lang=ar#faq-annual-discount"},{"id":"setup-separate","question":"لماذا يسعّر الإعداد والترحيل مستقلاً عن السعر الشهري؟","answer":"الإعداد والترحيل مشروع إطلاق يتحدد جهده حسب بيانات المصدر وجودتها والواجهات والتدريب والمواقع وعمل الانتقال. تصف الباقة الشهرية الاستخدام المتكرر ورصيد الخدمة المستمرة المتفق عليه. يحتاج استيراد صغير ونظيف وترحيل معقد من أنظمة متعددة إلى نطاقي إطلاق مختلفين. أي نطاق سعر ظاهر للإعداد هو ميزانية تخطيط، ويعتمد النطاق النهائي كتابياً.","url":"https://mansoq.com/faq?lang=ar#faq-setup-separate"},{"id":"third-party-costs","question":"ما تكاليف المورّدين التي يجب أن أضع لها ميزانية؟","answer":"حسب اختيارك، ضع ميزانية للرسائل والفيديو والاتصالات والأجهزة وتراخيص الأنظمة الخارجية أو رسوم واجهاتها والبنية التي تملكها. حدد المورّد والمسؤول عن الدفع وحد الاستخدام ومتطلبات الموافقة قبل التفعيل. لا يعني شمول المسار أو صيانة الواجهة أن المورّد يوفر الأجهزة أو حركة الاتصال مجاناً.","url":"https://mansoq.com/faq?lang=ar#faq-third-party-costs"},{"id":"avoid-surprise-fees","question":"كيف أتجنب الرسوم غير المتوقعة؟","answer":"اطلب أن يفصل العرض السعة الأساسية وأسعار الوحدات والمواقع الإضافية والساعات المشمولة والإضافية المعتمدة والواجهات والإعداد والبنية واستخدام المورّد. حدد من يعتمد العمل الإضافي وكيف يبلّغ عن الاستخدام. تنص شروط التشغيل الروتيني على إشعارات عند استخدام ٨٠٪ و١٠٠٪ من رصيد الساعات وعلى الاعتماد قبل العمل الإضافي.","url":"https://mansoq.com/faq?lang=ar#faq-avoid-surprise-fees"},{"id":"monthly-contract","question":"هل يعني السعر الشهري تلقائياً عقداً يجدد كل شهر؟","answer":"لا تستنتج مدة العقد من سعر البطاقة. يحدد العرض والاتفاق الموقع المدة وجدول الدفع والتجديد والإشعار والإلغاء. اطلب من المبيعات بيان هذه الشروط صراحة قبل التوقيع، بما يشمل أثر السداد السنوي المسبق أو التنفيذ المرحلي على الالتزام.","url":"https://mansoq.com/faq?lang=ar#faq-monthly-contract"},{"id":"request-no-payment","question":"هل أدفع لبناء خطة أو طلب عرض؟","answer":"يتيح لك المنشئ مراجعة نطاق مقترح وطلب المساعدة دون دفع. لا يؤدي إرسال طلب عرض إلى تفعيل خدمة سريرية أو قبول عقد. راجع النطاق التجاري والتنفيذي المفصل ثم اتبع إجراءات القبول والدفع المتفق عليها إذا قررت المتابعة.","url":"https://mansoq.com/faq?lang=ar#faq-request-no-payment"},{"id":"regional-pricing","question":"هل يستطيع العملاء خارج السعودية طلب باقة؟","answer":"ناقش الدولة ومسار الرعاية وقواعد الفوترة وموقع البيانات والاستضافة والاتصالات المحلية المطلوبة مع المبيعات. يمثل الكتالوج السعودي نقطة بداية للنطاق وليس وعداً تلقائياً بجميع تكاملات الدول أو ترتيباتها الضريبية. يجب أن يوضح العرض الإقليمي العملة والمتطلبات المحلية والنشر وفترة الدعم.","url":"https://mansoq.com/faq?lang=ar#faq-regional-pricing"},{"id":"clinics-extra-rates","question":"ما تكلفة السعة والمواقع وساعات التشغيل الإضافية في العيادات؟","answer":"الأساسية: ‏١٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٤٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nبريميوم: ‏٢٠٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٦٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nالماسية: ‏٢٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٩٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nهذه الأسعار قبل الضريبة ولا تزيد بقية الأرصدة المشمولة. تحدد إضافات المؤسسات في عرض المبيعات. العمل المخصص والبنية ورسوم المورّد مستقلة.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-extra-rates"},{"id":"polyclinics-extra-rates","question":"ما تكلفة السعة والمواقع وساعات التشغيل الإضافية في المجمعات الطبية؟","answer":"الأساسية: ‏١٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏١٬٥٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nبريميوم: ‏٢٠٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٢٬٠٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nالماسية: ‏٢٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٣٬٠٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nهذه الأسعار قبل الضريبة ولا تزيد بقية الأرصدة المشمولة. تحدد إضافات المؤسسات في عرض المبيعات. العمل المخصص والبنية ورسوم المورّد مستقلة.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-extra-rates"},{"id":"teleicu-extra-rates","question":"ما تكلفة السعة والمواقع وساعات التشغيل الإضافية في العناية المركزة عن بُعد؟","answer":"الأساسية: ‏٢٠٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏١٬٥٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏٢٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nبريميوم: ‏٣٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٢٬٥٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏٢٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nالماسية: ‏٥٠٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٤٬٠٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏٢٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nهذه الأسعار قبل الضريبة ولا تزيد بقية الأرصدة المشمولة. تحدد إضافات المؤسسات في عرض المبيعات. العمل المخصص والبنية ورسوم المورّد مستقلة.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-extra-rates"},{"id":"home_palliative-extra-rates","question":"ما تكلفة السعة والمواقع وساعات التشغيل الإضافية في الرعاية المنزلية والتلطيفية؟","answer":"الأساسية: ‏٢٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٧٥٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nبريميوم: ‏٣٥٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏١٬٢٥٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nالماسية: ‏٥٠٫٠٠ ر.س.‏ لكل وحدة رعاية إضافية شهرياً؛ ‏٢٬٠٠٠٫٠٠ ر.س.‏ لكل موقع إضافي شهرياً؛ ‏١٨٠٫٠٠ ر.س.‏ لكل ساعة تشغيل إضافية معتمدة.\n\nهذه الأسعار قبل الضريبة ولا تزيد بقية الأرصدة المشمولة. تحدد إضافات المؤسسات في عرض المبيعات. العمل المخصص والبنية ورسوم المورّد مستقلة.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-extra-rates"},{"id":"annual-price-worked-example","question":"هل توضح مثالاً حسابياً للسداد السنوي المسبق؟","answer":"مثال توضيحي باستخدام سعر بريميوم للعيادات المنشور: ‏١٬٠٩٠٫٠٠ ر.س.‏ للبرنامج الأساسي + ‏٩٠٠٫٠٠ ر.س.‏ للتشغيل المدار = ‏١٬٩٩٠٫٠٠ ر.س.‏ شهرياً قبل الضريبة.\n\nمع السداد السنوي للبرنامج، يصبح الإجمالي الأساسي المكافئ شهرياً ‏١٬٨٨١٫٠٠ ر.س.‏ ومكافئ السنة المتكررة ‏٢٢٬٥٧٢٫٠٠ ر.س.‏. يحصل البرنامج وحده على الخصم المنشور. تضاف الإضافات المعتمدة والإعداد والضريبة ورسوم المورّد، ويتبع توقيت الفاتورة العقد.","url":"https://mansoq.com/faq?lang=ar#faq-annual-price-worked-example"},{"id":"extra-capacity-worked-example","question":"هل توضح احتساب السعة الإضافية وموقع ثانٍ وساعات إضافية؟","answer":"مثال تركيب توضيحي لبريميوم للعيادات: 152 وحدة ممارس وموقعان وساعة تشغيل إضافية معتمدة.\n\nالأساس ‏١٬٩٩٠٫٠٠ ر.س.‏ + وحدتا رعاية إضافيتان ‏٤٠٠٫٠٠ ر.س.‏ + موقع إضافي ‏٦٠٠٫٠٠ ر.س.‏ + ساعة إضافية ‏١٨٠٫٠٠ ر.س.‏ = ‏٣٬١٧٠٫٠٠ ر.س.‏ شهرياً قبل الضريبة والإعداد وتكاليف المورّد.\n\nلا تضيف زيادة وحدات الرعاية ساعات أو واجهات. تحتاج التغييرات الفعلية إلى اعتماد والعرض المقبول.","url":"https://mansoq.com/faq?lang=ar#faq-extra-capacity-worked-example"},{"id":"capacity-measures","question":"لماذا تستخدم المنتجات مقاييس مختلفة للسعة؟","answer":"تحتسب العيادات والمجمعات الممارسين المستقلين المسمّين، والعناية عن بُعد أسرّة العناية المفعّلة، والرعاية المنزلية والتلطيفية المرضى النشطين الفريدين خلال الشهر. تعكس هذه المقاييس عمل كل بيئة رعاية. لا تعني وحدة الرعاية زيارة أو تسجيل دخول أو نوبة ما لم يحدد العقد المقبول ذلك صراحة.","url":"https://mansoq.com/faq?lang=ar#faq-capacity-measures"},{"id":"clinician-counting","question":"هل يستهلك التمريض والاستقبال والإدارة سعة الممارسين؟","answer":"يحتسب مقياس الممارسين الأشخاص المستقلين المسمّين الذين يقدمون الرعاية. لا تضيف حسابات التمريض المساعد والإدارة والدعم رسماً للممارسين وفق هذا التعريف. مثلاً، يستهلك ٢٠ ممارساً مستقلاً وخمسة حسابات استقبال ٢٠ وحدة ممارس. اتفق على هويات الممارسين والصلاحيات؛ ولا يعد هذا التعريف بحسابات أو موارد بنية غير محدودة.","url":"https://mansoq.com/faq?lang=ar#faq-clinician-counting"},{"id":"icu-counting","question":"هل تحتسب أسرة العناية عن بُعد عند إشغالها فقط؟","answer":"المقياس هو سرير عناية مفعّل ومقبول ضمن العقد، وليس عدد الأسرة المشغولة يومياً. مثلاً، تستهلك ٥٠ سريراً مفعلاً ٥٠ وحدة حتى إذا تغير الإشغال. حدد المواقع والأسرة المقبولة والمفعّلة وما يخرج من الخدمة لاحقاً ليظل الاحتساب المتعاقد عليه واضحاً.","url":"https://mansoq.com/faq?lang=ar#faq-icu-counting"},{"id":"home-patient-counting","question":"هل تحتسب كل زيارة منزلية كمريض إضافي؟","answer":"لا. يحتسب المريض الفريد الذي لديه زيارة متعاقد عليها مكتملة أو حلقة رعاية عن بُعد نشطة مرة واحدة خلال الشهر عبر الفروع المتعاقد عليها. تبقى أربع زيارات للمريض نفسه مريضاً نشطاً واحداً. لا يستمر احتساب المرضى المؤرشفين أو المتوفين وفق التعريف المنشور؛ اتفق على التسوية وسجلات النشاط قبل الفوترة.","url":"https://mansoq.com/faq?lang=ar#faq-home-patient-counting"},{"id":"capacity-not-hours","question":"هل تزيد ساعات التشغيل عند إضافة مرضى أو ممارسين أو أسرّة؟","answer":"لا تزيد وحدات الرعاية والمواقع الإضافية ساعات التشغيل أو الواجهات المصانة تلقائياً، فهذه أرصدة مستقلة. مثلاً، قد يحتاج عدد أكبر من مرضى الرعاية المنزلية إلى سعة مرضى إضافية ودعم إضافي متفق عليه للتنسيق؛ ويحتاج الجزء الثاني إلى نطاق ساعات خاص به. يجب أن يفصل العرض كل تغيير.","url":"https://mansoq.com/faq?lang=ar#faq-capacity-not-hours"},{"id":"sites-definition","question":"ماذا يعني شمول موقع واحد؟","answer":"تشمل الباقات غير المؤسسية منشأة أو فرعاً واحداً ضمن حدود البيانات المتعاقد عليها. تسعّر المواقع الإضافية مستقلاً وتحتاج صلاحيات وسعة وإعداداً متفقاً عليه. قد يحتاج كيان قانوني مستقل أو فصل بيانات المرضى إلى عرض مؤسسات بدلاً من رسم موقع إضافي فقط.","url":"https://mansoq.com/faq?lang=ar#faq-sites-definition"},{"id":"growth-planning","question":"ماذا أفعل عندما نقترب من سعة الباقة؟","answer":"راجع الاستخدام الفعلي للرعاية وعبء التشغيل واحتياجات الواجهات معاً. قارن السعة الإضافية المعتمدة بالباقة التالية بدلاً من النظر إلى سعر الوحدة وحده. اتفق على تغيير السعة وتاريخ تطبيقه والرسوم الناتجة قبل الاستخدام. يجب أن يشمل التغيير استمرارية الرعاية والصلاحيات وتسوية الفوترة.","url":"https://mansoq.com/faq?lang=ar#faq-growth-planning"},{"id":"enterprise-reference-capacity","question":"هل تعني السعة المرجعية للمؤسسات استخداماً غير محدود؟","answer":"تشير علامة «+» إلى نشر أكبر يحدد نطاقه مع المبيعات، وليست رصيداً غير محدود أو حداً أدنى تلقائياً للشراء. يحدد العرض وحدات الرعاية والمواقع والمستخدمين والواجهات والتشغيل المدار وحدود البنية الفعلية. استخدم الرقم المرجعي لبدء تحديد حجم احتياج المؤسسة بدقة.","url":"https://mansoq.com/faq?lang=ar#faq-enterprise-reference-capacity"},{"id":"current-capacity-ladder","question":"كم تبلغ سعة الرعاية المشمولة في كل باقة؟","answer":"العيادات: الأساسية ٥٠ ممارسون سريريون نشطون؛ بريميوم ١٥٠ ممارسون سريريون نشطون؛ الماسية ٢٥٠ ممارسون سريريون نشطون؛ المؤسسات ٥٥٠+ ممارسون سريريون نشطون\n\nالمجمعات الطبية: الأساسية ٥٠ ممارسون سريريون نشطون؛ بريميوم ١٥٠ ممارسون سريريون نشطون؛ الماسية ٢٥٠ ممارسون سريريون نشطون؛ المؤسسات ٥٥٠+ ممارسون سريريون نشطون\n\nالعناية المركزة عن بُعد: الأساسية ٥٠ أسرّة عناية مفعّلة؛ بريميوم ١٥٠ أسرّة عناية مفعّلة؛ الماسية ٢٥٠ أسرّة عناية مفعّلة؛ المؤسسات ٥٥٠+ أسرّة عناية مفعّلة\n\nالرعاية المنزلية والتلطيفية: الأساسية ٥٠ مرضى نشطون شهرياً؛ بريميوم ١٥٠ مرضى نشطون شهرياً؛ الماسية ٢٥٠ مرضى نشطون شهرياً؛ المؤسسات ٥٥٠+ مرضى نشطون شهرياً\n\nتشمل الباقات غير المؤسسية موقعاً واحداً. سعة المؤسسات مرجع لتحديد الحجم وتتفق حدودها الفعلية مع المبيعات. استخدم تعريف الاحتساب الخاص بالمنتج وطابق السعة المقبولة قبل الفوترة.","url":"https://mansoq.com/faq?lang=ar#faq-current-capacity-ladder"},{"id":"clinic-day","question":"كيف تسير زيارة العيادة من البداية إلى النهاية؟","answer":"ضمن المسار المقبول، يحدد الاستقبال الموعد ويسجل المريض ويوثق الممارس الاستشارة والطلبات، ثم يعد الفريق المصرح له الفوترة النقدية أو التأمينية والمتابعة. يربط سياق المريض والزيارة المشترك هذه الخطوات. مثلاً، تظل بيانات التأمين الناقصة مهمة تشغيلية ظاهرة بدلاً من ضياعها بعد الاستشارة.","url":"https://mansoq.com/faq?lang=ar#faq-clinic-day"},{"id":"clinic-cash-insurance","question":"هل تدعم باقة العيادات المرضى النقديين ومسارات التأمين معاً؟","answer":"يشمل نطاق العيادات المتعاقد عليه مسارات النقد والتأمين. حدد الخدمات والتعرفة وجهات التأمين ومتطلبات الموافقة والاتصالات الوطنية المنطبقة أثناء الإعداد. تساعد المنصة على ربط الرعاية الموثقة بالفوترة ومتابعة التأمين؛ وتعتمد الموافقة والتحصيل على الأدلة الصحيحة والأهلية والعقود ورد جهة التأمين.","url":"https://mansoq.com/faq?lang=ar#faq-clinic-cash-insurance"},{"id":"clinic-reminders","question":"كيف تستفيد العيادة من التذكير واستدعاء المرضى للمتابعة؟","answer":"تضيف بريميوم وما فوقها أتمتة التذكير والمتابعة المتفق عليها. حدد المتابعات التي تحتاج مهمة أو رسالة والمسؤول عن القائمة وكيف تعالج الموافقة وبيانات الاتصال. مثلاً، تساعد قائمة متابعة معتمدة الاستقبال على معرفة من يتواصل معه لاحقاً. لا يضمن ذلك تسليم الرسالة أو الحضور أو المتابعة السريرية، ويحدد استخدام المورّد مستقلاً.","url":"https://mansoq.com/faq?lang=ar#faq-clinic-reminders"},{"id":"clinic-departments","question":"هل تستطيع العيادة إضافة مختبر أو صيدلية أو أقسام أخرى لاحقاً؟","answer":"استخدم المنشئ المخصص أو ناقش التوسع مع المبيعات. تحتاج الأقسام الإضافية إلى نطاق وحداتها المقبول ومتطلباتها وإعدادها وصلاحياتها وأي اتصالات خارجية. لا تفترض أن باقة العيادات تشمل كل أقسام المستشفى. إذا كانت التخصصات ومسارات الأقسام المتعددة أساس عملك، فقارن نطاق المجمعات الطبية.","href":"/pricing/capabilities","url":"https://mansoq.com/faq?lang=ar#faq-clinic-departments"},{"id":"clinics-rcm-raas","question":"كيف تسعّر خدمة RaaS في العيادات؟","answer":"الأساسية: ١٨٪؛ بريميوم: ١٥٪؛ الماسية: ١٠٪؛ المؤسسات: ٤٫٥٪–٧٫٥٪. تطبق هذه النسب على التحصيل المحقق المؤهل والمعتمد وتضاف إلى الاشتراك. تتطلب المؤسسات نسبة محددة معتمدة ضمن النطاق ونطاقاً مقبولاً. تحتسب الرسوم الفعلية من الأدلة المالية المراجعة بعد المبالغ المستردة والاستبعادات المتفق عليها؛ لا ينشئ التقدير في المنشئ فاتورة.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-rcm-raas"},{"id":"clinics-prices","question":"ما أسعار العيادات المنشورة؟","answer":"الأساسية: ‏٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٦٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٣٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 50 ممارسون سريريون نشطون وموقعاً واحداً.\n\nبريميوم: ‏١٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏١٬٠٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٩٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 150 ممارسون سريريون نشطون وموقعاً واحداً.\n\nالماسية: ‏٣٬٤٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏١٬٦٩٠٫٠٠ ر.س.‏ للبرنامج + ‏١٬٨٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 250 ممارسون سريريون نشطون وموقعاً واحداً.\n\nالمؤسسات: يحدد السعر ونطاق التشغيل الفعلي في عرض المبيعات.\n\nكل المبالغ العامة قبل الضريبة. نطاق ميزانية الإعداد والترحيل استرشادي، ويتبع السعر النهائي بيان العمل. تحدد الإضافات وتكاليف المورّد بشكل مستقل. السعر غير المعتمد ليس عرضاً عاماً.","href":"/pricing#care-packages","url":"https://mansoq.com/faq?lang=ar#faq-clinics-prices"},{"id":"clinics-tier-benefits","question":"ما الذي يتغير بين باقات العيادات؟","answer":"الأساسية: أكمل مسار الرعاية. مسار المواعيد والاستشارة والإحالة والنقد والتأمين مع تقارير التشغيل الأساسية.\n\nبريميوم: قلل العمل المتكرر واكتشف الاستثناءات مبكراً. مسار المواعيد والاستشارة والإحالة والنقد والتأمين مع تقارير التشغيل الأساسية. أتمتة التذكير والمتابعة وقوائم الأهلية والموافقات وتحليل الرفض والتحسين الشهري مع مختص.\n\nالماسية: حدد مسؤولاً عن قوائم التشغيل المتفق عليها. مسار المواعيد والاستشارة والإحالة والنقد والتأمين مع تقارير التشغيل الأساسية. أتمتة التذكير والمتابعة وقوائم الأهلية والموافقات وتحليل الرفض والتحسين الشهري مع مختص. مسؤول محدد لقوائم المطالبات والمتابعة المتفق عليها ومتابعة الاستثناءات ومراجعة شهرية للتحصيل والأداء. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nالمؤسسات: حوكم الرعاية والتشغيل على مستوى المؤسسة. مسار المواعيد والاستشارة والإحالة والنقد والتأمين مع تقارير التشغيل الأساسية. أتمتة التذكير والمتابعة وقوائم الأهلية والموافقات وتحليل الرفض والتحسين الشهري مع مختص. مسؤول محدد لقوائم المطالبات والمتابعة المتفق عليها ومتابعة الاستثناءات ومراجعة شهرية للتحصيل والأداء. حوكمة المجموعة وصلاحيات حسب الكيان وتقارير موحدة وتكاملات ونطاق تشغيل متفق عليه. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nتحتفظ الباقات الأعلى بأساس الرعاية المتعاقد عليه. أرصدة السعة والساعات والواجهات مستقلة، ويحدد العرض المقبول نطاق التشغيل الحي.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-tier-benefits"},{"id":"clinics-care-workflow-example","question":"العيادات: كيف يعمل مسار الرعاية الأساسي وما فائدته؟","answer":"المعنى: مسار الرعاية اليومي في نظام واحد: المواعيد وسجل المريض والتوثيق السريري والطلبات والفوترة.\n\nطريقة العمل: يحجز الاستقبال الزيارة، ويوثق الممارس الرعاية، ويستخدم موظفو الفوترة المصرح لهم الخدمات المسجلة لإعداد الفاتورة أو مسار التأمين.\n\nمثال: يحجز المريض استشارة. يوثق الطبيب الزيارة ويطلب فحصاً، ثم يعد موظف الفوترة الرسوم المتفق عليها من الزيارة نفسها.\n\nالفائدة والنتيجة المتوقعة: إدخال متكرر أقل وسهولة تتبع الموعد وسجل الرعاية والرسوم معاً.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-care-workflow-example"},{"id":"clinics-automation-example","question":"العيادات: كيف تعمل الأتمتة في بيئة الرعاية هذه؟","answer":"المعنى: تتبع الخطوات الروتينية قواعد متفقاً عليها، وتظهر الحالات التي تحتاج تدخلاً بشرياً في قائمة عمل مشتركة.\n\nطريقة العمل: تحدد نقطة بدء المسار والخطوة التالية والدور المسؤول. عند نقص متطلب أو تعثر مهمة، تحول إلى الفريق المناسب للمراجعة.\n\nمثال: تكون الزيارة جاهزة للفوترة، لكن بيانات تأمين ناقصة. تنتقل الحالة إلى قائمة متابعة فريق الفوترة لتبقى واضحة بين الزيارات المكتملة.\n\nالفائدة والنتيجة المتوقعة: مهام منسية أقل ووقت أقل للبحث عن الإجراء التالي. يراجع فريقك الاستثناءات ويعالجها.\n\nالنطاق: تضبط قواعد الأتمتة لمسارك المعتمد؛ ولا تضمن موافقة شركة التأمين أو السداد.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-automation-example"},{"id":"clinics-named-owner-example","question":"العيادات: ماذا ينفذ المسؤول المحدد في بيئة الرعاية هذه؟","answer":"المعنى: مسؤول تشغيل محدد من منسوق يتولى متابعة قوائم العمل غير السريرية المتفق عليها.\n\nطريقة العمل: تحدد قائمة العمل والإجراءات ومسار التصعيد. يراجع المسؤول العمل المعلق وينسق مع فريقك ويسجل التقدم ضمن رصيد ساعات التشغيل المشمول.\n\nمثال: ينقص مهمة فوترة توثيق. ينسق المسؤول مع فريق الفوترة لديك ويسجل الإجراء التالي ويتابع تقدمه.\n\nالفائدة والنتيجة المتوقعة: مسؤولية أوضح وتنقل أقل بين جهات الاتصال، مع سجل ظاهر للمتابعة.\n\nالنطاق: يعمل المسؤول ضمن فترة الخدمة والساعات المتفق عليها. تحتاج إدارة الفوترة الخارجية الكاملة والعمل غير المحدود بالقوائم والكادر السريري إلى نطاق مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-clinics-named-owner-example"},{"id":"polyclinic-clinic-difference","question":"ما الفرق بين منتج المجمعات الطبية والعيادات؟","answer":"تضيف المجمعات السجلات المشتركة للعيادات والإحالات بين التخصصات مع نطاق الصيدلية والمختبر والمخزون وفوترة الأقسام المتعاقد عليه. تركز تشغيلياً على التسليم بين الفرق. مثلاً، يطلب الممارس خدمة مختبر مقبولة وتبقى النتيجة مرتبطة بالمريض وتدعم الخدمة الموثقة مسار الفوترة المصرح به.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinic-clinic-difference"},{"id":"cross-specialty-access","question":"هل يستطيع الاختصاصيون مشاركة سجل المريض دون وصول غير مقيد للجميع؟","answer":"تحكم الأدوار والمنشآت وحدود البيانات المعتمدة سياق الرعاية المشترك. حدد من الممارسين وفرق الأقسام يستطيع قراءة الأجزاء المطلوبة أو تحديثها ثم اختبر الصلاحيات قبل الإطلاق. تكون الفائدة إحالة أو تسليماً أكثر ترابطاً مع حفظ المسؤولية. تحتاج الكيانات القانونية المستقلة إلى نطاق مشاركة ونشر متفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-cross-specialty-access"},{"id":"polyclinic-stock","question":"ما فائدة ربط الصيدلية والمختبر والمخزون؟","answer":"تربط مسارات الأقسام المقبولة طلبات الخدمات والنتائج أو نشاط الأدوية بالمريض وبأدلة المخزون والرسوم المرتبطة. يساعد ذلك الفرق على متابعة ما طلب ونفذ ووثق. تضيف بريميوم أتمتة التسليم وتنبيهات المخزون والصلاحية وتقارير المساهمة المتفق عليها. تعتمد البيانات وإعداد الكتالوج واتصالات الأجهزة أثناء التنفيذ.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinic-stock"},{"id":"polyclinic-charge-leakage","question":"كيف تساعد الماسية في استثناءات الأقسام والرسوم غير المسجلة؟","answer":"اتفق مع مسؤول التشغيل المحدد على قوائم استثناءات أو إيرادات محددة. ينسق المسؤول التوثيق أو التسليم أو مشكلات أدلة الرسوم المعلقة ويسجل التقدم ضمن الساعات المشمولة. تساعد المراجعة الشهرية على تحديد الأسباب المتكررة وإسناد الإجراءات. هي خدمة متابعة محددة، وليست ضماناً لاسترداد كل رسم محتمل لم يسجل.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinic-charge-leakage"},{"id":"polyclinics-rcm-raas","question":"كيف تسعّر خدمة RaaS في المجمعات الطبية؟","answer":"الأساسية: ١٨٪؛ بريميوم: ١٥٪؛ الماسية: ١٠٪؛ المؤسسات: ٤٫٥٪–٧٫٥٪. تطبق هذه النسب على التحصيل المحقق المؤهل والمعتمد وتضاف إلى الاشتراك. تتطلب المؤسسات نسبة محددة معتمدة ضمن النطاق ونطاقاً مقبولاً. تحتسب الرسوم الفعلية من الأدلة المالية المراجعة بعد المبالغ المستردة والاستبعادات المتفق عليها؛ لا ينشئ التقدير في المنشئ فاتورة.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-rcm-raas"},{"id":"polyclinics-prices","question":"ما أسعار المجمعات الطبية المنشورة؟","answer":"الأساسية: ‏٢٬٤٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏١٬٤٩٠٫٠٠ ر.س.‏ للبرنامج + ‏١٬٠٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 50 ممارسون سريريون نشطون وموقعاً واحداً.\n\nبريميوم: ‏٤٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٢٬٧٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٢٬٢٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 150 ممارسون سريريون نشطون وموقعاً واحداً.\n\nالماسية: ‏٨٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٤٬٤٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٤٬٥٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 250 ممارسون سريريون نشطون وموقعاً واحداً.\n\nالمؤسسات: يحدد السعر ونطاق التشغيل الفعلي في عرض المبيعات.\n\nكل المبالغ العامة قبل الضريبة. نطاق ميزانية الإعداد والترحيل استرشادي، ويتبع السعر النهائي بيان العمل. تحدد الإضافات وتكاليف المورّد بشكل مستقل. السعر غير المعتمد ليس عرضاً عاماً.","href":"/pricing#care-packages","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-prices"},{"id":"polyclinics-tier-benefits","question":"ما الذي يتغير بين باقات المجمعات الطبية؟","answer":"الأساسية: أكمل مسار الرعاية. سجلات مشتركة للعيادات وإحالات بين التخصصات وصيدلية ومختبر ومخزون وفوترة الأقسام.\n\nبريميوم: قلل العمل المتكرر واكتشف الاستثناءات مبكراً. سجلات مشتركة للعيادات وإحالات بين التخصصات وصيدلية ومختبر ومخزون وفوترة الأقسام. أتمتة تسليم الأقسام ومراجعة التعرفة والرفض وتنبيهات المخزون والصلاحية وتقارير مساهمة الخدمات.\n\nالماسية: حدد مسؤولاً عن قوائم التشغيل المتفق عليها. سجلات مشتركة للعيادات وإحالات بين التخصصات وصيدلية ومختبر ومخزون وفوترة الأقسام. أتمتة تسليم الأقسام ومراجعة التعرفة والرفض وتنبيهات المخزون والصلاحية وتقارير مساهمة الخدمات. مسؤول تشغيل محدد لاستثناءات الأقسام وتسرب الإيرادات وقوائم الإيرادات المتفق عليها مع مراجعة إدارية شهرية. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nالمؤسسات: حوكم الرعاية والتشغيل على مستوى المؤسسة. سجلات مشتركة للعيادات وإحالات بين التخصصات وصيدلية ومختبر ومخزون وفوترة الأقسام. أتمتة تسليم الأقسام ومراجعة التعرفة والرفض وتنبيهات المخزون والصلاحية وتقارير مساهمة الخدمات. مسؤول تشغيل محدد لاستثناءات الأقسام وتسرب الإيرادات وقوائم الإيرادات المتفق عليها مع مراجعة إدارية شهرية. حوكمة المجموعة وصلاحيات حسب الكيان وتقارير موحدة وتكاملات ونطاق تشغيل متفق عليه. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nتحتفظ الباقات الأعلى بأساس الرعاية المتعاقد عليه. أرصدة السعة والساعات والواجهات مستقلة، ويحدد العرض المقبول نطاق التشغيل الحي.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-tier-benefits"},{"id":"polyclinics-care-workflow-example","question":"المجمعات الطبية: كيف يعمل مسار الرعاية الأساسي وما فائدته؟","answer":"المعنى: مسار الرعاية اليومي في نظام واحد: المواعيد وسجل المريض والتوثيق السريري والطلبات والفوترة.\n\nطريقة العمل: يحجز الاستقبال الزيارة، ويوثق الممارس الرعاية، ويستخدم موظفو الفوترة المصرح لهم الخدمات المسجلة لإعداد الفاتورة أو مسار التأمين.\n\nمثال: يحجز المريض استشارة. يوثق الطبيب الزيارة ويطلب فحصاً، ثم يعد موظف الفوترة الرسوم المتفق عليها من الزيارة نفسها.\n\nالفائدة والنتيجة المتوقعة: إدخال متكرر أقل وسهولة تتبع الموعد وسجل الرعاية والرسوم معاً.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-care-workflow-example"},{"id":"polyclinics-automation-example","question":"المجمعات الطبية: كيف تعمل الأتمتة في بيئة الرعاية هذه؟","answer":"المعنى: تتبع الخطوات الروتينية قواعد متفقاً عليها، وتظهر الحالات التي تحتاج تدخلاً بشرياً في قائمة عمل مشتركة.\n\nطريقة العمل: تحدد نقطة بدء المسار والخطوة التالية والدور المسؤول. عند نقص متطلب أو تعثر مهمة، تحول إلى الفريق المناسب للمراجعة.\n\nمثال: تكون الزيارة جاهزة للفوترة، لكن بيانات تأمين ناقصة. تنتقل الحالة إلى قائمة متابعة فريق الفوترة لتبقى واضحة بين الزيارات المكتملة.\n\nالفائدة والنتيجة المتوقعة: مهام منسية أقل ووقت أقل للبحث عن الإجراء التالي. يراجع فريقك الاستثناءات ويعالجها.\n\nالنطاق: تضبط قواعد الأتمتة لمسارك المعتمد؛ ولا تضمن موافقة شركة التأمين أو السداد.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-automation-example"},{"id":"polyclinics-named-owner-example","question":"المجمعات الطبية: ماذا ينفذ المسؤول المحدد في بيئة الرعاية هذه؟","answer":"المعنى: مسؤول تشغيل محدد من منسوق يتولى متابعة قوائم العمل غير السريرية المتفق عليها.\n\nطريقة العمل: تحدد قائمة العمل والإجراءات ومسار التصعيد. يراجع المسؤول العمل المعلق وينسق مع فريقك ويسجل التقدم ضمن رصيد ساعات التشغيل المشمول.\n\nمثال: ينقص مهمة فوترة توثيق. ينسق المسؤول مع فريق الفوترة لديك ويسجل الإجراء التالي ويتابع تقدمه.\n\nالفائدة والنتيجة المتوقعة: مسؤولية أوضح وتنقل أقل بين جهات الاتصال، مع سجل ظاهر للمتابعة.\n\nالنطاق: يعمل المسؤول ضمن فترة الخدمة والساعات المتفق عليها. تحتاج إدارة الفوترة الخارجية الكاملة والعمل غير المحدود بالقوائم والكادر السريري إلى نطاق مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-polyclinics-named-owner-example"},{"id":"teleicu-team-model","question":"هل تشمل العناية عن بُعد اختصاصيي عناية أو تمريضاً بجانب المريض؟","answer":"يوفر العميل الممارسين المرخصين عن بُعد وبجانب المريض والقرارات السريرية وتغطية التصعيد والحوكمة الطبية. توفر منسوق التقنية ودعم التشغيل غير السريري المتعاقد عليه. لا تعني سعة الأسرة المفعّلة شراء نوبات الكادر أو مراقبة الإنذارات السريرية المستمرة أو كادر الاستجابة للطوارئ.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-team-model"},{"id":"teleicu-essential-data","question":"هل تعمل الأساسية للعناية عن بُعد قبل ربط بيانات الأجهزة تلقائياً؟","answer":"يقوم نطاق الأساسية على الاستشارات الآمنة والبيانات المدخلة يدوياً أو الموثقة والتسليم والتصعيد وإجراءات التوقف. حدد المعلومات التي يحتاجها الممارسون ومن يدخلها وكيف يتحققون من وقتها ومصدرها. لا ينبغي عرض سجل يتضمن بيانات يدوية على أنه تدفق مباشر من أجهزة المراقبة.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-essential-data"},{"id":"teleicu-interface-examples","question":"ما الأنظمة التي يمكن ربطها بالعناية عن بُعد؟","answer":"من الأمثلة بيانات الدخول أو السجل الطبي وأجهزة المراقبة والتنفس الصناعي ونتائج المختبر ضمن رصيد الواجهات المصانة المختار. يحتاج كل اتصال إلى مصدر مصرح به وصيغة مدعومة وربط حقول ومطابقة المريض والسرير وفحص الحداثة واختبارات مقبولة. رصيد الباقة حد للنطاق، ولا يعني أن كل جهاز من كل مورّد مفعّل بالفعل.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-interface-examples"},{"id":"teleicu-stale-data","question":"كيف تعالج بيانات العناية القديمة أو المنقطعة؟","answer":"تعد ضوابط حداثة البيانات والانقطاع جزءاً من المسار المتصل المقبول. حدد كيف يتعرف الفريق على البيانات القديمة أو غير المتاحة ويتحقق من المعلومات الحالية ويستخدم إجراء التوقف. يجب ألا يعتمد الفريق السريري على قيمة قديمة باعتبارها حالية. تجرّب إجراءات التصعيد والتوثيق البديل والمسؤولية قبل الإطلاق السريري.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-stale-data"},{"id":"teleicu-alert-responsibility","question":"من يستجيب لإنذارات العناية أو التدهور السريري العاجل؟","answer":"تحدد مؤسستك السريرية المرخصة هذه الاستجابة وتوفرها. اعتمد تسلسل التصعيد بجانب المريض وعن بُعد وتغطية الاستجابة ومسار الطوارئ تحت الحوكمة الطبية لديك. لا تحل ساعات التشغيل المدارة أو مسؤول المسار التقني المحدد محل مراقبة الإنذارات السريرية أو فريق رعاية الطوارئ.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-alert-responsibility"},{"id":"teleicu-equipment","question":"هل تشمل الباقة الكاميرات وأجهزة المراقبة والحضور عن بُعد والاتصال؟","answer":"تكون الأجهزة والحضور عن بُعد والاتصال مملوكة للعميل أو مسعّرة بعرض مستقل. راجع توافق الأجهزة والصلاحيات وعرض الاتصال والصيانة والطاقة والاستعادة مع الفريقين التقني والسريري. تصف الباقة نطاق تقنية وتشغيل، ويجب أن يحدد العرض مسؤوليات الأجهزة والاتصالات اللازمة لتشغيله.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-equipment"},{"id":"teleicu-value","question":"ما الفائدة العملية المتوقعة لفريق العناية عن بُعد؟","answer":"الفائدة المقصودة هي توثيق أوضح للاستشارات وتسليم أكثر اتساقاً ومسار متابعة متفق عليه وظاهر. قد تقلل الاتصالات المقبولة تكرار جمع المعلومات، وتسهل المتابعة التشغيلية المحددة تتبع المهام التقنية المعلقة. قس التغيير مقابل خط الأساس لديك. تعتمد النتائج السريرية على الممارسين والبروتوكولات وجودة البيانات وبيئة تقديم الرعاية.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-value"},{"id":"teleicu-rcm-raas","question":"كيف تسعّر خدمة RaaS في العناية المركزة عن بُعد؟","answer":"الأساسية: ١٨٪؛ بريميوم: ١٥٪؛ الماسية: ١٠٪؛ المؤسسات: ٤٫٥٪–٧٫٥٪. تطبق هذه النسب على التحصيل المحقق المؤهل والمعتمد وتضاف إلى الاشتراك. تتطلب المؤسسات نسبة محددة معتمدة ضمن النطاق ونطاقاً مقبولاً. تحتسب الرسوم الفعلية من الأدلة المالية المراجعة بعد المبالغ المستردة والاستبعادات المتفق عليها؛ لا ينشئ التقدير في المنشئ فاتورة.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-rcm-raas"},{"id":"teleicu-prices","question":"ما أسعار العناية المركزة عن بُعد المنشورة؟","answer":"الأساسية: ‏٦٬٥٠٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٤٬٥٠٠٫٠٠ ر.س.‏ للبرنامج + ‏٢٬٠٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 50 أسرّة عناية مفعّلة وموقعاً واحداً.\n\nبريميوم: ‏١٢٬٥٠٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٨٬٥٠٠٫٠٠ ر.س.‏ للبرنامج + ‏٤٬٠٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 150 أسرّة عناية مفعّلة وموقعاً واحداً.\n\nالماسية: ‏٢٢٬٠٠٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏١٤٬٠٠٠٫٠٠ ر.س.‏ للبرنامج + ‏٨٬٠٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 250 أسرّة عناية مفعّلة وموقعاً واحداً.\n\nالمؤسسات: يحدد السعر ونطاق التشغيل الفعلي في عرض المبيعات.\n\nكل المبالغ العامة قبل الضريبة. نطاق ميزانية الإعداد والترحيل استرشادي، ويتبع السعر النهائي بيان العمل. تحدد الإضافات وتكاليف المورّد بشكل مستقل. السعر غير المعتمد ليس عرضاً عاماً.","href":"/pricing#care-packages","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-prices"},{"id":"teleicu-tier-benefits","question":"ما الذي يتغير بين باقات العناية المركزة عن بُعد؟","answer":"الأساسية: أكمل مسار الرعاية. مسار استشارات آمن للعناية المركزة عن بُعد مع بيانات مدخلة يدوياً وتسليم وتصعيد وإجراءات التوقف.\n\nبريميوم: قلل العمل المتكرر واكتشف الاستثناءات مبكراً. مسار استشارات آمن للعناية المركزة عن بُعد مع بيانات مدخلة يدوياً وتسليم وتصعيد وإجراءات التوقف. واجهتان للبيانات مقبولتان مثل الدخول والسجل الطبي والمراقبة؛ مع ضبط حداثة البيانات والانقطاع وتحسين المسار مع مختص.\n\nالماسية: حدد مسؤولاً عن قوائم التشغيل المتفق عليها. مسار استشارات آمن للعناية المركزة عن بُعد مع بيانات مدخلة يدوياً وتسليم وتصعيد وإجراءات التوقف. واجهتان للبيانات مقبولتان مثل الدخول والسجل الطبي والمراقبة؛ مع ضبط حداثة البيانات والانقطاع وتحسين المسار مع مختص. أربع واجهات مقبولة مثل الدخول والمراقبة والتنفس الصناعي والمختبر؛ ومسؤول محدد للمسار التقني ومراجعة الاستثناءات. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nالمؤسسات: حوكم الرعاية والتشغيل على مستوى المؤسسة. مسار استشارات آمن للعناية المركزة عن بُعد مع بيانات مدخلة يدوياً وتسليم وتصعيد وإجراءات التوقف. واجهتان للبيانات مقبولتان مثل الدخول والسجل الطبي والمراقبة؛ مع ضبط حداثة البيانات والانقطاع وتحسين المسار مع مختص. أربع واجهات مقبولة مثل الدخول والمراقبة والتنفس الصناعي والمختبر؛ ومسؤول محدد للمسار التقني ومراجعة الاستثناءات. حوكمة المجموعة وصلاحيات حسب الكيان وتقارير موحدة وتكاملات ونطاق تشغيل متفق عليه. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nتحتفظ الباقات الأعلى بأساس الرعاية المتعاقد عليه. أرصدة السعة والساعات والواجهات مستقلة، ويحدد العرض المقبول نطاق التشغيل الحي.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-tier-benefits"},{"id":"teleicu-care-workflow-example","question":"العناية المركزة عن بُعد: كيف يعمل مسار الرعاية الأساسي وما فائدته؟","answer":"المعنى: سجل مشترك لاستشارات العناية المركزة عن بُعد وخطط الرعاية وتسليم الحالات بين الفرق.\n\nطريقة العمل: يسجل فريقك المرخص الاستشارة ويوثق القرارات ويسند المتابعة إلى الممارس المسؤول. يطلع الزملاء المصرح لهم على سجل الرعاية نفسه.\n\nمثال: يوثق اختصاصي العناية عن بُعد استشارة لمريض في السرير ١٢. يقرأ الفريق بجانب المريض الخطة ويسجل المتابعة المتفق عليها.\n\nالفائدة والنتيجة المتوقعة: تسليم أوضح للحالة ووقت أقل للبحث عن آخر خطة. يظل فريقك السريري مسؤولاً عن العلاج والتصعيد.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-care-workflow-example"},{"id":"teleicu-automation-example","question":"العناية المركزة عن بُعد: كيف تعمل الأتمتة في بيئة الرعاية هذه؟","answer":"المعنى: إدخال مصادر بيانات العناية المتفق عليها في مسار الرعاية ليتمكن الفريق المصرح له من مراجعة المعلومات معاً.\n\nطريقة العمل: يحدد نظام المصدر والبيانات المطلوبة، ويربط الموصل ويختبر، ويحدد المسؤول عن المتابعة عندما تنقص المعلومات أو يحتاج الاتصال إلى معالجة.\n\nمثال: ترسل واجهة مستشفى معتمدة نتائج المختبر إلى مسار العناية. تظهر النتيجة الناقصة في قائمة متابعة متفق عليها للفريق المسؤول.\n\nالفائدة والنتيجة المتوقعة: نقل يدوي أقل ووضوح أكبر للمعلومات الناقصة. يبقى تفسير النتائج والتصعيد مسؤولية فريقك المرخص.\n\nالنطاق: تحتاج المصادر والأجهزة وتواتر التحديث إلى اعتماد الواجهة. لا توفر الميزة مراقبة مستمرة للإنذارات السريرية.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-automation-example"},{"id":"teleicu-named-owner-example","question":"العناية المركزة عن بُعد: ماذا ينفذ المسؤول المحدد في بيئة الرعاية هذه؟","answer":"المعنى: مسؤول تشغيل محدد من منسوق يتولى متابعة قوائم العمل غير السريرية المتفق عليها.\n\nطريقة العمل: تحدد قائمة العمل والإجراءات ومسار التصعيد. يراجع المسؤول العمل المعلق وينسق مع فريقك ويسجل التقدم ضمن رصيد ساعات التشغيل المشمول.\n\nمثال: تظل مهمة توثيق عناية متفق عليها غير مكتملة. يتابع المسؤول الفريق المعني ويسجل حالتها؛ ويتخذ ممارسوك القرارات السريرية.\n\nالفائدة والنتيجة المتوقعة: مسؤولية أوضح وتنقل أقل بين جهات الاتصال، مع سجل ظاهر للمتابعة.\n\nالنطاق: يعمل المسؤول ضمن فترة الخدمة والساعات المتفق عليها. تحتاج إدارة الفوترة الخارجية الكاملة والعمل غير المحدود بالقوائم والكادر السريري إلى نطاق مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-teleicu-named-owner-example"},{"id":"home-day","question":"كيف يسير مسار الرعاية المنزلية من الإحالة إلى المتابعة؟","answer":"ضمن النطاق المقبول، يسجل فريقك المريض ويعد خطة الرعاية المتفق عليها ويحدد الزيارات ويوثق الملاحظات ومعلومات الأدوية ويسجل المتابعة والتواصل المصرح به مع الأسرة. يستطيع فريق الزيارة مراجعة الخطة الحالية والملاحظات السابقة. يوفر العميل الكادر المرخص والاعتماد السريري للخطة.","url":"https://mansoq.com/faq?lang=ar#faq-home-day"},{"id":"home-routing","question":"كيف تساعد أتمتة الزيارات والجداول وتخطيط المسارات؟","answer":"تضيف بريميوم وما فوقها أتمتة الزيارات المتكررة وتحسين المسارات أو الجداول المتفق عليه. حدد تواتر الزيارات والمواقع وتوفر الفريق والاستثناءات. مثلاً، تبقى الزيارة المعاد جدولتها ظاهرة في قائمة العمل ليتمكن المنسق من ترتيب الإجراء التالي. يبقى تقدير التنقل الفعلي وتوفر الكادر والأولويات السريرية لدى المسؤولين.","url":"https://mansoq.com/faq?lang=ar#faq-home-routing"},{"id":"family-access","question":"هل يستطيع أفراد الأسرة ومقدمو الرعاية الاطلاع على التحديثات؟","answer":"يتبع وصول المريض والأسرة الهوية والموافقة والصلاحيات المتفق عليها. حدد من هو مصرح له وما المعلومات التي يطلع عليها ومن يدير تغييرات الوصول. مثلاً، يتلقى مقدم رعاية معتمد تحديث الزيارة المتفق عليه بينما تظل سجلات أخرى مقيدة. قد تحتاج الرسائل الخارجية والتطبيقات المخصصة إلى خدمات واستخدام مورّد يحددان مستقلاً.","url":"https://mansoq.com/faq?lang=ar#faq-family-access"},{"id":"palliative-records","question":"ما نطاق الرعاية التلطيفية؟","answer":"يشمل المسار المتعاقد عليه خطط الرعاية وتوثيق الأعراض والأدوية والتواصل مع مقدمي الرعاية وسجلات دعم الأسرة أو الفقد. يساعد الفرق المصرح لها على جمع سياق الرعاية والمتابعة. تحدد المؤسسة السريرية العلاج وتدبير الأعراض والتصعيد وتقديم دعم الأسرة، ولا يصف البرنامج العلاج أو يحل محل الكادر المرخص.","url":"https://mansoq.com/faq?lang=ar#faq-palliative-records"},{"id":"home-monitoring","question":"هل تشمل الباقة المراقبة عن بُعد للمرضى تلقائياً؟","answer":"مسارات المراقبة المتصلة اختيارية وتحتاج نطاق أجهزة وواجهات مقبولاً. حدد ما يقاس ومن يراجعه وتوقيته والتصعيد السريري وتكاليف المورّد. لا يمثل سجل المريض أو مسار الفيديو وحده مراقبة مستمرة، ولا يوفر دعم التشغيل المدار ممارساً لمتابعة البيانات.","url":"https://mansoq.com/faq?lang=ar#faq-home-monitoring"},{"id":"missed-home-visits","question":"كيف تساعد الماسية عندما تحتاج الزيارات أو الوثائق إلى متابعة؟","answer":"يتابع المسؤول المحدد قوائم التنسيق واستثناءات الزيارات والتوثيق المتفق عليها ضمن رصيد الساعات. ينسق مع المنسق أو الفريق السريري لديك ويسجل الإجراءات المعلقة ويراجع الاستمرارية والسعة شهرياً. مثلاً، يمكن إعادة إسناد توثيق زيارة غير مكتمل إلى فريقه المسؤول بدلاً من بقائه ضمن متأخرات دون مسؤول.","url":"https://mansoq.com/faq?lang=ar#faq-missed-home-visits"},{"id":"home-emergencies","question":"من يتعامل مع الطوارئ أثناء الرعاية المنزلية أو التلطيفية؟","answer":"يوفر العميل التغطية السريرية المرخصة ومسار الطوارئ أو التصعيد. اعتمد تعليمات المريض ومقدم الرعاية من خلال الحوكمة السريرية وجرّب إجراء التصعيد. لا ينبغي التعامل مع الرسائل والتذكيرات وقوائم التشغيل غير السريري على أنها خدمة استجابة للطوارئ.","url":"https://mansoq.com/faq?lang=ar#faq-home-emergencies"},{"id":"home_palliative-rcm-raas","question":"كيف تسعّر خدمة RaaS في الرعاية المنزلية والتلطيفية؟","answer":"الأساسية: ١٨٪؛ بريميوم: ١٥٪؛ الماسية: ١٠٪؛ المؤسسات: ٤٫٥٪–٧٫٥٪. تطبق هذه النسب على التحصيل المحقق المؤهل والمعتمد وتضاف إلى الاشتراك. تتطلب المؤسسات نسبة محددة معتمدة ضمن النطاق ونطاقاً مقبولاً. تحتسب الرسوم الفعلية من الأدلة المالية المراجعة بعد المبالغ المستردة والاستبعادات المتفق عليها؛ لا ينشئ التقدير في المنشئ فاتورة.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-rcm-raas"},{"id":"home_palliative-prices","question":"ما أسعار الرعاية المنزلية والتلطيفية المنشورة؟","answer":"الأساسية: ‏١٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٩٩٠٫٠٠ ر.س.‏ للبرنامج + ‏١٬٠٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 50 مرضى نشطون شهرياً وموقعاً واحداً.\n\nبريميوم: ‏٣٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏١٬٧٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٢٬٢٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 150 مرضى نشطون شهرياً وموقعاً واحداً.\n\nالماسية: ‏٦٬٩٩٠٫٠٠ ر.س.‏ شهرياً، وتتكون من ‏٢٬٤٩٠٫٠٠ ر.س.‏ للبرنامج + ‏٤٬٥٠٠٫٠٠ ر.س.‏ للتشغيل المدار. تشمل 250 مرضى نشطون شهرياً وموقعاً واحداً.\n\nالمؤسسات: يحدد السعر ونطاق التشغيل الفعلي في عرض المبيعات.\n\nكل المبالغ العامة قبل الضريبة. نطاق ميزانية الإعداد والترحيل استرشادي، ويتبع السعر النهائي بيان العمل. تحدد الإضافات وتكاليف المورّد بشكل مستقل. السعر غير المعتمد ليس عرضاً عاماً.","href":"/pricing#care-packages","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-prices"},{"id":"home_palliative-tier-benefits","question":"ما الذي يتغير بين باقات الرعاية المنزلية والتلطيفية؟","answer":"الأساسية: أكمل مسار الرعاية. زيارات وخطط رعاية وتوثيق الأعراض والأدوية وتواصل مقدمي الرعاية وسجلات دعم الأسرة والفقد.\n\nبريميوم: قلل العمل المتكرر واكتشف الاستثناءات مبكراً. زيارات وخطط رعاية وتوثيق الأعراض والأدوية وتواصل مقدمي الرعاية وسجلات دعم الأسرة والفقد. تحسين المسارات والجداول وأتمتة الزيارات المتكررة وتحديثات الأسرة ومسارات المراقبة المتصلة الاختيارية.\n\nالماسية: حدد مسؤولاً عن قوائم التشغيل المتفق عليها. زيارات وخطط رعاية وتوثيق الأعراض والأدوية وتواصل مقدمي الرعاية وسجلات دعم الأسرة والفقد. تحسين المسارات والجداول وأتمتة الزيارات المتكررة وتحديثات الأسرة ومسارات المراقبة المتصلة الاختيارية. مسؤول محدد للتوجيه واستثناءات الزيارات ومتابعة التوثيق ومراجعة شهرية لاستمرارية الرعاية والسعة. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nالمؤسسات: حوكم الرعاية والتشغيل على مستوى المؤسسة. زيارات وخطط رعاية وتوثيق الأعراض والأدوية وتواصل مقدمي الرعاية وسجلات دعم الأسرة والفقد. تحسين المسارات والجداول وأتمتة الزيارات المتكررة وتحديثات الأسرة ومسارات المراقبة المتصلة الاختيارية. مسؤول محدد للتوجيه واستثناءات الزيارات ومتابعة التوثيق ومراجعة شهرية لاستمرارية الرعاية والسعة. حوكمة المجموعة وصلاحيات حسب الكيان وتقارير موحدة وتكاملات ونطاق تشغيل متفق عليه. استخدم قاعدة PostgreSQL وتخزيناً خاصاً متوافقاً مع S3 في سحابتك أو Spaces أو خادمك. تستخدم الترحيلات والملفات السريرية والتقارير والمهام الخلفية وجهة العميل المعتمدة؛ تعتمد الصلاحيات والشبكة والنسخ والاستعادة قبل الإطلاق.\n\nتحتفظ الباقات الأعلى بأساس الرعاية المتعاقد عليه. أرصدة السعة والساعات والواجهات مستقلة، ويحدد العرض المقبول نطاق التشغيل الحي.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-tier-benefits"},{"id":"home_palliative-care-workflow-example","question":"الرعاية المنزلية والتلطيفية: كيف يعمل مسار الرعاية الأساسي وما فائدته؟","answer":"المعنى: سجل رعاية واحد للزيارات المنزلية والخطة المتفق عليها وملاحظات الأعراض والأدوية والتواصل المصرح به مع الأسرة.\n\nطريقة العمل: يحدد فريقك موعد الزيارة ويوثق ما تم ويحدث خطة الرعاية. يحفظ التواصل مع الأسرة والمتابعة ضمن سجل المريض وفق الصلاحيات المتفق عليها.\n\nمثال: بعد زيارة منزلية، يسجل الممرض ملاحظات الأعراض ويحدث الممارس خطة الرعاية. يراجع فريق الزيارة التالية الاثنين قبل الحضور.\n\nالفائدة والنتيجة المتوقعة: استمرارية أفضل بين الزيارات وسجل واضح لما اتفق عليه فريق الرعاية والأسرة.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-care-workflow-example"},{"id":"home_palliative-automation-example","question":"الرعاية المنزلية والتلطيفية: كيف تعمل الأتمتة في بيئة الرعاية هذه؟","answer":"المعنى: تنظيم الزيارات المتكررة ومساعدة منسقي الزيارات في إعداد جداول الفرق ومسارات التنقل.\n\nطريقة العمل: تحدد وتيرة الزيارة المعتمدة سريرياً وتوفر الفرق ونطاق الخدمة. يعد المسار الزيارات المتكررة ومعلومات التنقل ليراجعها المنسق ويؤكدها.\n\nمثال: يحتاج مريض إلى زيارتين أسبوعياً. ينشئ الجدول المتكرر الزيارتين، ويجمع المنسق الزيارات القريبة في مسار مناسب.\n\nالفائدة والنتيجة المتوقعة: عمل أقل لإعادة الجدولة وخطة يومية أوضح. يؤكد فريقك الأولوية السريرية والكادر والمسار النهائي.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-automation-example"},{"id":"home_palliative-named-owner-example","question":"الرعاية المنزلية والتلطيفية: ماذا ينفذ المسؤول المحدد في بيئة الرعاية هذه؟","answer":"المعنى: مسؤول تشغيل محدد من منسوق يتولى متابعة قوائم العمل غير السريرية المتفق عليها.\n\nطريقة العمل: تحدد قائمة العمل والإجراءات ومسار التصعيد. يراجع المسؤول العمل المعلق وينسق مع فريقك ويسجل التقدم ضمن رصيد ساعات التشغيل المشمول.\n\nمثال: تحتاج زيارة منزلية إلى إعادة جدولة. يتابع المسؤول منسقك ويتتبع الإجراء المتفق عليه حتى تتضح حالته التشغيلية.\n\nالفائدة والنتيجة المتوقعة: مسؤولية أوضح وتنقل أقل بين جهات الاتصال، مع سجل ظاهر للمتابعة.\n\nالنطاق: يعمل المسؤول ضمن فترة الخدمة والساعات المتفق عليها. تحتاج إدارة الفوترة الخارجية الكاملة والعمل غير المحدود بالقوائم والكادر السريري إلى نطاق مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-home_palliative-named-owner-example"},{"id":"managed-hours-definition","question":"فيم تستخدم ساعات التشغيل المدارة فعلياً؟","answer":"تغطي الإعداد والمراجعة المتخصصة والعمل بقوائم التشغيل المتفق عليها. مثلاً، قد يراجع مختص قائمة استثناءات محددة ويعدل مساراً مقبولاً ويوثق الإجراءات التالية. حدد القائمة والإجراءات المسموح بها والصلاحيات والمسؤول والمخرجات المتوقعة قبل العمل. ليست ساعات التشغيل نوبات كادر سريري أو إدارة خارجية غير محدودة.","url":"https://mansoq.com/faq?lang=ar#faq-managed-hours-definition"},{"id":"managed-hours-tracking","question":"كيف توثق ساعات التشغيل المدارة؟","answer":"توثق شروط الخدمة الروتينية العمل بفواصل قدرها ١٥ دقيقة. يحتسب إعداد المراجعة إضافة إلى الاجتماع نفسه. اتفق على سجل المهام وتقرير الاستخدام لتعرف المؤسسة ما نفذ وما تبقى. مثلاً، يستهلك تحضير مراجعة الاستثناءات ومناقشة إجراءاتها من الرصيد المتفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-managed-hours-tracking"},{"id":"unused-hours","question":"هل ترحل ساعات التشغيل غير المستخدمة إلى الشهر التالي؟","answer":"لا تنص شروط الخدمة الروتينية المنشورة على ترحيل الساعات إلا باتفاق مستقل. خطط للأولويات ومواعيد المراجعة مع الفريق المسؤول لاستخدام الرصيد الشهري في عمل مفيد. إذا كان العمل موسمياً، فاطلب ترتيباً مكتوباً ولا تفترض أن الساعات غير المستخدمة تنشئ رصيداً مستقبلياً غير محدود.","url":"https://mansoq.com/faq?lang=ar#faq-unused-hours"},{"id":"extra-hour-approval","question":"ماذا يحدث عندما يقارب رصيد ساعات التشغيل نهايته؟","answer":"تنص الشروط الروتينية على إشعارات عند استخدام ٨٠٪ و١٠٠٪ من الرصيد وعلى الاعتماد قبل العمل الإضافي. قرر إعادة ترتيب الأولويات أو إضافة ساعات معتمدة أو تغيير نطاق الخدمة. تتبع المسؤوليات السريرية والدعم الحرج ترتيباتها المقبولة، ولا تزيد سعة الرعاية والواجهات لمجرد شراء ساعات إضافية.","url":"https://mansoq.com/faq?lang=ar#faq-extra-hour-approval"},{"id":"service-window","question":"متى يتوفر التشغيل الروتيني المدار؟","answer":"الفترة الروتينية المنشورة من الأحد إلى الخميس، من ٠٨:٠٠ إلى ١٨:٠٠ بتوقيت السعودية، باستثناء الإجازات المتفق عليها. حدد الجدولة وجهات الاتصال وأي تغطية خاصة في العرض. تختلف هذه الفترة التشغيلية عن توافر التطبيق وتغطيتك السريرية وتغطية الحوادث التقنية الحرجة المعتمدة مستقلاً.","url":"https://mansoq.com/faq?lang=ar#faq-service-window"},{"id":"support-vs-managed","question":"ما الفرق بين دعم المنتج والتشغيل المدار؟","answer":"يعالج دعم المنتج المنتج المقبول والحوادث التقنية. ويغطي التشغيل المدار أعمال الإعداد والمراجعة والقوائم المستمرة المتفق عليها. تنص الشروط الروتينية على أن عيوب المنتج والدعم الحرج لا تستهلك رصيد ساعات التشغيل. يجب تعريف قنوات التواصل والحدة والتغطية والتزامات الاستجابة في اتفاق الدعم المقبول.","url":"https://mansoq.com/faq?lang=ar#faq-support-vs-managed"},{"id":"named-owner-accountability","question":"هل ينفذ مسؤول التشغيل المحدد كل أعمالنا؟","answer":"يتولى المسؤول متابعة القوائم المتفق عليها ضمن الساعات والصلاحيات وفترة الخدمة المقبولة. يظل فريقك يوفر الأدلة والاعتمادات والقرارات السريرية المطلوبة. تحتاج الفوترة الخارجية الكاملة أو فريق تشغيل أكبر إلى نطاق مستقل. الفائدة هي مسؤولية أوضح وإجراءات تالية موثقة للعمل المتفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-named-owner-accountability"},{"id":"queue-ownership-example","question":"كيف تبدو قائمة الاستثناءات التشغيلية عملياً؟","answer":"هي قائمة ظاهرة بعمل يحتاج اهتماماً، مع مسؤول وسبب وإجراء تالٍ وحالة. مثلاً، تكون الزيارة مكتملة لكن وثائق الفوترة ناقصة، فيتلقى الفريق المسؤول مهمة متابعة ويسجل التقدم. تساعد الأتمتة على تحديد الاستثناء ولا تنشئ أدلة ناقصة أو تعتمد قرار جهة التأمين.","url":"https://mansoq.com/faq?lang=ar#faq-queue-ownership-example"},{"id":"monthly-review-results","question":"ماذا يجب أن تنتج المراجعة الشهرية للأداء والسعة؟","answer":"اتفق على المؤشرات مسبقاً، مثل استخدام السعة والعمل المتأخر والاستثناءات المتكررة ومؤشرات الرعاية أو الإيرادات المناسبة. يراجع المسؤول البيانات المقبولة مع فريقك ويسجل الأولويات والإجراءات والمسؤولين وتغييرات السعة المعتمدة. يستهلك التحضير من ساعات التشغيل. النتيجة المفيدة خطة متابعة قابلة للتنفيذ وليست نسبة تحسن مضمونة.","url":"https://mansoq.com/faq?lang=ar#faq-monthly-review-results"},{"id":"clinical-staffing-responsibility","question":"من يظل مسؤولاً عن العلاج والوصفات والقرارات السريرية؟","answer":"يوفر العميل الممارسين المرخصين وقرارات العلاج والتصعيد السريري والحوكمة الطبية. توفر منسوق التقنية والتشغيل غير السريري المتعاقد عليه. قد تدعم المهمة الآلية أو لوحة المعلومات أو مسؤول التشغيل التنسيق، لكنها لا تستبدل اعتماد الممارس أو البروتوكول السريري أو ترتيب الكادر لديك.","url":"https://mansoq.com/faq?lang=ar#faq-clinical-staffing-responsibility"},{"id":"current-managed-hour-allowances","question":"كم ساعة تشغيل تشمل كل باقة ومنتج؟","answer":"العيادات: الأساسية ساعتان شهرياً؛ بريميوم ٦ ساعات شهرياً؛ الماسية ١٢ ساعة شهرياً؛ المؤسسات حسب اتفاق المبيعات\n\nالمجمعات الطبية: الأساسية ٤ ساعات شهرياً؛ بريميوم ١٢ ساعة شهرياً؛ الماسية ٢٤ ساعة شهرياً؛ المؤسسات حسب اتفاق المبيعات\n\nالعناية المركزة عن بُعد: الأساسية ٤ ساعات شهرياً؛ بريميوم ١٢ ساعة شهرياً؛ الماسية ٢٤ ساعة شهرياً؛ المؤسسات حسب اتفاق المبيعات\n\nالرعاية المنزلية والتلطيفية: الأساسية ٤ ساعات شهرياً؛ بريميوم ١٢ ساعة شهرياً؛ الماسية ٢٤ ساعة شهرياً؛ المؤسسات حسب اتفاق المبيعات\n\nالرصيد للعمل غير السريري المتفق عليه وليس نوبات كادر. يحتسب تحضير المراجعة، ولا تزيد الوحدات والمواقع الإضافية عدد الساعات.","url":"https://mansoq.com/faq?lang=ar#faq-current-managed-hour-allowances"},{"id":"rcm-raas-benefit","question":"ماذا تقدم RaaS لفريقنا؟","answer":"تسند RaaS قوائم الإيرادات غير السريرية المتفق عليها إلى فريق تشغيل مسؤول: متابعة الأهلية والموافقات وإعداد المطالبات وتقديمها والرفض والإنكار ومطابقة التسويات. تعتمد الجهات الدافعة والكيانات والأحجام ونافذة الخدمة والاعتمادات. يظل الممارسون مسؤولين عن الأدلة والقرارات السريرية، ويحتفظ فريق المالية باعتماد التغييرات المالية الحساسة.","url":"https://mansoq.com/faq?lang=ar#faq-rcm-raas-benefit"},{"id":"rcm-raas-additional","question":"هل تضاف نسبة RaaS إلى الاشتراك؟","answer":"نعم. تضاف رسوم التحصيل المعتمدة إلى اشتراك البرنامج والتشغيل المدار. يفصل العرض الرسوم الثابتة عن رسوم التحصيل. حدد العمل الذي تغطيه ساعات الباقة والعمل الذي يغطيه نطاق RaaS. يعبر الاختيار عن طلب الخدمة، ولا يفوض الرسوم التلقائية أو يثبت نطاق تشغيل مقبولاً.","url":"https://mansoq.com/faq?lang=ar#faq-rcm-raas-additional"},{"id":"rcm-raas-collection-basis","question":"ما مبلغ التحصيل الذي تحتسب عليه رسوم RaaS؟","answer":"تستخدم الفوترة الفعلية التحصيل المؤهل المحقق بنكياً للفترة المتفق عليها، بعد المبالغ المستردة الموثقة والاستبعادات والتعديلات المتفق عليها. لا تستخدم القيمة الاسمية للمطالبات أو الفواتير غير المسددة أو التقدير التخطيطي الذي أدخله العميل. طابق التسويات والأدلة المالية مع مسؤول المالية، وسجل المبلغ المستبعد واطلب مراجعة مستقلة للرسوم. يحدد العقد الكيانات والجهات الدافعة والمقبوضات المؤهلة.","url":"https://mansoq.com/faq?lang=ar#faq-rcm-raas-collection-basis"},{"id":"rcm-raas-yearly","question":"هل يخفض السداد السنوي رسوم RaaS على التحصيل؟","answer":"لا. يطبق الخصم السنوي على اشتراك البرنامج الأساسي المؤهل فقط. تحتسب رسوم التحصيل بشكل مستقل للفترة المتفق عليها بنسبة العقد المعتمدة. يبقى تقدير RaaS في المنشئ منفصلاً عن الاشتراك الشهري والسنوي الثابت، وليس رسوماً مدفوعة مسبقاً أو فاتورة مضمونة.","url":"https://mansoq.com/faq?lang=ar#faq-rcm-raas-yearly"},{"id":"rcm-raas-outcomes","question":"هل تضمن RaaS السداد أو عملاً غير محدود أو كادراً سريرياً؟","answer":"توفر الخدمة مسؤولية تشغيلية محددة وفوترة واضحة ترتبط بالتحصيل. اعتمد حجم العمل والفريق والتغطية وملكية القوائم والاعتمادات وتقارير الأداء في النطاق الموقع. تعتمد نتائج السداد والرفض على الأدلة وقرارات الجهات الدافعة. يوفر ممارسو العميل قرارات الرعاية والتوثيق السريري. لا تفعل النسبة المنشورة وحدها أحجاماً أو فرقاً غير محدودة أو تغطية دائمة.","url":"https://mansoq.com/faq?lang=ar#faq-rcm-raas-outcomes"},{"id":"interface-meaning","question":"ما المقصود بواجهة خارجية مصانة؟","answer":"هي اتصال متفق عليه لتبادل بيانات محددة مع نظام خارجي مسمّى ضمن رصيد الباقة المنشور. حدد المصدر والوجهة والصيغة وربط الحقول والتوقيت والصلاحيات والاختبارات ومسؤولية الصيانة. مثلاً، يحدث اتصال دخول مقبول سياق المريض أو السرير المتفق عليه. يحدد بناء موصل مخصص ودفع رسوم المورّد بشكل مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-interface-meaning"},{"id":"interface-counting","question":"كيف تحتسب الواجهة وماذا لو أرسل نظام واحد عدة تدفقات؟","answer":"تحدد مواصفات الواجهة المقبولة طريقة الاحتساب. لا يجعل اسم مورّد واحد جميع تدفقاته واجهة واحدة تلقائياً، ولا ينبغي تقسيم تدفق واحد إلى رسوم اعتباطية دون نطاق محدد. اتفق على كل مجال بيانات واتجاه ونقطة اتصال واختبار قبول والتزام صيانة قبل اعتماد العرض.","url":"https://mansoq.com/faq?lang=ar#faq-interface-counting"},{"id":"national-connectors","question":"هل تستهلك نفيس وزاتكا رصيد الواجهات الخارجية القياسي؟","answer":"تستثني شروط الخدمة المنشورة موصلات الأساس الوطنية المنطبقة من رصيد الواجهات الخارجية القياسي المصان. مسارات نفيس وزاتكا المطلوبة مشمولة في كل باقة. يُفعَّل الإرسال المباشر بعد توفير اعتمادات منشأتك لدى نفيس وزاتكا والقبول الخارجي. تراجع الإضافات المخصصة وعمل الموردين الخارجيين ورسومهم بشكل مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-national-connectors"},{"id":"nphies-live-readiness","question":"هل يعني وجود نفيس في الباقة أنه جاهز للاستخدام فوراً؟","answer":"وجود القدرة باسمها ليس إثباتاً لاتصال إنتاج مقبول. أكد الإصدار والمنشأة ونطاق التأمين والاعتمادات المصرح بها والتسجيل وربط الحقول والاختبارات المقبولة. الأهلية والموافقات والمطالبات وردود التأمين خطوات مستقلة. يوفر فريقك صلاحيات المصادر والأدلة السريرية والمالية الصحيحة.","href":"/saudi","url":"https://mansoq.com/faq?lang=ar#faq-nphies-live-readiness"},{"id":"zatca-coding","question":"ما الذي نؤكده بشأن زاتكا وSBS ومتطلبات الترميز الأخرى؟","answer":"اتفق على نطاق الفوترة والترميز المنطبق والكتالوجات المرخصة الحالية وربط الخدمات والاعتمادات المصرح بها وقبول الإنتاج. للفوترة الوطنية ومواءمة الخدمات التأمينية وأي متطلبات تجميع احتياجات إعداد مستقلة. راجع المراجع السعودية والتنفيذية مع الفرق المالية والتقنية المسؤولة ولا تستنتج الاعتماد من اسم تسويقي.","href":"/saudi","url":"https://mansoq.com/faq?lang=ar#faq-zatca-coding"},{"id":"keep-existing-system","question":"هل نستطيع الاحتفاظ بنظام السجل الطبي أو النظام المالي الحالي؟","answer":"ناقش نموذج الإضافة إلى النظام الحالي أو الترحيل الكامل أو الانتقال المرحلي. حدد النظام المسؤول عن كل سجل وكيف تتبادل الأنظمة البيانات المقبولة. يلزم توفر صلاحيات المصادر والاستخراج وتعاون المورّد وربط حقول مختبر. قد لا يشمل استخراج سريري بصيغة FHIR الجداول والمطالبات والأرصدة والمرفقات.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-keep-existing-system"},{"id":"integration-failure","question":"ماذا يحدث عند تعطل نظام خارجي أو اتصال؟","answer":"يجب أن يحدد نطاق الاتصال المقبول اكتشاف العطل والمسؤولية وقواعد إعادة المحاولة أو التسوية وعمل التوقف والتصعيد. سجل التبادلات الفاشلة أو المتأخرة ليتحقق الفريق المسؤول مما وصل إلى الوجهة. مثلاً، يفحص اتصال مختبر متأخر وتجرى تسويته بدلاً من اعتباره نقلاً كاملاً للنتائج. تتبع حوادث المورّد حدود المسؤولية المتفق عليها.","url":"https://mansoq.com/faq?lang=ar#faq-integration-failure"},{"id":"all-vendors","question":"هل نفترض أن كل جهاز أو نظام خارجي مدعوم بالفعل؟","answer":"أكد المورّد والمنتج والإصدار المثبت تحديداً مقابل نطاق الاتصال المقبول. القدرة العامة على التكامل ليست محولاً مفعلاً مسبقاً لكل طراز. وفر وثائق الواجهة والوصول المصرح به واتفق على ربط الحقول وعينة الاختبار واعتمد حالات نجاح التبادل وفشله قبل الاستخدام الحي.","url":"https://mansoq.com/faq?lang=ar#faq-all-vendors"},{"id":"current-interface-allowances","question":"كم واجهة مصانة تشمل كل باقة؟","answer":"العيادات: الأساسية ٠ واجهة؛ بريميوم واجهة واحدة؛ الماسية واجهتان؛ المؤسسات حسب اتفاق المبيعات\n\nالمجمعات الطبية: الأساسية ٠ واجهة؛ بريميوم واجهتان؛ الماسية ٤ واجهات؛ المؤسسات حسب اتفاق المبيعات\n\nالعناية المركزة عن بُعد: الأساسية واجهات الأجهزة تُحدد في العرض؛ بريميوم واجهتان؛ الماسية ٤ واجهات؛ المؤسسات حسب اتفاق المبيعات\n\nالرعاية المنزلية والتلطيفية: الأساسية ٠ واجهة؛ بريميوم واجهة واحدة؛ الماسية ٣ واجهات؛ المؤسسات حسب اتفاق المبيعات\n\nهذه اتصالات خارجية قياسية متفق عليها. موصلات الأساس الوطنية المنطبقة مستقلة عنها. يجب تفعيل كل اتصال، وتحدد رسوم المورّد وبناء الموصل المخصص بشكل مستقل.","url":"https://mansoq.com/faq?lang=ar#faq-current-interface-allowances"},{"id":"own-storage-plans","question":"ما الباقات التي تسمح بقاعدة بيانات وتخزين ملفات خاصين بنا؟","answer":"تتيح الماسية والمؤسسات هذا الخيار الاختياري للنشر. توفر مؤسستك قاعدة PostgreSQL مخصصة ومقبولة وتخزين ملفات خاصاً متوافقاً مع S3. يحدد نطاق البنية وعمل الربط وأي ترحيل بشكل مستقل. لا تشمل الأساسية وبريميوم خيار النشر هذا في نطاق باقات الرعاية المنشور.","url":"https://mansoq.com/faq?lang=ar#faq-own-storage-plans"},{"id":"storage-included-optional","question":"هل تلزمنا الماسية والمؤسسات باستضافة البيانات بأنفسنا؟","answer":"التخزين المملوك للعميل خيار وليس شراءً إلزامياً. اختر نشر منسوق المدار المقبول أو اقترح وجهتك الخاصة، ثم أكد شروط الاستضافة والاستعادة. قد تمنحك بنيتك تحكماً مباشراً أكبر في الموقع والوصول، لكنها تحتاج أيضاً مسؤوليات متفقاً عليها للإدارة والمراقبة والنسخ والحوادث.","url":"https://mansoq.com/faq?lang=ar#faq-storage-included-optional"},{"id":"supported-storage-types","question":"هل نستخدم سحابتنا أو DigitalOcean Spaces أو خادماً في منشأتنا؟","answer":"وجهة العميل المدعومة هي قاعدة PostgreSQL مخصصة مع تخزين كائنات خاص متوافق مع S3، مثل AWS S3 أو DigitalOcean Spaces أو MinIO على خادم العميل. لا يستبدل مجلد مشترك عادي أو نوع قاعدة اعتباطي تلك الواجهة المقبولة. أكد المنطقة والاتصال والشهادات والصلاحيات وتصميم النسخ قبل التفعيل.","url":"https://mansoq.com/faq?lang=ar#faq-supported-storage-types"},{"id":"storage-live-app","question":"هل يطبق التخزين الخاص أثناء الإعداد فقط أم في النظام الحي أيضاً؟","answer":"بعد قبول الاتصال، يستخدم التشغيل السريري قاعدة العميل ووجهة الملفات الخاصة المعتمدتين. يشمل النطاق ترحيلات قاعدة البيانات الأصلية والملفات السريرية وملفات المنشأة والتقارير والاستيرادات السريرية والتقارير والمهام الخلفية التي تستخدم ذلك التشغيل. الوجهة المختارة خيار نشر فعلي وليست تسمية في الإعداد فقط.","url":"https://mansoq.com/faq?lang=ar#faq-storage-live-app"},{"id":"storage-connection-acceptance","question":"ما المطلوب قبل تشغيل قاعدة بياناتنا وتخزيننا؟","answer":"وفر الوجهة المصرح بها واعتمادات خدمة محددة النطاق، ثم اعتمد الوصول الشبكي والتحقق من الشهادات وعمليات القاعدة والملفات وجاهزية الترحيل والنسخ والاستعادة. حدد المسؤولين وجهات الحوادث. لا يثبت اختيار مربع أو تقديم عنوان وجود اتصال حي مقبول؛ يتحقق التفعيل من الوجهة قبل الاستخدام السريري.","url":"https://mansoq.com/faq?lang=ar#faq-storage-connection-acceptance"},{"id":"storage-unavailable","question":"ماذا يحدث إذا تعطلت قاعدة بياناتنا أو مساحة التخزين الخاصة؟","answer":"لا يتحول التشغيل السريري تلقائياً إلى قاعدة أو حاوية لدى منسوق. تبلغ العملية المتأثرة عن مشكلة اتصال أو تخزين بدلاً من وضع البيانات السريرية في مكان آخر دون بيان. استخدم إجراء التوقف والتصعيد المقبول واستعد الوجهة وطابق العمل المتأثر. اتفق على مسؤوليات التعافي واستمرارية الرعاية قبل الإطلاق.","url":"https://mansoq.com/faq?lang=ar#faq-storage-unavailable"},{"id":"storage-infrastructure-cost","question":"من يدفع تكلفة سحابتنا أو خادمنا ويديره؟","answer":"تحدد بنية العميل وعمل ربطها أو الترحيل إليها بشكل مستقل. يجب أن يسمي الاتفاق المسؤول عن دفع المورّد وإدارة صيانة القاعدة والتخزين والسعة والشهادات والشبكة والنسخ والمراقبة. لا ينقل امتلاك الحساب وحده هذه المسؤوليات إلى منسوق ولا يجعل تكلفة البنية جزءاً من سعر البطاقة.","url":"https://mansoq.com/faq?lang=ar#faq-storage-infrastructure-cost"},{"id":"storage-move-later","question":"هل ننقل نظاماً حياً قائماً إلى تخزيننا لاحقاً؟","answer":"تعامل مع الانتقال كترحيل متفق عليه، وليس تغيير مربع في نظام حي. احصر القاعدة والملفات وجهز الوجهة الجديدة واربط السجلات وطابقها وجرّب الانتقال والاستعادة ثم اعتمد التحويل النهائي. اتفق على التوقف والمسؤولية والتراجع حتى لا ينقسم السجل السريري الحي بين وجهات غير معتمدة.","url":"https://mansoq.com/faq?lang=ar#faq-storage-move-later"},{"id":"data-location","question":"هل نشترط دولة أو منطقة محددة للاستضافة؟","answer":"حدد الموقع المطلوب في العرض واتفاق البيانات. أكد موقع مجالات البيانات والملفات والنسخ وتدفقات المورّدين الخارجيين المتفق عليها بشكل مستقل. تمنحك وجهتك تحكماً مباشراً في موقعها لكنها لا تؤكد وحدها موقع كل خدمة متصلة. يجب أن تصف شروط النشر والبيانات المقبولة الحدود كاملة.","url":"https://mansoq.com/faq?lang=ar#faq-data-location"},{"id":"security-certification","question":"هل تثبت هذه الباقات تلقائياً اعتماداً أمنياً أو موافقة تنظيمية؟","answer":"أسماء الباقات وميزات الأمان ليست أدلة اعتماد. راجع الإصدار الفعلي والضوابط واتفاق البيانات والنشر ومسؤوليات الموردين والاختبارات المقبولة مع مؤسستك. يحتاج أي ادعاء باعتماد أو موافقة إلى أدلة حالية مستقلة للنطاق المعني. يجب أن يحدد العرض وثائق الضمان المطلوبة بدلاً من افتراضها من اسم الباقة.","url":"https://mansoq.com/faq?lang=ar#faq-security-certification"},{"id":"backup-recovery-objectives","question":"هل تكفي النسخ الاحتياطية، وما معنى زمن الاستعادة ونقطة الاستعادة؟","answer":"يجب أن تكون النسخة قابلة للاستعادة ومقبولة لنشرك. يصف هدف زمن الاستعادة المدة المستهدفة لإعادة الخدمة، ويصف هدف نقطة الاستعادة مقدار فقد البيانات الحديثة الذي يسعى التصميم المتفق عليه إلى الحد منه. حدد الأهداف والجدول والاحتفاظ والمسؤولين واختبارات الاستعادة. لا تعد البطاقات بزمن موحد للاستعادة أو عدم فقد أي بيانات.","url":"https://mansoq.com/faq?lang=ar#faq-backup-recovery-objectives"},{"id":"data-contract-retention","question":"من يملك السجلات ويقرر الاحتفاظ بها أو حذفها؟","answer":"يجب أن يحدد اتفاق البيانات حقوق المؤسسة ومسؤولياتها والمعالجة المصرح بها والوصول والتصدير والاحتفاظ والحذف. تضيف البنية المملوكة للعميل تحكماً في الوجهة المقبولة ولا تستبدل هذه الشروط. اطلب حدود الاحتفاظ بالبيانات السريرية وبيانات الخدمة المتفق عليها قبل إدخال سجلات حقيقية.","url":"https://mansoq.com/faq?lang=ar#faq-data-contract-retention"},{"id":"launch-sequence","question":"ما التسلسل الكامل لتنفيذ المنصة؟","answer":"اتفق على المنتجات والإصدار والمنشآت وحدود البيانات والمسؤوليات. جهز الحساب والأساس وتهيئة المنتجات والاستيرادات المصرح بها. اعتمد الواجهات وطابق السجلات والأرصدة المرحلة ودرب المستخدمين وجرّب المسارات العادية والفاشلة واعتمد التوقف والاستعادة والانتقال. ثم سلم المراقبة وترتيبات الدعم المقبولة.","href":"/resources/implementation","url":"https://mansoq.com/faq?lang=ar#faq-launch-sequence"},{"id":"launch-timeline","question":"كم يستغرق التنفيذ؟","answer":"تعتمد خطة التنفيذ على بيانات المصدر والواجهات والمواقع والبنية والتدريب وعمل القبول. تتفق المبيعات والتنفيذ على المراحل والمسؤولين بعد تحديد تلك المدخلات. لا يعد سعر البطاقة بتاريخ إطلاق ثابت. يمكن أن يبدأ التنفيذ المرحلي بموقع تجريبي متفق عليه ثم يتوسع بعد قبول فحوص جاهزيته.","url":"https://mansoq.com/faq?lang=ar#faq-launch-timeline"},{"id":"customer-launch-inputs","question":"ما الذي نوفره قبل بدء الإعداد؟","answer":"وفر مسؤولي المشروع والحوكمة السريرية والمنشآت والأدوار وكتالوج الخدمات والتعرفة وجداول الممارسين واستخراج الأنظمة المصرح به ومعلومات الواجهات. إذا استخدمت تخزينك، وفر البنية والوصول الخدمي المحدد المتفق عليه أيضاً. لا تضع الاعتمادات الحقيقية في استفسارات عامة؛ استخدم إجراء التفعيل الآمن المتفق عليه.","url":"https://mansoq.com/faq?lang=ar#faq-customer-launch-inputs"},{"id":"imports-templates","question":"ما الذي نستطيع استيراده وكيف يفحص؟","answer":"يوفر دليل التنفيذ قوالب وأمثلة وقواميس حقول لبيانات الأساس والمنتجات المختارة، ومنها الأقسام والمستخدمون والأدوار والخدمات والأطباء والجداول والأصول والمخزون. تحقق من الصيغ والمراجع وراجع الأخطاء وطابق السجلات المقبولة قبل تثبيت الاستيراد. ليس كل جدول ملف ترحيل جاهزاً للتحميل.","href":"/resources/implementation#templates","url":"https://mansoq.com/faq?lang=ar#faq-imports-templates"},{"id":"migration-quality","question":"كيف نعرف أن الترحيل كامل وصحيح؟","answer":"اعتمد مجالات البيانات وربط الحقول قبل النقل واحتفظ بمعرّفات المصدر وطابق السجلات والأرصدة المالية والمرفقات والعلاقات بشكل مستقل. استخدم عينة اختبار متفقاً عليها وافحص الاستثناءات. نجاح الرفع وحده ليس قبولاً لترحيل سريري ومالي كامل؛ يعتمد المسؤولون المخولون الأدلة المتفق عليها.","url":"https://mansoq.com/faq?lang=ar#faq-migration-quality"},{"id":"legacy-history","question":"هل نحتفظ بالسجلات القديمة كأرشيف بدلاً من ترحيل كل حقل؟","answer":"يمكن بحث أرشيف تاريخي محكوم ضمن نطاق الانتقال. حدد التاريخ الذي يجب أن يكون نشطاً وما يبقى في أرشيف مصرح به وكيف يجد المستخدمون السجلات ويطلعون عليها. احفظ المصدر والمعرّفات. يجب أن يحدد العرض الاحتفاظ واحتياجات البحث أو الوصول والمسؤولية؛ فالأرشيف ليس تلقائياً سجل مريض حياً قابلاً للتعديل الكامل.","href":"/resources/migration-integration","url":"https://mansoq.com/faq?lang=ar#faq-legacy-history"},{"id":"training","question":"ما التدريب والتأهيل الذي نتفق عليه؟","answer":"حدد فئات المستخدمين والمسارات والمدربين والمواد والأدلة على قدرة المسؤولين على تنفيذ مهامهم المقبولة. يشمل أساس الباقة التأهيل الأساسي ومواصفات ترحيل متفقاً عليها؛ وتحدد أيام التنفيذ والسفر والتدريب في الموقع مستقلاً. يجب أن يشمل التدريب الاستثناءات وحدود الصلاحيات وإجراءات التوقف إضافة إلى الشاشات العادية.","url":"https://mansoq.com/faq?lang=ar#faq-training"},{"id":"production-readiness","question":"هل يعني اختيار باقة استخدامها فوراً لمرضى حقيقيين؟","answer":"الاختيار التجاري ليس قبولاً للإطلاق السريري. أكد الإصدار المنشور والقدرات والصلاحيات والترحيل والواجهات والتدريب والحوكمة السريرية والدعم المقبولة. جرّب التوقف والتصعيد ثم اعتمد أدلة الإطلاق. لا تفترض تشغيل القدرات المخططة أو الاتصالات غير المفعّلة لمجرد ظهورها في عرض.","url":"https://mansoq.com/faq?lang=ar#faq-production-readiness"},{"id":"pilot-and-phases","question":"هل نطلق فرعاً أو مساراً واحداً أولاً؟","answer":"يمكن أن يقلل التنفيذ المرحلي مقدار التغيير الذي تتعامل معه الفرق دفعة واحدة. حدد نطاق التجربة وحدود البيانات والمؤشرات وبوابة القبول وخطة التوسع. مثلاً، اعتمد صلاحيات الفرع الأول وترحيله ومسار فوترته قبل إضافة بقية الفروع. يحدد العرض التنفيذي جدول العمل المرحلي وتكلفته.","url":"https://mansoq.com/faq?lang=ar#faq-pilot-and-phases"},{"id":"cutover-and-rollback","question":"ما الانتقال النهائي ولماذا نجرب التراجع؟","answer":"الانتقال النهائي هو التحويل المتفق عليه من ترتيب التشغيل القديم إلى الجديد المقبول. جرّب التغييرات النهائية للبيانات والتسوية والصلاحيات والتواصل عند التوقف ومسار الاستعادة قبل الموعد. تحدد خطة التراجع استجابة الفريق المخول إذا فشل القبول. يمنح ذلك المؤسسة قراراً أوضح بشأن الاستمرارية عند الإطلاق.","url":"https://mansoq.com/faq?lang=ar#faq-cutover-and-rollback"},{"id":"current-setup-budgets","question":"ما ميزانيات الإعداد والترحيل الظاهرة لكل منتج؟","answer":"العيادات: الأساسية ‏١٬٥٠٠٫٠٠ ر.س.‏–‏٣٬٠٠٠٫٠٠ ر.س.‏؛ بريميوم ‏٢٬٥٠٠٫٠٠ ر.س.‏–‏٥٬٠٠٠٫٠٠ ر.س.‏؛ الماسية ‏٤٬٠٠٠٫٠٠ ر.س.‏–‏٨٬٠٠٠٫٠٠ ر.س.‏؛ المؤسسات حسب اتفاق المبيعات\n\nالمجمعات الطبية: الأساسية ‏٥٬٠٠٠٫٠٠ ر.س.‏–‏١٠٬٠٠٠٫٠٠ ر.س.‏؛ بريميوم ‏٨٬٠٠٠٫٠٠ ر.س.‏–‏١٨٬٠٠٠٫٠٠ ر.س.‏؛ الماسية ‏١٥٬٠٠٠٫٠٠ ر.س.‏–‏٣٠٬٠٠٠٫٠٠ ر.س.‏؛ المؤسسات حسب اتفاق المبيعات\n\nالعناية المركزة عن بُعد: الأساسية ‏١٠٬٠٠٠٫٠٠ ر.س.‏–‏٢٠٬٠٠٠٫٠٠ ر.س.‏؛ بريميوم ‏٢٠٬٠٠٠٫٠٠ ر.س.‏–‏٥٠٬٠٠٠٫٠٠ ر.س.‏؛ الماسية ‏٤٠٬٠٠٠٫٠٠ ر.س.‏–‏١٠٠٬٠٠٠٫٠٠ ر.س.‏؛ المؤسسات حسب اتفاق المبيعات\n\nالرعاية المنزلية والتلطيفية: الأساسية ‏٣٬٠٠٠٫٠٠ ر.س.‏–‏٦٬٠٠٠٫٠٠ ر.س.‏؛ بريميوم ‏٥٬٠٠٠٫٠٠ ر.س.‏–‏١٠٬٠٠٠٫٠٠ ر.س.‏؛ الماسية ‏٨٬٠٠٠٫٠٠ ر.س.‏–‏٢٠٬٠٠٠٫٠٠ ر.س.‏؛ المؤسسات حسب اتفاق المبيعات\n\nهذه النطاقات قبل الضريبة ومستقلة عن الإجمالي المتكرر. نطاق ميزانية الإعداد والترحيل استرشادي، ويتبع السعر النهائي بيان العمل.","url":"https://mansoq.com/faq?lang=ar#faq-current-setup-budgets"},{"id":"optional-vs-required","question":"ما المطلوب في كل باقة وما الاختياري؟","answer":"يشكل مسار الرعاية المتعاقد عليه ومتطلباته أساس الباقة: سياق المريض والتوثيق والطلبات والأدوية والفوترة والوصول الآمن والتدقيق والنسخ والمسارات الوطنية المنطبقة. تختار خدمات مثل الذكاء المساند والهوية والأجهزة والواجهات الإضافية والإدارة الخارجية الكاملة للإيرادات ويحدد نطاقها مستقلاً. يبين التركيب الموقع ما يشمل فعلياً.","url":"https://mansoq.com/faq?lang=ar#faq-optional-vs-required"},{"id":"addon-checkbox-activation","question":"هل يفعل اختيار إضافة الخدمة أو يثبت سعرها؟","answer":"يسجل الاختيار اهتمامك بالنطاق المقترح. لا يفعّل جهازاً أو ينشئ تكاملاً مقبولاً أو يعتمد مورّداً أو يحسم سعر العمل المخصص. يراجع الفريق التوافق والمتطلبات والمسؤوليات والاستخدام ثم يسعّر الخدمة ويعتمدها. يحدد النشر والصلاحيات المقبولان فقط ما يدخل التشغيل الحي.","url":"https://mansoq.com/faq?lang=ar#faq-addon-checkbox-activation"},{"id":"package_ai_scribe-benefit","question":"كيف تعمل إضافة مساعد التوثيق بالذكاء الاصطناعي؟","answer":"اختياري؛ يلزم مراجعة الطبيب والموافقة ومراجعة الاستخدام المقصود والمورّد.\n\nيمكن أن يساعد مساعد توثيق مقبول في إعداد نص يراجعه الممارس. حدد الاستخدام المقصود والموافقة ومعالجة المورّد وخطوة الاعتماد البشري؛ ولا يستبدل الحكم السريري أو يجعل كل عبارة مولدة صحيحة.\n\nمثال: يراجع الممارس مسودة مساعدة ويصححها قبل اعتماد الملاحظة.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_ai_scribe-benefit"},{"id":"package_branded_app-benefit","question":"كيف تعمل إضافة تطبيق مخصص للمريض والأسرة؟","answer":"يحدد نطاق الهوية والنشر وصيانة التطبيق بشكل مستقل.\n\nقد تسهل تجربة مريض أو أسرة بهوية متفق عليها التعرف على الخدمة والوصول إليها. حدد المسارات المدعومة والهوية والصلاحيات والنشر والصيانة والملكية في نطاق مستقل.\n\nمثال: يرى المستخدمون المصرح لهم هوية المؤسسة المتفق عليها عند الوصول إلى مسار المريض المقبول.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_branded_app-benefit"},{"id":"package_bespoke_interfaces-benefit","question":"كيف تعمل إضافة واجهات إضافية أو مخصصة؟","answer":"لكل موصل مواصفات قبول وتكلفة مورّد محددة.\n\nاربط مساراً خارجياً تحتاجه خارج الرصيد أو نطاق الموصل القياسي. اعتمد بيانات المصدر وربط الحقول والاختبار والصيانة والمتطلبات ورسوم المورّد قبل التطوير أو التفعيل.\n\nمثال: يحدد تبادل مع النظام المالي بحقوله المطلوبة واختبارات التسوية.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_bespoke_interfaces-benefit"},{"id":"package_equipment-benefit","question":"كيف تعمل إضافة الأجهزة والاتصال والحضور عن بُعد؟","answer":"أجهزة العميل أو عرض مستقل للأجهزة والاتصالات ورسوم المورّد.\n\nتدعم الأجهزة والاتصالات المناسبة والمقبولة المسار المختار. أكد التوافق والتوريد والتركيب وسعة الشبكة والصيانة ومسؤولية الحوادث بدلاً من افتراض شمول الأجهزة في الاشتراك.\n\nمثال: يستخدم مسار العناية عن بُعد أجهزة حضور عن بُعد يوفرها العميل وتعتمد أثناء الإعداد.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_equipment-benefit"},{"id":"package_onsite_training-benefit","question":"كيف تعمل إضافة التدريب في الموقع؟","answer":"تتفق أيام التدريب والحضور والسفر مسبقاً.\n\nيساعد التدريب العملي حسب الدور المستخدمين على تجربة المسار المقبول بحضور المدرب. اعتمد أيام التنفيذ والحضور والسفر والمواد وفحوص الكفاءة قبل الجدولة.\n\nمثال: يتدرب مستخدمو الاستقبال والفوترة على التسجيل واستثناءات الفوترة وإجراء التوقف المتفق عليه.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_onsite_training-benefit"},{"id":"package_dedicated_hosting-benefit","question":"كيف تعمل إضافة استضافة مخصصة وتصميم استمرارية الأعمال؟","answer":"تتطلب البنية وأهداف التعافي والبنية التحتية عرض مؤسسات.\n\nقد يعالج نشر وتصميم استمرارية مستقلان احتياجات بنية المؤسسة والتعافي. يتطلب ذلك عرض مؤسسات يحدد بنية التطبيق والتشغيل وأهداف الاستعادة. لا يثبت خيار القاعدة الخاصة في الماسية وحده نشراً مخصصاً لكل مكونات التطبيق.\n\nمثال: تتفق مجموعة مؤسسية على نشر التطبيق وتغطية الحوادث وأهداف التعافي المختبرة.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_dedicated_hosting-benefit"},{"id":"package_full_rcm-benefit","question":"كيف تعمل إضافة خدمة إدارة دورة الإيرادات RaaS؟","answer":"نسبة الباقة المختارة من التحصيل الفعلي المؤهل، تضاف إلى الاشتراك. تتطلب المؤسسات نسبة محددة معتمدة ضمن نطاقها المضبوط ونطاق تشغيل مقبولاً.\n\nتتولى RaaS المسؤولية التشغيلية المتفق عليها لقوائم الإيرادات بما يتجاوز رصيد ساعات الباقة. تضاف نسبة الباقة إلى الاشتراك وتحتسب على التحصيل المحقق المؤهل والمراجع بعد المبالغ المستردة والاستبعادات المتفق عليها. تعتمد القوائم والصلاحيات والأدلة والتقارير قبل التفعيل. تتطلب المؤسسات نسبة محددة معتمدة ضمن النطاق المضبوط.\n\nمثال: تقدم خدمة محددة لمتابعة المطالبات تقارير الإجراءات والتحصيل المتفق عليها وفق العقد المقبول.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_full_rcm-benefit"},{"id":"package_messages-benefit","question":"كيف تعمل إضافة استخدام الرسائل والفيديو؟","answer":"تتفق ميزانية الاستخدام لدى المورّد والموافقة؛ لا تشمل رسوماً غير محدودة.\n\nقد تدعم الرسائل والفيديو الخارجيان المقبولان التذكير والاستشارات والتحديثات المصرح بها. حدد المورّد وموافقة المريض وتدفق البيانات وميزانية الاستخدام ورسومه. لا يشمل مسار التواصل البرمجي استخداماً غير محدود لدى مورّد الرسائل أو الفيديو.\n\nمثال: تستخدم تذكيرات المواعيد المتفق عليها مورّداً معتمداً ضمن ميزانية الرسائل المقبولة.\n\nيعبر الاختيار عن طلب؛ ويؤكد السعر والتوافق والقبول في العرض.","url":"https://mansoq.com/faq?lang=ar#faq-package_messages-benefit"},{"id":"builder-open","question":"كيف أفتح منشئ المنصة المخصصة؟","answer":"اختر «ابنِ منصتك حسب احتياجك» بجانب عنوان الباقات أو في مقدمة الصفحة. تختفي الباقات ويظهر المنشئ في الصفحة نفسها. اختر المنشأة ثم الرعاية والخدمات وراجع الخطة وأدخل بيانات طلبك. يفصل ذلك مقارنة الباقات عن التهيئة التفصيلية في عرضين واضحين.","url":"https://mansoq.com/faq?lang=ar#faq-builder-open"},{"id":"builder-back","question":"هل أعود إلى الباقات دون فقد تقدم المنشئ؟","answer":"استخدم «العودة إلى الباقات». يختفي المنشئ وتعود الباقات. تحفظ إعادة فتح المنشئ في جلسة الصفحة نفسها الاختيارات والخطوة الحالية. تتبع أزرار المتصفح للخلف والأمام تبديل العرض أيضاً. يحمّل تغيير باقة البداية نطاق الباقة الجديدة، لذا راجع السعة والإضافات بعد اختيار باقة أخرى.","url":"https://mansoq.com/faq?lang=ar#faq-builder-back"},{"id":"choose-package-entry","question":"ماذا يحدث عند اختيار الأساسية أو بريميوم أو الماسية؟","answer":"يفتح منتج الرعاية وباقة البداية المختاران في المنشئ لمراجعة الخدمات المشمولة والسعة والإضافات الاختيارية. تستطيع إبقاء الباقة أو تخصيص النطاق المقترح. يبدأ «اطلب تواصل المبيعات» للمؤسسات استفسار عرض يتضمن المنتج والباقة، ولا يكشف سعراً عاماً لنطاق غير محدد.","url":"https://mansoq.com/faq?lang=ar#faq-choose-package-entry"},{"id":"builder-four-steps","question":"ماذا يحدث في كل خطوة من خطوات المنشئ الأربع؟","answer":"تحدد «منشأتك» بيئة الرعاية. تختار «الرعاية والخدمات» نموذج التشغيل والباقة أو خطتك والوحدات والحجم المطلوب. تظهر «مراجعة خطتك» التركيب المقترح والتفصيل التجاري. تجمع «بياناتك» الطلب والموافقة. راجع كل خطوة قبل الإرسال؛ طلب العرض ليس نشراً سريرياً حياً.","url":"https://mansoq.com/faq?lang=ar#faq-builder-four-steps"},{"id":"native-or-augment","question":"ما الفرق بين نظام رعاية متكامل والإضافة إلى نظامي الحالي؟","answer":"يشغل النظام المتكامل نطاق الرعاية والتشغيل المقبول على منسوق. أما الإضافة إلى نظام قائم فتحافظ عليه وتربط الخدمات المختارة ضمن نطاق تكامل مقبول. حدد النظام المسؤول عن كل سجل والبيانات المطلوب تبادلها. قد يؤثر نموذج التشغيل في الأهلية والواجهات والإعداد والسعر النهائي.","url":"https://mansoq.com/faq?lang=ar#faq-native-or-augment"},{"id":"required-companions","question":"لماذا تختار بعض الوحدات تلقائياً أو لا يمكن حذفها؟","answer":"تعتمد بعض الخدمات على هوية المريض المشتركة أو التوثيق أو الطلبات أو الفوترة أو الصلاحيات أو متطلبات أخرى. يضم المنشئ هذه المتطلبات لمراجعة المسار المقترح كنطاق كامل. المتطلب المشمول تلقائياً ليس إضافة اعتباطية؛ راجع التفصيل ونموذج التشغيل المقبول إذا لم يتضح سبب وجوده.","url":"https://mansoq.com/faq?lang=ar#faq-required-companions"},{"id":"saved-plan-device","question":"هل أحفظ خطة مقترحة أو أقارنها؟","answer":"عند توفر الحفظ في مسار المراجعة، يحفظ النطاق المقترح في المتصفح أو الجهاز الحالي لتقارنه لاحقاً. لا يساوي ذلك إرسال طلب أو حجز سعر. تجنب وضع بيانات مرضى في نطاق تجاري محفوظ. إذا تغير الكتالوج، فراجع النطاق والرسوم المحدثة قبل الاعتماد على اختيار سابق.","url":"https://mansoq.com/faq?lang=ar#faq-saved-plan-device"},{"id":"proposal-contents","question":"ماذا يجب أن يتضمن العرض النهائي؟","answer":"يجب أن يحدد منتجات الرعاية ونموذج التشغيل والإصدار والوحدات والسعة والمواقع ورسوم البرنامج والتشغيل المتكررة والإعداد والترحيل والواجهات والعمل الاختياري والضريبة ورسوم المورّد. ويجب أن يحدد المسؤوليات وشروط البيانات والمراحل والقبول والتزامات الدعم والدفع والعقد. تحتاج المؤسسات إلى سعر تحدده المبيعات للنطاق الكامل.","url":"https://mansoq.com/faq?lang=ar#faq-proposal-contents"},{"id":"trial-activation","question":"إذا توفرت تجربة، متى تبدأ فعلياً؟","answer":"المدة المنشورة ليست تفعيل التجربة. تؤكد الأهلية والتوقيت مع فريقك للمنتجات المختارة ونطاق التقييم المتفق عليه قبل التفعيل. تحكم تواريخ التفعيل والانتهاء المقبولة فترة التقييم الفعلية.","url":"https://mansoq.com/faq?lang=ar#faq-trial-activation"},{"id":"demo-real-data","question":"هل نستخدم سجلات مرضى حقيقية في العرض أو التقييم؟","answer":"تستخدم عملية قبول التقييم الموجه سيناريو بيانات اصطناعية. حدد مستخدمي الاختبار والمسار والدعم ومعايير النجاح. يحتاج تشغيل المرضى الحقيقيين إلى ترتيبات بيانات وسريرية وأمنية وإطلاق مقبولة مستقلة. يمكن أن يوضح العرض المسار ويساعد على التحقق من الملاءمة دون اعتبار المعاينة أو اتصال غير مقبول إنتاجاً سريرياً.","url":"https://mansoq.com/faq?lang=ar#faq-demo-real-data"},{"id":"current-trial-policy","question":"هل لكل باقات منسوق الفترة التجريبية نفسها؟","answer":"لا تشمل باقات الرعاية المنشورة حالياً فترة تجريبية تلقائية. تستطيع طلب عرض توضيحي ومناقشة تقييم يقبل مستقلاً مع الفريق. لا تفترض تجربة موحدة لمدة ١٤ يوماً من باقة أخرى أو تركيب خطة خاصة. يعتمد أي تقييم على النطاق والجاهزية والسياسة والبيانات الاصطناعية وتاريخ تفعيل مقبول.","href":"/pricing#configuration","url":"https://mansoq.com/faq?lang=ar#faq-current-trial-policy"},{"id":"upgrades","question":"هل نرقي الباقة عندما تنمو المؤسسة؟","answer":"ناقش السعة والواجهات وعبء التشغيل والمواقع ومتطلبات البيانات الجديدة مع المبيعات. اتفق على تاريخ التطبيق والرسوم والصلاحيات المحدثة وأي ترحيل أو إعداد قبل تغيير النطاق الحي. يساعد المنشئ على مقارنة باقة مقترحة، ولا يعدل عقد العميل القائم بنفسه.","url":"https://mansoq.com/faq?lang=ar#faq-upgrades"},{"id":"downgrades","question":"ما الذي نراجعه قبل خفض الباقة؟","answer":"راجع قدرة الباقة الأصغر على دعم سعة الرعاية والاتصالات المصانة والعمل التشغيلي الفعلي. راجع الوظائف أو خيارات النشر المرتبطة بالماسية أو المؤسسات. إذا استخدمت التخزين الخاص فلا تفترض احتفاظ الباقة الأقل به؛ اتفق على نشر مدعوم وخطة ترحيل. يتبع توقيت العقد وتغيير السعر الشروط الموقعة.","url":"https://mansoq.com/faq?lang=ar#faq-downgrades"},{"id":"change-products","question":"هل نضيف المنتجات أو نحذفها بعد الإطلاق؟","answer":"تعامل مع التغيير كتحديث مراجع لنطاق التشغيل. أكد المتطلبات والمستخدمين والسجلات المتأثرة والواجهات واستمرارية الرعاية والأثر التجاري. قد تحتاج إضافة قسم إلى إعداد وتدريب وقبول، وقد يحتاج حذفه إلى خطة وصول للسجلات أو أرشفة. اعتمد التغيير قبل تعديل المسارات الحية.","url":"https://mansoq.com/faq?lang=ar#faq-change-products"},{"id":"renewal-cancellation-refund","question":"ما قواعد التجديد والإلغاء والاسترداد؟","answer":"يحدد العرض والاتفاق الموقعان هذه القواعد؛ ولا تنشر بطاقات الباقات مدة إشعار موحدة أو حق استرداد موحداً أو سياسة تجديد تلقائي عامة. اطلب تحديد المدة والإشعار والرسوم المعلقة ومعالجة السداد السنوي وشروط الخروج المبكر قبل التوقيع. طبق الشروط المقبولة على حالة مؤسستك.","url":"https://mansoq.com/faq?lang=ar#faq-renewal-cancellation-refund"},{"id":"export-and-exit","question":"هل نحصل على سجلاتنا عند مغادرة منسوق؟","answer":"النسخ والتصدير جزء من أساس الباقة، ويحدد اتفاق الخروج مجالات التصدير المصرح بها وصيغته وملفاته وتوقيته ومستلميه ومسؤولياته. اتفق على السجلات السريرية والمرفقات والتاريخ المالي وسجلات الخدمة المتفق عليها بشكل مستقل. تحقق من الاكتمال والوصول قبل إيقاف الخدمة القديمة.","url":"https://mansoq.com/faq?lang=ar#faq-export-and-exit"},{"id":"exit-with-own-storage","question":"هل يجعل امتلاك القاعدة الخروج أو ترحيل التطبيق تلقائياً؟","answer":"يمنحك امتلاك البنية المقبولة تحكماً مباشراً في تلك الوجهة. تظل بحاجة إلى انتقال منظم للتطبيق والبيانات، يشمل التصدير المدعوم وعلاقات السجلات والملفات والمعرّفات والصلاحيات والنسخ وأي ربط للهيكل أو الواجهات مع النظام المستلم. يتبع الاحتفاظ وإيقاف الخدمة شروط البيانات والخروج المتفق عليها.","url":"https://mansoq.com/faq?lang=ar#faq-exit-with-own-storage"},{"id":"scope-change-approval","question":"كيف تعتمد الطلبات المخصصة وتغييرات النطاق؟","answer":"صف الحاجة العملية والمسار المتأثر والمسؤول والمخرجات المتوقعة واختبار القبول. يجب أن يحدد العرض أو سجل التغيير جهد التنفيذ والسعر والمسؤوليات والمتطلبات والأثر على الإصدار أو الدعم. لا تعتبر فكرة شفهية أو مربعاً اختيارياً التزاماً مقبولاً بتطوير مخصص.","url":"https://mansoq.com/faq?lang=ar#faq-scope-change-approval"},{"id":"success-measurement","question":"كيف نقيس إن كانت المنصة تحقق قيمة؟","answer":"اتفق قبل الإطلاق على خط أساس ومجموعة صغيرة من مؤشرات المسار، مثل المهام التشغيلية المتأخرة واكتمال التسليم وتكرار الإدخال واكتمال التوثيق واستخدام السعة. استخدم تعريفات ثابتة وقارن الفترات بعد تدريب المستخدمين. تابع إجراءات المراجعة الشهرية وميز التحسن المرصود عن فائدة توضيحية أو ادعاء إيرادات غير متحقق.","url":"https://mansoq.com/faq?lang=ar#faq-success-measurement"}],"faqTopics":[{"id":"start-here","title":"ابدأ من هنا","summary":"تعرّف على المنصة ومن تخدمهم والخطوة التالية.","answers":["https://mansoq.com/faq?lang=ar#faq-mansoq-overview","https://mansoq.com/faq?lang=ar#faq-which-organizations","https://mansoq.com/faq?lang=ar#faq-existing-software-coexistence","https://mansoq.com/faq?lang=ar#faq-product-vs-service","https://mansoq.com/faq?lang=ar#faq-request-a-demo","https://mansoq.com/faq?lang=ar#faq-english-arabic"]},{"id":"roles-access","title":"المستخدمون والأدوار والصلاحيات","summary":"امنح كل فريق صلاحيات مناسبة ومسؤوليات واضحة.","answers":["https://mansoq.com/faq?lang=ar#faq-which-user-roles","https://mansoq.com/faq?lang=ar#faq-multi-site-governance","https://mansoq.com/faq?lang=ar#faq-who-approves-clinical-records","https://mansoq.com/faq?lang=ar#faq-account-vs-clinical-access"]},{"id":"clinical-governance","title":"المسارات السريرية والاستخدام الآمن","summary":"افهم حدود المسارات والمراجعة البشرية ونطاق الأقسام.","answers":["https://mansoq.com/faq?lang=ar#faq-clinical-workflow-coverage","https://mansoq.com/faq?lang=ar#faq-department-vs-results","https://mansoq.com/faq?lang=ar#faq-medication-safety-workflow","https://mansoq.com/faq?lang=ar#faq-ai-clinical-review","https://mansoq.com/faq?lang=ar#faq-teleicu-responsibilities","https://mansoq.com/faq?lang=ar#faq-clinical-downtime"]},{"id":"migration-planning","title":"الترحيل والأنظمة القائمة","summary":"انقل البيانات أو اربطها بمسؤولية وتسوية وخطة انتقال واضحة.","answers":["https://mansoq.com/faq?lang=ar#faq-migration-source-systems","https://mansoq.com/faq?lang=ar#faq-migration-data-domains","https://mansoq.com/faq?lang=ar#faq-migration-patient-matching","https://mansoq.com/faq?lang=ar#faq-migration-rehearsal","https://mansoq.com/faq?lang=ar#faq-migration-no-downtime","https://mansoq.com/faq?lang=ar#faq-historical-archive"]},{"id":"it-integrations","title":"التقنية والواجهات والإعداد التقني","summary":"خطط للمتطلبات التقنية واختبر الاتصال الفعلي.","answers":["https://mansoq.com/faq?lang=ar#faq-integration-standards","https://mansoq.com/faq?lang=ar#faq-integration-scope-checklist","https://mansoq.com/faq?lang=ar#faq-national-activation","https://mansoq.com/faq?lang=ar#faq-identity-sso","https://mansoq.com/faq?lang=ar#faq-devices-network","https://mansoq.com/faq?lang=ar#faq-deployment-hosting-options","https://mansoq.com/faq?lang=ar#faq-integration-change-management"]},{"id":"privacy-governance","title":"الخصوصية والأمن والحوكمة","summary":"أكد الضوابط والأدلة ومسؤولية كل تدفق للبيانات.","answers":["https://mansoq.com/faq?lang=ar#faq-security-evidence","https://mansoq.com/faq?lang=ar#faq-data-ownership-access","https://mansoq.com/faq?lang=ar#faq-data-location-subprocessors","https://mansoq.com/faq?lang=ar#faq-backup-recovery-evidence","https://mansoq.com/faq?lang=ar#faq-privacy-requests","https://mansoq.com/faq?lang=ar#faq-safe-support-information"]},{"id":"delivery-support","title":"التنفيذ والتدريب والدعم","summary":"جهّز فريقك واعتمد المسار واتفق على الدعم المستمر.","answers":["https://mansoq.com/faq?lang=ar#faq-implementation-start-checklist","https://mansoq.com/faq?lang=ar#faq-implementation-timeline","https://mansoq.com/faq?lang=ar#faq-training-by-role","https://mansoq.com/faq?lang=ar#faq-go-live-acceptance","https://mansoq.com/faq?lang=ar#faq-support-hours-sla","https://mansoq.com/faq?lang=ar#faq-report-a-problem","https://mansoq.com/faq?lang=ar#faq-new-site-module"]},{"id":"procurement-partners","title":"الشراء والمشتريات والشراكات","summary":"ابنِ نطاقاً قابلاً للمراجعة وقراراً تجارياً واضحاً.","answers":["https://mansoq.com/faq?lang=ar#faq-procurement-information","https://mansoq.com/faq?lang=ar#faq-quotation-total-cost","https://mansoq.com/faq?lang=ar#faq-contract-before-activation","https://mansoq.com/faq?lang=ar#faq-roi-guarantees","https://mansoq.com/faq?lang=ar#faq-partner-implementation","https://mansoq.com/faq?lang=ar#faq-data-exit-portability"]},{"id":"patient-family-guide","title":"المرضى والأسر والاستفسارات العامة","summary":"اعثر على المسار المناسب للرعاية والسجلات والوصول.","answers":["https://mansoq.com/faq?lang=ar#faq-patient-medical-advice","https://mansoq.com/faq?lang=ar#faq-patient-portal-access","https://mansoq.com/faq?lang=ar#faq-family-proxy-consent","https://mansoq.com/faq?lang=ar#faq-patient-billing-insurance"]},{"id":"product-workflows","title":"دليل مسارات المنتجات والأقسام","summary":"إجابات من أدلة المنتجات المنشورة حول المهام والتسليم والاتصالات والقبول.","answers":["https://mansoq.com/faq?lang=ar#faq-module-core","https://mansoq.com/faq?lang=ar#faq-module-outpatient","https://mansoq.com/faq?lang=ar#faq-module-inpatient","https://mansoq.com/faq?lang=ar#faq-module-emergency","https://mansoq.com/faq?lang=ar#faq-module-teleicu","https://mansoq.com/faq?lang=ar#faq-module-home-palliative","https://mansoq.com/faq?lang=ar#faq-module-operating-room","https://mansoq.com/faq?lang=ar#faq-module-icu","https://mansoq.com/faq?lang=ar#faq-module-pharmacy","https://mansoq.com/faq?lang=ar#faq-module-laboratory","https://mansoq.com/faq?lang=ar#faq-module-radiology","https://mansoq.com/faq?lang=ar#faq-module-inventory","https://mansoq.com/faq?lang=ar#faq-module-clinical-documentation","https://mansoq.com/faq?lang=ar#faq-module-orders-medication","https://mansoq.com/faq?lang=ar#faq-module-patient-access","https://mansoq.com/faq?lang=ar#faq-module-billing-finance","https://mansoq.com/faq?lang=ar#faq-module-revenue-cycle","https://mansoq.com/faq?lang=ar#faq-module-sbs-specific","https://mansoq.com/faq?lang=ar#faq-module-sbs-full","https://mansoq.com/faq?lang=ar#faq-module-drg","https://mansoq.com/faq?lang=ar#faq-module-nphies","https://mansoq.com/faq?lang=ar#faq-module-zatca","https://mansoq.com/faq?lang=ar#faq-module-analytics","https://mansoq.com/faq?lang=ar#faq-module-ai","https://mansoq.com/faq?lang=ar#faq-module-interfaces","https://mansoq.com/faq?lang=ar#faq-module-network-governance","https://mansoq.com/faq?lang=ar#faq-module-managed-revenue"]},{"id":"choosing","title":"اختيار المنصة والباقة","summary":"ابدأ ببيئة الرعاية وفريقك واحتياجات التشغيل.","answers":["https://mansoq.com/faq?lang=ar#faq-what-is-mansoq","https://mansoq.com/faq?lang=ar#faq-software-and-services","https://mansoq.com/faq?lang=ar#faq-four-care-products","https://mansoq.com/faq?lang=ar#faq-essential-fit","https://mansoq.com/faq?lang=ar#faq-premium-fit","https://mansoq.com/faq?lang=ar#faq-diamond-fit","https://mansoq.com/faq?lang=ar#faq-enterprise-fit","https://mansoq.com/faq?lang=ar#faq-same-safety-foundation","https://mansoq.com/faq?lang=ar#faq-choose-by-benefit","https://mansoq.com/faq?lang=ar#faq-mixed-care-group","https://mansoq.com/faq?lang=ar#faq-all-plan-foundation"]},{"id":"benefits","title":"شرح الميزات وفوائدها","summary":"المعنى وطريقة العمل ومثال واضح والنتيجة المتوقعة.","answers":["https://mansoq.com/faq?lang=ar#faq-feature-rcm-raas","https://mansoq.com/faq?lang=ar#faq-feature-patient-access","https://mansoq.com/faq?lang=ar#faq-feature-dashboards","https://mansoq.com/faq?lang=ar#faq-feature-monthly-review","https://mansoq.com/faq?lang=ar#faq-feature-entity-governance","https://mansoq.com/faq?lang=ar#faq-feature-group-reporting","https://mansoq.com/faq?lang=ar#faq-feature-custom-integrations","https://mansoq.com/faq?lang=ar#faq-feature-implementation","https://mansoq.com/faq?lang=ar#faq-feature-national-workflows","https://mansoq.com/faq?lang=ar#faq-feature-customer-storage"]},{"id":"pricing","title":"الأسعار والرسوم والشراء","summary":"افهم الرسم المتكرر والعمل الذي يسعّر بشكل مستقل.","answers":["https://mansoq.com/faq?lang=ar#faq-package-price","https://mansoq.com/faq?lang=ar#faq-currency-tax","https://mansoq.com/faq?lang=ar#faq-enterprise-price-hidden","https://mansoq.com/faq?lang=ar#faq-annual-discount","https://mansoq.com/faq?lang=ar#faq-setup-separate","https://mansoq.com/faq?lang=ar#faq-third-party-costs","https://mansoq.com/faq?lang=ar#faq-avoid-surprise-fees","https://mansoq.com/faq?lang=ar#faq-monthly-contract","https://mansoq.com/faq?lang=ar#faq-request-no-payment","https://mansoq.com/faq?lang=ar#faq-regional-pricing","https://mansoq.com/faq?lang=ar#faq-clinics-extra-rates","https://mansoq.com/faq?lang=ar#faq-polyclinics-extra-rates","https://mansoq.com/faq?lang=ar#faq-teleicu-extra-rates","https://mansoq.com/faq?lang=ar#faq-home_palliative-extra-rates","https://mansoq.com/faq?lang=ar#faq-annual-price-worked-example","https://mansoq.com/faq?lang=ar#faq-extra-capacity-worked-example"]},{"id":"capacity","title":"السعة والمستخدمون والنمو","summary":"اعرف ما الذي يحتسب وما يتغير مع نموك.","answers":["https://mansoq.com/faq?lang=ar#faq-capacity-measures","https://mansoq.com/faq?lang=ar#faq-clinician-counting","https://mansoq.com/faq?lang=ar#faq-icu-counting","https://mansoq.com/faq?lang=ar#faq-home-patient-counting","https://mansoq.com/faq?lang=ar#faq-capacity-not-hours","https://mansoq.com/faq?lang=ar#faq-sites-definition","https://mansoq.com/faq?lang=ar#faq-growth-planning","https://mansoq.com/faq?lang=ar#faq-enterprise-reference-capacity","https://mansoq.com/faq?lang=ar#faq-current-capacity-ladder"]},{"id":"clinics","title":"العيادات: الرعاية اليومية","summary":"من المواعيد والاستشارة إلى الفوترة والمتابعة.","answers":["https://mansoq.com/faq?lang=ar#faq-clinic-day","https://mansoq.com/faq?lang=ar#faq-clinic-cash-insurance","https://mansoq.com/faq?lang=ar#faq-clinic-reminders","https://mansoq.com/faq?lang=ar#faq-clinic-departments","https://mansoq.com/faq?lang=ar#faq-clinics-rcm-raas","https://mansoq.com/faq?lang=ar#faq-clinics-prices","https://mansoq.com/faq?lang=ar#faq-clinics-tier-benefits","https://mansoq.com/faq?lang=ar#faq-clinics-care-workflow-example","https://mansoq.com/faq?lang=ar#faq-clinics-automation-example","https://mansoq.com/faq?lang=ar#faq-clinics-named-owner-example"]},{"id":"polyclinics","title":"المجمعات الطبية: ربط التخصصات","summary":"نسق الأقسام حول المريض نفسه وأدلة الخدمات.","answers":["https://mansoq.com/faq?lang=ar#faq-polyclinic-clinic-difference","https://mansoq.com/faq?lang=ar#faq-cross-specialty-access","https://mansoq.com/faq?lang=ar#faq-polyclinic-stock","https://mansoq.com/faq?lang=ar#faq-polyclinic-charge-leakage","https://mansoq.com/faq?lang=ar#faq-polyclinics-rcm-raas","https://mansoq.com/faq?lang=ar#faq-polyclinics-prices","https://mansoq.com/faq?lang=ar#faq-polyclinics-tier-benefits","https://mansoq.com/faq?lang=ar#faq-polyclinics-care-workflow-example","https://mansoq.com/faq?lang=ar#faq-polyclinics-automation-example","https://mansoq.com/faq?lang=ar#faq-polyclinics-named-owner-example"]},{"id":"teleicu","title":"العناية عن بُعد: مسارات الرعاية الحرجة","summary":"افهم الاستشارات وربط البيانات والمسؤولية السريرية.","answers":["https://mansoq.com/faq?lang=ar#faq-teleicu-team-model","https://mansoq.com/faq?lang=ar#faq-teleicu-essential-data","https://mansoq.com/faq?lang=ar#faq-teleicu-interface-examples","https://mansoq.com/faq?lang=ar#faq-teleicu-stale-data","https://mansoq.com/faq?lang=ar#faq-teleicu-alert-responsibility","https://mansoq.com/faq?lang=ar#faq-teleicu-equipment","https://mansoq.com/faq?lang=ar#faq-teleicu-value","https://mansoq.com/faq?lang=ar#faq-teleicu-rcm-raas","https://mansoq.com/faq?lang=ar#faq-teleicu-prices","https://mansoq.com/faq?lang=ar#faq-teleicu-tier-benefits","https://mansoq.com/faq?lang=ar#faq-teleicu-care-workflow-example","https://mansoq.com/faq?lang=ar#faq-teleicu-automation-example","https://mansoq.com/faq?lang=ar#faq-teleicu-named-owner-example"]},{"id":"home","title":"الرعاية المنزلية والتلطيفية: الاستمرارية","summary":"نسق الزيارات وخطط الرعاية والمتابعة المصرح بها مع الأسرة.","answers":["https://mansoq.com/faq?lang=ar#faq-home-day","https://mansoq.com/faq?lang=ar#faq-home-routing","https://mansoq.com/faq?lang=ar#faq-family-access","https://mansoq.com/faq?lang=ar#faq-palliative-records","https://mansoq.com/faq?lang=ar#faq-home-monitoring","https://mansoq.com/faq?lang=ar#faq-missed-home-visits","https://mansoq.com/faq?lang=ar#faq-home-emergencies","https://mansoq.com/faq?lang=ar#faq-home_palliative-rcm-raas","https://mansoq.com/faq?lang=ar#faq-home_palliative-prices","https://mansoq.com/faq?lang=ar#faq-home_palliative-tier-benefits","https://mansoq.com/faq?lang=ar#faq-home_palliative-care-workflow-example","https://mansoq.com/faq?lang=ar#faq-home_palliative-automation-example","https://mansoq.com/faq?lang=ar#faq-home_palliative-named-owner-example"]},{"id":"operations","title":"التشغيل المدار والدعم","summary":"اعرف من ينفذ العمل وكيف تستخدم الساعات وما معنى الدعم.","answers":["https://mansoq.com/faq?lang=ar#faq-managed-hours-definition","https://mansoq.com/faq?lang=ar#faq-managed-hours-tracking","https://mansoq.com/faq?lang=ar#faq-unused-hours","https://mansoq.com/faq?lang=ar#faq-extra-hour-approval","https://mansoq.com/faq?lang=ar#faq-service-window","https://mansoq.com/faq?lang=ar#faq-support-vs-managed","https://mansoq.com/faq?lang=ar#faq-named-owner-accountability","https://mansoq.com/faq?lang=ar#faq-queue-ownership-example","https://mansoq.com/faq?lang=ar#faq-monthly-review-results","https://mansoq.com/faq?lang=ar#faq-clinical-staffing-responsibility","https://mansoq.com/faq?lang=ar#faq-current-managed-hour-allowances"]},{"id":"rcm-raas","title":"إدارة الإيرادات RaaS: الخدمة ورسوم التحصيل","summary":"افهم خدمة الإيرادات المدارة وأساس الرسوم والفوترة المعتمدة.","answers":["https://mansoq.com/faq?lang=ar#faq-rcm-raas-benefit","https://mansoq.com/faq?lang=ar#faq-rcm-raas-additional","https://mansoq.com/faq?lang=ar#faq-rcm-raas-collection-basis","https://mansoq.com/faq?lang=ar#faq-rcm-raas-yearly","https://mansoq.com/faq?lang=ar#faq-rcm-raas-outcomes"]},{"id":"connections","title":"التكاملات والمسارات الوطنية","summary":"ميز بين المسار المشمول والاتصال الحي المقبول.","answers":["https://mansoq.com/faq?lang=ar#faq-interface-meaning","https://mansoq.com/faq?lang=ar#faq-interface-counting","https://mansoq.com/faq?lang=ar#faq-national-connectors","https://mansoq.com/faq?lang=ar#faq-nphies-live-readiness","https://mansoq.com/faq?lang=ar#faq-zatca-coding","https://mansoq.com/faq?lang=ar#faq-keep-existing-system","https://mansoq.com/faq?lang=ar#faq-integration-failure","https://mansoq.com/faq?lang=ar#faq-all-vendors","https://mansoq.com/faq?lang=ar#faq-current-interface-allowances"]},{"id":"storage","title":"حماية البيانات والتخزين والاستعادة","summary":"افهم خيار التخزين والمسؤوليات المرتبطة به.","answers":["https://mansoq.com/faq?lang=ar#faq-own-storage-plans","https://mansoq.com/faq?lang=ar#faq-storage-included-optional","https://mansoq.com/faq?lang=ar#faq-supported-storage-types","https://mansoq.com/faq?lang=ar#faq-storage-live-app","https://mansoq.com/faq?lang=ar#faq-storage-connection-acceptance","https://mansoq.com/faq?lang=ar#faq-storage-unavailable","https://mansoq.com/faq?lang=ar#faq-storage-infrastructure-cost","https://mansoq.com/faq?lang=ar#faq-storage-move-later","https://mansoq.com/faq?lang=ar#faq-data-location","https://mansoq.com/faq?lang=ar#faq-security-certification","https://mansoq.com/faq?lang=ar#faq-backup-recovery-objectives","https://mansoq.com/faq?lang=ar#faq-data-contract-retention"]},{"id":"implementation","title":"الإعداد والترحيل والإطلاق","summary":"تابع المسار من النطاق المتفق عليه إلى الخدمة التشغيلية المقبولة.","answers":["https://mansoq.com/faq?lang=ar#faq-launch-sequence","https://mansoq.com/faq?lang=ar#faq-launch-timeline","https://mansoq.com/faq?lang=ar#faq-customer-launch-inputs","https://mansoq.com/faq?lang=ar#faq-imports-templates","https://mansoq.com/faq?lang=ar#faq-migration-quality","https://mansoq.com/faq?lang=ar#faq-legacy-history","https://mansoq.com/faq?lang=ar#faq-training","https://mansoq.com/faq?lang=ar#faq-production-readiness","https://mansoq.com/faq?lang=ar#faq-pilot-and-phases","https://mansoq.com/faq?lang=ar#faq-cutover-and-rollback","https://mansoq.com/faq?lang=ar#faq-current-setup-budgets"]},{"id":"additions","title":"الإضافات الاختيارية والخدمات المتخصصة","summary":"اعرف سبب إضافة الخدمة وكيف يعتمد نطاقها.","answers":["https://mansoq.com/faq?lang=ar#faq-optional-vs-required","https://mansoq.com/faq?lang=ar#faq-addon-checkbox-activation","https://mansoq.com/faq?lang=ar#faq-package_ai_scribe-benefit","https://mansoq.com/faq?lang=ar#faq-package_branded_app-benefit","https://mansoq.com/faq?lang=ar#faq-package_bespoke_interfaces-benefit","https://mansoq.com/faq?lang=ar#faq-package_equipment-benefit","https://mansoq.com/faq?lang=ar#faq-package_onsite_training-benefit","https://mansoq.com/faq?lang=ar#faq-package_dedicated_hosting-benefit","https://mansoq.com/faq?lang=ar#faq-package_full_rcm-benefit","https://mansoq.com/faq?lang=ar#faq-package_messages-benefit"]},{"id":"builder","title":"المنشئ والعروض والتقييم","summary":"خصص النطاق وراجع اختياراتك وافهم التفعيل.","answers":["https://mansoq.com/faq?lang=ar#faq-builder-open","https://mansoq.com/faq?lang=ar#faq-builder-back","https://mansoq.com/faq?lang=ar#faq-choose-package-entry","https://mansoq.com/faq?lang=ar#faq-builder-four-steps","https://mansoq.com/faq?lang=ar#faq-native-or-augment","https://mansoq.com/faq?lang=ar#faq-required-companions","https://mansoq.com/faq?lang=ar#faq-saved-plan-device","https://mansoq.com/faq?lang=ar#faq-proposal-contents","https://mansoq.com/faq?lang=ar#faq-trial-activation","https://mansoq.com/faq?lang=ar#faq-demo-real-data","https://mansoq.com/faq?lang=ar#faq-current-trial-policy"]},{"id":"changes","title":"التغييرات والاتفاقات والمغادرة","summary":"خطط للنمو وتغيير الخدمة والخروج المنظم.","answers":["https://mansoq.com/faq?lang=ar#faq-upgrades","https://mansoq.com/faq?lang=ar#faq-downgrades","https://mansoq.com/faq?lang=ar#faq-change-products","https://mansoq.com/faq?lang=ar#faq-renewal-cancellation-refund","https://mansoq.com/faq?lang=ar#faq-export-and-exit","https://mansoq.com/faq?lang=ar#faq-exit-with-own-storage","https://mansoq.com/faq?lang=ar#faq-scope-change-approval","https://mansoq.com/faq?lang=ar#faq-success-measurement"]}]}}]}