Exeley Inc.

LIU, TIAN-HAO

ZHOU, YIN

TAO, WEN-CONG

LIU, YANG

ZHANG, XIAO-MEI

TIAN, SHOU-ZHENG

English

Bacterial Diversity in Roots, Stems, and Leaves of Chinese Medicinal Plant Paris polyphylla var. yunnanensis

Liu, Pingping

Lu, Jiaxing

International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
DOI: 10.21307/ijanmc-2020-003                                                         15 
Research on Enterprise Application Integration Platform 
Based on SOA Architecture 
 
Liu Pingping  
School of Computer Science and Engineering  
Xi’an Technological University 
Xi’an, 710021, China 
E-mail: 1341369601@qq.com 
 
 
Lu Jiaxing  
School of Computer Science and Engineering  
Xi’an Technological University 
Xi’an, 710021, China 
E-mail: 1721653661@qq.com 
 
 
 
Abstract—Tobacco industry is a relatively early industry in 
China&apos; information industry, so there are many 
problems, such as the lack of overall planning, the wide 
application system, but the low degree of integration of 
information resources, and the serious problem of 
"information island". In order to solve how to establish an 
efficient and flexible way of information interaction within the 
enterprise, an enterprise application integration platform 
based on SOA architecture is proposed. The platform takes 
ESB as the core, transforms enterprise information integration 
into a new way conforming to SOA architecture, and 
establishes the idea of basic data management, so as to achieve 
the purpose of optimizing the overall information resources of 
the enterprise 
Keywords-SOA Framework; Information Interaction; ESB; 
Information Integration 
I. INTRODUCTION  
SOA is widely used in the IT industry in the 21st 
century. SOA is service oriented architecture, Service 
oriented architecture. It is architecture, not a 
technology or a method. We can also say that SOA is 
an idea. In China, many enterprises begin to build 
enterprise integration platform based on SOA. For 
example, Kingdee Apusic SOA. Fmqm exotica, 
developed by Almaden Laboratory of IBM company, is 
a distributed workflow management system based on 
persistent message queue, which can save the execution 
information of workflow through persistent message 
queue and complete the complete independence of all 
nodes in the execution process 
SOA architecture has three significant advantages: 
loose coupling, coarse granularity, and location 
protocol transparency. Through the encapsulation of 
services to achieve a comprehensive loose coupling, 
loose coupling can reduce the dependency between 
services, so that the flexibility of the service itself can 
be improved, and it will not be forced to adjust because 
of other services adjustment, thus greatly improving the 
reusability of services. Coarse granularity means that 
the interface of services defined in SOA is close to the 
actual user operation. Location protocol transparency 
means that when accessing the service defined by SOA, 
you do not need to know the specific location and 
transport protocol of the service. Even if the location 
and transport protocol of the service change, the client 
that invokes the service does not need to change. Based 
on the investigation and analysis of the problems of 
information island, high coupling degree and poor 
integration expansibility of each system in BJ cigarette 
factory based on SOA architecture, an enterprise 
application integration platform design scheme suitable 
for the actual situation of the enterprise is proposed to 
solve the current problems. 
Therefore, through the research on the practical 
application of the enterprise application integration 
platform based on SOA architecture in cigarette 
enterprises, through the research on SOA architecture 
and ESB technology, combined with the analysis of the 
actual problems of information integration in cigarette 
manufacturing enterprises, this paper puts forward the 
design scheme of the enterprise application integration 
platform that adapts to the actual situation of 
enterprises. 
II. THE CURRENT SITUATION  
Tobacco industry is an industry with an early start 
of information construction in China. At present, the 
level of information is generally high. BJ cigarette 
factory, as the main cigarette manufacturing enterprise 
in Shaanxi Province, has many application systems 
after years of information construction, covering all 
aspects of the factory from production to management. 
The main information systems include manufacturing 
execution (MES) system and enterprise Industrial 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
16 
resource planning (ERP) system, logistics system, data 
acquisition system in the car room, centralized control 
system in the silk making workshop, power and energy 
management system, human resource management 
system, enterprise card system, etc. 
The more application systems there are, the problem 
is not only the disunity of basic data, but also the 
complexity of system integration. The traditional 
integration method generally adopts the point-to-point 
mode. Each system needs a special channel to integrate 
Chengdu. As shown in Figure 1, the integration of N 
application systems will generate N * (n-1) integration 
channels with high complexity. When new application 
systems need to be integrated, the complexity 
improvement will also be exponential. 
 
Figure 1. Integration complexity 
In summary, the current informatization problems 
of BJ cigarette factory mainly include the following 
aspects: 
1) There are some isolated information islands and 
some application systems are in information closed 
state due to lack of external integration means. 
2) The basic data in the enterprise is scattered in 
different application systems, which need to be 
maintained separately, so it is difficult to ensure the 
unity of the basic data of the whole enterprise, so as to 
"count out one place". The lack of a unified basic data 
code system makes information interaction difficult. 
3) Basic data depends on business system and has 
high coupling. At present, the basic data in the 
enterprise mainly depends on ERP system, and the 
purpose of the basic data is to provide the most basic 
data information for all application systems of the 
whole enterprise, so relying on a single application 
system will cause unnecessary impact on the users of 
other basic data. 
4) Poor integration scalability. At present, the 
information system of the whole enterprise adopts the 
point-to-point integration mode. If the new application 
system wants to join the integration system, it needs the 
cooperation of each application system. The upgrading 
or transformation of the existing application system 
also needs to involve a lot of external interface changes, 
because of this poor scalability. 
5) The lack of management and monitoring of data 
interaction process makes it difficult to find and deal 
with problems in the process of data interaction in time. 
Some data have high requirements for timeliness. If it 
can not be communicated in time, it will have a 
significant impact on the actual business. Therefore, 
effective management and monitoring measures are 
needed for the data interaction process. 
6) The integration of point-to-point results in the 
aggravation of network burden, and many data 
interaction contents are repeated, but the data can not 
be reused, resulting in the waste of resources. 
Through the analysis and optimization of the 
current problems of the enterprise, the core of which is 
to establish a reasonable and efficient way of 
information integration. In recent years, with the 
continuous development of information integration 
technology and the formulation of a series of standards 
and specifications, a new solution is gradually being 
paid attention to, which is based on service oriented 
architecture the enterprise application integration (EAI) 
of Architecture (SOA) regards each application system 
in the enterprise as the service unit of SOA architecture, 
and establishes the enterprise application integration 
platform to realize the information integration between 
each application system. In this enterprise application 
integration platform, an enterprise service bus (ESB) is 
needed to provide standardized services. Enterprise 
service bus is the service operation support platform in 
SOA architecture, and the services encapsulated by 
other application systems run on this service bus, as 
shown in Figure 2, its establishment can effectively 
optimize the current enterprise &apos; s disordered and 
meshed integration mode. Secondly, we need to 
establish a data exchange management platform to 
manage all services running in the enterprise service 
bus and monitor the data interaction process in the 
integration. Finally, we need to establish a basic data 
management platform, as a service provider in the SOA 
architecture, to provide basic data management 
functions for other application systems. The basic data 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
17 
management platform will integrate the basic data of 
other application systems and manage them uniformly. 
Other systems do not need to be managed separately. 
 
Figure 2. Schematic diagram of optimized enterprise integration channel 
III. DESIGN AND  IMPLEMENTATION 
Because IBM WMB is used as the enterprise 
service bus, IBM DB2 will be used as the database and 
IBM was (WebSphere Application Server) will be used 
as the application server for better overall stability. 
According to the demand analysis, the data 
exchange platform as the enterprise service bus will 
provide a unified entry service WS? MB. After other 
application systems call the service, the ESB will parse 
and route the called messages, and find the 
corresponding registered business processing 
WebService to call. 
The data exchange management platform is 
responsible for the management and monitoring of 
IBM WMB enterprise service bus. In the data exchange 
management platform, it is necessary to register, 
modify, disable, reuse and other management functions 
for the service processing business. At the same time, 
the data exchange management platform should also 
realize the log recording of data sending, so as to 
complete the monitoring of data exchange process. 
 
Figure 3. Technical framework of the platform 
IV. DESIGN OF ENTERPRISE SERVICE BUS DATE 
EXCHANGE PLATFORM 
As the core module of enterprise application 
integration platform, data exchange platform needs to 
undertake the important work of message transmission. 
As shown in Figure 4, it is a basic data exchange 
process. The data exchange platform publishes a 
unified entry service WS? MB through the web service. 
The service caller calls the service first, and sends the 
call request to the data exchange platform in the form 
of XML message. The data exchange platform will 
analyze the message content, find the actual service to 
call, and send the message to the actual, the actual 
service provider will return the processed results to the 
data exchange platform in the form of XML message, 
and then the data exchange platform will return to the 
original caller. 
 
Figure 4. Flow chart of data exchange 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
18 
Finally, complete content and organizational editing 
before formatting. Please take note of the following 
items when proofreading spelling and grammar: 
A. Abbreviations and Acronyms 
Define abbreviations and acronyms the first time 
they are used in the text, even after they have been 
defined in the abstract. Abbreviations such as IEEE, SI, 
MKS, CGS, sc, dc, and rms do not have to be defined. 
Do not use abbreviations in the title or heads unless 
they are unavoidable the request message sent by the 
service caller should contain complete routing 
information, so how to define the routing information? 
In fact, from the process of data exchange, it can be 
seen that the three elements of data sender, data 
receiver and the service to be called can constitute a 
unique data process, so the routing information should 
also contain three elements. 
Unified format definition of service call request 
XML message: 
<?xml version="1.0" encoding="GB2312"?> 
<Msg> 
<Head> 
< ID > < ID > / / message ID or serial number 
< name > < name > / / message description 
< source > < source > / / data source 
< target > < target > / / data destination 
< sername > < / sername > / / call service ID 
< msgtype > < / msgtype > / / type of message (0: 
normal 1: request 2: answer) 
< rtcode > < / rtcode > / / the return value of the 
corresponding request (1: success 0: failure) 
< rtdesc > < / rtdesc > / / return description of the 
corresponding request 
< backup1 > < backup1 > / / standby information 
<Backup2></Backup2> 
<Backup3></Backup3> 
< date > XXXX / XX / XX XX: XX: XX < / date > 
/ / message sending time 
</Head> 
<DATA> 
<table tablename = &apos;table name 1&apos; 
fieldname1 = &apos;column 1 description&apos; 
fieldname2 = &apos;column 2 description&apos; 
fieldname3 = &apos;column 3 description&apos;... > 
<row action = insert &apos;id = &apos; primary 
key value &apos;fieldname1 = &apos; AAA &apos; 
fieldname2 = &apos; BBB &apos;... > 
<table tablename = &apos; table name 2&apos; 
fieldname1 = &apos; column 1 description&apos; 
fieldname2 = &apos; column 2 description&apos; 
fieldname3 = &apos; column 3 description&apos;... > 
<ROW ACTION = &apos;INSERT&apos; ID = 
&apos;&apos; FIELDNAME1 = &apos;AAA&apos; 
FIELDNAME2=&apos;BBB&apos; .../> 
</ROW> 
</TABLE> 
</ROW> 
< / Table > / / the main body of the data sent. Table 
represents a data table. Row is the specific data. Table 
can be nested in table to represent the data of the main 
sub table structure. 
</DATA> 
</Msg> 
In the XML definition, the head part describes the 
basic information of the data, and the three attributes of 
source, target and sername are the most important 
routing information. Through these three attributes, you 
can uniquely determine the service that the data needs 
to call, that is, the user of the service, the provider of 
the service and the name of the service. These 
attributes are registered by the service management 
module and are in the unified portal after receiving the 
XML data, the service calls the corresponding service 
according to the three attributes and the service 
registration information in the management module to 
send the data. 
V. IMPLEMENTATION  
The main functions of data exchange management 
platform are service management and data exchange 
process monitoring. As shown in Figure 5, it is the 
main interface of the data exchange management 
platform. The frequency of data exchange can be 
calculated through the log, and the reception and 
transmission volume of each system and data accessing 
the platform can be displayed intuitively. 
 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
19 
 
Figure 5. Main interface of data exchange management platform 
 
a) The function of service governance is realized 
by registering and managing the web service published 
by each application system. As shown in Figure 6, the 
contents to be registered include: sequence number, 
system name, interface name, enabling tag, source, 
target, interface service name and WebServiceURL, 
namespace, calling method input object, input 
parameter name, output parameter name, calling 
method output object, extended input parameter, 
extended input parameter value, authentication 
information, WebService technology, remarks, etc. 
(due to confidentiality reasons, the figure is not 
complete). 
b) Figure 7 is the implementation interface of the 
authority management function of the management 
platform for basic data. The maintenance of basic data 
is usually carried out by the personnel in charge of 
specific business. Different business personnel are 
usually responsible for different data. The authority 
management module can configure the addition, 
modification, deletion and query authority of various 
basic data according to different roles, and can also 
configure whether specific attributes are visible The 
RBAC mode is implemented. 
 
 
 
Figure 6. Data operation module 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
20 
First, configure different roles in role management, 
then configure the permissions of roles through role 
and function relationship, and finally configure the 
roles of different users through role and user 
relationship or user and role relationship. A user can 
have multiple roles, and a role can be played by 
multiple users at the same time. 
Figure 8 is the implementation of the data 
synchronization module of the basic data management 
platform. By customizing the interface content and 
configuring different sending interfaces for different 
systems, you can configure whether the attribute 
column of the basic data is sent, the name of the sent 
column, etc., and you can also filter and group the sent 
content through SQL statements. 
 
Figure 7. Authority management 
 
 
Figure 8. Definition of interface service 
Other application systems publish and register the 
service of receiving basic data in the data exchange 
management platform. After the basic data 
management platform configures the interface, when 
the new basic data maintenance is completed, the 
platform will automatically send the data to the 
corresponding system through the data exchange 
platform according to the interface configuration. All 
application systems adopt this mode, and the basic data 
is unified. 
International Journal of Advanced Network, Monitoring and Controls      Volume 05, No.01, 2020 
21 
VI. CONCLUSION  
In this paper, through understanding the application 
status of SOA architecture in BJ cigarette enterprise, 
the enterprise integrated information system based on 
SOA architecture is proposed to solve the problems of 
the enterprise&apos;s current information island, high 
coupling between various systems, and poor integration 
and expansion. The basic data management platform 
manages and synchronizes the basic data of the whole 
enterprise in a centralized way, so as to solve the 
integration problem of application systems caused by 
the data inconsistency. 
 
REFERENCES 
[1] Li Zi, Yang Bin. Application of Enterprise Service Bus Technology 
(ESB) in large enterprises [J]. Information technology, 2013, 2:146-
147. 
[2] Lu Hongwei. Enterprise application integration solution based on 
SOA and ESB [J]. Computer application and software, 2010, 4:215-
216. 
[3] Chen Lingping. Design and implementation of unified application 
service interface platform based on SOA [J]. Network security 
technology and application, 2009, 4:89K. Elissa, “Title of paper if 
known,” unpublished. 
[4] Jin Baohua, he Zhenyuan, Zhang Liang, et al. Analysis and design of 
data sharing and exchange platform based on SOA [J]. Journal of 
Zhengzhou Institute of light industry (NATURAL SCIENCE 
EDITION), 2011, 2:102-103. 
[5] Du Wanya. Design and implementation of SOA framework based on 
ESB [D]. Beijing: Beijing Jiaotong University, 2008. 
[6] Zhang Jun. research and implementation of distributed ESB bus based on 
SOA Architecture [D]. Nanjing: Nanjing University of technology, 2009. 
[7] Wang Li, ye Weiquan. Planning and design of Anyan tobacco data 
center based on SOA Architecture [J]. Computer knowledge and 
technology, 2013, 1:476-478. 
[8] Electronic Publication: Digital Object Identifiers (DOIs): 
[9] Lin Yuqin, Huang Chenhui. Research on ESB framework for 
enterprise application integration [J]. Computer application, 2010, 
6:1658-1660. 
[10] Ma Ruijuan, he Lili. Research on data exchange service system of 
tobacco industry based on ESB [J]. Computer programming skills and 
maintenance, 2013, 6:33-35. 
 


Research on Enterprise Application Integration Platform Based on SOA Architecture

Schapkin, Sergei A.

Raggatz, Jonas

Hillmert, Markus

Böckelmann, Irina

EEG correlates of cognitive load in a multiple choice reaction task

HAMIDA, Mohammad B.

HASSANAIN, Mohammad A.

POST OCCUPANCY EVALUATION OF ADAPTIVELY REUSED BUILDINGS: CASE STUDY OF AN OFFICE BUILDING IN SAUDI ARABIA

Weinstock, C.

Anliker, M.

von Zabern, I.

An update on the CD59 blood group system

Combs, M.R.

An update on the Lewis blood group system

Thornton, N.M.

Grimsley, S.P.

PROCEEDINGS FROM THE INTERNATIONAL SOCIETY OF BLOOD TRANSFUSION WORKING PARTY ON IMMUNOHAEMATOLOGY, WORKSHOP ON THE CLINICAL SIGNIFICANCE OF RED BLOOD CELL ALLOANTIBODIES, SEPTEMBER 9, 2016, DUBAI: Clinical significance of antibodies to antigens in the ABO, MNS, P1PK, Rh, Lutheran, Kell, Lewis, Duffy, Kidd, Diego, Yt, and Xg blood group systems

Peyrard, T.

Workshop on the clinical significance of red blood cell alloantibodies organized by the Working Party on Immunohaematology of the International Society of Blood Transfusion

Bowman, K.L.

Dunlap, B.C.

Hawthorne, L.M.

Billingsley, K.L.

116 IMMUNOHEMATOLOGY, Volume 35, Number 3, 2019
Most antibodies to blood group antigens react optimally at 
a pH range of 6.5–7.5, similar to that of normal plasma or 
serum. Some antibodies, however, including anti-M, react 
preferentially or exclusively in an acidic environment with a pH 
below 6.5. Antibodies with anti-M specificity often show dosage. 
They can be weakly reactive and even look like nonspecific 
reactivity at the antihuman globulin phase especially when 
immediate spin and/or room temperature testing is not part of 
routine screening. Acidification of serum or plasma may help to 
identify these antibodies as clinically insignificant versus as an 
unidentified antibody for which clinical significance is unknown. 
Immunohematology 2019;35:116–118.
Key Words: Acidification, pH enhanced, antibody detection, 
anti-M
Principle
The MNS blood group system antigens are structurally 
similar polypeptides that transverse the cell membrane once 
with a carboxyl cytoplasmic region and an extracellular 
amino terminal domain.1,2 The extracellular domain of both 
molecules has many sialic acid–rich O-glycans. The majority 
of these O-linked carbohydrate structures are branched 
tetrasaccharides containing one N-acetylgalactosamine 
(GalNAc), one galactose (Gal), and two NeuNAc (sialic acid).3 
The culmination of the carboxyl group charges of these sialic 
acids results in a negatively charged red blood cell (RBC) 
membrane.4 The pH dependency or enhancement of some 
antibodies with M specificity may be due to the charged 
carboxyl groups present on the glycophorin A that carry the 
M antigen.5
The first naturally occurring pH-dependent anti-M was 
discovered in 1964 when a saline agglutinin was present in a 
donor’s acid citrate dextrose plasma that was not demonstrable 
in the serum from the same donation. After screening more 
than 1000 random NN donors, Kathryn M. Beattie and 
Wolf W. Zuelzer found an additional 23 examples of this pH-
dependent anti-M. The data presented by Beattie and Zuelzer 
support the hypothesis that the acidification of the serum, and 
therefore the addition of hydrogen ions, activates or enhances 
the charge of the antibody molecule facilitating agglutination. 
Subsequent alkalization and a decrease in hydrogen ions result 
in the reduction of the antibody charge and the disassociation 
of the antigen–antibody complex.6
Indications
Most antibodies to blood group antigens react optimally 
at a pH range of 6.5–7.5, similar to that of normal plasma 
Acidification of plasma for detection of pH-
dependent antibodies
K.L. Bowman, B.C. Dunlap, L.M. Hawthorne, and K.L. Billingsley
S
E
R
O
L
O
G
IC
 M
E
T
H
O
D
 R
E
V
IE
W
Reagents/Supplies
Reagents Supplies
• Plasma or serum containing 
antibody of interest
• 0.2 N HCL (1.0 N HCL diluted 
with distilled H2O)
• Isotonic saline
• Reagent RBCs
• Anti-IgG (optional)
• IgG–coated RBCs (optional)
• Test tubes
• pH meter or pH strips
• Transfer pipettes
• Centrifuge
• Cell washer
• Agglutination viewer
• Microscope
• 37°C incubator or water bath
• 4°C refrigerator or ice bath
HCL = hydrochloric acid; RBCs = red blood cells.
Procedural Steps
1. Mix one volume of 0.2 N HCL with nine volumes of plasma (or 
serum) for each sample to be tested.
2. Verify that the pH of each sample is between 6.0 and 6.5 with a 
pH meter or pH paper.
3. Select RBCs for testing; wash RBCs at least one time with 
isotonic saline.  
4. Prepare a 3–4 percent RBC suspension in isotonic saline.
5. Add one drop of prepared RBCs to two drops of plasma to a 
properly labeled test tube.
6. Incubate for a time and temperature of interest.
7. Centrifuge for 15 seconds at 3400 rpm (or as otherwise 
indicated).
8. Examine tube for agglutination.
9. Indirect antiglobulin testing (IAT) may be included, if desired, 
using standard methods.
HCL = hydrochloric acid; RBCs = red blood cells;  
PBS = phosphate-buffered saline.
IMMUNOHEMATOLOGY, Volume 35, Number 3, 2019 117
Plasma acidification for antibody identification
or serum. Yet some antibodies, including anti-M, react 
preferentially or exclusively in an acidic pH below 6.5. Anti-M 
is generally considered insignificant and not causative of 
decreased RBC survival or hemolytic disease of the fetus 
and newborn (HDFN).2 However, 50–80 percent of these 
antibodies are IgG or have an IgG component that is capable of 
direct agglutination.7,8 Antibodies reactive at 37°C and/or the 
antihuman globulin (AHG) phase may be IgM, IgG, or both 
and should be considered clinically significant unless testing 
to confirm significance is performed. Although rare, anti-M 
has the potential to cause HDFN if present in maternal plasma 
as IgG.9
Limitations
The acidification of plasma (or serum) to detect pH-
dependent antibodies should only be used in conjunction with 
approved routine blood bank methods and procedures for 
the screening and/or identification of RBC antibodies. This 
procedure is designed to enhance or detect pH-dependent 
antibodies and serves only as one of many tools to aid in 
resolution of routine and/or complex serologic problems.
As with all serologic procedures, failure to obtain the 
correct or expected results may be caused by contamination 
or improper use and storage of reagents. In addition, failure 
to follow the procedure, the use of incorrect incubation 
temperature or time, improper centrifugation time or rpm, 
and failure to add samples or reagents will all result in invalid 
results. Specific limitations for this procedure include failure 
to use the proper concentration of hydrochloric acid (0.2 N 
HCL), improper washing of test RBCs, not adjusting the pH 
of the test samples properly, and the resuspension of RBCs in 
phosphate-buffered saline (PBS) rather than isotonic saline. 
Note: PBS can buffer the acidified plasma and should not be 
used. 
Quality Control
Routine blood bank daily quality control should be followed 
depending on the type of testing for which the acidified plasma 
will be used. The RBCs used for testing should be confirmed to 
be M+N– and M+N+, if testing for dosage. An M– RBC should 
be considered if reactivity is present in all samples. The pH of 
the acidified plasma should be checked with a pH meter or pH 
paper (litmus paper) and should be between 6.0 and 6.5.
Summary/Conclusions
Antibodies with M specificity often show dosage. In 
addition, they can be weak and look like nonspecific reactivity 
at the AHG phase, especially when immediate spin or room 
temperature testing is not part of routine antibody detection 
or identification. Anti-M is usually clinically insignificant if 
reactivity is confined to low temperatures and not present at 
37°C or at the AHG phase. However, identifying an anti-M 
reacting only at cooler temperatures may be important for 
patients undergoing procedures that induce hypothermia, 
including some cardiac surgeries. Additionally, identifying 
weak examples of anti-M, even those typically considered 
insignificant, might be beneficial for patients in sickle cell 
crisis who have a history of hyperhemolysis.5 In these cases, 
it may be desired to provide M– RBC units to prevent further 
immunization or exacerbation of hemolysis.
Acidification of plasma to detect pH-dependent antibodies 
seems to be used to detect naturally occurring cold-reacting 
pH-dependent M antibodies. Still, for some transfusion-
dependent known antibody producers susceptible to hemolytic 
transfusion reactions, this procedure and the identification of 
these weak latent antibodies may be beneficial.
Like anti-M, anti-i present in cold hemagglutinin disease10 
and anti-Pr can show pH dependency3,5 but are more likely to 
be clinically significant. Other antibodies usually considered 
clinically significant have also been reported, including anti-s2 
and anti-f.11 Acidification of serum may aid in identification of 
these antibodies. The pH dependency of some antibodies may 
explain discrepant reactivity sometimes seen between fresh 
plasma and serum samples from the same patient or between 
antibody detection reagents. Little research has been done 
to determine the clinical significance of these pH-dependent 
antibodies and, because this procedure is rarely used, it is 
difficult to say how many pH-dependent antibodies remain 
undiscovered.
References
 1. Daniels G. Human blood groups. 3rd ed. West Sussex, UK: 
Wiley-Blackwell, 2013:96–157.
 2. Reid ME, Lomas-Francis C, Olsson ML. The blood group 
antigen factsbook. 3rd ed. London, UK: Academic Press, 
2012:53–74.
118 IMMUNOHEMATOLOGY, Volume 35, Number 3, 2019
K.L. Bowman et al.
 3. Harmening DM. Modern blood banking and transfusion 
practices. 6th ed. Philadelphia, PA: F.A. Davis Company, 
2012:185–91.
 4. Daniels G. Functional aspects of red cell antigens. Blood Rev 
1999;13:14–35.
 5. Judd WJ, Johnson ST, Storry JR. Judd’s methods in 
immunohematology. 3rd ed. Bethesda, MD: AABB, 2008: 
314–5.
 6. Beattie KM, Zuelzer WW. The frequency and properties of pH-
dependent anti-M. Transfusion 1965;5:322–6.
 7. Smith ML, Beck ML. The immunoglobulin structure of human 
anti-M agglutinins. Transfusion 1979;19:472–4.
 8. Issitt PD, Anstee DJ. Applied blood group serology. 4th ed. 
Durham, NC: Montgomery Scientific, 1998.
 9. Arora S, Doda V, Maria A, Kotwal U, Goyal S. Maternal anti-M 
induced hemolytic disease of newborn followed by prolonged 
anemia in newborn twins. Asian J Transfus Sci 2015;9: 
98–101.
 10. Joshi SR, Naik RA, Gupte SC. Unusual spontaneous cold 
auto-hemagglutination phenomenon in blood units stored 
under blood bank condition: a retrospective analysis. Asian J 
Transfus Sci 2015;9:141–4.
 11. Lucia SP, Wild GM, Hunt ML. Anti-f sensitization detected by 
an acidified indirect Coombs test. Vox Sang 1960;5:77.
Kelly L. Bowman, MT(ASCP)SBBCM, Immunohematology Technologist 
III; Brett C. Dunlap, MS, MLS(ASCP), Immunohematology 
Technologist II; Linda M. Hawthorne, MHS, MT(ASCP)SBB, 
Immunohematology Technologist II; and Katrina L. Billingsley, 
MSTM, MT(ASCP)SBBCM, Director (corresponding author), Scientific 
Services, LifeShare Blood Center, 8910 Linwood Avenue, Shreveport, 
LA 71106, katrina.billingsley@lifeshare.org.
Attention:  
State Blood Bank Meeting Organizers
If you are planning a state meeting and would like copies of 
Immunohematology for distribution, please send a request, 
4 months in advance, to immuno@redcross.org.
Notice to Readers
All articles published, including communications and  
book reviews, reflect the opinions of the authors and do 
not necessarily reflect the official policy of the American 
Red Cross.


Not a member yet

Bacterial Diversity in Roots, Stems, and Leaves of Chinese Medicinal Plant Paris polyphylla var. yunnanensis

Research on Enterprise Application Integration Platform Based on SOA Architecture

EEG correlates of cognitive load in a multiple choice reaction task

POST OCCUPANCY EVALUATION OF ADAPTIVELY REUSED BUILDINGS: CASE STUDY OF AN OFFICE BUILDING IN SAUDI ARABIA

An update on the CD59 blood group system

An update on the Lewis blood group system

Workshop on the clinical significance of red blood cell alloantibodies organized by the Working Party on Immunohaematology of the International Society of Blood Transfusion

Acidification of plasma for detection of pH-dependent antibodies

Application of PCR for Specific Diagnosis of Leptospirosis in Humans in Ukraine

4,746

6,096