Learning from development of a third-party patient-oriented application using Australian national personal health records system
Niranjan Bidargaddi

TL;DR
This paper analyzes the development process and regulatory considerations for creating a third-party patient-oriented application using Australia's national personal health record system, My Health Record.
Contribution
It provides insights into the development processes and regulatory requirements for third-party applications leveraging national health record data.
Findings
Identified key regulatory requirements for app development
Outlined processes for integrating with My Health Record
Demonstrated implementation of a patient-oriented application
Abstract
Large-scale national level Personal Health Record (PHR) has been implemented in Australia. However, usability, data quality and poor functionalities have resulted in low utility affecting enrollment and participation rates by both patients and clinicians alike. Development of new applications deriving secondary utility of data can enhance use of PHRs but there is limited understanding on processes involved in development of third-party applications with nationally run PHRs. This paper prsents an analysis of processes and regulatory requirements for developing applications of data from My Health Record, Australian nationally run PHR and subsequently implementation of a patient oriented software application using data sourced from My Health Record.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsElectronic Health Records Systems · Clinical practice guidelines implementation · Biomedical Text Mining and Ontologies
