PHR Profiling System Based on FHIR

KIPS Transactions on Software and Data Engineering, Vol. 4, No. 7, pp. 277-282, Jul. 2015
10.3745/KTSDE.2015.4.7.277, Full Text:


HL7 released V3 CDA(Clinical Document Architecture) and V2.x message standards for medical information exchange. Currently, these standards are successfully adopted by a number of nations across the globe. However, substantial amount of time is required to develop and implement these standards. Moreover, developers need a lot of time to understand these standards. To solve these issues from 2011, the HL7 standard framework started to discuss Fast Healthcare Interoperability Resources(FHIR) as next generation standard of healthcare information exchange. People’s interests toward personal health record and smartphone penetration rate are growing and increasing rapidly. Therefore, our research team believes it is necessary to develop a PHR profiling system which could be accessed by using a smartphone and we developed the system. Through a FHIR Profile editor tool developed in Furore, we found that improvements could be made in generating and changing the profile. In order to build the PHR Profiling system, an Open-API on FHIR is used for exchanging information between electronic medical record system and PHR Profiling system. In the PHR Profiling system, the transactions of information between two systems are provided by RESTful service. In this study, we verify the efficiency of development of the PHR Profiling system through FHIR.

Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.

Cite this article
[IEEE Style]
Y. S. Kim and I. K. Kim, "PHR Profiling System Based on FHIR," KIPS Transactions on Software and Data Engineering, vol. 4, no. 7, pp. 277-282, 2015. DOI: 10.3745/KTSDE.2015.4.7.277.

[ACM Style]
Young Sik Kim and Il Kon Kim. 2015. PHR Profiling System Based on FHIR. KIPS Transactions on Software and Data Engineering, 4, 7, (2015), 277-282. DOI: 10.3745/KTSDE.2015.4.7.277.