Vanna Health IG
0.0.2 - ci-build
Vanna Health IG
0.0.2 - ci-build
Vanna Health IG - Local Development build (v0.0.2) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| VannaBundle |
A generic list of resources used for sending data to/from an API. (Not a DomainResource) |
| VannaCareTeam |
Used for Individual Care Teams for assigning Staff to a Member. |
| VannaClinicalImpression |
Used for clinical summary, clinical notes, and clinical one liner. |
| VannaCommunication |
A message or alert. Used for Team Meeting Notes. |
| VannaFlag |
Used for Must Knows to a indicate warning of potential issues when providing care to a Vanna Member. |
| VannaOrganization |
Used for both Client and Center level Vanna organizations. |
| VannaPatient |
The Vanna Member a.k.a. Patient resource. |
| VannaPractitioner |
A Vanna staff member that delivers care services to Members. |
| VannaPractitionerRole |
Used to document functional roles of Practitioners and assign/link them to other resources such as CareTeams. |
| VannaProblemList |
A FHIR Condition Resource that inherits from the US Core Problem List or Health Concern Condition Profile. This resource is intended to be used for storing the list of Conditions that we are actively managing with our Members. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Vanna Description Extension |
Extension for adding a description field to various elements such as address and telecom. |
These define sets of codes used by systems conforming to this implementation guide.
| Vanna Communication Category ValueSet |
Expansion of CommunicationCategory to include Team Meeting, Must Know, etc. |
| Vanna Communication Category ValueSet |
Expansion of OrganizationType to include Client, Center, etc. |
| Vanna Member Status ValueSet |
The purpose of this value set is to document the custom Member statuses introduced at Vanna like Outreach, Enrolled, etc. |
| Vanna Member Substatus ValueSet |
This value set is currently not used. It exists to substatus slice of meta.tag when sliced by system. |
| Vanna PractitionerRole Code ValueSet |
Expansion of PractitionerRole Code to include Vanna-specific codes |
These define new code systems used by systems conforming to this implementation guide.
| Vanna Communication Category Code System |
A local code system defined within the context of the Vanna IG to hold custom categories referenced by Communication. |
| Vanna Communication Category Code System |
A local code system defined within the context of the Vanna IG to hold custom org types. |
| Vanna Member Status Code System |
A local code system defined within the context of the Vanna IG to hold the custom codes for Member Status. |
| Vanna Practitioner Role Code System |
This code system defines the Vanna Practitioner Role codes. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| CareTeamExample |
An example of a Vanna CareTeam. |
| ClinicalImpressionExample |
clinical_one_liner |
| MustKnowExample |
Example of a Must Know |
| OrganizationExample |
An example using the Philly pilot. |
| PatientExample |
An example of a Vanna Member. |
| PractitionerExample |
An example of a Vanna staff member. |
| TeamMeetingNoteExample |
An example of Team Meeting “Note” (i.e. message). |
| VannaBundleExample |
A typical API response “searchset” bundle containing a single Patient reference. |
| VannaPractitionerRoleExample |
An example of VannaPractitionerRole. |
| VannaProblemListExample |
An example of VannaProblemList Condition. |