Reproducible, open, transparent, ethical Research when confronted to (patient) data anonymization : is it at all possible in practice? A lot of Hype goes in reproducible, open and transparency for data analysis theses days in some fields mores that other. The code is to be share as well as the dataset. 
How to achieve this in a context of patient data protection that all ethics' committees will require ? What are the best practice to overcome theses antagonistics goals ? 
My team seems to think patient's data protection means the data (already anonymized) shouldn't leak and thus we have to work on the database's server without ever getting the anon db on our stations. This feels a tad too much / an overkill ?
Its totally normal practice for patient data to be allowed to be stored only on properly secured, regulated and monitored servers. 

In my field (genomics), databases exist where researchers can deposit anonymized patient data, that is not "publically" available, but can be accessed by users that can demonstrate that they have good reason to use the data, that their use falls within the consent agreement and have the IT systems in place to keep the data safe (see for e.g. dbGaP and EGA) by making an application to a data-protection committee. 

Code can be written in such a way that no patient data is in the code (loaded from secure locations, etc), so that the code can be shared.