Yêu cầu bản demo

Báo cáo bản địa hóa

Heidi

Healthcare AI

heidihealth.com

Sản phẩm: Heidi is an AI care partner for clinicians, supporting clinical documentation, note-taking, coding, evidence-based decisions, care gap outreach, and patient communications. It is designed to reduce administrative work across the care journey.

Giọng điệu thương hiệu: Reassuring, practical, clinician-focused

Điểm bản địa hóa

63/100

Cần cải thiện

Người dùng có thể gặp phải các vấn đề bản địa hóa đáng chú ý.

  • 77Kiểm tra kỹ thuật
  • 42Kiểm tra ngôn ngữ
  • 73Kiểm tra theo ngữ cảnh
  • 61Kiểm tra trực quan
Audited: 8/17/2026Scope: Mẫu thông minh công khai · ghi công về kỹ thuật, ngôn ngữ, ngữ cảnh và hình ảnhĐộ tin cậy: Kiểm tra sơ bộ tình trạng từ các trang được lấy mẫu — không phải quá trình quét toàn bộ trang web.

Đã lấy mẫu 15 trang dựa trên các tiêu chí tín dụng bản địa hóa về kỹ thuật, ngôn ngữ, ngữ cảnh và hình ảnh. Cách chúng tôi chấm điểm các cuộc kiểm tra bản địa hóa

Bạn so sánh như thế nào

Xếp hạng #16 trong số 22 cuộc kiểm tra công khai

Top 32% số miền được kiểm traĐiểm trung bình công khai: 68/100

Khắc phục trước

  • highlinguistic · 92% độ tin cậy

    Untranslated call to action

    A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.

    Tìm thấy tại đây

    Primary action · <button>

    https://www.heidihealth.com/fr-ca

    Điều chúng tôi nhận thấy

    Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr

    Cách khắc phục

    Translate leftover source-language CTAs to match the surrounding locale copy.

  • mediumtechnical · 88% độ tin cậy

    Sitemap omits some published locales

    Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    Sitemap locales in sample: en; missing: fr, de, es, it

    Cách khắc phục

    Include URLs for every published locale prefix in the sitemap.

  • mediumvisual · 88% độ tin cậy

    Localized text is much longer than the source

    A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de

    Cách khắc phục

    Shorten the translation or give the control more room so the longer copy does not overflow.

Tiêu chí kiểm tra

5 đạt · 22 cần sửa · 8 không áp dụng

Cần chú ý (22)

  • Language switcher

    Fail55kỹ thuật

    Visitors should move between locales without losing the current page.

    • mediumtechnical · 70% độ tin cậy

      Current-page preservation is not demonstrated

      The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.

      Tìm thấy tại đây

      Header · language switcher

      https://www.heidihealth.com/en-us

      Điều chúng tôi nhận thấy

      "locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".

      Cách khắc phục

      Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.

  • Sitemap

    Fail70kỹ thuật

    Like Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.

    • mediumtechnical · 88% độ tin cậy

      Sitemap omits some published locales

      Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      Sitemap locales in sample: en; missing: fr, de, es, it

      Cách khắc phục

      Include URLs for every published locale prefix in the sitemap.

  • Structured data

    Fail0kỹ thuật

    JSON-LD inLanguage should match the page locale when structured data is present.

    • lowtechnical · 95% độ tin cậy

      Structured data omits inLanguage

      JSON-LD is present but does not declare inLanguage on sampled pages.

      Tìm thấy tại đây

      JSON-LD · <script type="application/ld+json">

      https://www.heidihealth.com/en-us

      Điều chúng tôi nhận thấy

      Organization is present but inLanguage is missing

      Cách khắc phục

      Set JSON-LD inLanguage to match each page locale.

  • Accessibility localisation

    Fail72kỹ thuật

    lang, aria-label, and alt text should match the page locale.

    • infotechnical · 82% độ tin cậy

      Locale metadata is explicit for the sampled English pages

      The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "htmlLang":"en-us" and "htmlLang":"en-gb"

      Cách khắc phục

      Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.

  • Translation completeness

    Fail0linguistic

    Localized pages should not leave source-language copy in place, except brand names and URLs.

    • highlinguistic · 92% độ tin cậy

      Untranslated call to action

      A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.

      Tìm thấy tại đây

      Primary action · <button>

      https://www.heidihealth.com/fr-ca

      Điều chúng tôi nhận thấy

      Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr

      Cách khắc phục

      Translate leftover source-language CTAs to match the surrounding locale copy.

  • Terminology consistency

    Fail50linguistic

    Important concepts should not be translated differently across pages.

    • infolinguistic · 95% độ tin cậy

      Cross-locale terminology cannot be assessed

      The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.

      Cách khắc phục

      Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.

  • Translation accuracy

    Fail50linguistic

    Target copy should preserve the source meaning, numbers, and product actions.

    • infolinguistic · 95% độ tin cậy

      Translation accuracy cannot be assessed

      No target-language copy or source-to-target comparison is provided in the evidence.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".

      Cách khắc phục

      Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.

  • Fluency

    Fail50linguistic

    Copy should sound natural, without grammar issues or machine-translation artifacts.

    • infolinguistic · 95% độ tin cậy

      Localized fluency cannot be assessed

      The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Relief in every visit The AI Care Partner for clinicians"

      Cách khắc phục

      Review rendered copy in each target locale with a native-language reviewer.

  • Brand voice

    Fail50linguistic

    Localized copy should preserve the intended tone of the source.

    • infolinguistic · 95% độ tin cậy

      Localized brand voice cannot be assessed

      The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Relief in every visit" and "The AI Care Partner for clinicians"

      Cách khắc phục

      Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.

  • Grammar and style

    Fail50linguistic

    Locale-specific capitalization, punctuation, formality, and agreement should be correct.

    • infolinguistic · 95% độ tin cậy

      Locale-specific grammar and style cannot be assessed

      Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".

      Cách khắc phục

      Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.

  • CTA intent

    Fail72contextual

    Localized calls to action should communicate the intended product action.

    • infocontextual · 82% độ tin cậy

      English CTA intent is clear in the sampled page

      The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Get Heidi free" and "Book a demo"

      Cách khắc phục

      Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.

  • UI context

    Fail72contextual

    Translations should fit the UI component: button, nav, form, modal, or error.

    • infocontextual · 82% độ tin cậy

      English UI contexts are identifiable

      The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"

      Cách khắc phục

      Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.

  • Product context

    Fail72contextual

    Language should match product concepts such as plans, settings, and workflows.

    • infocontextual · 82% độ tin cậy

      Product context is clear in the sampled English copy

      The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"

      Cách khắc phục

      Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.

  • Contextual meaning

    Fail72contextual

    Strings should be judged in surrounding page and component context, not in isolation.

    • infocontextual · 82% độ tin cậy

      English strings have visible page context

      The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.

      Cách khắc phục

      Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.

  • Audience context

    Fail78contextual

    Language should fit the intended audience, such as consumer, enterprise, or developer.

    • infocontextual · 88% độ tin cậy

      The sampled page clearly targets clinicians

      The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      "Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"

      Cách khắc phục

      Keep clinician-facing terminology and professional positioning consistent across all target locales.

  • Text expansion

    Fail40trực quan

    Longer translations should not create obvious length pressure versus the source UI.

    • mediumvisual · 88% độ tin cậy

      Localized text is much longer than the source

      A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de

      Cách khắc phục

      Shorten the translation or give the control more room so the longer copy does not overflow.

  • Localized images and assets

    Fail50trực quan

    Language-specific images and alt text should match the page locale.

    • infovisual · 65% độ tin cậy

      Localized assets cannot be verified

      The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.

      Tìm thấy tại đây

      Cách khắc phục

      Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.

  • Visual hierarchy

    Fail55trực quan

    Localization should not make headings or CTAs lose scanability.

    • lowvisual · 80% độ tin cậy

      Heading is excessively long

      A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      „Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it

      Cách khắc phục

      Shorten the heading so it does not crowd the visual hierarchy.

  • Component consistency

    Fail70trực quan

    Repeated components should stay visually consistent across locales.

    • lowvisual · 95% độ tin cậy

      Repeated components differ across locales

      Button counts differ between the source locale and fr.

      Tìm thấy tại đây

      Điều chúng tôi nhận thấy

      Source locale has 14 buttons; fr has 8.

      Cách khắc phục

      Keep the same repeated controls across locales, or drop unused ones on purpose.

  • Text overflow

    Fail70trực quan

    Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

  • Layout breakage

    Fail70trực quan

    Localized pages should not overlap, break grids, or overflow modals.

  • Responsive localisation

    Fail70trực quan

    Localized layouts should hold up across mobile, tablet, and desktop widths.

Các kiểm tra đã đạt (5)

Không áp dụng (8)

Các ngôn ngữ được phát hiện

de-be (hreflang)de-ch (hreflang)de-de (hreflang)de-lu (hreflang)en-au (hreflang)en-ca (hreflang)en-gb (hreflang)en-hk (hreflang)en-ie (hreflang)en-my (hreflang)en-nz (hreflang)en-sg (hreflang)en-us (html_lang)en-za (hreflang)es-ar (hreflang)es-es (hreflang)es-mx (hreflang)fr-be (hreflang)fr-ca (hreflang)fr-ch (hreflang)fr-fr (hreflang)fr-lu (hreflang)it-it (hreflang)ja-jp (hreflang)

Toàn bộ phát hiện

  • mediumtechnical · 88% độ tin cậy

    Sitemap omits some published locales

    Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    Sitemap locales in sample: en; missing: fr, de, es, it

    Cách khắc phục

    Include URLs for every published locale prefix in the sitemap.

  • lowtechnical · 95% độ tin cậy

    Structured data omits inLanguage

    JSON-LD is present but does not declare inLanguage on sampled pages.

    Tìm thấy tại đây

    JSON-LD · <script type="application/ld+json">

    https://www.heidihealth.com/en-us

    Điều chúng tôi nhận thấy

    Organization is present but inLanguage is missing

    Cách khắc phục

    Set JSON-LD inLanguage to match each page locale.

  • highlinguistic · 92% độ tin cậy

    Untranslated call to action

    A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.

    Tìm thấy tại đây

    Primary action · <button>

    https://www.heidihealth.com/fr-ca

    Điều chúng tôi nhận thấy

    Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr

    Cách khắc phục

    Translate leftover source-language CTAs to match the surrounding locale copy.

  • mediumvisual · 88% độ tin cậy

    Localized text is much longer than the source

    A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de

    Cách khắc phục

    Shorten the translation or give the control more room so the longer copy does not overflow.

  • lowvisual · 80% độ tin cậy

    Heading is excessively long

    A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    „Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it

    Cách khắc phục

    Shorten the heading so it does not crowd the visual hierarchy.

  • lowvisual · 95% độ tin cậy

    Repeated components differ across locales

    Button counts differ between the source locale and fr.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    Source locale has 14 buttons; fr has 8.

    Cách khắc phục

    Keep the same repeated controls across locales, or drop unused ones on purpose.

  • mediumtechnical · 70% độ tin cậy

    Current-page preservation is not demonstrated

    The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.

    Tìm thấy tại đây

    Header · language switcher

    https://www.heidihealth.com/en-us

    Điều chúng tôi nhận thấy

    "locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".

    Cách khắc phục

    Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.

  • infotechnical · 82% độ tin cậy

    Locale metadata is explicit for the sampled English pages

    The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "htmlLang":"en-us" and "htmlLang":"en-gb"

    Cách khắc phục

    Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.

  • infolinguistic · 95% độ tin cậy

    Cross-locale terminology cannot be assessed

    The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.

    Cách khắc phục

    Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.

  • infolinguistic · 95% độ tin cậy

    Translation accuracy cannot be assessed

    No target-language copy or source-to-target comparison is provided in the evidence.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".

    Cách khắc phục

    Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.

  • infolinguistic · 95% độ tin cậy

    Localized fluency cannot be assessed

    The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Relief in every visit The AI Care Partner for clinicians"

    Cách khắc phục

    Review rendered copy in each target locale with a native-language reviewer.

  • infolinguistic · 95% độ tin cậy

    Localized brand voice cannot be assessed

    The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Relief in every visit" and "The AI Care Partner for clinicians"

    Cách khắc phục

    Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.

  • infolinguistic · 95% độ tin cậy

    Locale-specific grammar and style cannot be assessed

    Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".

    Cách khắc phục

    Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.

  • infocontextual · 82% độ tin cậy

    English CTA intent is clear in the sampled page

    The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Get Heidi free" and "Book a demo"

    Cách khắc phục

    Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.

  • infocontextual · 82% độ tin cậy

    English UI contexts are identifiable

    The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"

    Cách khắc phục

    Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.

  • infocontextual · 82% độ tin cậy

    Product context is clear in the sampled English copy

    The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"

    Cách khắc phục

    Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.

  • infocontextual · 82% độ tin cậy

    English strings have visible page context

    The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.

    Cách khắc phục

    Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.

  • infocontextual · 88% độ tin cậy

    The sampled page clearly targets clinicians

    The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.

    Tìm thấy tại đây

    Điều chúng tôi nhận thấy

    "Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"

    Cách khắc phục

    Keep clinician-facing terminology and professional positioning consistent across all target locales.

  • infovisual · 65% độ tin cậy

    Localized assets cannot be verified

    The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.

    Tìm thấy tại đây

    Cách khắc phục

    Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.

Các trang được lấy mẫu

  • 200 · https://www.heidihealth.com/en-us · lang=en-us
  • 200 · https://www.heidihealth.com/en-us · lang=en-us
  • 200 · https://www.heidihealth.com/en-gb · lang=en-gb
  • 200 · https://www.heidihealth.com/en-ca · lang=en-ca
  • 200 · https://www.heidihealth.com/fr-ca · lang=fr-ca
  • 200 · https://www.heidihealth.com/en-au · lang=en-au
  • 200 · https://www.heidihealth.com/en-nz · lang=en-nz
  • 200 · https://www.heidihealth.com/en-ie · lang=en-ie
  • 200 · https://www.heidihealth.com/en-hk · lang=en-hk
  • 200 · https://www.heidihealth.com/en-za · lang=en-za
  • 200 · https://www.heidihealth.com/en-sg · lang=en-sg
  • 200 · https://www.heidihealth.com/de-de · lang=de-de
  • 200 · https://www.heidihealth.com/fr-fr · lang=fr-fr
  • 200 · https://www.heidihealth.com/es-es · lang=es-es
  • 200 · https://www.heidihealth.com/it-it · lang=it-it

Gửi cho tôi bản tóm tắt qua email

Không bắt buộc. Nhập email công việc của bạn và chúng tôi sẽ gửi cho bạn bản tóm tắt ngắn gọn về báo cáo công khai này.

Bước tiếp theo

Nền tảng vững chắc nhưng vẫn còn dư địa để cải thiện. Hãy tạo một không gian làm việc để liên tục theo dõi bản địa hóa hoặc đặt lịch đánh giá kiểm tra.

Đặt lịch xem xét kiểm tra