4 ms·
I plead ignorance about 510(k). Scanning the wikipedia article, it might have come into play if our "patient portal" (think Microsoft HealthVault, Google Health
by specialist 11y ago
I plead ignorance about 510(k). Scanning the wikipedia article, it might have come into play if our "patient portal" (think Microsoft HealthVault, Google Health) ever got traction. Because our brilliant notion was to store patient collected data (heart, glucose), to be shared with care providers. Another complete non-starter.
We did have live data feeds to the CDC. If there was a hoop, I assume we jumped thru it.
validation without checks on overwriting patient info
Our data store was write-only. In SQL parlance, no UPDATEs, just INSERTs (and SELECTs).
One hard requirement was to be able to show what was known when about a patient. "Traditional" data store solutions have "live" tables, separate history tables (recording changes), and maybe audit logs. My solution just had the log. Queries used a date range. Made QA/test trivial.