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 are currently hashing our visit_id (as well as patient_id) rendering this into a string and therefore failing the validation check as an integer is expected.
Would it be possible to change the schema accordingly to allow or this column to be hashed?
The text was updated successfully, but these errors were encountered:
Agree this would be ok if the visit_id isn't required to link to any other datasets. Is the visit_id intended to link the Emergency Care to the Admitted Care table?
That is a good point. But, to my knowledge these have been requested as separate unlinked datasets and the analysis plan does not appear to suggest linked analysis.
Please use the workaround as above for now and I will incorporate this change in the next release.
We are currently hashing our visit_id (as well as patient_id) rendering this into a string and therefore failing the validation check as an integer is expected.
Would it be possible to change the schema accordingly to allow or this column to be hashed?
The text was updated successfully, but these errors were encountered: