Quote:
|
Originally Posted by FightThisPatent
I asked this question at that panel because i have talked to a couple of companies who are creating 2257 compliant databases and have been getting legal opinions that you could have a remote server/database manage the records.
It was good to get some consensus from the attornies on this issue, and i hope that all those bright software developers who are going down the path of developing/releasing 2257 software based on the idea of remote database should get a second legal opinion.
it was clear to me, based on Clyde's and JD's viewpoint as defense attornies, that the DOJ may want to seize records and computers.. and thus the requirement and absolute necessity to have your electronic 2257 records on a dedicated machine, in case they decide they want to take the whole thing.
Fight the third opinion!
|
I assume this refers to sponsors who are offering remote 2257 data to their affiliates? Couldn't you have local software that just imports the relevant data from the remote database to your local machine for the images/models you're using?
What is the main point of using a remote database in the first place other than centralized distribution of the data by sponsors?