Add EUDAMED Device Monitor (Apify actor) to related tools#4
Open
lmt991931-alt wants to merge 1 commit into
Open
Add EUDAMED Device Monitor (Apify actor) to related tools#4lmt991931-alt wants to merge 1 commit into
lmt991931-alt wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi — thanks for maintaining this reference; it's the clearest writeup of the EUDAMED API out there.
In the spirit of goal #2 ("so that others can hook into the data and contribute"), I built a small tool on top of the public
udiDiDataAPI and thought it might fit the "More links" list: an Apify actor that turns the registry into structured JSON/CSV/Excel and adds a change-monitoring mode (returns only devices whoselastUpdateDateis on/after a given date — a daily diff feed).It's free, public-data-only, no PII by default (the authorised-representative name is redacted unless explicitly enabled), and explicitly not affiliated with the Commission. Happy to drop it if it's out of scope — just thought it was directly relevant to people landing here.
One small thing I can confirm from building it, in case it's useful for the reference: the device list endpoint's page-size param is
size(notpageSize, which is silently ignored), andriskClass/deviceStatusTypecome back as nested objects with a.codestring. Glad to open a separate PR adding those as notes/examples to the OpenAPI spec if you'd want that.