Adverse Event Clinical Care
0.2.0 - ci-build
Adverse Event Clinical Care
0.2.0 - ci-build
Adverse Event Clinical Care, published by HL7 International - Patient Care Work Group, Vulcan AdverseEvent groups. This is not an authorized publication; it is the continuous build for version 0.2.0). This version is based on the current content of https://github.com/HL7/fhir-ae-care-ig/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/adverseeventclinicalcare/ImplementationGuide/hl7.fhir.uv.adverseeventclinicalcare | Version: 0.2.0 | |||
| IG Standards status: Informative | Maturity Level: 1 | Computable Name: adverseeventclinicalcare | ||
| Page standards status: Informative |
A single Adverse Event may need to be reported in multiple ways. Choosing the appropriate form of the reporting is dependent upon workflow patterns. In particular, the implementation guides for Clinical Care adverse events and Clinical Research adverse events provide important extensions, value-sets and examples for implementing AdverseEvent.
This guide, the Clinical Care adverse event Profile implementation guide, is for the clinical care setting. Implementers should use the profile in this guide as a base profile for more specific clinical use cases.
Within this guide are some examples. Every effort has been made to capture important details of the use of the AdverseEvent profile. However, some examples may provide only a stub to referenced resources (e.g. instances of Patient Resource will be referenced using logical ids but are not resolvable, implementation of Patient is left for other guidance and is not the subject of this guide). Connectathons are ideal opportunities to create, compare and consider the holistic implementation of all FHIR Resources. And, as mentioned the profile in this guide is meant to be a base to build upon. It is expected that further constraints would be used in IGs for more specific use cases or settings (e.g. US Core).
FHIR STU4 contained a non-normative version of the AdverseEvent Resource. The specification here is based on changes made in R5 and supersedes the use of the R4 Resource.
Implementers should use this guide to AdverseEvent Clinical Care communications in an interoperable way. It is understood that this guide is not complete, and implementers might identify additional concepts and data elements. Please review this guidance for ways to handle those use cases. Additionally, it is recommended that additional Implementation Guides should be adapted from this one as a base for tighter specifications.
The Clinical Care Adverse Event Implementation Guide is a product of the HL7 Patient Care Work Group. Questions or comments regarding this implementation guide should be directed to Patient Care at patientcare@lists.hl7.org.
The authors of this guide wish to recognize the following participants who contributed their time and expertise to the continued development of this guide: