Choosing AutoML Entity Extraction for Custom Medical Labels
Short answer
C Use AutoML Entity Extraction to train a custom medical entity extraction model on your annotated text and custom labels.
Question
Key Takeaways
The exam tests matching custom-labeled entity extraction to a managed AutoML service, while the trap is overvaluing 'state-of-the-art algorithms' and choosing a hand-built BERT or TensorFlow model.
This PMLE item tests selecting a managed custom entity extraction service for unstructured medical text with organization-defined labels; the correct answer is C, AutoML Entity Extraction.
Common mistake: The most tempting wrong answer is B: 'state-of-the-art algorithms' suggests fine-tuning a BERT model, but that adds ML/NLP expertise and operational work when AutoML Entity Extraction already trains on annotated medical text and custom categories.
Expert Analysis
Custom labels decide the service
The scenario supplies unstructured medical text plus labels the firm defines, and asks to extract and classify medical phrases. That is custom entity extraction, not standard entity recognition. Google Cloud's AutoML Entity Extraction for Healthcare explicitly trains on your annotated medical text and your categories, so option C matches both the data and the classification requirement.
Why A is close but wrong
The Healthcare Natural Language API is attractive because it parses medical records and returns structured entities. But its entity types are prebuilt; it does not learn the organization's custom label inventory. Comments on this item stress that a prebuilt model cannot know your labels, and the supporting documentation says AutoML Entity Extraction allows 'a custom entity extraction model trained using your own annotated medical text and using your own categories.' If the stem asked for standard diseases or medications, with no custom categories and no annotated data, A could become the answer.
Why B and D lose on fit, not feasibility
'State-of-the-art algorithms' tempts option B: fine-tune a BERT-based model. Fine-tuning can work, and comments defending B reasonably argue it may outperform AutoML on unusual medical phrasing. But the question asks what to do, not what is theoretically most powerful; B adds ML/NLP expertise, training, tuning, and serving burden. Option D repeats that burden with TensorFlow. PMLE doctrine prefers a managed, low-code service when custom labels and annotated text are the defining constraints. B or D would flip if the requirement demanded bespoke architecture, research-grade experimentation, or control beyond AutoML limits.
Operational consequence
Choosing C gives a managed endpoint trained on labeled medical phrases, faster iteration, and less infrastructure. Choosing A silently misses custom labels, degrading recall; choosing B or D without need raises cost, latency, and maintenance. Comments converging on C frame it as the balance of ease, speed, and custom-label effectiveness.
Official Reference
https://cloud.google.com/healthcare-api/docs/concepts/nlp
This link opens the official vendor documentation in a new tab.
Exam Strategy
When an item stresses custom labels on healthcare text, separate prebuilt entity types from labels your organization defines. Scan for 'own annotated text', 'custom categories', or 'classify phrases'—these signal AutoML Entity Extraction; switch to Healthcare NL API only when standard medical entities suffice, and to BERT or TensorFlow when the stem demands bespoke architecture or full training control. Eliminate options that cannot learn your label inventory before comparing model quality.
Frequently Asked Questions
Why can't the Healthcare Natural Language API handle custom medical labels?
When would a BERT-based fine-tuned model be the better PMLE choice?
What input does AutoML Entity Extraction need for this healthcare use case?
Community Votes
63% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 11 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 11
-
b1a8fae 👍 11 Answered CC. "AutoML Entity Extraction for Healthcare allows you to create a custom entity extraction model trained using your own annotated medical text and using your own categories." https://cloud.google.com/healthcare-api/docs/concepts/nlp#choosing_between_the_and
-
fitri001 👍 3 Answered CPre-built Functionality: It's a pre-built and managed service within Vertex AI that streamlines the process of building custom entity extraction models. This can save you time and resources compared to building a model from scratch using TensorFlow (option D). Customizable Labels: AutoML Entity Extraction allows you to define your custom labels for medical phrases, which aligns well with your specific needs. Unstructured Text Support: It's designed to handle unstructured text data like your medical records. Faster Experimentation: Compared to a custom BERT-based model (option B), AutoML Entity Extraction often allows for faster experimentation as it automates many hyperparameter tuning aspects.
-
Dagogi96 👍 3 Answered AA.- "The Healthcare Natural Language API parses unstructured medical text such as medical records or insurance claims. It then generates a structured data representation of the medical knowledge entities stored in these data sources for downstream analysis and automatio"
-
fitri001 👍 2A. Healthcare Natural Language API: While this API can extract medical entities like diseases or medications, it might not support the level of customization you need for your specific medical phrases with custom labels. B. BERT-based Model with Fine-tuning: Fine-tuning a BERT model can be effective, but it requires significant expertise in machine learning and natural language processing. AutoML Entity Extraction provides a more accessible and potentially faster approach for your use case. D. TensorFlow for Custom Model: Building a custom model with TensorFlow offers maximum control, but it requires a high level of expertise and can be time-consuming, especially for a team that might not specialize in NLP.
-
pikachu007 👍 2 Answered BA. Healthcare Natural Language API: While convenient, it lacks the customization capabilities for fine-tuning with custom labels, potentially limiting accuracy for your specific needs. C. AutoML Entity Extraction: It's generally well-suited for common entity types, but its pre-defined label set might not accommodate the full range of medical entities and relationships you need to extract. D. TensorFlow Custom Model: Building a model from scratch requires significant expertise, time, and resources, often less efficient than leveraging the power of pre-trained BERT models.
Show 6 more comments
-
guilhermebutzke 👍 2 Answered BMy answer: B Looking for “developing state-of-the-art algorithms for various use cases” in the question, I think the best approach is BERT-based model. AutoML Entity Extraction could be a approach for a quickstart, and Healthcare Natural Language API might not have your custom labels built-in, limiting its effectiveness. Tensorflow model can be time-consuming and require significant expertise https://cloud.google.com/healthcare-api/docs/concepts/nlp#choosing_between_the_and
-
taylz876 👍 1 Answered CWhy C is right You have unstructured text with your own custom labels, and you need to find and classify medical phrases using those labels. A pre-built model can't know your labels, so you need a model trained on your data. AutoML Entity Extraction (now AutoML text entity extraction in Agent Platform, formerly Vertex AI) does this with no code. You supply the text with the labeled phrases, and it trains the extraction model for you. Why the others are wrong • A: The Healthcare Natural Language API extracts a fixed set of standard medical entities. It can't learn your custom labels. • B: Fine-tuning a BERT-based model works, but it means writing and managing the training code yourself, so it's slower and takes more effort than AutoML. • D: Building a custom TensorFlow model from scratch is the most work of all, and it also needs a lot of data.
-
lunalongo 👍 1 Answered CC is the best option because AutoML Entity Extraction provides the best balance of ease of use, speed, and effectiveness for building a custom medical entity extraction model with your specific labeled data. *A is not proper for custom labels, B requires deep expertise and is time consuming. D is too complex, requires deep expertise and extensive code.
-
VinaoSilva 👍 1 Answered C"unstructured textual data with custom labels " = AutoML Entity Extraction
-
sonicclasps 👍 1textbook use case as described in the link provided
-
daidai75 👍 1Full Agreed
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →