Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NMED (Package) R/3MED: Medical documentation GSD
IMG Activity
| ID | SIMG_ISHMED_RAD_BA05 | BAdI: Create RIS Study Key |
| Transaction Code | S_KK4_96000398 | IMG |
| Created on | 20010306 | |
| Customizing Attributes | SIMG_ISHMED_RAD_BA05 | IS-H*MED RAD: BAdI - Generate Study Ident |
| Customizing Activity | SIMG_ISHMED_RAD_BA05 | IS-H*MED RAD: BAdI - Generate Study Ident |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_RAD_STUDYID |
The BAdI ISHMED_RAD_STUDYID supports the definition and formatting of the RIS Study ID based on the relevant application. The system calls the BAdI when creating the Study Document.
You can find further information in the following documentation:
Example
Requirements
Standard settings
The active Standard BAdI creates the Study ID from <Client> <Service Number>, which appears right-justified with buffering zeros.
As an additional attribute, an Accession Number is supplied, made up of a <Client><Request ID>.
Recommendation
Activities
- If you use the standard supplied BAdI implementation no activity is necessary.
- If you need a different BAdI implementation, you must execute the following activities:
Via the IMG activities, create an implementation of the BAdI in the customer name space. Each one still contains no program code for the method(s). you can use the standard BAdI implementation as a template for your individual development.
Further notes
The values for STUDY_ID and ACCESSION_NUMBER are derived from data for the RIS study document management record. You must make sure of the system-wide uniqueness of the code used and implement a customer enhancement if necessary.
MITRA PACS Broker assigns an accession number to every service in the data model We recommend that in this case you use the prepared STUDY_ID with the sequential service number (surrogate).
ACCESSION_NUMBER can be transferred as the ORDER_NUMBER (PACS Broker Mapping).
You must co-ordinate with the PACS supplier which code will be used for identification of a DICOM Study. The standard BAdI Implementation is intended for implementing the MITRA Simple Interface (MSI).
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20010313 |
| SAP Release Created in | 463 |
