-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Continuity of Care Summary Composition initialised
- Loading branch information
1 parent
fe075d0
commit 71b1a02
Showing
10 changed files
with
339 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| None. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| #### Australian Digital Health Agency Continuity of Care Summary Composition | ||
| The purpose of this profile is to define a representation of an Continuity of Care Summary Document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile standardises the core, common or critical information for exchange of information between healthcare providers, and individual, to support continuity of care across encounters and healthcare settings. Specific use cases are supported by defined profiles for those use cases such as Shared Health Summary, Event Summary, Discharge Summary, Transfer Summary, Referral; where available the most specific applicable profile should be used. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation. | ||
|
|
||
| This profile identifies the additional constraints, extensions, and value sets that build on and extend [Composition](http://hl7.org/fhir/R4/composition.html) that are supported. | ||
|
|
||
| Where a more specific document composition profile is applicable, e.g. shared health summary, event summary, discharge summary, or transfer summary, an implementation **SHALL** ensure the Resource conforms to that specific profile. | ||
|
|
||
| This profile supports the equivalent of all HL7 CDA conformance levels for a clinical document as defined in the Agency's Common Conformance Profile for Clinical Documents. | ||
|
|
||
| This profile is designed to set a Composition standard for: | ||
| * exchanging a FHIR Continuity of Care Summary Document | ||
| * Query for a Continuity of Care Summary document for a patient | ||
| * Record or update a Continuity of Care Summary document record for a patient | ||
|
|
||
| #### Boundaries and relationships | ||
| The following profiles are specialised use case profiles of a continuity of care summary document: | ||
| * [ADHA Event Summary Composition](StructureDefinition-dh-composition-es-1.html) | ||
| * [ADHA Event Summary Mixed Narrative and Structure](StructureDefinition-dh-composition-es-mix-1.html) | ||
| * [ADHA Event Summary Narrative](StructureDefinition-dh-composition-es-narrative-1.html) | ||
| * [ADHA Shared Health Summary Composition](StructureDefinition-dh-composition-shs-1.html) | ||
| * [ADHA Aged Care Transfer Summary Composition](StructureDefinition-dh-composition-acts-1.html) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| <table class="list" width="100%"> | ||
| <tbody> | ||
| <tr> | ||
| <th>Reference</th> | ||
| <th>Description</th> | ||
| <th>Issue No.</th> | ||
| </tr> | ||
| <tr> | ||
| <td>Constraint presentation</td> | ||
| <td>The full set of constraints (i.e. invariants) defined in this profile are only presented in the Detailed Descriptions tab or the raw representation (e.g. XML) of the profile. The Differential Table only presents constraints introduced in this profile in addition to the constraints present in the base profile and base resource. The Snapshot Table only presents the constraints visible in the Differential Table and additionally presents those constraints set in slices in the base profile.</td> | ||
| <td>See Zulip <a href="https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Derived.20profile.20snapshot.20missing.20upstream.20invariants">Derived profile snapshot missing upstream invariants</a> stream</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| This file is intentionally empty. It is required to be included by the IG Publisher. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.