GeminiHost

ProtocolVisit_v2Create

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

**ProtocolVisit_v2Create** Parameters:
Name	Parameter	Data Type	Required	Description
Token	query	string	No
UserId	query	int	No

**ProtocolVisit_v2Return** 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
OperationResult	form	int	No
Note	form	string	No
NV	form	string	No
KV	form	string	No
SF	form	decimal?	No
CY	form	decimal?	No
Error	form	bool	No
ErrorMessage	form	string	No

**ProtocolVisit_v2Return** 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
OperationResult	form	int	No
Note	form	string	No
NV	form	string	No
KV	form	string	No
SF	form	decimal?	No
CY	form	decimal?	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_v2Create HTTP/1.1 
Host: data.oriem.cz 
Content-Type: application/json
Content-Length: length

{"Token":"String","UserId":0,"PatientId":0,"VisitId":0,"ClinicId":0,"Date":"\/Date(-62135596800000-0000)\/","EyeType":"String","Status":"String","OperationResult":0,"Note":"String","NV":"String","KV":"String","SF":0,"CY":0,"Error":false,"ErrorMessage":"String"}

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","OperationResult":0,"Note":"String","NV":"String","KV":"String","SF":0,"CY":0,"Error":false,"ErrorMessage":"String"}