Configuration - Merge Healthcare

More documents

Recommendations

Info

Merge DICOM Toolkit Reference Manual 228 MC_REQUIRED_ATTRIBUTE_MISSING Some DICOM services require certain command level attributes (group 0) to have values set. This status indicates that a required attribute value for the service related to MessageID has not been set. MC_UNACCEPTABLE_SERVICE The service related to MessageID has not been successfully negotiated for this association. MC_SYSTEM_ERROR An unexpected, potentially serious, problem was detected in the operating environment. A message describing the error has been written to the Merge DICOM Toolkit log file. The association is dropped if any of the following are returned: MC_ASSOCIATION_ABORTED The association has been aborted. A message describing the error has been written to the Merge DICOM Toolkit log file. See Also MC_Register_Callback_Function MC_Send_Request_Message MC_Send_Response_Message MC_Open_Message MC_Read_Message MC_Get_Meta_ServiceName MC_Send_Response_Message Sends a response to a message received from the remote application. Synopsis #include “mergecom.h” MC_STATUS MC_Send_Response_Message ( int AssociationID, RESP_STATUS ResponseStatus, int ResponseMessageID ) AssociationID The association object’s identification number ResponseStatus This is the status code to be returned. It must be one of the enumerated RESP_STATUS codes defined in “mergecom.h”. ResponseMessageID This is the ID of a message object containing the response message.
Merge DICOM Toolkit Reference Manual Remarks MC_Send_Response_Message allows the caller to respond to a message received from the remote application. MC_Send_Response_Message is called after receiving a request message using MC_Read_Message. ResponseStatus must be set to a valid response code for the service involved. Response codes for standard DICOM services are defined in the “mergecom.h” file. ResponseMessageID must be set to an identifier returned by MC_Open_Message. Many DICOM services do not require a response of more than just a status. Others, however, (e.g. C_FIND_RSP) require the setting of several message attributes. Note: Some DICOM services require that values for certain “command level” message attributes (i.e. group 0 attributes) be set. (Merge DICOM Toolkit automatically adds command level attributes to the message when MC_Open_Message is called. With the exceptions listed below, the caller must set any command level attribute values before sending the message. MC_Send_Response_Message does, however, set the following attribute values for you - if you have not set them: • The group length attribute (0000,0000) value is always set by Merge DICOM Toolkit. • If the message command requires it, the Affected SOP Class UID attribute (0000,0002) value is set to the service’s abstract syntax UID. • The command attribute (0000,0100) value is always set by Merge DICOM Toolkit. • The Response Message ID attribute (0000,0120) value is set to the Message ID value of the last received Request message. • The Data Set Type attribute (0000,0800) value is always set by Merge DICOM Toolkit. If MC_Send_Response_Message returns MC_ASSOCIATION_ABORTED, no further calls may be made for that association. Return Value One of the enumerated MC_STATUS codes defined in “mcstatus.h”: Value Meaning MC_NORMAL_COMPLETION The function completed normally. MC_INVALID_ASSOC_ID AssociationID is not a valid association object ID. MC_INVALID_MESSAGE_ID The MessageID value is not a valid message object ID. 229
Page 1 and 2:
Merge DICOM Toolkit C/C++ Reference
Page 3 and 4:
Merge DICOM Toolkit Reference Manua
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186: Merge DICOM Toolkit Reference Manua
Page 235: Merge DICOM Toolkit Reference Manua
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467:
show all

Configuration - Merge Healthcare

Create successful ePaper yourself

Delete template?

Save as template?