Is DEVICE_EXPOSURE.unique_device_id only related to the devices regulated by the FDA?

Aperta
#677 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@clairblacketer ci sta già lavorando.

Dal 25/4/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Proposal

For the DEVICE_EXPOSURE.unique_device_id field, is it only related to the devices regulated by the FDA?

According to some OHDSI posts and GitHub issue, some people have questions about how to store non-regulated device details into DEVICE_EXPOSURE. They devices are not regulated by FDA. As a result, it is not convenient for them to store their non-FDA regulated device details including those devices ID.

image

In OHDSI posts, they suggest to use DEVICE_EXPOSURE.device_source_value to store their devices detailed information.

  1. https://forums.ohdsi.org/t/adding-manufacturer-and-model-information-to-the-device-exposure-table/16561/6
  2. https://forums.ohdsi.org/t/how-to-record-non-regulated-device-details-in-cdm-6-0/18605

In CDM GitHub issue: https://github.com/OHDSI/CommonDataModel/issues/353, Vojtech Huser made a full proposal which includes suggesting: remove talking about FDA and make sure wording is in world wide scope. But it seems no further response.

For me, I am in China. If this field is only limited to FDA, I may not be able to use this field to store the ID of devices in China because devices may not be regulated by FDA. I also need to store these information into device_source_value field.

Lingua principale
HTML
Stelle
1.1k
Fork
515
Merge medio
8g 3h
PR unite (30g)
4

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OHDSI/CommonDataModel

Tutte le issue di OHDSI/CommonDataModel

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.