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
{{ message }}
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.
In Rose usecase : two SQL Input have distinct condition because they have different id in the database.
Description
In Rose mapping, a date/time is required but the date and the time do not have the same id in the database. I need to have a FHIR dateTime attribut with 0...1 occurence.
First solution : to have possibility to merge Input group in Pyrog
Alternatives
Alternative solutions : in an Input group, if more than one condition are filled, possibility to choose between intersection or union. (At the moment, it is an intersection).
The text was updated successfully, but these errors were encountered:
Thank you for reporting this, I understand the issue and agree that it needs some work to make this possible!
I personally don't think it makes sense to merge several Input groups together: since you need two columns to fill a single attribute, it fits the definition of an "input group" for which you need to merge values together (aka: using a merging script).
Therefore I would vote for implementing unions between conditions. What's your opinion @Jasopaum ?
Problem
In Rose usecase : two SQL Input have distinct condition because they have different id in the database.
Description
In Rose mapping, a date/time is required but the date and the time do not have the same id in the database. I need to have a FHIR dateTime attribut with 0...1 occurence.
First solution : to have possibility to merge Input group in Pyrog
Alternatives
Alternative solutions : in an Input group, if more than one condition are filled, possibility to choose between intersection or union. (At the moment, it is an intersection).
The text was updated successfully, but these errors were encountered: