Sélectionner vos préférences de cookies

Nous utilisons des cookies essentiels et des outils similaires qui sont nécessaires au fonctionnement de notre site et à la fourniture de nos services. Nous utilisons des cookies de performance pour collecter des statistiques anonymes afin de comprendre comment les clients utilisent notre site et d’apporter des améliorations. Les cookies essentiels ne peuvent pas être désactivés, mais vous pouvez cliquer sur « Personnaliser » ou « Refuser » pour refuser les cookies de performance.

Si vous êtes d’accord, AWS et les tiers approuvés utiliseront également des cookies pour fournir des fonctionnalités utiles au site, mémoriser vos préférences et afficher du contenu pertinent, y compris des publicités pertinentes. Pour accepter ou refuser tous les cookies non essentiels, cliquez sur « Accepter » ou « Refuser ». Pour effectuer des choix plus détaillés, cliquez sur « Personnaliser ».

Questions - Healthcare Industry Lens
Cette page n'a pas été traduite dans votre langue. Demande de traduction

Questions

HCL_OE4: How do you track model revisions and ensure traceability of your ML artifacts?

Employ version control for source code, data, and ML artifacts to ensure traceability and reliability of production ML deployments. Version control and traceability may be required by applicable regulatory frameworks, if for example models are deployed in support of medical devices.

HCL_SEC16. How does your organization review, accept, and manage the licenses of open-source software dependencies?

Data science in healthcare often depends on open-source libraries for data processing, model development, training, and hosting. Establish a process to review the privacy and license agreements for all software and ML libraries needed throughout the ML lifecycle. Verify that these agreements comply with your organization’s legal, privacy, and security requirements.

HCL_SEC17. Does your organization deidentify heath data used for machine learning, or otherwise limit access to sensitive, identifiable health data?

Many ML workflows do not require identified health data. Applying ML to deidentified data is one way to develop AI-powered applications without compromising privacy or data security. Cloud services like the Amazon Comprehend Medical DetectPHI API can streamline generating deidentified datasets.

HCL_REL4: How does your organization identify and limit biases in training data and statistical models?

Statistical models trained on real-world health data are susceptible to biases. Health data may inadvertently be collected from populations of individuals with similar characteristics, such as median household income, social determinants of health, and access to care. Care setting and health insurance coverage may also impart biases. For example, treatment cohorts may exhibit higher household income because such individuals may have greater access to advanced care.

Trained models may be misleading if biases are not quantified and mitigated. Also, models may be inaccurate when trained on biased data and applied to settings with different distributions. Examine data distributions and perform analyses to quantify and mitigate biases before training models.

HCL_PERF10: What processes do you use to monitor model performance after deployment and protect against drift?

Health data is often complex, and subject to temporal variations in quality and concept expression. Model performance may degrade over time due to data quality, model quality, and concept drift. Create a baseline for data quality, and automate monitoring performance in production. Automate alerts for changes in data quality or distributions, such as age deciles and prevalence of relevant chronic diseases. SageMaker AI Model Monitor provides an end-to-end framework model monitoring and lifecycle management.

Rubrique suivante :

Conclusion

Rubrique précédente :

Reference architecture
ConfidentialitéConditions d'utilisation du sitePréférences de cookies
© 2025, Amazon Web Services, Inc. ou ses affiliés. Tous droits réservés.