When you transfer data to partner systems by means of HL7 messages, certain message fields are not filled.Or certain data is not transferred at all.
Or the PV1 segment is not filled in an A08 message, (only the header PV1 is specified).
A known general problem is the fact that HL7 does not provide any special date/time field in which the time of the transfer can be transferred in the standard system for transfer messages A02.
Consulting, adt^a08, adta08, NP0100, NP0200
This might be caused by a program error.However, the cause is more likely to be one of the following:
- a) the data in HL7 is not intended at all for transmission;
- b) the corresponding message field is not (yet) supported by SAP (for whatever reason);
- c) the empty PV1 segment cannot be supported related to events because a pure patient master action occurred without case selection (Transaction NP02 "Change Patient Master Data", for instance).
- d) In A02 messages 'Transfer patient', there is no special date/time field in which the time of the transfer can be transferred. There is the field of the event date in the EVN segment, but with that, the creation date should be explicitly transferred into the administration.
- a) This can be checked directly in the HL7 description.Owing to different data models, some problem areas are known in this context (for example, insurance relationships, insurance providers, case classifications ...).
These problems can actually only be corrected by additional user-defined message segments ("Z segments"). However, no support is currently offered by SAP for such Z segments. Neither is it planned to offer such support in the near future.If a (communication) standard can only work through individual programming, then it is in fact not standard.
In such cases, our SAP-HCM format is better suited since it much easier to use.In addition, all the available relevant data is supplied in the SAP-HCM format.Any new data (for example, the new legal regulations such as German Law Paragraph §301, German Social Security Code V) is also supported here as quickly as possible.
- b) Can be checked as follows:
Start program RNCUTL05.
Specify 'HL7' as the communications standard and the HL7 identifier as the segment number (for example, 'PID' for patient master data).
After 'Execute', you receive a list of the segment structureA 'N' (="No") character in a field in the column headed by 'U' (="Support") means that this field is not supported by SAP.
Example:in the 'PID' segment, field number 21 (field name 'PATDRVLIC') is not supported by SAP.
- c) In general, this only occurs for the HL7 event ADT^A08 (or the IS-H events NP01* and NP02*).In this case the PV1 segment is empty and the DG1 segment does not exist.
You can now remove the events NP01* and NP02* from the dispatch control. These changes are however no longer communicated, which causes data inconsistencies.
In theory you can also carry out a search for a certain (or all the) case(s) concerning this patient, and then create such a message for every case. However, this will not be supported by SAP as standard.This would have to be implemented as a modification or an enhancement by means of additional user-defined message segments ("Z segments").
SAP recommends that you make the message with empty PV1 segment itself understandable for the partner system.In contrast to American systems (and therefore also the HL7 standard), SAP partners should know the patient and case distinction.This makes processing the A08 message also possible without the PV1 segment.
If the system is not able to do this, the only remaining option to attain a 100-percent watertight solution is to determine all the cases and to create a separate message for each one.
- d) Cannot be solved in the standard system. There is no determination without a corresponding data. Here, you can possibly manage with customer-specific message versions. Of course, these must fit with the linked systems.
No comments:
Post a Comment