Adjumed Webservice API-GUIDE
|
|
|
- Isaac Ryan
- 10 years ago
- Views:
Transcription
1 Adjumed Webservice API-GUIDE Version: 0.99 Date: Status: in progress Author: Ignaz Walgis / Milena Rajkovic Pages: 25 Classification: Public Adjumed Webservice API-Guide V.0.98 Page 1 / 25
2 Document History Version / Status Datum, Autor Bemerkung 0.1 / in progress , Ignaz Walgis Initial version 0.2 / in progress , Milena Rajkovic Added method description 0.3 / in progress , Milena Rajkovic Added SOAP envelope description 0.9 / in progress , Milena Rajkovic Overall corrections, Added method description 0.95 / in progress , Milena Rajkovic Changed the ImportCase method description 0.96 / in progress , Ignaz Walgis Layout optimizations. Live / Staging system better explained. Added AQC-XML format file sample. Explanation of single and multi-value fields. Added link to XSD- Schema / in progress , Ignaz Walgis Added new method GetCase 0.98 / in progress , Ignaz Walgis Description extended for method CheckCaseId 0.99 / in progress , Ignaz Walgis Extended status code for webservice methods: 99, 2. Overall descriptions optimized. Adjumed Webservice API-Guide V.0.99 Page 2 / 25
3 Table of contents 1. Overview Webservice Url Live System Staging System Webservice Access Management Webservice Protocol XML Envelope 4 2. Using the webservice Initial sequence SOAP 5 3. API Methods CheckCaseId SOAP GetCaseStatus SOAP GetCase Export format SOAP ImportCase Import format SOAP CheckCase SOAP 22 Adjumed Webservice API-Guide V.0.99 Page 3 / 25
4 1. Overview Adjumed developed this API to facilitate developers and make their tasks of getting information from Adjumed Collect easier than before. The webservice is developped under.net Framework 4.5, Visual Studio 2013 and written in C#. 1.1 Webservice Url Live System Located at: Request WSDL located at: Staging System Located at: Request WSDL located at: Webservice Access Management The access management is done under the Adjumed Collect System. A valid webservice access login must be of user type Webservice. 1.3 Webservice Protocol The webservice protocol is SOAP. 1.4 XML Envelope Every call return a standardized XML data structure. Each call may return additional individual data, e.g. a single integer or more comples XML data structures. Please read the API description for each individual call. <?xml version= 1.0 encoding= utf-8?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> </data> </service> Adjumed Webservice API-Guide V.0.99 Page 4 / 25
5 2. Using the webservice 2.1 Initial sequence The requesting client application must first acquire a valid Access Token. For any further calls the Access Token must be provided. The Access Token is valid for 1 Minute. Every subsequent call to any webservice method - within 1 minute - renews the the validity of the Access Token to 1 minute again. The user must have a valid login (type WebService) in Adjumed system. Method: RequestAccessToken(username, clinicnumber, password) Success, the webservice returns the access token in the data field of the XML envelope: <?xml version= 1.0 encoding= utf-8?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data>50a8fa16-16f2-45e4-a94e-badea8db8313</data> </service> statuscode statustext Description 0 success Returns a valid Access Token in the data field of the XML envelope. 1 failed UserName, ClinicNumber or Password incorrect. 99 system exception SOAP The following is a sample SOAP request. Returns no additional data. Returns a system stack trace in the data field of the XML envelope. <soapenv:envelope xmlns:soapenv= xmlns:tem= > <soapenv:header/> <soapenv:body> <tem:requestaccesstoken> <tem:username>[email protected]</tem:username> <tem:clinicnumber>string</tem:clinicnumber> <tem:password>string</tem:password> </tem:requestaccesstoken> </soapenv:body> </soapenv:envelope> The following is a sample SOAP response. <s:envelope xmlns:s= > <s:body> <RequestAccessTokenResponse xmlns= > <RequestAccessTokenResult> <![CDATA[ <service> <statuscode>0</statuscode> <statustext>success</statustext> <data>e0412ef0-aece-43fd-9ad5-c72eb37786cb</data> </service>]]> </RequestAccessTokenResult> </RequestAccessTokenResponse> </s:body> </s:envelope> Adjumed Webservice API-Guide V.0.99 Page 5 / 25
6 3. API Methods 3.1 CheckCaseId CheckCaseId method compares the given entry date and patient ID with the entry date and patient ID of the case in Adjumed system, if any. Otherwise, returns the code for case not found. Client application must provide acquired access token, case ID, patient ID and entry date. The possible results are 0 (case with the given case ID is not found), 1 (case with the given case ID is found, patient ID and entry date are the same as provided ones), 2 (case with the given case ID is found, patient ID or entry date are different from the provided ones), 3 (more than 1 case found with the same caseid). Method: CheckCaseId(accessToken, caseid, patientid, entrydate) Success, the webservice returns the check case ID status in the data field of the XML envelope: <?xml version="1.0" encoding="utf-8"?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data>0</data> </service> statuscode statustext Description 0 success Returns check case ID result in the data field of the XML envelope. 1 failed Access Token incorrect or expired, case doesn t exist. Returns no additional data. 2 case not found Returns no additional data. 99 system exception Returns a system stack trace in the data field of the XML envelope SOAP The following is a sample SOAP request. <soapenv:envelope xmlns:soapenv=" xmlns:tem=" <soapenv:header/> <soapenv:body> <tem:checkcaseid> <tem:accesstoken>b4f666c2-4a21-419b d63bb652c75</tem:accesstoken> <tem:caseid> </tem:caseid> <tem:patientid> </tem:patientid> <tem:entrydate> </tem:entrydate> </tem:checkcaseid> </soapenv:body> </soapenv:envelope> The following is a sample SOAP response. <s:envelope xmlns:s=" <s:body> <CheckCaseIdResponse xmlns=" <CheckCaseIdResult> <![CDATA[<service> <statuscode>0</statuscode> <statustext>success</statustext> <data>1</data></service>]]> </CheckCaseIdResult> </CheckCaseIdResponse> </s:body> </s:envelope> Adjumed Webservice API-Guide V.0.99 Page 6 / 25
7 3.2 GetCaseStatus GetCaseStatus method returns the status of a case in Adjumed system. The possible results are 0 (open case), 10 (complete case) and -1 (deleted case). It also returns the date of creation, date of modification and the information about manual modification. The client application must provide acquired access token and case ID. Method: GetCaseStatus(accessToken, caseid) Success, the webservice returns the case status in the data field of the XML envelope: <?xml version= 1.0 encoding= utf-8?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <status> <casestatus>10</casestatus> <manualedit>true</manualedit> <datecreated> :26:43</datecreated> <datemodified> :21:50</datemodified> </status> </data> </service> statuscode statustext Description 0 success Returns a case status in the data field of the XML envelope. 1 failed Access Token incorrect or expired, case doesn t exist. Returns no additional data. 2 case not found Returns no additional data. 3 case id not unique Case ID is not unique. 99 system exception Returns a system stack trace in the data field of the XML envelope SOAP The following is a sample SOAP request. <soapenv:envelope xmlns:soapenv=" xmlns:tem=" <soapenv:header/> <soapenv:body> <tem:getcasestatus> <tem:accesstoken>d38696d6-d0ff-4a9f-8625-e29b06de4e44</tem:accesstoken> <tem:caseid>1234</tem: caseid> </tem:getcasestatus> </soapenv:body> </soapenv:envelope> Adjumed Webservice API-Guide V.0.99 Page 7 / 25
8 The following is a sample SOAP response. <s:envelope xmlns:s=" <s:body> <GetCaseStatusResponse xmlns=" <GetCaseStatusResult> <![CDATA[ <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <status> <casestatus>10</casestatus> <manualedit>true</manualedit> <datecreated> :26:43</datecreated> <datemodified> :21:50</datemodified> </status> </data> </service>]]> </GetCaseStatusResult> </GetCaseStatusResponse> </s:body> </s:envelope> Adjumed Webservice API-Guide V.0.99 Page 8 / 25
9 3.3 GetCase GetCase method gets a specific case from the Adjumed system. The client application must provide acquired access token and the ID of the case. The case is returned in AQC-XML Format and can. This format can be used to reimport this case. Method: GetCase (accesstoken, caseid) Success, the webservice returns the case in the data field of the XML envelope: <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <caselist> <case> <key> <clinicnumber>0</clinicnumber> <entrydate> </entrydate> <patientid> </patientid> <caseid> </caseid> </key> <form level="a0" number="1"> <field number="4" name="patientennummer" type="patientennummer"> <value priority="1"> </value> <field number="370" name="geburtsjahr" type="textbox"> <value priority="1">1960</value> <field number="365" name="geschlecht" type="radiobuttonlist"> <field number="363" name="eintrittsdatum" type="customtextboxdate"> <value priority="1"> </value> <field number="361" name="behandlungsart" type="dropdownlist"> <value priority="1">3</value> <field number="14" name="klasse" type="dropdownlist"> <value priority="1">3</value> <field number="11" name="eintrittsgrund" type="dropdownlist"> <field number="362" name="asarisikostufe" type="dropdownlist"> <value priority="1">32</value> <field number="30" name="koerpergewicht" type="textbox"> <value priority="1">135</value> <field number="32" name="koerpergroesse" type="textbox"> <value priority="1">170</value> <field number="36" name="thromboembolieprophylaxe" type="dropdownlist"> <value priority="1">157</value> <field number="16" name="austrittsdatum" type="customtextboxdate"> <value priority="1"> </value> <field number="37" name="stdintensivmedizin" type="textbox"> <field number="38" name="intubiert" type="radiobuttonlist"> <value priority="1">0</value> <field number="44" name="artdesaustritts" type="dropdownlist"> <field number="2426" name="export" type="checkbox"> <value priority="1">true</value> <field number=" " name="euro-qol_eintritt_neuro" type="euroquol_neuro"> <value priority="1">---2-</value> Adjumed Webservice API-Guide V.0.99 Page 9 / 25
10 <field number=" " name="euro-qol_nachkontrolle_neuro" type="euroquol_neuro"> <value priority="1">---1-</value> <field number="912" name="anastomoseninsuffizienzart_viszeral2" type="dropdownlist"> <value priority="1">1745</value> <field number="889" name="komplikationenviszeraldindo" type="dropdownlist"> <value priority="1">1630</value> <field number="10" name="eintrittsart_2012" type="dropdownlist"> <field number="42" name="aufenthaltnachaustritt_2012" type="dropdownlist"> <field number="56" name="komplikationfallbezogenschweregrad" type="dropdownlist"> <value priority="1">631</value> <field number="2330" name="istvis1fall" type="radiobuttonlist"> <field number="2332" name="isthandfall" type="radiobuttonlist"> <field number="2333" name="istneurofall" type="radiobuttonlist"> <field number="2334" name="istorthofall" type="radiobuttonlist"> <field number="2335" name="istsmobfall" type="radiobuttonlist"> <value priority="1">3</value> <field number="2336" name="istvascfall" type="radiobuttonlist"> <field number="2374" name="isturologiefall" type="radiobuttonlist"> <field number="2380" name="transcode_alter" type="textbox"> <value priority="1">55</value> <field number="2381" name="transcode_anzahloperationen" type="textbox"> <field number="2382" name="transcode_anzahleingriffsteile" type="textbox"> <field number="2383" name="transcode_aufenthaltsdauer" type="textbox"> <value priority="1">10</value> <field number="2384" name="transcode_bodymassindex" type="textbox"> <value priority="1">46.71</value> <field number="2385" name="transcode_tagepraeoperativ" type="textbox"> <field number="2386" name="transcode_tagepostoperativ" type="textbox"> <value priority="1">9</value> <field number="2387" name="transcode_altersklasse" type="dropdownlist"> <value priority="1">6</value> <field number="2388" name="transcode_aufenthaltsdauerklasse" type="dropdownlist"> <value priority="1">3</value> <field number="2389" name="transcode_austrittsmonat" type="dropdownlist"> <value priority="1">4</value> <field number="2390" name="transcode_austrittswochentag" type="dropdownlist"> <value priority="1">5</value> <field number="2391" name="transcode_bodymassindexklasse" type="dropdownlist"> <value priority="1">8</value> <field number="2394" name="transcode_eintrittsmonat" type="dropdownlist"> <value priority="1">4</value> Adjumed Webservice API-Guide V.0.99 Page 10 / 25
11 <field number="2395" name="transcode_eintrittswochentag" type="dropdownlist"> <value priority="1">3</value> <field number="2396" name="transcode_gewichtsklasse" type="dropdownlist"> <value priority="1">7</value> <field number="2397" name="transcode_groessenklasse" type="dropdownlist"> <value priority="1">9</value> <field number="2399" name="transcode_tagepraeoperativklasse" type="dropdownlist"> <field number="2400" name="transcode_tagepostoperativklasse" type="dropdownlist"> <value priority="1">4</value> <field number="2403" name="transcode_overallkomplikationsschweregrad" type="dropdownlist"> <value priority="1">0</value> <field number="2407" name="transcode_blutverlust" type="textbox"> <value priority="1">0</value> <field number="2408" name="transcode_blutverlustklasse" type="dropdownlist"> <value priority="1">0</value> <field number="2410" name="transcode_operationsdauer_kl" type="textbox"> <value priority="1">60</value> <field number="2411" name="transcode_operationsdauerklasse" type="dropdownlist"> <value priority="1">5</value> <field number="2415" name="transcode_fallbezogeneallgemeinekomplikationen" type="textbox"> <value priority="1">0</value> <field number="2455" name="transcode_operationsdatum_viszeral" type="textbox"> <value priority="1"> </value> <field number="71" name="patient_informiert" type="radiobuttonlist"> <field number="2420" name="istkinderchirurgiefall" type="radiobuttonlist"> <field number="3" name="fid" type="textbox"> <value priority="1"> </value> <field number="2341" name="istplasticfall" type="radiobuttonlist"> <field number="2342" name="istburnfall" type="radiobuttonlist"> <field number="2910" name="transcode_euroqol_eintritt_beweglichkeit" type="dropdownlist"> <value priority="1">-</value> <field number="2911" name="transcode_euroqol_eintritt_selbstständigkeit" type="dropdownlist"> <value priority="1">-</value> <field number="2912" name="transcode_euroqol_eintritt_allgtätigkeiten" type="dropdownlist"> <value priority="1">-</value> <field number="2913" name="transcode_euroqol_eintritt_schmerzen" type="dropdownlist"> <field number="2914" name="transcode_euroqol_eintritt_angst" type="dropdownlist"> <value priority="1">-</value> <field number="2922" name="transcode_euroqol_nachkontrolle_beweglichkeit" type="dropdownlist"> <value priority="1">-</value> <field number="2923" name="transcode_euroqol_nachkontrolle_selbstständigkeit" type="dropdownlist"> <value priority="1">-</value> <field number="2924" name="transcode_euroqol_nachkontrolle_allgtätigkeiten" type="dropdownlist"> <value priority="1">-</value> <field number="2925" name="transcode_euroqol_nachkontrolle_schmerzen" type="dropdownlist"> Adjumed Webservice API-Guide V.0.99 Page 11 / 25
12 <field number="2926" name="transcode_euroqol_nachkontrolle_angst" type="dropdownlist"> <value priority="1">-</value> <field number="2950" name="istvis3fall" type="radiobuttonlist"> <value priority="1">3</value> <field number="2955" name="re-operation_vis3" type="radiobuttonlist"> <value priority="1">0</value> <field number="2956" name="30_tage:mortalität_vis3" type="radiobuttonlist"> <value priority="1">0</value> <field number="2984" name="datum_erstkonsultation_bariatrie_vis3" type="customtextboxdate"> <value priority="1"> </value> <field number="2990" name="anastomoseninsuffizienz_bariartrie_vis3" type="dropdownlist"> <value priority="1">0</value> <field number="2991" name="blutung_bariartrie_vis3" type="dropdownlist"> <value priority="1">1725</value> <field number="2992" name="wundinfekt_bariartrie_vis3" type="dropdownlist"> <value priority="1">1705</value> <field number="2993" name="thrombose_bariartrie_vis3" type="dropdownlist"> <value priority="1">1795</value> <field number="2997" name="ileus_bariartrie_vis3" type="dropdownlist"> <value priority="1">1815</value> <field number="3004" name="erstkontakt_bariatrie_unbekannt_vis3" type="checkbox"> <value priority="1">false</value> <field number="3008" name="erkrankung_berechnet_vis3" type="radiobuttonlist"> <value priority="1">5</value> <field number="3009" name="ci_berechnet_vis3" type="textbox"> <value priority="1">0</value> <field number="45" name="diagnose_haupt_2015" type="icd10_14"> <value priority="1">e66.0</value> <field number="35" name="antibiotikaprophylaxe_2015" type="dropdownlist"> <value priority="1">152</value> <field number="3455" name="istbewegungsapparatfall" type="radiobuttonlist"> <form level="a1" number="1"> <field number="97" name="operationsnummer" type="textbox"> <field number="100" name="operationsdatum" type="customtextboxdate"> <value priority="1"> </value> <field number="104" name="operationsart" type="dropdownlist"> <field number="101" name="komplikationenalsoperationsgrund" type="dropdownlist"> <field number="105" name="ortdeseingriffs" type="dropdownlist"> <field number="106" name="antibiotikaperioperativ" type="dropdownlist"> <field number="750" name="operationsdringlichkeit_viszeral" type="dropdownlist"> <field number="2392" name="transcode_operationsmonat" type="dropdownlist"> <value priority="1">4</value> <field number="2393" name="transcode_operationswochentag" type="dropdownlist"> <value priority="1">4</value> Adjumed Webservice API-Guide V.0.99 Page 12 / 25
13 <field number="2404" name="transcode_anzahleingriffsteile_pro_op" type="textbox"> <field number="2405" name="transcode_tagepraeoperativ_pro_op" type="textbox"> <field number="2406" name="transcode_tagepostoperativ_pro_op" type="textbox"> <value priority="1">9</value> <field number="882" name="transcode_eingriffsart_logbook" type="dropdownlist"> <value priority="1">1625</value> <field number="2954" name="operations_intention_vis3" type="dropdownlist"> <value priority="1">5</value> <field number="3003" name="operationsdringlichkeit_vis3" type="dropdownlist"> <value priority="1">3</value> <form level="a2" number="1"> <field number="116" name="operateurnummer" type="arztnummer"> <value priority="1">126</value> <field number="103" name="operateurklasse" type="dropdownlist"> <field number="121" name="dauer" type="textbox"> <value priority="1">60</value> <field number="123" name="anzahleckonzintraop" type="textbox"> <field number="131" name="artdertransfusion" type="customcheckboxlist"> <value priority="1">240</value> <field number="125" name="anzahlffpintraop" type="textbox"> <field number="130" name="anaesthesieart" type="customcheckboxlist"> <value priority="1">217</value> <field number="124" name="transfusionenpostop" type="radiobuttonlist"> <value priority="1">0</value> <field number="360" name="komplikationenpostopschweregrad" type="dropdownlist"> <value priority="1">301</value> <field number="50" name="komplikationenintraopschweregrad" type="dropdownlist"> <value priority="1">245</value> <field number="2412" name="transcode_operationsdauerklasse_pro_et" type="textbox"> <value priority="1">5</value> <field number="884" name="transcode_operationsgruppe_logbook" type="dropdownlist"> <value priority="1">1681</value> <field number="2000" name="opcode_smob_2015" type="customtreeviewlist"> <value priority="1">1031</value> <field number="109" name="opcodenummern_2015" type="chop15gruppe"> <value priority="1"> </value> <field number="3010" name="opcode_hsm_2015_vis3" type="customtreeviewlist"> <value priority="1"> </value> <field number="107" name="opcodenummern_2015" type="chop15"> <value priority="1"> </value> </case> </caselist> </data> </service> Adjumed Webservice API-Guide V.0.99 Page 13 / 25
14 statuscode statustext Description 0 success Returns the requested case in the data field of the XML envelope. 1 failed Access Token incorrect or expired, case doesn t exist. Returns no additional data. 3 case id not unique Case ID is not unique. 99 Failed Returns a system stack trace in the data field of the XML envelope Export format See Chapter SOAP The following is a sample SOAP request. <soapenv:envelope xmlns:soapenv=" xmlns:tem=" <soapenv:header/> <soapenv:body> <tem:getcase> <tem:accesstoken>f f77-a10b-fb551ea11b39</tem:accesstoken> <tem:caseid> </tem:caseid> </tem:getcase> </soapenv:body> </soapenv:envelope> Adjumed Webservice API-Guide V.0.99 Page 14 / 25
15 3.4 ImportCase ImportCase method imports the case in Adjumed system. The client application must provide acquired access token, the import case string, formid and filterformid. The parameter overwritecases can have one of the following values: All, SkipExistingCases, and SkipManuallyChangedCases. Import case string must be in a form of XML. Method: ImportCase(accessToken, importcase, formid, filterformid, overwritecases) Success, the webservice returns the import result in the data field of the XML envelope: <?xml version="1.0" encoding="utf-8"?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <caselist> <case> <key> <clinicnumber>43</clinicnumber> <entrydate> </entrydate> <patientid>1234</patientid> <caseid></caseid> </key> <checkresults> <errorcount>10</errorcount> <infocount >2</infocount> <protocol> 11:19:54 *** Prüfung gestartet<br /> 11:19:55 KL Info Euro-Qol Eintritt<br /> 11:19:55 KL Info Euro-Qol Nachkontrolle<br /> 11:19:57 Fall erfolgreich geprüft<br /> 11:19:57 *** Prüfung beendet </protocol> <caseurl> </caseurl> </checkresults> <case> <caselist> <data> <service> statuscode statustext Description 0 success Returns import results in the data field of the XML envelope. 1 failed Access Token incorrect or expired. Returns no additional data. 2 no case found No cases are imported. Returns no additional data. 4 xml not valid The structure of the provided xml data is not valid. Return the results of the validation errors in the data field of the XML envelope. 99 failed Returns a system stack trace in the data field of the XML envelope. Adjumed Webservice API-Guide V.0.99 Page 15 / 25
16 3.4.1 Import format The import format is AQC-XML. Please find the XSD-Schema online: Sample file with 1 operation and 1 intervention part: <caselist xmlns=" <case> <key> <clinicnumber>0</clinicnumber> <entrydate> </entrydate> <patientid>800138</patientid> <caseid></caseid> </key> <form level="a0"> <field number="4" name="patientennummer"> <value priority='1'>'800138</value> <field number="3" name="fid"> <value priority='1'>'</value> <field number="370" name="geburtsjahr"> <value priority='1'>1967</value> <field number="365" name="geschlecht"> <value priority='1'>1</value> <field number="363" name="eintrittsdatum"> <value priority='1'> </value> <field number="10" name="eintrittsart_2012"> <value priority='1'>1</value> <field number="361" name="behandlungsart"> <value priority='1'>3</value> <field number="14" name="klasse"> <value priority='1'>1</value> <field number="11" name="eintrittsgrund"> <value priority='1'>1</value> <field number="362" name="asarisikostufe"> <value priority='1'>31</value> <field number="66" name="praeoperativerisiken"> <value priority='1'>63</value> <field number="891" name="statusnachlaparotomie_viszeral2"> <value priority='1'>0</value> <field number="35" name="antibiotikaprophylaxe_2015"> <value priority='1'>152</value> <field number="36" name="thromboembolieprophylaxe"> <value priority='1'>156</value> <field number="16" name="austrittsdatum"> <value priority='1'> </value> <field number="37" name="stdintensivmedizin"> <value priority='1'>12</value> <field number="38" name="intubiert"> <value priority='1'>0</value> <field number="42" name="aufenthaltnachaustritt_2012"> <value priority='1'>5</value> <field number="44" name="artdesaustritts"> <value priority='1'>1</value> <field number="889" name="komplikationenviszeraldindo"> Adjumed Webservice API-Guide V.0.99 Page 16 / 25
17 <value priority='1'>1630</value> <field number="56" name="komplikationfallbezogenschweregrad"> <value priority='1'>631</value> <field number="45" name="diagnose_haupt_2015"> <value priority='1'>i20.1</value> <field number="368" name="diagnose_zusatz_2015"> <value priority='1'>g01</value> <field number="47" name="diagnose_neben_2015"> <value priority='1'>o00.0</value> <form level="a1"> <field number="97" name="operationsnummer"> <value priority='1'>1</value> <field number="100" name="operationsdatum"> <value priority='1'> </value> <field number="104" name="operationsart"> <value priority='1'>1</value> <field number="101" name="komplikationenalsoperationsgrund"> <value priority='1'>1</value> <field number="105" name="ortdeseingriffs"> <value priority='1'>2</value> <field number="106" name="antibiotikaperioperativ"> <value priority='1'>2</value> <form level="a2"> <field number="109" name="opcodenummern_2015"> <value priority="1"> </value> <value priority="2"> </value> <field number="116" name="operateurnummer"> <value priority='1'>3</value> <field number="103" name="operateurklasse"> <value priority='1'>2</value> <field number="118" name="1assistenzoperateurnummer"> <value priority='1'>4</value> <field number="119" name="teachingassistenz"> <value priority='1'>1</value> <field number="121" name="dauer"> <value priority='1'>60</value> <field number="122" name="blutverlust"> <value priority='1'>0</value> <field number="123" name="anzahleckonzintraop"> <value priority='1'>0</value> <field number="131" name="artdertransfusion"> <value priority='1'>240</value> <field number="125" name="anzahlffpintraop"> <value priority='1'>0</value> <field number="50" name="komplikationenintraopschweregrad"> <value priority='1'>245</value> <field number="130" name="anaesthesieart"> <value priority='1'>217</value> <field number="360" name="komplikationenpostopschweregrad"> <value priority='1'>301</value> <field number="124" name="transfusionenpostop"> <value priority='1'>0</value> Adjumed Webservice API-Guide V.0.99 Page 17 / 25
18 <form level="a2"> <field number="109" name="opcodenummern_2015"> <value priority='1'> </value> <field number="116" name="operateurnummer"> <value priority='1'>5</value> <field number="103" name="operateurklasse"> <value priority='1'>4</value> <field number="121" name="dauer"> <value priority='1'>15</value> <field number="122" name="blutverlust"> <value priority='1'>0</value> <field number="123" name="anzahleckonzintraop"> <value priority='1'>0</value> <field number="131" name="artdertransfusion"> <value priority='1'>240</value> <field number="125" name="anzahlffpintraop"> <value priority='1'>0</value> <field number="50" name="komplikationenintraopschweregrad"> <value priority='1'>245</value> <field number="130" name="anaesthesieart"> <value priority='1'>217</value> <field number="360" name="komplikationenpostopschweregrad"> <value priority='1'>301</value> <field number="124" name="transfusionenpostop"> <value priority='1'>0</value> <form level="b0"> </case> </caselist> Example: Single value field <field number="4" name="patientennummer"> <value priority='1'>'800138</value> Example: Multi value field <field number="109" name="opcodenummern_2015"> <value priority="1"> </value> <value priority="2"> </value> Adjumed Webservice API-Guide V.0.99 Page 18 / 25
19 3.4.2 SOAP The following is a sample SOAP request. <soapenv:envelope xmlns:soapenv=" xmlns:tem=" <soapenv:header/> <soapenv:body> <tem:importcase> <!--Optional:--> <tem:accesstoken>dd758f d6-852f-5b24f55a7551</tem:accesstoken> <!--Optional:--> <tem:importcase> <![CDATA[<caseList xmlns=" ydate><patientid> </patientid><caseid > </caseid></key><form level="a0"><field number="71" name="patient_informiert"><value priority='1'>1</value><field number="2330" name="istvis1fall"><value priority='1'>2</value><field number="2331" name="istvis2fall"><value priority='1'>2</value><field number="2332" name="isthandfall"><value priority='1'>2</value><field number="2333" name="istneurofall"><value priority='1'>2</value><field number="2334" name="istorthofall"><value priority='1'>2</value><field number="2335" name="istsmobfall"><value priority='1'>2</value><field number="2336" name="istvascfall"><value priority='1'>2</value><field number="2374" name="isturologiefall"><value priority='1'>2</value><field number="2420" name="istkinderchirurgiefall"><value priority='1'>2</value><field number="2375" name="istt03fall"><value priority='1'>2</value><field number="2341" name="istplasticfall"><value priority='1'>2</value><field number="2342" name="istburnfall"><value priority='1'>2</value><field number="4" name="patientennummer"><value priority='1'> </value><field number="3" name="fid"><value priority='1'> </value><field number="370" name="geburtsjahr"><value priority='1'>1955</value><field number="363" name="eintrittsdatum"><value priority='1'> </value><field number="10" name="eintrittsart_2012"><value priority='1'>3</value><field number=" " name="euro- Qol_Eintritt_Neuro"><value priority='1'>73</value><field number="361" name="behandlungsart"><value priority='1'>3</value><field number="14" name="klasse"><value priority='1'>2</value><field number="2871" name="aqc_selbstzahler"><value priority='1'>false</value><field number="11" name="eintrittsgrund"><value priority='1'>3</value><field number="30" name="koerpergewicht"><value priority='1'>57</value><field number="32" name="koerpergroesse"><value priority='1'>170</value><field number="35" name="antibiotikaprophylaxe"><value priority='1'>152</value><field number="36" name="thromboembolieprophylaxe"><value priority='1'>157</value><field number="16" name="austrittsdatum"><value priority='1'> </value><field number="37" name="stdintensivmedizin"><value priority='1'>0</value><field number="38" name="intubiert"><value priority='1'>0</value><field number="56" name="komplikationfallbezogenschweregrad"><value priority='1'>633</value><form level="a1"><field number="97" name="operationsnummer"><value priority='1'>1</value><field number="750" name="operationsdringlichkeit_viszeral"><value priority='1'>1</value><field number="104" name="operationsart"><value priority='1'>2</value><field number="101" name="komplikationenalsoperationsgrund"><value priority='1'>4</value><field number="105" name="ortdeseingriffs"><value priority='1'>2</value><field number="106" name="antibiotikaperioperativ"><value priority='1'>2</value><form level="a2"><field number="109" name="opcodenummern_2014"><value priority='1'>00.01</value><field number="121" name="dauer"><value priority='1'>10</value><field number="122" name="blutverlust"><value priority='1'>11</value><field number="123" name="anzahleckonzintraop"><value priority='1'>22</value><field number="131" name="artdertransfusion"><value priority="1">241</value><value priority="2">242</value><field number="130" name="anaesthesieart"><value priority="1">206</value><value priority="2">215</value><field number="439" name="opdauzeit_outcome"><value priority='1'>00.10</value><field number="50" name="komplikationenintraopschweregrad"><value priority='1'>603</value><form level="b0"></case></caselist>]]> </tem:importcase> <tem:formid>-1</tem:formid> <tem:filterformid>-1</tem:filterformformid> <tem:overwritecases>all</tem:overwritecases > </tem:importcase> </soapenv:body> </soapenv:envelope> Adjumed Webservice API-Guide V.0.99 Page 19 / 25
20 The following is a sample SOAP response. <s:envelope xmlns:s=" <s:body> <ImportCaseResponse xmlns=" <ImportCaseResult> <![CDATA[<service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <caselist> <case> <key> <clinicnumber>0</clinicnumber> <entrydate> </entrydate> <patientid> </patientid> <caseid> </caseid> </key> <checkresults> <errorcount>16</errorcount> <protocol>fall in Analyze gelöscht.<br/>bestehenden Fall in Collect gelöscht<br/>aqc Feld ID (KL): 71 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2330 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2331 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2332 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2333 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2334 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2335 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2336 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2374 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2420 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2375 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2341 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2342 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (KL): 2871 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (OP): 750 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br />AQC Feld ID (ET): 439 nicht gefunden in Importformular: 2014 AQC Standard (RTTM). Feld wurde nicht importiert.<br /></protocol> <caseurl> </caseurl> </checkresults> </case> </caselist> </data> </service>]]> </ImportCaseResult> </ImportCaseResponse> </s:body> </s:envelope> Adjumed Webservice API-Guide V.0.99 Page 20 / 25
21 3.5 CheckCase CheckCase method checks the case in Adjumed system. The client application must provide acquired access token and the ID of the case. Method: CheckCase(accessToken, caseid) Success, the webservice returns the check result in the data field of the XML envelope: <?xml version="1.0" encoding="utf-8"?> <service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <caselist> <case> <key> <clinicnumber>43</clinicnumber> <entrydate> </entrydate> <patientid>1234</patientid> <caseid></caseid> </key> <!-- Check results - Total --> <checkresults> <errorcount>10</errorcount> <infocount >2</infocount> <protocol> 11:19:54 *** Prüfung gestartet<br /> 11:19:55 KL Info Euro-Qol Eintritt<br /> 11:19:55 KL Info Euro-Qol Nachkontrolle<br /> 11:19:57 Fall erfolgreich geprüft<br /> 11:19:57 *** Prüfung beendet </protocol> <caseurl> </caseurl> </checkresults> <checklist filterform="2014 AQC Standard (RTTM)"> <!-- Check results per CheckList --> <checkresults> <errorcount>1</errorcount> <infocount>0</infocount> <protocol> 11:19:54 *** Prüfung gestartet<br /> 11:19:55 KL Info Euro-Qol Eintritt<br /> 11:19:55 KL Info Euro-Qol Nachkontrolle<br /> 11:19:57 Fall erfolgreich geprüft<br /> 11:19:57 *** Prüfung beendet </protocol> </checkresults> <!-- Level, KL-Teil --> <form level="a0" number="1"> <!-- Type can be error or info --> <field number="97" name="operationsnummer" type="error"> Errormessage </field > <!-- Level, OP-Teil --> <form level="a1" number="1"> <!-- Type can be error or info --> <field number="97" name="operationsnummer" type="error"> Errormessage </field > <!-- Level, ET-Teil --> <form level="a2" number="1"> <!-- Type can be error or info --> <field number="109" name="opcodenummern_2013" type="error"> Errormessage Adjumed Webservice API-Guide V.0.99 Page 21 / 25
22 <!-- Level, ET-Teil --> <form level="a2" number="2"> <!-- Type can be error or info --> <field number="109" name="opcodenummern_2013" type="error"> Errormessage <!-- Level, OP-Teil --> <form level="a1" number="2"> <!-- Type can be error or info --> <field number="97" name="operationsnummer" type="error"> Errormessage </field > <!-- Level, GB-Teil --> <form level="b0"> <!-- Type can be error or info --> <field number="150" name="geburtsnummer_gb" type="error"> Errormessage </field >... </checklist> <checklist filterform="2014 Viszeral OP DB (VIS)"> <errorcount>0</errorcount> <infocount>0</infocount> <protocol></protocol>... </checklist>... </case> </caselist> </data> </service> statuscode statustext Description 0 success Returns check results in the data field of the XML envelope. 1 failed Access Token incorrect or expired, case doesn t exist. 2 case not found SOAP The following is a sample SOAP request. Returns no additional data. Returns no additional data. 99 failed Returns a system stack trace in the data field of the XML envelope. <soapenv:envelope xmlns:soapenv=" xmlns:tem=" <soapenv:header/> <soapenv:body> <tem:checkcase> <tem:accesstoken>d38696d6-d0ff-4a9f-8625-e29b06de4e44</tem:accesstoken> <tem:caseid>1234</tem:caseid> </tem:checkcase> </soapenv:body> </soapenv:envelope> Adjumed Webservice API-Guide V.0.99 Page 22 / 25
23 The following is a sample SOAP response. <s:envelope xmlns:s=" <s:body> <CheckCaseResponse xmlns=" <CheckCaseResult> <![CDATA[<service> <statuscode>0</statuscode> <statustext>success</statustext> <data> <caselist> <case> <key> <clinicnumber>0</clinicnumber> <entrydate> </entrydate> <patientid>1234</patientid> <caseid></caseid> </key> <checkresults> <errorcount>25</errorcount> <infocount>6</infocount> <protocol>16:51:20 *** Prüfung gestartet<br />16:51:26 Fall Flag nicht gesetzt. Es wird keine Prüfung durchgeführt für Filterformular: 2014 AQC Standard (RTTM)<br />16:51:26 Prüfe Fall mit Prüfliste für Filterformular: 2014 Visceral OP DB (Vis1)<br />16:51:28 KL Info Höchster Grad aller Komplikationen fehlt<br />16:51:28 KL Info Euro-Qol Eintritt<br />16:51:28 KL Info Euro-Qol Nachkontrolle<br />16:51:29 OP (1) Error Operationsdatum fehlt<br />16:51:29 OP (1) Error Dringlichkeit nicht gewählt<br />16:51:29 OP (1) Error Zugang nicht gewählt<br />16:51:31 OP (1) ET (1) Error Hauptoperateur Viszeralchirurgie nicht gewählt<br />16:51:31 OP (1) ET (1) Error Nicht angegeben ob Teaching-Assistenz<br />16:51:31 *** 5 Fehler für 2014 Visceral OP DB (Vis1)<br />16:51:31 Fall Flag nicht gesetzt. Es wird keine Prüfung durchgeführt für Filterformular: 2014 Visceral Register (Vis2)<br />16:51:31 Prüfe Fall mit Prüfliste für Filterformular: 2014 AQC SMOB<br />16:51:33 KL Info Höchster Grad aller Komplikationen fehlt<br />16:51:33 KL Error Geburtsjahr fehlt<br />16:51:33 KL Error Geschlecht nicht ausgewählt<br />16:51:33 KL Info Euro-Qol Eintritt<br />16:51:33 KL Error Eintrittsart nicht ausgewählt<br />16:51:33 KL Error Behandlungsart nicht ausgewählt<br />16:51:33 KL Error Klasse nicht ausgewählt<br />16:51:33 KL Error Eintrittsgrund nicht ausgewählt<br />16:51:33 KL Error ASA- Risikostufe nicht ausgewählt<br />16:51:33 KL Error Körpergewicht fehlt<br />16:51:33 KL Error Körpergrösse fehlt<br />16:51:33 KL Info Euro-Qol Nachkontrolle<br />16:51:33 KL Error Aufenthalt nach Austritt nicht ausgewählt<br />16:51:33 KL Error Art des Austritts nicht ausgewählt<br />16:51:34 OP (1) Error Operationsdatum fehlt<br />16:51:34 OP (1) Error Operationsart nicht ausgewählt<br />16:51:36 OP (1) ET (1) Error SMOB Op-Code ungültig<br />16:51:36 OP (1) ET (1) Error Operateur-Nr. fehlt<br />16:51:36 OP (1) ET (1) Error Operateur-Klasse fehlt<br />16:51:36 OP (1) ET (1) Error Dauer (Schnitt-Naht) fehlt<br />16:51:36 OP (1) ET (1) Error Komplikationen intraoperativ nicht ausgewählt<br />16:51:36 OP (1) ET (1) Error Komplikationen postoperativ nicht ausgewählt<br />16:51:36 OP (1) ET (1) Error SMOB Op-Code 13/14: Wert wurde nicht in den Stammdaten gefunden: SMOB-Code - please differenciate<br />16:51:36 *** 20 Fehler für 2014 AQC SMOB<br />16:51:36 Fall Flag nicht gesetzt. Es wird keine Prüfung durchgeführt für Filterformular: 2014 AQC Vasc<br />16:51:36 Fall Flag nicht gesetzt. Es wird keine Prüfung durchgeführt für Filterformular: 2014 AQC Child Surgery<br />16:51:36 *** Fall nicht abgeschlossen<br />16:51:36 *** Total 25 Fehler<br />16:51:36 *** Prüfung beendet<br /> </protocol> <caseurl> </caseurl> </checkresults> <checklist filterform="2014 Visceral OP DB (Vis1)"> <checkresults> <errorcount>5</errorcount> <infocount>3</infocount> </checkresults> Adjumed Webservice API-Guide V.0.99 Page 23 / 25
24 <form level="a0" number="1"> <field number="889" name="komplikationenviszeraldindo" type="info">kl Info Höchster Grad aller Komplikationen fehlt <field number=" " name="euro-qol_eintritt_neuro" type="info">kl Info Euro-Qol Eintritt <field number=" " name="euro-qol_nachkontrolle_neuro" type="info">kl Info Euro- Qol Nachkontrolle <form level="a1" number="1"> <field number="100" name="operationsdatum" type="error">op (1) Error Operationsdatum fehlt <field number="750" name="operationsdringlichkeit_viszeral" type="error">op (1) Error Dringlichkeit nicht gewählt <field number="753" name="zugang_viszeral" type="error">op (1) Error Zugang nicht gewählt <form level="a2" number="1"> <field number="755" name="hauptoperateur_viszeral" type="error">op (1) ET (1) Error Hauptoperateur Viszeralchirurgie nicht gewählt <field number="119" name="teachingassistenz" type="error">op (1) ET (1) Error Nicht angegeben ob Teaching-Assistenz </checklist> <checklist filterform="2014 AQC SMOB"> <checkresults> <errorcount>20</errorcount> <infocount>3</infocount> </checkresults> <form level="a0" number="1"> <field number="889" name="komplikationenviszeraldindo" type="info">kl Info Höchster Grad aller Komplikationen fehlt <field number="370" name="geburtsjahr" type="error">kl Error Geburtsjahr fehlt <field number="365" name="geschlecht" type="error">kl Error Geschlecht nicht ausgewählt <field number=" " name="euro-qol_eintritt_neuro" type="info">kl Info Euro-Qol Eintritt <field number="10" name="eintrittsart_2012" type="error">kl Error Eintrittsart nicht ausgewählt <field number="361" name="behandlungsart" type="error">kl Error Behandlungsart nicht ausgewählt <field number="14" name="klasse" type="error">kl Error Klasse nicht ausgewählt <field number="11" name="eintrittsgrund" type="error">kl Error Eintrittsgrund nicht ausgewählt <field number="362" name="asarisikostufe" type="error">kl Error ASA-Risikostufe nicht ausgewählt <field number="30" name="koerpergewicht" type="error">kl Error Körpergewicht fehlt <field number="32" name="koerpergroesse" type="error">kl Error Körpergrösse fehlt <field number=" " name="euro-qol_nachkontrolle_neuro" type="info">kl Info Euro-Qol Nachkontrolle <field number="42" name="aufenthaltnachaustritt_2012" type="error">kl Error Aufenthalt nach Austritt nicht ausgewählt <field number="44" name="artdesaustritts" type="error">kl Error Art des Austritts nicht ausgewählt <form level="a1" number="1"> <field number="100" name="operationsdatum" type="error">op (1) Error Operationsdatum fehlt <field number="104" name="operationsart" type="error">op (1) Error Operationsart nicht ausgewählt <form level="a2" number="1"> <field number="1900" name="opcode_smob_2013" type="error">op (1) ET (1) Error SMOB Op-Code ungültig <field number="116" name="operateurnummer" type="error">op (1) ET (1) Error Operateur-Nr. fehlt <field number="103" name="operateurklasse" type="error">op (1) ET (1) Error Operateur-Klasse fehlt <field number="121" name="dauer" type="error">op (1) ET (1) Error Dauer (Schnitt-Naht) fehlt <field number="50" name="komplikationenintraopschweregrad" type="error">op (1) ET (1) Error Komplikationen intraoperativ nicht ausgewählt <field number="360" name="komplikationenpostopschweregrad" type="error">op (1) ET (1) Error Komplikationen postoperativ nicht ausgewählt <field number="1900" name="opcode_smob_2013" type="error">op (1) ET (1) Error SMOB Op-Code 13/14: Wert wurde nicht in den Stammdaten gefunden: SMOB-Code - please differenciate Adjumed Webservice API-Guide V.0.99 Page 24 / 25
25 </checklist> </case> </caselist> </data> </service>]]> </CheckCaseResult> </CheckCaseResponse> </s:body> </s:envelope> Adjumed Webservice API-Guide V.0.99 Page 25 / 25
dctrack Web Services API - Ticketing User Guide 3.0.0
dctrack Web Services API - Ticketing User Guide 3.0.0 Copyright 2013 Raritan, Inc. dctrack-ws-api-0e-3.0.0-e February 2013 255-80-8008-00 This document contains proprietary information that is protected
United Concordia (UCD) Real Time Claim Submission & Adjudication Connectivity Specifications
United Concordia (UCD) Real Time Claim Submission & Adjudication Connectivity Specifications May 15, 2015 Contents 1. Real Time Overview 2. Requirements 3. SOAP Messages 4. SOAP Faults 5. CORE-Compliant
Version: 1. Cellfind_MPG SDK Technical Specification
Cellfind SDK Technical Specification Version: 1 Filename: Cellfind_MPG SDK Technical Specification Last Revision Date: 09/10/2014 Contents WEB SERVICE QA AND LIVE URL ADDRESSES... ERROR! BOOKMARK NOT DEFINED.
B2B Appointment Booking Specification
From Issue date 12 nd May 2008 Subject Broadband Connectivity Service and Full Access (T-)TAL Appointment Booking Status released Contract Version - WSG Version 10 Valid until Server location recalled
Alliance Access Integration SOAP Host Adaptor
Alliance Access Integration SOAP Host Adaptor Technical Qualification Test 2013 This document lists the tests for application providers that integrate their back-office application or middleware with Alliance
Integration Overview. Web Services and Single Sign On
Integration Overview Web Services and Single Sign On Table of Contents Overview...3 Quick Start 1-2-3...4 Single Sign-On...6 Background... 6 Setup... 6 Programming SSO... 7 Web Services API...8 What is
Middleware and the Internet
Middleware and the Internet Middleware today Designed for special purposes (e.g. DCOM) or with overloaded specification (e.g. CORBA) Specifying own protocols integration in real world network? Non-performant
Pervasive Data Integrator. Oracle CRM On Demand Connector Guide
Pervasive Data Integrator Oracle CRM On Demand Connector Guide Pervasive Software Inc. 12365 Riata Trace Parkway Building B Austin, Texas 78727 USA Telephone: (512) 231-6000 or (800) 287-4383 Fax: (512)
Single Sign-On Implementation Guide
Salesforce.com: Salesforce Winter '09 Single Sign-On Implementation Guide Copyright 2000-2008 salesforce.com, inc. All rights reserved. Salesforce.com and the no software logo are registered trademarks,
X12 837 Real-Time Claim Submission & Connectivity Specifications. Highmark, Inc. October 1, 2014 Document Version 1.1
X12 837 Real-Time Claim Submission & Connectivity Specifications Highmark, Inc. October 1, 2014 Document Version 1.1 Contents 1. Real-Time Overview 2. Requirements 3. SOAP Messages 4. SOAP Faults 5. Highmark
File Transfer Service (Batch SOAP) User Guide. A Guide to Submitting batches through emedny FTS
File Transfer Service (Batch SOAP) User Guide A Guide to Submitting batches through emedny FTS June 1, 2013 TABLE OF CONTENTS TABLE OF CONTENTS 1 Introduction... 4 2 Requirements... 5 2.1 Exchange mailboxes...
webcrm API Getting Started
webcrm API Getting Started 17.09.2012 / 08.12.2015 TS Contents.NET Application with autogenerated proxy class... 2.NET Application sending SOAP messages directly... 10 .NET Application with auto generated
Integrating CRM On Demand with the E-Business Suite to Supercharge your Sales Team
Integrating CRM On Demand with the E-Business Suite to Supercharge your Sales Team Presented by: Tom Connolly, Jason Lieberman Company: BizTech Session ID: #10351 Overview Introductions Background Web
Introduction to Testing Webservices
Introduction to Testing Webservices Author: Vinod R Patil Abstract Internet revolutionized the way information/data is made available to general public or business partners. Web services complement this
A Design Pattern and Step-by-Step Implementation Guide for Salesforce Cloud Integration through IBM Integration Bus (v9)
A Design Pattern and Step-by-Step Implementation Guide for Salesforce Cloud Integration through IBM Integration Bus (v9) By Dipak Kumar Pal ([email protected]) Introduction Many enterprises have
AXL Troubleshooting. Overview. Architecture
AXL Troubleshooting This chapter contains the following topics: Overview, page 35 Architecture, page 35 Postinstallation Checklist, page 36 Troubleshooting Tools, page 39 Error Codes, page 43 Overview
Encryption, Signing and Compression in Financial Web Services
Danske Bank Encryption, Signing and Compression in Financial Web Services Details of how to call the Danske Bank financial web service Version 2.4.7 Encryption, Signing and Compression in Financial Web
Call Detail Record Access Service Part No. 520-0015-01R01
Call Detail Record Access Service Part No. 520-0015-01R01 Summary Objective WSDL URL (Testing) WSDL URL (Hosting Production) Endpoint URL (Testing) Endpoint URL (Hosting Production) Namespace URI Service
Integration of Hotel Property Management Systems (HPMS) with Global Internet Reservation Systems
Integration of Hotel Property Management Systems (HPMS) with Global Internet Reservation Systems If company want to be competitive on global market nowadays, it have to be persistent on Internet. If we
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material,
Exchange Synchronization AX 2012
Exchange Synchronization AX 2012 Autor... Pascal Gubler Dokument... Exchange Synchronization 2012 (EN) Erstellungsdatum... 25. September 2012 Version... 2 / 17.06.2013 Content 1 PRODUKTBESCHREIBUNG...
Single Sign-On Implementation Guide
Version 27.0: Spring 13 Single Sign-On Implementation Guide Last updated: February 1, 2013 Copyright 2000 2013 salesforce.com, inc. All rights reserved. Salesforce.com is a registered trademark of salesforce.com,
HireDesk API V1.0 Developer s Guide
HireDesk API V1.0 Developer s Guide Revision 1.4 Talent Technology Corporation Page 1 Audience This document is intended for anyone who wants to understand, and use the Hiredesk API. If you just want to
SOPG (Service Oriented Prepaid Gateway - xml based protocol) Documentation. Version Date Description Author
CLASSIC PAYMENT API SOPG (Service Oriented Prepaid Gateway - xml based protocol) Documentation Version history Version Date Description Author 0.1 2013-10-03 Initial draft Paul Kneidinger 0.2 2013-20-03
Authentication and Single Sign On
Contents 1. Introduction 2. Fronter Authentication 2.1 Passwords in Fronter 2.2 Secure Sockets Layer 2.3 Fronter remote authentication 3. External authentication through remote LDAP 3.1 Regular LDAP authentication
The presentation explains how to create and access the web services using the user interface. WebServices.ppt. Page 1 of 14
The presentation explains how to create and access the web services using the user interface. Page 1 of 14 The aim of this presentation is to familiarize you with the processes of creating and accessing
Your customer engagement transformation starts here
Your customer engagement transformation starts here Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Developing with the MediaBin
Twinfield Single Sign On
Twinfield Single Sign On manual, version 5.4 April 2009 For general information about our webservices see the Twinfield Webservices Manual Twinfield International NV De Beek 9-15 3871 MS Hoevelaken Netherlands
Sage CRM. Sage CRM 2016 R1 Web Services Guide
Sage CRM Sage CRM 2016 R1 Web Services Guide Copyright 2015 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced,
Safeguard Ecommerce Integration / API
Safeguard Ecommerce Integration / API Product Manual Version 3 Revision 1.11 Table of Contents 1. INTRODUCTION... 4 1.1 Available commands... 4 2. HOW THE ADMINISTRATION SYSTEM IS EXPECTED TO BE USED OPERATIONALLY...
How to consume a Domino Web Services from Visual Studio under Security
How to consume a Domino Web Services from Visual Studio under Security Summary Authors... 2 Abstract... 2 Web Services... 3 Write a Visual Basic Consumer... 5 Authors Andrea Fontana IBM Champion for WebSphere
Temando Api. Release 1.13. Developer Documentation. Temando IT Department
Api Release 1.13 Developer Documentation IT Department 1 st Edition July 2009 Contents 1. INTRODUCTION... 3 1.1. PURPOSE... 3 1.2. REVISION HISTORY... 3 1.3. NAMESPACES... 5 1.4. DOCUMENT CONVENTIONS...
e-filing Secure Web Service User Manual
e-filing Secure Web Service User Manual Page1 CONTENTS 1 BULK ITR... 6 2 BULK PAN VERIFICATION... 9 3 GET ITR-V BY TOKEN NUMBER... 13 4 GET ITR-V BY ACKNOWLEDGMENT NUMBER... 16 5 GET RETURN STATUS... 19
Riverbed Cascade Shark Common REST API v1.0
Riverbed Cascade Shark Common REST API v1.0 Copyright Riverbed Technology Inc. 2015 Created Feb 1, 2015 at 04:02 PM Contents Contents Overview Data Encoding Resources information: ping information: list
Single Sign-On Implementation Guide
Single Sign-On Implementation Guide Salesforce, Summer 15 @salesforcedocs Last updated: July 1, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
GetLibraryUserOrderList
GetLibraryUserOrderList Webservice name: GetLibraryUserOrderList Adress: https://www.elib.se/webservices/getlibraryuserorderlist.asmx WSDL: https://www.elib.se/webservices/getlibraryuserorderlist.asmx?wsdl
Sage 100 ERP. ebusiness Web Services Installation and Reference Guide
Sage 100 ERP ebusiness Web Services Installation and Reference Guide 2012 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product and service names mentioned herein are registered
CRM On Demand. Oracle CRM On Demand CTI Developer s Guide
CRM On Demand Oracle CRM On Demand CTI Developer s Guide Release 19 September 2011 Copyright 2005, 2011 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided
Office of Court Administration Automated Registry (AR) Interface Design Document for DSHS - Clinical Management for Behavioral Health Services (CMBHS)
Office of Court Administration Automated Registry (AR) Interface Design Document for DSHS - Clinical Management for Behavioral Health Services (CMBHS) August 04, 2009 Interface Design Document for CMBHS
Server based signature service. Overview
1(11) Server based signature service Overview Based on federated identity Swedish e-identification infrastructure 2(11) Table of contents 1 INTRODUCTION... 3 2 FUNCTIONAL... 4 3 SIGN SUPPORT SERVICE...
Table of contents. 2. Technical details... 7 2.1. Protocols used... 7 2.2. Messaging security... 7 2.3. Encoding... 7 2.4. Input and output...
Table of contents Revision history... 3 Introduction... 4 1. Environments... 5 1.1. Test/ acceptance environment... 5 1.2. Production environment... 5 1.3. Methods... 5 1.3.1. DataRequest... 5 1.3.2. StandardDataRequest...
Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager
Paper SAS1787-2015 Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager Chris Upton and Lori Small, SAS Institute Inc. ABSTRACT With the latest release of SAS
Developer Guide to Authentication and Authorisation Web Services Secure and Public
Government Gateway Developer Guide to Authentication and Authorisation Web Services Secure and Public Version 1.6.3 (17.04.03) - 1 - Table of Contents Government Gateway 1 Developer Guide to Authentication
HTTP and HTTPS Statistics Services
CHAPTER 9 This chapter describes the HTTP and HTTPS Statistics service, which returns HTTP and HTTPS connection information and statistics for individual WAEs, device groups, and for the WAAS network,
TXODDS Running Ball Feed US Sports Edition. User Guide
TXODDS Running Ball Feed US Sports Edition User Guide Document version 2.05 January 2012 Table of Contents TXODDS RUNNING BALL FEED...1 US SPORTS EDITION...1 TABLE OF CONTENTS...2 WHAT IS THE RUNNING BALL
PHP Language Binding Guide For The Connection Cloud Web Services
PHP Language Binding Guide For The Connection Cloud Web Services Table Of Contents Overview... 3 Intended Audience... 3 Prerequisites... 3 Term Definitions... 3 Introduction... 4 What s Required... 5 Language
Real-Time Connectivity Specifications For. 270/271 and 276/277 Inquiry Transactions. United Concordia Dental (UCD)
Real-Time Connectivity Specifications For 270/271 and 276/277 Inquiry Transactions United Concordia Dental (UCD) May 15, 2015 1 Contents 1. Overview 2. Trading Partner Requirements 3. Model SOAP Messages
SPARROW Gateway. Developer API. Version 2.00
SPARROW Gateway Developer API Version 2.00 Released May 2015 Table of Contents SPARROW Gateway... 1 Developer API... 1 Overview... 3 Architecture... 3 Merchant Private Key and Payment Types... 3 Integration...
Fairsail REST API: Guide for Developers
Fairsail REST API: Guide for Developers Version 1.02 FS-API-REST-PG-201509--R001.02 Fairsail 2015. All rights reserved. This document contains information proprietary to Fairsail and may not be reproduced,
Web Service Facade for PHP5. Andreas Meyer, Sebastian Böttner, Stefan Marr
Web Service Facade for PHP5 Andreas Meyer, Sebastian Böttner, Stefan Marr Agenda Objectives and Status Architecture Framework Features WSD Generator PHP5 eflection API Security Aspects used approach planned
HTTP/SOAP Application Program Interface (API) Version 1.0
HTTP/SOAP Application Program Interface (API) Version 1.0 September 2010 INTRODUCTION: ChillNet introduces a new HTTP SMS API to address the requirements of the SMS software developer community. This HTTP
CAS Protocol 3.0 specification
CAS Protocol 3.0 specification Contents CAS Protocol 3.0 Specification 5 Authors, Version 5 1. Introduction 5 1.1. Conventions & Definitions.................... 5 1.2 Reference Implementation....................
CA Nimsoft Service Desk
CA Nimsoft Service Desk Web Services Guide 7.0.6 Legal Notices Copyright 2013, CA. All rights reserved. Warranty The material contained in this document is provided "as is," and is subject to being changed,
Single Sign-On Implementation Guide
Single Sign-On Implementation Guide Salesforce, Winter 16 @salesforcedocs Last updated: November 4, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
Office365Mon Subscription Management API
Office365Mon Subscription Management API Office365Mon provides a set of APIs for managing subscriptions in our service. With it you can do things like create a subscription, change the details about the
vcommander will use SSL and session-based authentication to secure REST web services.
vcommander REST API Draft Proposal v1.1 1. Client Authentication vcommander will use SSL and session-based authentication to secure REST web services. 1. All REST API calls must take place over HTTPS 2.
Examining the InDesign Server Solution
Examining the InDesign Server Solution This is an online bonus article for Chapter 13 of Paperless: Real-World Solutions with Adobe Technology. This article details the tools and techniques that were used
Merchant Service Provider Guide for Mobilpenge Based Acquiring
Merchant Service Provider Guide for Mobilpenge Based Acquiring November 14, 2011 Version 1.07 Nets Technical Guide Copyright Nets Danmark A/S Page 1 Contents 1 Introduction... 4 1.1 Notation convention...
Marketo Integration Setup Guide
Page 1 of 30 Table of Contents About the RingLead Integration with Marketo Create the Marketo Webhook - Response Mapping - Configure Webhook Response Mapping Create the Marketo Program and Campaign - Create
APPLICATION SETUP DOCUMENT
APPLICATION SETUP DOCUMENT HeiTek Software Development GmbH Add-Ons Oracle Application Change Layout in Receiving Personalisation Example Ref Prepared by HeiTek Software Development GmbH Author: : Georg
SAML v2.0 for.net Developer Guide
SAML v2.0 for.net Developer Guide Copyright ComponentSpace Pty Ltd 2004-2015. All rights reserved. www.componentspace.com Contents 1 Introduction... 1 1.1 Features... 1 1.2 Benefits... 1 1.3 Prerequisites...
Technical Interface Description
Technical Interface Description Version 2.4.1 28.04.2015 Table of Contents 1 Introduction... 6 1.1 Preamble... 6 1.2 Structure of the Document... 6 1.3 Referenced Documents... 7 1.4 List of Abbreviations...
Data Center Automation with SUSE Manager Federal Deployment Agency Bundesagentur für Arbeit Data Center Automation Project
Data Center Automation with SUSE Manager Federal Deployment Agency Bundesagentur für Arbeit Data Center Automation Project Ralf Bueker DSE Bundesagentur für Arbeit [email protected] What is a DSE? DSE means
CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS)
CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS) Implementation Guide for Insurance Companies Version 1.1 August 15, 2015 MV Solutions, Inc. 2014 Table of Contents 1. INTRODUCTION... 3 2. BOOK OF BUSINESS
Magensa Services. Administrative Account Services API Documentation for Informational Purposes Only. September 2014. Manual Part Number: 99810058-1.
Magensa Services Administrative Account Services API Documentation for Informational Purposes Only September 2014 Manual Part Number: 99810058-1.01 REGISTERED TO ISO 9001:2008 Magensa I 1710 Apollo Court
How To Use Web Services In Matlab
WEB SERVICES BASED DATA ACQUISITION FROM A PROCESS DATABASE J. Cigler 1, J. Široký 2,3, M. Kulvejt 3, M. Chlupáč 3, D. Gyalistras 4 1 Department of Control Engineering, Faculty of Electrical Engineering,
Quiz! Database Indexes. Index. Quiz! Disc and main memory. Quiz! How costly is this operation (naive solution)?
Database Indexes How costly is this operation (naive solution)? course per weekday hour room TDA356 2 VR Monday 13:15 TDA356 2 VR Thursday 08:00 TDA356 4 HB1 Tuesday 08:00 TDA356 4 HB1 Friday 13:15 TIN090
Web Services Integration Case Study - Housing
SUNGARD SUMMIT 2007 sungardsummit.com 1 Web Services Integration Case Study - Housing Presented by: Tom Chamberlin, Suresh Chellapilla, Richard Moon SunGard Higher Education March 21, 2007 A Community
Copyright 2013 Consona Corporation. All rights reserved www.compiere.com
COMPIERE 3.8.1 SOAP FRAMEWORK Copyright 2013 Consona Corporation. All rights reserved www.compiere.com Table of Contents Compiere SOAP API... 3 Accessing Compiere SOAP... 3 Generate Java Compiere SOAP
Web Services. Distributed Object Systems 11. Web Services, SOAP and NET. Web Applications. Web Services. Web services vs Distributed Objects
Distributed Object Systems 11 Web Services, SOAP and NET Piet van Oostrum Web Services Some Definitions A Web Service is a software system designed to support interoperable machine-to-machine interaction
GATEWAY FREEDOM INTEGRATION GUIDE
Payment solutions for online commerce GATEWAY FREEDOM INTEGRATION GUIDE Copyright PayPoint.net 2010 This document contains the proprietary information of PayPoint.net and may not be reproduced in any form
Salesforce.com Integration Using SAP PI: A Case Study
Salesforce.com Integration Using SAP PI: A Case Study Applies to: SAP NetWeaver Process Integration 7.1. For more information, visit the Service Bus-based Integration homepage. Summary This article explains
eservice B2B Installation and Configuration Guide
eservice B2B Installation and Configuration Guide V1.0 October 2015 Contents About this guide... 1 Audience... 1 Related documentation... 1 Getting started... 1 How to contact IP Australia customer support...
Web Services in Eclipse. Sistemi Informativi Aziendali A.A. 2012/2013
Web Services in Eclipse A.A. 2012/2013 Outline Apache Axis Web Service Clients Creating Web Services 2 Apache Axis Web Services in Eclipse WS basics (I) Web services are described by their WSDL file Starting
vcenter Single Sign On Programming Guide vcenter Single Sign On SDK vsphere 5.5
vcenter Single Sign On Programming Guide vcenter Single Sign On SDK vsphere 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced
KMx Enterprise: Integration Overview for Member Account Synchronization and Single Signon
KMx Enterprise: Integration Overview for Member Account Synchronization and Single Signon KMx Enterprise includes two api s for integrating user accounts with an external directory of employee or other
Please see the attached file: "SendExample.asp" for an example of how you can send files using classic ASP.
NVMS, Inc Data Exchange Specifications Version 1.5.1010 Client: Client Here Client ID: Client Num This document should explain the setup of the B2B data exchange using the transfer of data using an HTTP
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-EDCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
T320 E-business technologies: foundations and practice
T320 E-business technologies: foundations and practice Block 3 Part 1 Activity 5: Implementing a simple web service Prepared for the course team by Neil Simpkins Introduction 1 Components of a web service
IBM SPSS Collaboration and Deployment Services Version 6 Release 0. Single Sign-On Services Developer's Guide
IBM SPSS Collaboration and Deployment Services Version 6 Release 0 Single Sign-On Services Developer's Guide Note Before using this information and the product it supports, read the information in Notices
PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者
PASS4TEST 専 門 IT 認 証 試 験 問 題 集 提 供 者 http://www.pass4test.jp 1 年 で 無 料 進 級 することに 提 供 する Exam : C2090-420 Title : IBM InfoSphere MDM Server v9.0 Vendors : IBM Version : DEMO NO.1 Which two reasons would
Copyright 2012, Oracle and/or its affiliates. All rights reserved.
1 OTM and SOA Mark Hagan Principal Software Engineer Oracle Product Development Content What is SOA? What is Web Services Security? Web Services Security in OTM Futures 3 PARADIGM 4 Content What is SOA?
Force.com Migration Tool Guide
Force.com Migration Tool Guide Version 35.0, Winter 16 @salesforcedocs Last updated: October 29, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
JASPERREPORTS SERVER WEB SERVICES GUIDE
JASPERREPORTS SERVER WEB SERVICES GUIDE RELEASE 5.0 http://www.jaspersoft.com JasperReports Server Web Services Guide Copyright 2012 Jaspersoft Corporation. All rights reserved. Printed in the U.S.A. Jaspersoft,
The BritNed Explicit Auction Management System. Kingdom Web Services Interfaces
The BritNed Explicit Auction Management System Kingdom Web Services Interfaces Version 5.1 November 2014 Contents 1. PREFACE... 6 1.1. Purpose of the Document... 6 1.2. Document Organization... 6 2. Web
Configuration Guide - OneDesk to SalesForce Connector
Configuration Guide - OneDesk to SalesForce Connector Introduction The OneDesk to SalesForce Connector allows users to capture customer feedback and issues in OneDesk without leaving their familiar SalesForce
Documentation Cendris Web Services Version 20 12 July 2013
Documentation Cendris Web Services Version 20 12 July 2013 Document: Documentation Cendris Webservices.docx blz 1 van 40 Index 1 Introduction... 3 2 Webportal Cendris Web services... 4 3 Implementation
Using Web Services to Exchange data with Qualtrics and Hobsons Connect
Using Web Services to Exchange data with Qualtrics and Hobsons Connect Definitions Let s not argue over small differences Web Service A method of communication between two devices over the Internet. Two
EUR-Lex 2012 Data Extraction using Web Services
DOCUMENT HISTORY DOCUMENT HISTORY Version Release Date Description 0.01 24/01/2013 Initial draft 0.02 01/02/2013 Review 1.00 07/08/2013 Version 1.00 -v1.00.doc Page 2 of 17 TABLE OF CONTENTS 1 Introduction...
MasterPass Service Provider Onboarding & Integration Guide Fileand API-Based Merchant Onboarding Version 6.10
MasterPass Service Provider Onboarding & Integration Guide Fileand API-Based Merchant Onboarding Version 6.10 7 January 2016 SPBM Summary of Changes, 7 January 2016 Summary of Changes, 7 January 2016 This
Address Phone & Fax Internet
Smilehouse Workspace 1.13 Payment Gateway API Document Info Document type: Technical document Creator: Smilehouse Workspace Development Team Date approved: 31.05.2010 Page 2/34 Table of Content 1. Introduction...
2015-11-30. Web Based Single Sign-On and Access Control
0--0 Web Based Single Sign-On and Access Control Different username and password for each website Typically, passwords will be reused will be weak will be written down Many websites to attack when looking
Web-Programmierung (WPR)
Web-Programmierung (WPR) Vorlesung X. Web Services Teil 2 mailto:[email protected] 1 21 Web Service World Wide Web seit Anfang 1990er Jahren Mensch Web-Browser Applikation HTTP XML over HTTP Web-Server Geschäftslogik
mframe Software Development Platform KEY FEATURES
mframe Software Development Platform mframe is a comprehensive software development platform for building modern modular WEB and B2B applications. It consists of basic core modules as well as other delevoped
MINISTRY OF FINANCE SYSTEM INTEGRATION PLAN ATTACHMENT NR 2 SEAP XML SPECIFICATION WEBSERVICE INTERFACE FOR EXTERNAL SYSTEMS PROJECT ECIP/SEAP
MINISTRY OF FINANCE SYSTEM INTEGRATION PLAN ATTACHMENT NR 2 SEAP XML SPECIFICATION WEBSERVICE INTERFACE FOR EXTERNAL SYSTEMS PROJECT ECIP/SEAP VERSION 1 z 26 Table of Contents 1. WebService Interface
Force.com REST API Developer's Guide
Force.com REST API Developer's Guide Version 35.0, Winter 16 @salesforcedocs Last updated: December 10, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
Contents. 2 Alfresco API Version 1.0
The Alfresco API Contents The Alfresco API... 3 How does an application do work on behalf of a user?... 4 Registering your application... 4 Authorization... 4 Refreshing an access token...7 Alfresco CMIS
HOST EUROPE CLOUD STORAGE REST API DEVELOPER REFERENCE
HOST EUROPE CLOUD STORAGE REST API DEVELOPER REFERENCE REST API REFERENCE REST OVERVIEW Host Europe REST Storage Service uses HTTP protocol as defned by RFC 2616. REST operations consist in sending HTTP
Responsys Interact January 2011. 900 Cherry Ave. 5 th Floor San Bruno, CA 94066 650.745.1700 www.responsys.com
Interact Campaign Interact Web Services API Developer Guide Responsys Interact January 2011 900 Cherry Ave. 5 th Floor San Bruno, CA 94066 650.745.1700 www.responsys.com Table of Contents Table of Contents
