If there were a known table (as opposed to say a study dataset where the name might change) you could just create a sql view in the EHR schema and use it like any other table.

Since this is a study dataset, that won't work. We do not have a way to 'passthrough' arbitrary functions to the underlying database. It's technically possible, but we'd need some sort of mechanism to specify 'safe' functions. This is not currently planned work.