You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a separate database/document and interface for registering and describing devices - such as ventilator prototypes and possibly test equipment. Depending on how general our definition of the device is, a single subsystem might be adequate for both types, or two separate ones may be needed.
multiple fields for describing its overall static features - installed valves, filters, regulators, daughter-cards, serial numbers of installed components, such as PCB
multiple fields describing the value ranges for manually adjustable settings. These ranges could be used to validate (or reject) uploaded datasets and thus spot human errors in tester reporting, etc..
pictures, to show any unique features or configurations
possibly BOMs compiled at time of manufacture
history of changes to any of the above parameters
Authenticated users should be able to edit these device profiles. Profiles should be automatically linked from uploaded datasets by the device serial number, which should match. And if history is properly implemented, it should be possible to examine the device profile at the exact timepoint that the experiment was run. It should also be possible to find links to all datasets produced by a particular device.
Some of these functions may be split off into separate tickets.
The text was updated successfully, but these errors were encountered:
We need a separate database/document and interface for registering and describing devices - such as ventilator prototypes and possibly test equipment. Depending on how general our definition of the device is, a single subsystem might be adequate for both types, or two separate ones may be needed.
Some things a device definition should include:
Authenticated users should be able to edit these device profiles. Profiles should be automatically linked from uploaded datasets by the device serial number, which should match. And if history is properly implemented, it should be possible to examine the device profile at the exact timepoint that the experiment was run. It should also be possible to find links to all datasets produced by a particular device.
Some of these functions may be split off into separate tickets.
The text was updated successfully, but these errors were encountered: