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
Postgres has a notion of composite types that might better model some vitals like blood pressure, which always has two components. Right now, those are independent columns in the database, but it never makes sense to include a systolic pressure without a diastolic one, or vice versa. This would also make it easier to have a single "BP field" component that handles entry, rather than two independent input fields.
This could also be used for temperature, if we wanted to include the selection of units with the value.
The text was updated successfully, but these errors were encountered:
Postgres has a notion of composite types that might better model some vitals like blood pressure, which always has two components. Right now, those are independent columns in the database, but it never makes sense to include a systolic pressure without a diastolic one, or vice versa. This would also make it easier to have a single "BP field" component that handles entry, rather than two independent input fields.
This could also be used for temperature, if we wanted to include the selection of units with the value.
The text was updated successfully, but these errors were encountered: