Obligation Discussion
0.2.0 - Working Draft to present the Concept Ideas and Background Details (FO)
Obligation Discussion
0.2.0 - Working Draft to present the Concept Ideas and Background Details (FO)
Obligation Discussion - Local Development build (v0.2.0) 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.
Alpha Group
| A) Base Patient Profile |
Base Patient Profile that combines the requirements |
| A) Profile Sender Profile |
This profile only includes the obligation extension for a sender. |
| Obligation1Definition |
Obligation 1 Definition Description: is to be placed behind the actor: profile 0..* <- 1 actor 0..* <-> 0..* obligation |
Beta Group
| Obligation2Definition |
Obligation 2 Definition Description: is to be placed before the actor - profile 0..* <- 1 obligation 1..* <- 1 actor |
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| my other own Actor Definition2 |
my own Actor Definition2 to test characteristics |
| my own Actor Definition 1 |
my own Actor Definition 1 This puts the actor in the middle, and points to obligations |
| my own Actor Definition 2 |
my own Actor Definition 2 This puts the obligation into the middle, and takes pointers from actors. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| A) Profile Receiver Obligation Profile |
This profile includes the obligation extension to the receiver. |
| A) Profile Receiver Profile |
This profile only includes the obligation extension for a receiver. |
| A) Profile Sender Obligation Profile |
This profile includes the obligation extension to the sender. |
| B) Super Patient Profile |
super profile that combines all requirements |
| Patient (Obligation Test) |
This profile represents the constraints applied to the Patient resource to test obligation extensions |
These define sets of codes used by systems conforming to this implementation guide.
| Data Expectation ValueSet |
Valueset for data expectations |
| Obligation ValueSet |
Valueset for obligations |
| Verb ValueSet |
Conformance verbs ValueSet |
These define new code systems used by systems conforming to this implementation guide.
| Data Expectation Codes |
Data Expectation CodeSystem |
| Obligation Codes |
Obligation CodeSystem Remarks: *in-narrative: does not make sense, should be added to the text element directly *must-explain: belongs to the specification of the application, not sure whether it should be added here *ignore: is a negative expression = ‘not’ |
| Verb Codes |
verb CodeSystem |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| A) Patient 2 Example |
This patient instance is used to demonstrate how obligation extensions are used |
| Actor 1: Receiver |
This actor is used to demonstrate receiving capabilities |
| Actor 1: Sender | |
| Actor 1: Test | |
| Actor 2: Receiver |
This actor is used to demonstrate receiving capabilities |
| Actor 2: Sender | |
| Actor 2: Test | |
| Actor a: Sender Test | |
| Actor b: Receiver Test |
This actor is used to demonstrate receiving capabilities |
| Actor c: Test (unused) | |
| B) Patient B 1 |
Simple Instance |
| Obligation 1a: send exactly | |
| Obligation 1b: store equivalent | |
| Obligation 1c: store exactly | |
| Obligation 2a: send exactly | |
| Obligation 2b: store equivalent | |
| Obligation 2c: store exactly |