Mapeo Objeto/Relacional

Use

As of SAP ECC 6.0, Industry Extension Healthcare, Enhancement Package 4 (IS-H 604), Business Function SAP Patient Management: Rearchitecture BP/OM

(ISH_BP_OM), there are separate new tables to store the master data. All central data (common data) for all the business partners, patients, and patients with provisional master data is stored in the BUT000 table provided by SAP Business Partner (SAP BP). BUT000 has foreign-key relationships to the Address (BUT020), Roles (BUT100) and Relationships (BUT050) tables. Table NBUP hosts all data that is common to all SAP Patient Management (IS-H) business partners but is not handled by SAP BP (in other words, by BUT000). New tables are created to store the role-specific data for business partners, patients, and patients with provisional master data.

The following table gives the relationships between the tables that existed prior to this release and the new tables:

o For business partners:

IS-H BP SAP BP Re-Architecture Description

NGPA BUT000 and NBUP General business

partner data

NDEB NCUS Customer

NKRH NHSP Hospital

NABG NEPR Employer

NPER NPRS Person*

NKTR NINS Insurance provider

*Person refers to physicians, external physicians, and employees.

o For patients:

IS-H Data Source SAP BP Data Target

NPAT BUT000

NPNT o For patients with provisional master data:

IS-H Data Source SAP BP Data Target

NPAP BUT000

NPPT

Data must be migrated from the IS-H data source to the SAP BP data target mentioned above.

The primary keys of master data tables NGPA and NPAT must be stored as references to the old records in the corresponding tables of SAP BP (NBUP and NPNT,

respectively). This is necessary for the IS-H programs to distinguish between business partners in non-patient roles and business partners in HC Patient role. The reference

62 H object has changed in the meantime (delta migration before switching to SAP BP).

The primary key of table NPAP will not be stored in the SAP BP table NPPT as reference. Instead, the old primary key of NPAP and references to this key in other IS-H tables will be updated during migration with the primary key of the SAP BP in role IS-HC Patient w. Prov. Data. The references of the dependent tables for the HC Patient w.

Prov. Data (in other words, other tables that store references to the primary key of NPAP) will be updated with the SAP BP keys.

The following are also migrated: IS-H BPs with the deletion indicator set, IS-H patients with the cancellation indicator set . IS-H patients with provisional master data with the cancellation indicator set are not migrated.

o For Address Data

SAP BP uses Business Address Service (BAS) for address validation and postal code correctness. BAS stores address details in its own table (ADRC). Thus, data is migrated from the NADR table (which was used to store address details prior to this release) to the ADRC table. Except for the geographical area, all NADR fields can be mapped to table ADRC of BAS. The geographical area is stored in table NPNT for business partners in role Patient only.

o For Relationship Data - For business partners:

Relationships amongst insurance providers are stored in the BUT050 table (contains central details for the relationship) and NIPR table (contains data specific to the Insurance Provider - Insurance Provider relationship). Data is migrated from TNREL to these tables. These include the following relationships:

Is Form Recipient of Is HC SC Head Office of Is Invoice Recipient of

Is Head Office for Data Exchange acc. to 301 SGB V (DE) of

In this release, an employer acting as the accident insurance provider (stored in NABG table) is stored as a relationship between an HC Insurance Provider and an HC Employer. Also, the responsible PPA stored in the insurance provider table (NKTR) is stored as a relationship between an HC Insurance Provider and a business partner. The

relationship details of these two relationships are stored in the BUT050 table.

- For Patient:

Next of Kin

The details of the two next of kin of the patient were stored in the NPAT table prior to this release. After migration, this data is maintained as relationships to the patient, and data is stored in the BUT050 and NNOK (table to store data specific to next of kin relationship) tables after migration.

Patient's Employer

If the patient's employer is maintained as free text in the NPAT table then these details are migrated into the corresponding fields of the NPNT table.

In this release, if an employer is assigned to a patient, this is stored as a Patient-Employer relationship. After migration, data is stored in the BUT050 and NPEP (table to store data specific to Patient-Employer relationship) tables.

Patient's Physician

In this release, the referral and family physician assigned to a patientare stored as relationships to a patient. Data is stored in the BUT050 table.

Effects on Customizing

The data migration programs of Phase 2 can be accessed in Customizing for SAP Healthcare - Industry-Specific Components for Hospitals under Tools -> Migration of Business Partner and Hospital Structure -> Migration of Business Partner ->

Phase 2: Data Migration for BP During Uptime

The data migration programs of Phase 3 can be accessed in Customizing for SAP Healthcare - Industry-Specific Components for Hospitals under Tools -> Migration of Business Partner and Hospital Structure -> Migration of Business Partner ->

Phase 3: Data Migration of BP During Downtime

64

ISH_BP_OM: BAPI "BAPI_BUSPARTNER_CHANGE" (New)

Use

As of SAP ECC 6.0, Industry Extension Healthcare, Enhancement Package 4 (IS-H 604), Business Function SAP Patient Management BP/OM (ISH_BP_OM), you can use the Business Application Programming Interface (

BAPI

BAPI_BUSPARTNER_CHANGE to delete a business partner's title, name affix, and name prefix.

It was not possible to delete this data until now, because the BAPI only took the data into account if the fields TITLE, AFFIX, and PREFIX were not initial in the BAPI change structure BAPI1309BPARTINX.

You can now use the BAPI to change the business partner's short name.

The field for the short name was previously not available in the change structure BAPI1309BPARTINX. The fields SHORT_NAME_BP and SHORT_NAME_BPX have now been added to the structure for this purpose.

ISH_BP_OM: Business Partner Grouping for Patients and Next of Kin