SAP ABAP IMG Activity SIMG_ISHCM_TYPSPEC (Describe Special Features of Message Formats)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID SIMG_ISHCM_TYPSPEC Describe Special Features of Message Formats  
Transaction Code S_KK4_74000441   IMG Activity: SIMG_ISHCM_TYPSPEC 
Created on 19990816    
Customizing Attributes SIMG_ISHCM_TYPSPEC   Describe Special Features of Message Formats 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_ISHCM_TYPSPEC    

Description of Special Features of Message Formats

Contents

  1. General format specifications
    1. Character set
    2. IDs and alpha-conversion
    3. Check digits
    4. No value specification
  2. SAP-HCM-Format
    1. General
    2. Type 103 Surgery specifications
    3. Type 104 Surgeries 2
  3. HL7 format
    1. General
    2. Segment PID Patient identification
    3. Segment DG1 Diagnosis

The message formats used by HCM can be displayed in the SAP system and printed using the programs RNCUTL01 and RNCUTL02. The SAP-HCM original formats and the supported HL7 message structures are appended to the hardcopy of this documentation.

It is assumed in the following documentation that you are in possession of this HCM format description. In this section, only topics are discussed that are not covered directly in the format description.

  1. General format specifications
    1. Character set

      HCM only supports the transmission of ASCII characters. The special characters in character format are handled as defined by ISO 8859-1. However, it also possible to carry out data exchange in another character set. This is made possible by simply specifying the required character set for the partner system in Customizing. The new line character is not affected by this conversion: it is always CRLF (hexadecimal '0D0A'). For a discussion on the problem of new lines, refer to the section File structure under Explain Programming of Partner Programs.

    2. IDs and alpha-conversion

      Alpha-conversion is used with all IDs within the SAP System. This conversion of numeric values with leading zeros into a format without leading zeros for character fields (and vice-versa) simplifies the entry of numeric keys that are shorter than the corresponding field. You do not need to enter leading zeros provided the key in question is purely numerical.

      Example for case number: The case number is internally a 10-digit character field without lowercase entry. If the case number entered is left-justified and contains only digits (0-9), this number is handled internally with leading zeros. However, if it contains a letter (in combination with digits) the case number is handled as if it were a character field (with leading blanks, if specified). These internal formats are transferred by HCM in the following way:

      'ABCDE ', '0000012345', '12345A ', '0000000001'.

      Alpha-conversion is also employed when data is transferred to the IS-H System. This means that received case numbers which contain only left-justified digits (0-9) are first converted into the internal format with leading zeros.

      For example, the following inputs

      'ABCDE ', '12345 ', '12345A ', '00001 '

      are assigned to precisely the example cases above.

      Alpha-conversion is also performed when numbers are entered with leading blanks.

      Example: entry ' 123 ' becomes '000000123'

      i.e. leading blanks before pure digit strings are ignored.

      To avoid 'misunderstandings' between communication partners, it is advisable to transmit all specifications of keys to be imported into the IS-H System in the internal format (i.e. with leading zeros where numbers are concerned) or strictly left-justified. To prevent ambiguity when data is sent from IS-H to partner systems, IDs are always transmitted with leading zeros.

    3. Check digits

      In the IS-H System, check digits are calculated exclusively according to DIN ISO 7064, MOD 11, 10 standard. Other check digit schemes are not supported. Leading zeros with purely numeric keys are always transferred. Thus, the number of positions to calculate the check digit for this field corresponds automatically to the field length. This must be taken into account when connecting partner systems. Checks on single check digits or such checks in programs must ensure the correct field length taking into account the leading zeros.

      You can obtain the exact documentation on the calculation of the check digits from the publisher BEUTH in Berlin (tel. 030/26010). They are the only distributor, all rights remain with them.

      For control purposes, the recursive calculation schema is listed below:

      4. character string is processed from left to right;
      N => number of digits in string including check digit;
      J = 1, 2, ..., N => index;
      a(J) => digit value at J-th position (a(1) = check digit at far right!);
      P(1) = 10 => starting value.
      The calculations are:
          S(J) = P(J)mod11 + a(N-J+1)
          P(J+1) = S(J)mod10 x 2
      where
      mod10 => remainder of division by 10; if remainder is 0, then substitute
      10 instead;
      mod11 => remainder of division by 11 (never equal to 0).
      string is correct if S(N) = 1 (mod 10).
      To calculate the check digit a(1), the following
          P(N)mod11 + a(1) = 1 (mod 10).

      Essentially customers can implement their own check digit procedure (IS-H user exit for event PZIF). The description of the corresponding algorithm must then be supplied by the customer.

    4. No value specification

      The SAP system enables you to define for each client a special character to prevent the contents of a field from being transferred in batch input processing. SAP suggests you use a slash '/' for this no value character.

      If the first position of a field (from a sequential file or imported via HCM) contains the special character that has been defined as the no value character and no other characters are present in this field, the contents of this field are not transferred. The special character is interpreted as "no entry for this field". Consequently, when a data record is created, default values are used from Customizing or from associated master files. When a data record is changed, existing values are not overwritten.

      When data is transferred into the IS-H System this logic must be taken into account for all critical fields. Critical fields in IS-H are those that are filled with values from master data or Customizing if no user entry is made. Note that if a no value character is not used, empty entries are made. This usually causes defaulting to Customizing or master entries to be deactivated.

      A similar logic does not apply to the transmission of messages from the IS-H System. 'Initial value' and 'no specification' are not distinguished in the SAP database. Hence, HCM cannot make this distinction when transmitting field contents to partner systems.

  2. SAP-HCM format
    1. General

      Two versions of the SAP-HCM standard are currently in use. When setting up new connections, you should always implement the latest version (currently Version 1.2).

      SAP-HCM Version 1.2 provides two message types for transmitting data relating to performed case-related services: types 101 and 102. If possible, the (more comprehensive) type 102 should be used.

      All SAP-HCM messages are always transmitted in their full length. A mode that allows for messages to be compressed using field separators (see HEA segment 001, field 2 FLDSEPARTR) is currently not supported.

    2. Type 103 surgery specifications

      The SAP-HCM message type 103 surgery specifications contains the two essential data segments OPD surgery data and OPS surgery-related services. Both segments are repeat segments and, as such, may be allowed to occur as many times as required within a message.

      To enable the services to be correctly assigned to the surgeries when the transmitted data is subsequently written to the database, the field REFSURGNO Reference surgery number must be correctly filled both in the surgery data segment OPD and in each of the corresponding service segments OPS. The assignment of services to surgeries is carried out exclusively via this reference number!

      Please enter a number that is unique at least per case and surgery in this field. This is essential if services are to be assigned to the correct surgery. If you leave the initial value in this field, and there are several surgeries for the same case within a batch input session (corresponds to an HCM transfer, which in turn corresponds to a transfer file), it is assumed that the services were used for all the surgeries. Dividing up the services in different messages has no influence on this result.

      Caution: Message type 103 becomes obsolete with IS-H Release 4.03. The surgery entry transaction has been redesigned for IS-H Release 4.03 and provides a number of

Business Attributes
ASAP Roadmap ID 899   not to be assigned 
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 SIMG_ISHCM_TYPSPEC 0 I010004207 O I010004232 O I010004233  
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990816 
SAP Release Created in