GeminiHost

ProtocolVisit

The following routes are available for this service:
All Verbs	/ProtocolVisit

**ProtocolVisit** Parameters:
Name	Parameter	Data Type	Required
Token	query	string	No
UserId	query	int	No
VisitId	query	int	No

**ProtocolVisitReturn** Parameters:
Name	Parameter	Data Type	Required
PatientId	form	int	No
VisitId	form	int	No
ClinicId	form	int	No
Date	form	DateTime	No
EyeType	form	string	No
Status	form	string	No
Note	form	string	No
OperationResult	form	int	No
NVD	form	string	No
KVD	form	string	No
SFD	form	decimal?	No
CYD	form	decimal?	No
AXD	form	decimal?	No
NTD	form	string	No
NVS	form	string	No
KVS	form	string	No
SFS	form	decimal?	No
CYS	form	decimal?	No
AXS	form	decimal?	No
NTS	form	string	No
Error	form	bool	No
ErrorMessage	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/ProtocolVisit HTTP/1.1 
Host: data.oriem.cz 
Content-Type: application/json
Content-Length: length

{"Token":"String","UserId":0,"VisitId":0}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"PatientId":0,"VisitId":0,"ClinicId":0,"Date":"\/Date(-62135596800000-0000)\/","EyeType":"String","Status":"String","Note":"String","OperationResult":0,"NVD":"String","KVD":"String","SFD":0,"CYD":0,"AXD":0,"NTD":"String","NVS":"String","KVS":"String","SFS":0,"CYS":0,"AXS":0,"NTS":"String","Error":false,"ErrorMessage":"String"}