Setting up Reference Ranges on a Care Plan
| Info |
|---|
NOTE: THIS SECTION IS STILL UNDER CONSTRUCTION. |
Process for Closing an Episode Of Care
An EpisodeOfCare provides context for and is referenced from a potentially large number of resources of differing type, including CarePlan, Observation and Task to name a few. This function as context is not affected by the lifecycle of the EpisodeOfCare. There are some resources with a lifecycle somewhat linked to that of the EpisodeOfCare, such as the zero, one or more CarePlan and associated one or more ProcedureRequest.
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The description in the following accounts for a technical view on closing an EpisodeOfCare. The description does not encompass the business process for terminating an episode of care which would, presumably, also include handling of outstanding tasks and communication, evaluation of submitted measurements, reclaiming of devices, and such.
It is reasonable to suggest a natural order of lifecycle that could help the clinicians keep an overview of the general status of a Patient. This natural order would include that the EpisodeOfCare should have status active before associated CarePlan can become active and vice-versa that CarePlan should have status other than draft and active before an EpisodeOfCare can have status finished. The service providing operations for creating and maintaining EpisodeOfCare, CarePlan and ProcedureRequest does not depend on nor enforce any specific order when closing an EpisodeOfCare. Such dependency, however, exists for the following automated processing functionality of the Infrastructure:
patient reminders - a periodic check of all active CarePlan and ProcedureRequest to determine whether a reminder for submitting measurements should be sent to the Patient
overdue measurement submits - a periodic check of all active CarePlan and ProcedureRequest whether measurements have been submitted.
These checks do not involve the EpsidoeOfCare status.
Therefore, the process of closing an EpisodeOfCare is:
Close all ProcedureRequest belonging to a CarePlan before closing the CarePlan
Close all sub-plans of a CarePlan before closing the parent CarePlan
Close all CarePlan belonging to an EpisodeOfCare before closing the EpisodeOfCare
...
| Child pages (Children Display) |
|---|
...
Filtering included resources when searching
Note: This functionality is available from release 6.1 when including referenced ClinicalImpressions in a Task search. It may later be extended to other resource types
For the primary resource, it is possible to verify search parameters against security token before performing the actual search against the database. This ensures that the user is allowed access to all resources found by the search.
However, this cannot be determined if the search includes referenced resources. In that case access is checked for each included resource just before a page of search results are returned to the client. If any security violations are found, then an error is returned to the client.
This behavior is changed to a filtering mechanism instead. Any included resources that the user is not allowed to access will be removed from the search result, but the remaining resources will be returned to the client.
To indicate that some resources were filtered, an OperationOutcome will be added to the search result.
...
OperationOutcome.issue.severity: warning
...
OperationOutcome.issue.code: suppressed
...