The Health level seven developed Clinical Document Architecture (CDA) is a core document that supports XML-based mark-up commonplace that is used to specify the structure, linguistics, and encryption of a clinical document like a discharge outline or progress note for the aim of exchange between totally different hospitals. A CDA document is a set of the complete information object that may embody text, images, sound, and alternative transmission content. CDA will hold any reasonably clinical information that enclosed in every patient’s anamnesis like discharge outline following patient’s care history & physical specialist reports like those for medical imaging or pathology. Electronic Health Record helps improve patient safety and quality of care; however, it`s the necessity of interoperability between health data exchange at completely different hospitals. CDA document generation and integration Open API service supported cloud computing, through that hospital`s area allowed to handily generate CDA documents whereas not having to buy proprietary code software. The CDA document integration system integrates multiple CDA documents per patient into one CDA document and doctor and patients can browse the clinical information in chronological order. In this, the CDA document generation and integration depend on cloud computing and so the service is gettable in Open API. Developers using totally different platforms thus can use this system to increase ability. It providing security to the CDA document and unique identity (id) is generated and given to the patients for avoiding the interchanging and duplication of medical reports. Every detail in CDA Document is Encrypted and stored in the Database. All Details in CDA Document is secured utilizing different Security Algorithms

Health Information System (HIS), Infrastructure as a Services, Cloud Computing, Health Level 7 (HL7), Electronic Health Record (EHR).

[1] K. Ashish, “Meaningful use of electronic health records the road ahead,”JAMA, vol. 304, no. 10, pp. 1709–1710, 2010.
[2] J. D. D’Amore, D. F. Sittig, A. Wright, M. S. Iyengar, and R. B. Ness, “The promise of the CCD: Challenges and opportunity for quality improvement and population health,” in Proc. AMIA Annu. Symp. Proc., pp. 285–294, 2011.
[3] M. Armbrust, A. Fox, R. Griffith, A. D. Joseph, R. Katz, A. Konwinski, G. Lee, D. Patterson, A. Rabkin, I. Stoica, and M. Zaharia, “A view of cloud computing,” Commun. ACM, vol. 53, no. 4, pp. 50–58, 2010.
[4] S. Lee, J. Song, and I. Kim, “Clinical document architecture integration system to support patient referral and reply letters,” Health Informat. J., Published online before print Jun. 2014.
[5] S. R. Simon, R. Kaushal, P. D. Cleary, C. A. Jenter, L. A. Volk, E. G. Poon, E. J. Orav, H. G. Lo, D. H. Williams, and D. W. Bates, “Correlates of electronic health record adoption in office practices: A statewide survey,” J. Am. Med. Inform. Assoc., vol. 14, pp. 110–117, 200.
[6] J. L€ahteenm€aki, J. Lepp€anen, and H. Kaijanranta, “Interoperability of personal health records,” in Proc. IEEE 31st Annu. Int. Conf. Eng. Med. Biol. Soc., pp. 1726–1729, 2009.
[7] S. Kikuchi, S. Sachdeva, and S. Bhalla, “Applying cloud computing model in PHR architecture,” in Proc. Joint Int. Conf. Human-Centered Comput. Environments, pp. 236–237, 2012.
[8] M. Eichelberg, T. Aden, J. Riesmeier, A. Dogac, and Laleci, “A survey and analysis of electronic healthcare record standards,” ACM Comput. Surv., vol. 37, no. 4, pp. 277–315, 2005.
[9] C. Martınez-Costa, M. Menarguez-Tortosa, and J. Tomas Fernan-dez-Breis, “An approach for the semantic interoperability of ISO EN 13606 and OpenEHR archetypes,” J. Biomed. Inform., vol. 43, no. 5, pp. 736–746, Oct. 2010.
[10] M. L. Muller,€ F. Ǖckert, and T. Burkle,€ “Cross-institutional data exchange using the clinical document architecture (CDA),” Int. J. Med. Inform., vol. 74, pp. 245–256, 2005.
[11] R. H. Dolin, L. Alschuler, C. Beebe, P. V. Biron, S. L. Boyer, D. Essin, E. Kimber, T. Lincoln, and J. E. Mattison, “The HL7 Clinical Document Architecture,” J. Am. Med. Inform. Assoc., vol. 8,pp. 552–569, 2001.
[12] K. Huang, S. Hsieh, Y. Chang, F. Lai, S. Hsieh, and H. Lee, “Application of portable cda for secure clinical-document exchange,” J. Med. Syst., vol. 34, no. 4, pp. 531–539, 2010.
[13] S. Lee, J. Song, and I. Kim, “Clinical document architecture integration system to support patient referral and reply letters,” Health Informat. J., Published online before print Jun. 2014.
[14] J. Walker, E. Pan, D. Johnston, J. Adler-Milstein, D. W. Bates, and B. .Middleton, “The value of health care information exchange and interoperability,” in Proc. Health Aff., pp. 10–18, 2005.
[15] E. W. Huang, T. L. Tseng, M. L. Chang, M. L. Pan, and D. M. Liou, “Generating standardized clinical documents for medical infor-mation exchanges,” in Proc. IT Pro., pp. 26–32, 2010.
[16] P. C. Tang, J. S. Ash, D. W. Bates, J. M. Overhage, and D. Z. Sands, “Personal health records: Definitions, benefits, and strategies for overcoming barriers to adoption,” J. Am. Med. Inform. Assoc., vol. 13, no. 2, pp. 121–126, 2006.
[17] Y. Kwak, “International standards for building electronic health record (ehr),” in Proc. Enterprise Netw. Comput. Healthcare Ind., 18–23, Jun. 2005.