[null,null,["最后更新时间 (UTC)：2025-07-26。"],[],[],null,["# Medical Records\n\nThe Health Connect platform provides a [range of data types](/health-and-fitness/guides/health-connect/plan/data-types),\nmostly covering wellness and fitness use cases, enabling apps in the Android\necosystem to share data without the need for high-cost one-to-one\nAPI integrations.\n\nMedical Records extends this capability to include basic medical\ndata in [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/overview.html)\nformat. FHIR is an open-source global specification describing schema and\nsemantics for medical data published by HL7 (Health Level Seven International).\n\nMedical Records on Health Connect features:\n\n- An API for applications writing medical data.\n- A user-facing browser experience for medical data stored in Health Connect as new medical data types, along with fine-grained permissions for allowing downstream reads.\n- An API for applications reading medical data based on user-granted permissions.\n\n**Figure 1.** How Medical Records work with Health Connect.\n\nLimitations\n-----------\n\nAs these APIs are still under development, there are still some limitations and\nsome components aren't fully available.\n\nThe Medical Records APIs are marked with an annotation of\n`ExperimentalPersonalHealthRecordApi`, which indicates that these APIs are still\nunder development and subject to change.\n\nThere are still some limitations and some components aren't fully available:\n\n- The Play Policy for Medical Records access is still being developed, and apps may need to meet additional requirements before they can be released on the Play Store.\n- Some features, such as changelogs-based APIs, have not been developed for Medical Records APIs yet.\n\nGet Started\n-----------\n\nBecause Medical Records is a set of new record types in Health Connect, the\nsame process for getting started with Health Connect applies to Medical Records.\nSee [Get started with Health Connect](/health-and-fitness/guides/health-connect/develop/get-started) for more information.\n\nIf you have been experimenting with the Medical Records Framework APIs that\nwere initially available, we strongly recommend you transition to Jetpack for\nan improved developer experience for the following reasons:\n\n- All guides and sample code are written for Jetpack\n- Ecosystem tools use the Jetpack APIs\n- The API surface is Kotlin native\n- Jetpack has improved compatibility support (such as the [Feature\n Availability API](/health-and-fitness/guides/health-connect/develop/feature-availability))\n\nMedical Records APIs are made available through Health Connect version\n[1.1.0-beta02](/jetpack/androidx/releases/health-connect#1.1.0-beta02) in Jetpack. Updating your Jetpack dependency to\nthis version requires that apps be compiled against the [Android 16\nSDK](/about/versions/16/setup-sdk).\n\nOnce you're set up and ready to write and read Medical Records data in your app,\nsee [Write medical data](/health-and-fitness/guides/medical-records/write-data) and [Read medical data](/health-and-fitness/guides/medical-records/read-data).\n\nUser experience\n---------------\n\nGeneral information about the user experience is provided in this section.\n\n### Permissions\n\nRequesting read or write medical record permissions behaves similarly to the\nexisting Health Connect permissions screens, but a separate\nhealth records screen is shown:\n\n### Data browsing\n\nHealth Connect also provides basic visualization and browsing of Medical Records\ndata stored, similar to existing Health Connect data types."]]
