> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/h/healthcare-episode.md). # healthcare episode ## healthcare episode A grouping of one or more healthcare encounters, in which a subject of care receives health care services for one or more health problems or disorders from a healthcare provider. #### Notes * A *healthcare episode* may be part of another *healthcare episode.* For example, a *healthcare episode* may include several outpatient encounters and one or more inpatient episodes. * This general definition applies to SNOMED International documentation but it should be interpreted taking account of more specific national or organizational definitions of *healthcare episode.* This is particularly important as these definitions may have specific legal or financial implications. ## Alternatives * **episode of care** Provide Feedback --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/h/healthcare-episode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.