Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
N1CONN_MED (Package) i.s.h.med: Connectivity
IMG Activity
| ID | ISHMED_CON_HNDL_REG | Registration of Connectivity Handlers |
| Transaction Code | S_P7C_98000356 | (empty) |
| Created on | 20070817 | |
| Customizing Attributes | ISHMED_CON_HNDL_REG | Registration of Connectivity Handlers |
| Customizing Activity | ISHMED_CON_HNDL_REG | Registration of Connectivity Handlers |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_CON_HNDL_REG |
Use
In this IMG activity you register the handlers for the transmission of data (e.g. order types) to third party systems (outbound communication).
To guarantee central and standardized administration of all outbound communication of clinical order data using various communication types, we have created the i.s.h.med Connectivity Handler Framework.
This handler framework offers:
- a standard programming model
- some standard functions (e.g. logging)
- automated integration in the dialog for customizing clinical order types and in the process of entering and managing a clinical order
- Example implementations for various communication channels
The connectivity handler framework basically consists of a class model, which supplies the basic functionality for the following types of communication channels:
- HTTP
- RFC
- Web services
- Local storage
For each of these communication channels there are one or more example implementations available as derivations of the relevant basic class.
You can actually use these example implementations. However, in connectivity scenarios, scenario-specific adaptations are almost always necessary. You can make such adaptations in customer-specific handler classes by deriving from the relevant basic classes or the example implementations. You can use the example implementations as templates for this.
Each of the existing basic classes allows the implementation of one or more of the following actions in derived handlers:
- Create
- Read
- Update
- Delete
The handler registration to be executed in this IMG activity enables the assignment of handlers and handler actions for clinical ordering as well as subsequent customizing and reuse during order type definition. This is therefore the interface between developers and application support.
The developer creates a service consumer (e.g. web service client), "packs" this into an i.s.h.med connectivity handler of the suitable action (e.g. create) and registers it using handler registration. The handler is available in customizing from this point onwards.
You can also deactivate a handler (temporarily or permanently) using this handler registration.
Requirements
You must have implemented the handler class, corresponding actions and the necessary logical ports.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | ISHMED_CON_HNDL_REG | 0 | PRI1000001 | Connectivity |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| N1CONNHNDLREG | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20070817 |
| SAP Release Created in |
