Replace patient create bapi with enterprise service

[Former Member]

Hi all,

I've compared the input data of the patient create bapi with the input message of the patient create enterprise service. There are some differences and so I don't know if it's possible to replace the bapi with the enterprise service. As example, the bapi offers input fields for contact persons (first and last name, relationship, address number) which are stored in the table NPAT.

In contrast, the enterprise service offers the input type dependent relationship with fields DependendId and RoleCode.

Which table does the service use to store the contact information?

Does the create patient service fill the same tables as the bapi?

Is it possible to replace the bapi create patient with the enterprise service?

Best regards,

Christian Sonek

[nektarios_dourdas · Accepted solution]

Hi,

With the Create Patient service you can only create relationships to existing business partners. This is possible when you are using the standard SAP Business Partner instead of the "old" patient. Precondition: the business partner you want to create a relationship to must already exist, as you need to provide its ID (PartyID), along with the RelationshipRoleCode which specifies the type of relationship. For dependents, we provide a separate node (DependentRelationship), in which you can specify this kind of relationships to other business partners.

In terms of storage, the service uses the standard business partner tables.

My colleague will soon provide more information on the differences between the BAPI and the enterprise service.

Best regards,

Nektarios Dourdas

[Former Member]

Hi,

so the Create Patient service and the Patient Create BAPI are not compatible.

Because all our customers use the "old" patient and the ISH business partner tables, it seems

that we can't replace the BAPI communication with the Enterprise Services.

Best regards,

Christian Sonek

[former_member293229]

Hi Christian,

Enterprise services expose more or less the business partner interface whereas BAPIs expose the patient management interfaces complying to the former data model. As my colleagued described before, next of kin is handled as a separate business partner and due to that fact, services and BAPIs behave in a different way.

That means, in case a customer does not want to upgrade to the new patient management concept with using the central business parter he cannot create next of kin data with the PatientCreate service. In case he wants to upgrade to the new Patient concept and he agrees to store patients and next of kin as business partners, he can replace the API with the service.

Apart from next of kin data, the service for patient create can be used to create patients even with the old patient

Best Regards, Doris Karbach

[Former Member]

Hi Doris,

I assume that, within the next years, most of our customers don't want to change their running systems to use

the new patient management concept, but on the other side they don't want to work without next of kin information.

Is there a way to extend the enterprise service to handle also the 'former', or better present, data model?

Best regards,

Christian

[Claudius]

Hi Christian,

to your question how to extend an Enterprise Service - please see the [Enterprise Services Enhancement Guide|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0bb5687-00b2-2a10-ed8f-c9af69942e5d?overridelayout=true]. We are currently looking into options how to provide an example for Healthcare services. Maybe we can jointly create one based on your "next of kin" issue?

Best regards

Claudius

[nektarios_dourdas]

Hi,

As an additional information, in order to extend the signature of an enterprise service you require the ESR (Enterprise Services Repository). You can get the ESR either by installing a SAP NetWeaver PI or SAP NetWeaver Composition Environments 7.1x.

Best regards,

Nektarios Dourdas

[Former Member]

Thanks Claudius and Nektorios,

it will take some time till we are able to extend enterprise services, but I think we can

find together examples for Healthcare services. But don't you think that the "next of kin"

issue should be integrated in a released enterprise service, because otherwise most of the

users prefer using the Patient BAPI which provides the "next of kin" issue.

Best regards,

Christian

[former_member293229]

Hi Christian,

do you have a PI or do you only have the backend system?

Best Regards, Doris

[Former Member]

Hi Doris,

at the moment we only have the backend system, but it's possible that we also get a PI.

Best regards,

Christian