ResMed Core Implementation Guide
0.37.0 - ci-build
ResMed Core Implementation Guide
0.37.0 - ci-build
ResMed Core Implementation Guide - Local Development build (v0.37.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
The AirView Compliance Engine (ACE) software is modeled as a device. Each software release is a different resource.
Each software version of the AirView Compliance Engine (ACE) is represented by one AirView Compliance Engine Device resource. There should only be one active Device resource at any given time.
The referenced patient’s managing organization. Included as part of the resource so that it can be queried using a patient’s organization.
An organization managing a population of ResMed patients
Provides the organizational context for the client and is related to many of the resources involved in AirView Compliance Engine rules..
The set of known ResMed organization identifiers
Used to relate a resource’s identifier to a known type of identifier used throughout ResMed systems, solutions and applications.
See ResMedOrganizationIdentifierValueSet
A person receiving care from a ResMed product
This patient resource is created in the context of a client. As a consequence, there may be more than one patient resources for the same person for each time the person needs to be represented by different systems.
See ResMedPatient
An overview of the resources that should be in place before creating an ACE Rule Outcome Observation resource
The base profile for all rules engine outcomes as an Observation.
AirView Compliance Engine outcomes are represented as resources and are related to a Service Request and AirView Compliance Engine software version.
Profile for Patient Rule Definitions
Each rule that can be used to enroll a patient for monitoring within the AirView Compliance Engine is represented by one of these resources.
Profile for a Rule Instance that is assigned to a patient.
The Service Request resource represents the patient’s enrollment in an instance of an ACE Rule.
A value set of all non-abstract rule outcome types
Rule outcomes will have a type for this list of type codes.
See ValueSetResMedAllRuleOutcomeTypeCodes
A value set consisting of codes identifying rule outcome component values.
The component codes represent the elements that define each part of an AirView Compliance Engine rule expression. Rules make use of one or more of these components.
See ValueSetResMedRuleOutcomeComponentCodes
A value set consisting of codes identifying rule outcome interpretations.
These codes are used to indicate whether compliant is met/not met, conditions for an alert has been met, etc.
See ValueSetResMedRuleOutcomeInterpretationCodes
ResMed Service Request Type ValueSet
Information to identify the type of rule that is covered by the Service Request.
See ValueSetResMedRulesServiceRequestTypes
An overview of the resources that should be in place before creating an ACE Rule Outcome Observation resource. Note that this diagram also includes the ACE Rule Outcome Observation which is displayed in more detail above.
The set of supported status values for ResMed DetectedIssues
See ResMedDetectedIssueStatusValueSet
Profile of DetectedIssue for recording a therapy alert identified by clinical rule outcome Observations being recorded while monitoring a patient’s therapy.
Applications can subscribe to detected issues so that action can be taken as needed whenever such an event occurs.
See ResMedPatientTherapyDetectedIssue
A value set of all the clincal rule outcome types
This is referenced by a patient therapy detected issue resource to indicate the reason for the alert.
See ValueSetResMedClincalRuleOutcomeTypeCodes
Profile of core Provenance resource used for capturing patient record changes
Patient provenance resources are used to capture events relating to patient resources. Provenance resources can provide a historical record of events that have occurred over time when they are created for each significant event.
Profile for Patient Rule Definitions
Each provenance is the result of an activity whose type is defined by this list.
Detected issue profile for alerts contained in a Provenance resource
The set of supported categories for ResMed DetectedIssues
See ResMedDetectedIssueCodeValueSet
Profile for provenance resource used to track alerts being raised
Profile for provenance resource used to track alert reviews by practitioners
Profile for Provenance resource to track rule changes
TODO
See ResMedProvenanceTemplateChangeIdentifierValueSet
Profile for a patients care plan that keeps track of the template (PlanDefinition) as well as rules currently assigned to the patient.