# AccessGUDID Medical Device Lookup Scraper (`automation-lab/accessgudid-medical-device-lookup-scraper`) Actor Enrich DI and UDI medical device identifiers from the public NIH/NLM AccessGUDID database with manufacturer, model, GMDN, FDA and status metadata. - **URL**: https://apify.com/automation-lab/accessgudid-medical-device-lookup-scraper.md - **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community) - **Categories:** Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per event This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## AccessGUDID Medical Device Lookup Scraper Look up medical device identifiers in the public NIH/NLM AccessGUDID database and turn DI or UDI values into clean, export-ready device metadata. The actor accepts Device Identifiers (DI), full UDI strings, pasted CSV, or newline lists. It returns one row per input with manufacturer, brand, model, GMDN, FDA product-code context, commercial distribution status, package identifiers, and the raw AccessGUDID JSON payload when you need audit traceability. ### What does AccessGUDID Medical Device Lookup Scraper do? AccessGUDID Medical Device Lookup Scraper enriches medical device identifiers from the U.S. FDA Global Unique Device Identification Database. It calls the AccessGUDID JSON lookup endpoint directly, normalizes the response, and keeps not-found inputs as structured rows. Use it when you have a spreadsheet of UDI/DI values and need a repeatable API-friendly enrichment workflow instead of manual web lookups. ### Who is it for? - ๐Ÿฅ Hospital procurement teams normalizing device catalogs. - โœ… Medtech compliance teams checking published GUDID status. - ๐Ÿ“ฆ Distributors matching package identifiers to primary devices. - ๐Ÿ” Recall and audit analysts enriching device records before downstream checks. - ๐Ÿงพ Data teams preparing ERP, CMMS, or inventory imports. ### Why use this actor? - No login, browser, cookies, or proxy needed. - Handles batch identifiers with bounded concurrency. - Emits `found=false` rows for missing devices, so spreadsheet row counts stay aligned. - Preserves raw source payload for long-tail AccessGUDID metadata. - Works in Apify datasets, API integrations, schedules, and MCP workflows. ### Data source The actor uses the public AccessGUDID API hosted by NIH/NLM: `https://accessgudid.nlm.nih.gov/api/v3/devices/lookup.json` The output reflects data returned by that source at run time. ### Input options | Field | Type | Description | |---|---:|---| | `deviceIdentifiers` | array | DI or UDI values, one string per identifier. | | `identifiersText` | string | Optional pasted text, CSV, or newline list. | | `maxItems` | integer | Maximum identifiers processed from combined inputs. | | `concurrency` | integer | Parallel lookup count. | | `includeRawPayload` | boolean | Adds the full AccessGUDID response to each row. | | `requestTimeoutSecs` | integer | Timeout for each lookup request. | ### Example input ```json { "deviceIdentifiers": [ "00860005855124", "00851424007140", "00851424007119" ], "maxItems": 100, "concurrency": 5, "includeRawPayload": true } ```` ### Output data | Field | Description | |---|---| | `inputIdentifier` | Original identifier from input. | | `normalizedIdentifier` | Trimmed identifier used for lookup. | | `lookupMode` | `di` or `udi`. | | `found` | Whether AccessGUDID returned a device. | | `status` | `found`, `not_found`, `invalid`, or `error`. | | `deviceId` | Primary Device Identifier when available. | | `brandName` | Published device brand name. | | `versionModelNumber` | Version or model number. | | `companyName` | Labeler/manufacturer company name. | | `deviceCommDistributionStatus` | Commercial distribution status. | | `gmdnTerms` | GMDN preferred terms when returned. | | `productCodes` | FDA product codes when returned. | | `identifiers` | Primary/package identifiers from GUDID. | | `rawPayload` | Optional full API response. | ### Example output ```json { "inputIdentifier": "00860005855124", "normalizedIdentifier": "00860005855124", "lookupMode": "di", "found": true, "status": "found", "deviceId": "00860005855124", "brandName": "ArchCath", "versionModelNumber": "GateKeeper-110-GK20", "companyName": "Arch Catheter LLC", "deviceCommDistributionStatus": "In Commercial Distribution" } ``` ### How much does it cost to enrich AccessGUDID medical device identifiers? This actor uses pay-per-event pricing: a small start fee and a per-result fee for each output row. Because it is HTTP-only and does not use proxies, it is designed for low-cost batch enrichment. Check the Apify pricing panel for the current tiered prices before running large batches. ### How to use it 1. Open the actor on Apify. 2. Paste DI/UDI values into the list or text area. 3. Keep the default concurrency unless you have a reason to tune it. 4. Run the actor. 5. Export the dataset as JSON, CSV, Excel, XML, or through the Apify API. ### Tips for best results - Use the DI portion of a UDI when you have it; DI lookups are direct. - Keep `includeRawPayload` enabled for compliance audits. - Disable `includeRawPayload` for lighter CSV exports. - Use `found=false` rows to identify stale, mistyped, or non-U.S. identifiers. - Start with a small batch before scheduling thousands of records. ### Handling not-found identifiers The actor does not fail a run just because a device is missing. Instead, it returns a row with: - `found: false` - `status: not_found` or `invalid` - `errorMessage` from AccessGUDID when available This makes it easier to join results back to your original spreadsheet. ### Integrations You can connect this actor to: - Google Sheets exports for catalog enrichment. - Inventory databases through Apify API clients. - Recall-monitoring workflows that need normalized DI fields first. - Procurement data-quality checks. - Compliance dashboards and BI tools. ### API usage with Node.js ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('automation-lab/accessgudid-medical-device-lookup-scraper').call({ deviceIdentifiers: ['00860005855124', '00851424007140'], includeRawPayload: true }); console.log(run.defaultDatasetId); ``` ### API usage with Python ```python from apify_client import ApifyClient client = ApifyClient('YOUR_APIFY_TOKEN') run = client.actor('automation-lab/accessgudid-medical-device-lookup-scraper').call(run_input={ 'deviceIdentifiers': ['00860005855124', '00851424007140'], 'includeRawPayload': True, }) print(run['defaultDatasetId']) ``` ### API usage with cURL ```bash curl -X POST "https://api.apify.com/v2/acts/automation-lab~accessgudid-medical-device-lookup-scraper/runs?token=$APIFY_TOKEN" \ -H 'Content-Type: application/json' \ -d '{"deviceIdentifiers":["00860005855124","00851424007140"],"includeRawPayload":true}' ``` ### MCP usage Use this actor from Apify MCP in Claude Code or Claude Desktop with: `https://mcp.apify.com/?tools=automation-lab/accessgudid-medical-device-lookup-scraper` Claude Code setup example: ```bash claude mcp add apify-accessgudid "https://mcp.apify.com/?tools=automation-lab/accessgudid-medical-device-lookup-scraper" ``` Claude Desktop JSON config example: ```json { "mcpServers": { "apify-accessgudid": { "url": "https://mcp.apify.com/?tools=automation-lab/accessgudid-medical-device-lookup-scraper" } } } ``` Example prompts: - "Look up these AccessGUDID DI values and summarize manufacturer names." - "Enrich this hospital device list and flag not-found identifiers." - "Return the package identifiers for these UDI values." ### Scheduling Schedule the actor to run against recurring device lists, then connect the dataset export to your downstream workflow. For changing input files, update the run input through the Apify API or a task configuration. ### Data quality notes AccessGUDID records are maintained by labelers and FDA systems. The actor normalizes returned data, but it does not independently verify device claims, recalls, or current market availability beyond fields exposed by AccessGUDID. ### Legality and ethical use AccessGUDID is a public medical-device database. Use this actor for lawful compliance, procurement, catalog, and research workflows. Do not treat scraped output as medical advice or as a replacement for official regulatory review. ### Troubleshooting #### Why did my identifier return `found=false`? The value may be a full UDI where the DI portion is different, a non-U.S. identifier, a typo, or a device not published in AccessGUDID. #### Why is `rawPayload` large? AccessGUDID returns nested metadata. Disable `includeRawPayload` if you only need top-level normalized columns. #### Can I run thousands of identifiers? Yes, but keep concurrency modest and respect the public API. Start with a small sample, then increase batch size. ### Related scrapers - https://apify.com/automation-lab/fda-510k-device-clearances-scraper - https://apify.com/automation-lab/fda-device-classification-scraper - https://apify.com/automation-lab/medical-device-alert-monitor ### FAQ #### Does this actor require an AccessGUDID API key? No. The lookup endpoint is public and does not require authentication. #### Does it use proxies? No. It is an HTTP API actor and does not use Apify Proxy. #### Does every input produce one output row? Yes. Found, not-found, invalid, and error cases all produce rows so your input and output can be reconciled. #### Can it search by brand name? This version focuses on DI/UDI lookup enrichment. Brand search is a separate workflow and is not part of the MVP. #### Is it browser-based? No. It calls AccessGUDID JSON endpoints directly for speed and reliability. ### Changelog - 0.1: Initial DI/UDI lookup actor with normalized medical device metadata and raw payload support. # Actor input Schema ## `deviceIdentifiers` (type: `array`): Device Identifier (DI) or full UDI values to enrich. Use DI values such as 00860005855124 or 00851424007140 for the fastest lookups. ## `identifiersText` (type: `string`): Optional newline-, comma-, semicolon-, or tab-separated DI/UDI values. This is combined with the list above. ## `maxItems` (type: `integer`): Maximum number of identifiers to process from the combined list/text inputs. ## `concurrency` (type: `integer`): Number of AccessGUDID API requests to run in parallel. Keep this modest for reliable public API usage. ## `includeRawPayload` (type: `boolean`): Include the full source API response in rawPayload for long-tail fields not normalized into top-level columns. ## `requestTimeoutSecs` (type: `integer`): Timeout for each individual AccessGUDID API request. ## Actor input object example ```json { "deviceIdentifiers": [ "00860005855124", "00851424007140", "00851424007119" ], "identifiersText": "00860005855124\n00851424007140", "maxItems": 10, "concurrency": 5, "includeRawPayload": true, "requestTimeoutSecs": 30 } ``` # Actor output Schema ## `overview` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "deviceIdentifiers": [ "00860005855124", "00851424007140", "00851424007119" ], "identifiersText": `00860005855124 00851424007140`, "maxItems": 10, "concurrency": 5, "includeRawPayload": true, "requestTimeoutSecs": 30 }; // Run the Actor and wait for it to finish const run = await client.actor("automation-lab/accessgudid-medical-device-lookup-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`๐Ÿ’พ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // ๐Ÿ“š Want to learn more ๐Ÿ“–? Go to โ†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "deviceIdentifiers": [ "00860005855124", "00851424007140", "00851424007119", ], "identifiersText": """00860005855124 00851424007140""", "maxItems": 10, "concurrency": 5, "includeRawPayload": True, "requestTimeoutSecs": 30, } # Run the Actor and wait for it to finish run = client.actor("automation-lab/accessgudid-medical-device-lookup-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("๐Ÿ’พ Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # ๐Ÿ“š Want to learn more ๐Ÿ“–? Go to โ†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "deviceIdentifiers": [ "00860005855124", "00851424007140", "00851424007119" ], "identifiersText": "00860005855124\\n00851424007140", "maxItems": 10, "concurrency": 5, "includeRawPayload": true, "requestTimeoutSecs": 30 }' | apify call automation-lab/accessgudid-medical-device-lookup-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=automation-lab/accessgudid-medical-device-lookup-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "AccessGUDID Medical Device Lookup Scraper", "description": "Enrich DI and UDI medical device identifiers from the public NIH/NLM AccessGUDID database with manufacturer, model, GMDN, FDA and status metadata.", "version": "0.1", "x-build-id": "afGCCcdmSdMgbulJh" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/automation-lab~accessgudid-medical-device-lookup-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-automation-lab-accessgudid-medical-device-lookup-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/automation-lab~accessgudid-medical-device-lookup-scraper/runs": { "post": { "operationId": "runs-sync-automation-lab-accessgudid-medical-device-lookup-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/automation-lab~accessgudid-medical-device-lookup-scraper/run-sync": { "post": { "operationId": "run-sync-automation-lab-accessgudid-medical-device-lookup-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "deviceIdentifiers": { "title": "Device Identifiers (DI/UDI)", "type": "array", "description": "Device Identifier (DI) or full UDI values to enrich. Use DI values such as 00860005855124 or 00851424007140 for the fastest lookups.", "items": { "type": "string" } }, "identifiersText": { "title": "Paste identifiers as text or CSV", "type": "string", "description": "Optional newline-, comma-, semicolon-, or tab-separated DI/UDI values. This is combined with the list above." }, "maxItems": { "title": "Maximum identifiers to process", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Maximum number of identifiers to process from the combined list/text inputs.", "default": 10 }, "concurrency": { "title": "Lookup concurrency", "minimum": 1, "maximum": 20, "type": "integer", "description": "Number of AccessGUDID API requests to run in parallel. Keep this modest for reliable public API usage.", "default": 5 }, "includeRawPayload": { "title": "Include raw AccessGUDID payload", "type": "boolean", "description": "Include the full source API response in rawPayload for long-tail fields not normalized into top-level columns.", "default": true }, "requestTimeoutSecs": { "title": "Request timeout (seconds)", "minimum": 5, "maximum": 120, "type": "integer", "description": "Timeout for each individual AccessGUDID API request.", "default": 30 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```