Service
The following operations are supported. For a formal definition, please review the Service Description.
-
CheckForNewPatientForm
Checks for new completed Patient Questionnaires -
CleanupDWRegDB
Cleanup the DWRegistration database with passed UID -
CombinedTextAppend
Returns CombinedText.length after appending the passed text into the UserItemRow -
CombinedTextInitialize
Sets the specified UserItemRow.ItemValue to empty -
DemoDeleteAllPatientForms
For demonstration purposes, deletes all PatientForms so they can be re-entered. -
DemoResetAllSubmissionForDownload
For demonstration purposes, sets all PatientFormss to not downloaded yet so they are al re-downloaded. -
Enterprise1QuestExamDownloadCompleted
Called by EnterpriseVersion1 when a combined Quest/Exam is downloadedReturns the number of PatientFormRows affected (1=success, 0=failure to update) -
Enterprise1QuestExamImportCompleted
Called by EnterpriseVersion1. Sends the Online server the Offline PatientRow used (new or existing), and includes theand in Patient.PropertiesReturns the number of PatientRows affected (1=success, 0=failure to update) -
Enterprise1QuestOnlyDownloadCompleted
Called by EnterpriseVersion1. Notifies the Server to mark the specified PatientForm withTrue plus the current server datetime. This keeps the form from being downloaded again.Returns the number of PatientFormRows affected (1=success, 0=failure to update) -
Enterprise1QuestOnlyImportCompleted
Called by EnterpriseVersion1. Sends the Online server the Offline PatientRow used (new or existing), and includes theand in Patient.PropertiesReturns the number of PatientRows affected (1=success, 0=failure to update) -
GetExmRsltRowsByPatientFormID
Returns ExmRsltRows with the specified PatientFormID -
GetPatientAndFormsReport
Cleanup the DWRegistration database with passed UID -
GetPatientImagesRow
Returns the specifiec row from the patientImages table -
GetPatientRow
Returns a PatientRow -
GetProviderList
Gets a simple list of DWRegistration.Provider IDs and names -
PatientFormAcceptedRejected
In current usage this function simply deletes the Questionnaire and ExmRslt datarows when the Questionnaire is either Accepted or Rejected. It returns the number of PatientFormRows affected (1=success, 0=failure r delete) -
PatientFormDownloadCompleted
Notifies the Server to mark the specified PatientForm withTrue plus the current server datetime. Returns the number of PatientFormRows affectedd (1=success, 0=failure to update) -
SynchronizeDataSet
Updates the DentalRegistration dataset tables using XML previously stored in a UserItemRow.
This web service is using http://tempuri.org/ as its default namespace.
Recommendation: Change the default namespace before the XML Web service is made public.
Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.
Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)
For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":
C#
[WebService(Namespace="http://microsoft.com/webservices/")] public class MyWebService { // implementation }
Visual Basic
<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService ' implementation End Class
C++
[WebService(Namespace="http://microsoft.com/webservices/")] public ref class MyWebService { // implementation };
For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.
For more details on WSDL, see the WSDL Specification.
For more details on URIs, see RFC 2396.