From 977615a74f1f3aa873f01e80bb4b2bdbb702e959 Mon Sep 17 00:00:00 2001 From: Rob Eastwood Date: Fri, 20 Mar 2020 08:48:45 +1000 Subject: [PATCH 1/3] PDL profile intro pages - updates to first line and headers --- .../_includes/device-dh-base-1-intro.md | 4 ++-- .../_includes/device-ident-1-intro.md | 4 ---- .../_includes/patient-ident-1-intro.md | 2 +- .../_includes/practitioner-ident-1-intro.md | 2 +- .../_includes/provenance-list-gen-1-intro.md | 6 +++--- .../_includes/relatedperson-dh-base-1-intro.md | 2 +- .../_includes/relatedperson-ident-1-intro.md | 2 +- 7 files changed, 9 insertions(+), 13 deletions(-) diff --git a/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md index 11cf7cee1..5f7bbfae8 100644 --- a/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md @@ -1,5 +1,5 @@ -### Base Device *[[Draft](http://hl7.org/fhir/stu3/versions.html#maturity)]* +#### Base Device *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* -##### Implementation guidance +#### Implementation guidance No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. diff --git a/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md index 0a7ff9235..4c16c81f3 100644 --- a/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md @@ -1,9 +1,5 @@ #### Device with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* -#### Usage scenarios - -TBD - #### Implementation guidance No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. diff --git a/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md index 8b3bfabe0..3f19b857c 100644 --- a/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md @@ -1,4 +1,4 @@ -### Patient with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Patient with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. diff --git a/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md index a7a3c97f2..548ed37a3 100644 --- a/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md @@ -1,4 +1,4 @@ -### Practitioner with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Practitioner with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. diff --git a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md index 05b2f0374..e9ed8359d 100644 --- a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md @@ -1,6 +1,6 @@ -### Provenance for the Generation of a List *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Provenance for the Generation of a List *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* -##### Usage scenarios +#### Usage scenarios * A clinical information system (CIS) sends or receives a list with provenance with the My Health Record system * A contracted service provider (CSP) sends or receives a list with provenance with the My Health Record system * A CIS sends or receives a list with provenance with another CIS or CSP @@ -13,7 +13,7 @@ An expected usage scenario, further scoping the above overarching scenarios is: Further scoping of applicable usage scenarios (e.g. point-to-point or point-to-share) is done at the referencing Composition profile. -##### Implementation guidance +#### Implementation guidance For the supported scenarios in this implementation guide: diff --git a/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md index 604302895..c01463bde 100644 --- a/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md @@ -1,4 +1,4 @@ -### Base RelatedPerson *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Base RelatedPerson *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. diff --git a/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md index aaebb87c1..e3c58ea7b 100644 --- a/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md @@ -1,4 +1,4 @@ -### RelatedPerson with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### RelatedPerson with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance From a035eb6759fef17327773e7fd1978b05ba35cb79 Mon Sep 17 00:00:00 2001 From: Rob Eastwood Date: Fri, 20 Mar 2020 11:05:47 +1100 Subject: [PATCH 2/3] provenance-list-gen-1-intro.md edited online with Bitbucket Updated implementation guidance --- .../_includes/provenance-list-gen-1-intro.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md index e9ed8359d..28de98c45 100644 --- a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md @@ -10,17 +10,17 @@ An expected usage scenario, further scoping the above overarching scenarios is: * Prescription and dispense view (PDV) exchanged with the My Health Record as a list with provenance -Further scoping of applicable usage scenarios (e.g. point-to-point or point-to-share) is done at the referencing Composition profile. +Further scoping of applicable usage scenarios (e.g. point-to-point or point-to-share) is done at the referencing Composition profile. #### Implementation guidance -For the supported scenarios in this implementation guide: +For the overarching usage scenarios in this implementation guide it is expected that: -* Where the list is a filtered view of an existing list, the source list may be referenced as an entity with the role of 'source' and what pointing to that list resource -* Where the list is created with a set of existing resources, e.g. AllergyIntolerance, the resources that initially populated the list may be referenced as entities with the role of 'source' and what pointing to that resource -* Where the generated list is a filtered view of an existing list, or a source system, or generated from a time-based search query it is expected that filtering dates are captured in the provenance period with the earliest filtering date provided in the period start and the latest filtering date provided in the period end +* When creating a list as a filtered view of an existing list (e.g. filtering to only current medicines), the source list can be identified using the entity element with an entity.role of 'source' and entity.whatReference pointing to that source list resource +* If a list has been generated from a time-based query or time-based filter it is expected that filtering dates are captured in the provenance period with the earliest filtering date provided in the period start and the latest filtering date provided in the period end +* When creating the list the list is created with a set of existing resources, e.g. AllergyIntolerance, the resources that initially populated the list may be referenced as entities with the role of 'source' and what pointing to that resource -#### When the list is a PDV -* It is expected that the only agent provided is the assembling device -* It is expected that there is only one instance of target, which is the Prescription and dispense view list resource \ No newline at end of file +When the list is a prescription and dispense view it is expected that: +* only one instance of agent (the assembling device e.g. My Health Record system) is provided +* only one instance of target (the Prescription and dispense view list resource) is provided From 01c6e43f5ec9c90854ccb1e99cb278ddc334efd9 Mon Sep 17 00:00:00 2001 From: Rob Eastwood Date: Fri, 20 Mar 2020 15:00:08 +1000 Subject: [PATCH 3/3] PDL profile intro pages - multiple updates - revised wording particularly for List of Prescription and or Dispense Records and Provenance for the Generation of a List profiles - standardised formatting of lists etc - updated publication status to match StructureDefinition.status value - added line "This profile is referenced by TBD" except for 2 profiles where the referencing profile is shown - added a known issue regarding the above "TBD" - used standard text from common profiles (organisation, practitioner etc) --- .../_includes/composition-pdl-1-intro.md | 6 +- .../_includes/device-dh-base-1-intro.md | 3 +- .../_includes/device-ident-1-intro.md | 4 +- .../_includes/humanname-dh-base-1-intro.md | 4 +- .../_includes/intro.md | 4 + .../_includes/list-pdl-1-intro.md | 96 ++++++++++--------- .../_includes/organization-dh-base-1-intro.md | 6 +- .../_includes/organization-ident-1-intro.md | 6 +- .../_includes/patient-dh-base-1-intro.md | 5 +- .../_includes/patient-ident-1-intro.md | 8 +- .../_includes/practitioner-dh-base-1-intro.md | 6 +- .../_includes/practitioner-ident-1-intro.md | 14 ++- ...ionerrole-withpractitionerident-1-intro.md | 16 ++-- .../_includes/provenance-list-gen-1-intro.md | 8 +- .../relatedperson-dh-base-1-intro.md | 7 +- .../_includes/relatedperson-ident-1-intro.md | 6 +- 16 files changed, 111 insertions(+), 88 deletions(-) diff --git a/pages/PrescriptionDispenseLists/_includes/composition-pdl-1-intro.md b/pages/PrescriptionDispenseLists/_includes/composition-pdl-1-intro.md index 7ff334fcd..d1076501b 100644 --- a/pages/PrescriptionDispenseLists/_includes/composition-pdl-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/composition-pdl-1-intro.md @@ -2,7 +2,6 @@ #### Usage scenarios The following are the overarching usage scenarios this profile is intended to support: - * A clinical information system (CIS) sends or receives * a prescription list as a document with the My Health Record system * a dispense record list as a document with the My Health Record system @@ -25,13 +24,11 @@ The following are the overarching usage scenarios this profile is intended to su * a prescription and dispense record list as a document An expected usage scenario, further scoping the above overarching scenarios is: -* Prescription and dispense view (PDV) exchanged with the My Health Record +* Prescription and dispense view (PDV) exchanged with the My Health Record system This profile does not support sending medicines change information (e.g. indicating cancellation or newly prescribed items) or event-specific information; in this case it is recommended that information is supplied as a shared medicines list. - #### Implementation guidance - When the list is a prescription list it is expected that: * code will be 57828-6 "Prescription list" * one section of type Prescription List with the code 57828-6 "Prescription list" is expected @@ -53,7 +50,6 @@ When the list is a prescription and dispense list it is expected that: * a non-empty section will be sent with a list entry * if the list is generated from a filter or search query a provenance entry will be sent - Additionally when a prescription and dispense list is a PDV it is expected that: * author will be the My Health Record system as a Device * custodian will be the My Health Record system operator diff --git a/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md index 5f7bbfae8..bba4dbaf2 100644 --- a/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/device-dh-base-1-intro.md @@ -1,5 +1,6 @@ #### Base Device *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. +No additional guidance is suggested to support implementation of this profile for the overarching usage scenarios of this implementation guide. +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md index 4c16c81f3..3a9640fd4 100644 --- a/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/device-ident-1-intro.md @@ -1,6 +1,6 @@ #### Device with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance +No additional guidance is suggested to support implementation of this profile for the overarching usage scenarios of this implementation guide. -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. - +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/humanname-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/humanname-dh-base-1-intro.md index ffeb4aa55..2f79e61b7 100644 --- a/pages/PrescriptionDispenseLists/_includes/humanname-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/humanname-dh-base-1-intro.md @@ -1 +1,3 @@ -#### Base HumanName *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* \ No newline at end of file +#### Base HumanName *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* + +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/intro.md b/pages/PrescriptionDispenseLists/_includes/intro.md index e715a25c5..0df364544 100644 --- a/pages/PrescriptionDispenseLists/_includes/intro.md +++ b/pages/PrescriptionDispenseLists/_includes/intro.md @@ -137,6 +137,10 @@ This table lists known issues with this specification at the time of publishing. Examples There are no examples available in this FHIR implementation guide. Some example resources conforming to profiles, such as Patient with Mandatory Identifier, can be found in a GitHub release, e.g. Shared Medicines List implementation guide (v1.1.0), or the examples folder of the GitHub ci-fhir-stu3 repository. + + Profile pages missing references + Many profile pages are missing the list of which other profiles include it as a reference. + diff --git a/pages/PrescriptionDispenseLists/_includes/list-pdl-1-intro.md b/pages/PrescriptionDispenseLists/_includes/list-pdl-1-intro.md index 2f130eec9..26eb520ef 100644 --- a/pages/PrescriptionDispenseLists/_includes/list-pdl-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/list-pdl-1-intro.md @@ -1,66 +1,76 @@ #### List of Prescription and or Dispense Records *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Usage scenarios +The following are the overarching usage scenarios this profile is intended to support: +* A clinical information system (CIS) sends or receives + * a prescription list with the My Health Record system + * a dispense record list with the My Health Record system + * a prescription and dispense record list with the My Health Record system +* A contracted service provider (CSP) sends or receives + * a prescription list with the My Health Record system + * a dispense record list with the My Health Record system + * a prescription and dispense record list with the My Health Record system +* A CIS sends or receives + * a prescription list with another CIS or CSP + * a dispense record list with another CIS or CSP + * a prescription and dispense record list with another CIS or CSP +* A CSP sends or receives + * a prescription list with a CIS or another CSP + * a dispense record list with a CIS or another CSP + * a prescription and dispense record list list with a CIS or another CSP +* A registered portal or registered repository receives + * a prescription list + * a dispense record list + * a prescription and dispense record list -* A clinical information system (CIS) sends or receives a prescription and or a dispense record list with the My Health Record system -* A contracted service provider (CSP) sends or receives a prescription and or a dispense record list with the My Health Record system -* A CIS sends or receives a prescription and or a dispense record list with another CIS or CSP -* A CSP sends or receives a prescription and or a dispense record list with a CIS or another CSP -* A registered portal or registered repository receives a prescription and or a dispense record list - -Expected usage scenarios, further scoping the above overarching scenarios are: - -* Prescription and dispense view (PDV) exchanged with the My Health Record as a list -* Prescription and dispense view (PDV) exchanged with the My Health Record as a document +An expected usage scenario, further scoping the above overarching scenarios is: +* Prescription and dispense view (PDV) exchanged with the My Health Record system This profile does not support sending medicines change information (e.g. indicating cancellation or newly prescribed items) or event-specific information; in this case it is recommended that information is supplied as a shared medicines list. #### Implementation guidance +For the above overarching scenarios in this implementation guide it is expected that: +* the use of MedicationStatement is discouraged +* where possible systems are encouraged to send MedicationDispense or MedicationRequest -For the above overarching scenarios in this implementation guide: - -* with a List.code of ‘100.32014’ Dispense List will be sent with only dispensed medicine items -* with a List.code of ‘57828-6’ Prescription list will be sent with only prescribed medicine items -* although an allowed type of list item is MedicationStatement its use is discouraged +When the list is a prescription and dispense view it is expected that: +* the source will be a Device (My Health Record system) +* the date will be the time the PDV is generated -When the list is a PDV -* The source will be a Device, and is expected to be the My Health Record system -* The date will be the time the PDV is generated - -#### When the list is part of a document -When the list is sent as part of a document (referenced in Composition.section.entry) rather than as a standalone resource the following guidance applies: +When the list is sent as part of a document (referenced in Composition.section.entry) the following guidance applies: - + - - + + - - + + - + - - - + + + - - - + + + - - - + + + - - - + + + - - -
ItemList element Guidance
author roleWill reference the same PractitionerRole as in Composition.composition-author-roleauthor-roleWill be sent with the same PractitionerRole as Composition.composition-author-role
author related personWill reference the same RelatedPerson as in Composition.authorauthor-related-personWill be sent with the same Relatedperson as Composition.author
codeWill have the same value as in the referencing Composition.section.code
Will be sent with the same code as Composition.section.code
subjectWill reference the same Patient as in Composition.subject
Will be sent with the same Patient as Composition.subject
dateWill hold the same value as Composition.date
Will be sent with the same datetime as Composition.date
sourceWill reference the same resource as in Composition.author
Will be sent with the same resource as Composition.author
titleWill not be provided
- \ No newline at end of file + Will not be sent + + + +This profile is referenced by [Prescription and / or Dispense List](StructureDefinition-composition-pdl-1.html) \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/organization-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/organization-dh-base-1-intro.md index 1e034535e..8e662c129 100644 --- a/pages/PrescriptionDispenseLists/_includes/organization-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/organization-dh-base-1-intro.md @@ -1,7 +1,7 @@ -#### Base Organization *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Base Organization *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance - For the overarching usage scenarios in this implementation guide it is recommended that: +* an Australian address conforms to [AU Base Address](https://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) -* an Australian address conforms to [AU Base Address](https://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) \ No newline at end of file +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/organization-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/organization-ident-1-intro.md index 17563c5f9..360679aac 100644 --- a/pages/PrescriptionDispenseLists/_includes/organization-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/organization-ident-1-intro.md @@ -1,10 +1,10 @@ -#### Organization with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Organization with Mandatory Identifier *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance - For the overarching usage scenarios in this implementation guide it is recommended that: -* an Australian address conforms to [AU Base Address](https://hl7.org.au/fhir/base/aubase1.1/StructureDefinition-au-address.html) +* an Australian address conforms to [AU Base Address](https://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) When sending a Prescription and or Dispense Record List to the My Health Record system it is expected that: * an HPI-O will be sent +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/patient-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/patient-dh-base-1-intro.md index 3cd6e5fa2..66ada58e2 100644 --- a/pages/PrescriptionDispenseLists/_includes/patient-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/patient-dh-base-1-intro.md @@ -1,6 +1,7 @@ -#### Base Patient *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Base Patient *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance - For the overarching usage scenarios in this implementation guide it is recommended that: * an Australian address conforms to [AU Base Address](https://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) + +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md index 3f19b857c..f77f0c3e1 100644 --- a/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/patient-ident-1-intro.md @@ -1,7 +1,7 @@ -#### Patient with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Patient with Mandatory Identifier *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. - - +For the overarching usage scenarios in this implementation guide it is recommended that: +* an Australian address conforms to [AU Base Address](https://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) +This profile is referenced by TBD diff --git a/pages/PrescriptionDispenseLists/_includes/practitioner-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/practitioner-dh-base-1-intro.md index c6518e2cb..850aef146 100644 --- a/pages/PrescriptionDispenseLists/_includes/practitioner-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/practitioner-dh-base-1-intro.md @@ -1,4 +1,4 @@ -#### Base Practitioner *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Base Practitioner *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance For the overarching usage scenarios in this implementation guide it is recommended that: @@ -6,4 +6,6 @@ For the overarching usage scenarios in this implementation guide it is recommend * an employee identifier local to an organisation, e.g. a hospital or lab, be sent with: * a type code of 'EI' 'http://terminology.hl7.org/CodeSystem/v2-0203' * the system will be filled with a namespace specific to the organisation, e.g. 'https://territorymedicalcentre.example.com/provider' or 'http://ns.electronichealth.net.au/id/abn-scoped/service-provider-individual/1.0/51824753556' - * the value is the actual employee identifier in the organisation's system, e.g. 'frankburns27' or '123456' \ No newline at end of file + * the value is the actual employee identifier in the organisation's system, e.g. 'frankburns27' or '123456' + +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md index 548ed37a3..946e5071a 100644 --- a/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/practitioner-ident-1-intro.md @@ -1,6 +1,14 @@ -#### Practitioner with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Practitioner with Mandatory Identifier *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. +For the overarching usage scenarios in this implementation guide it is recommended that: +* an Australian address conforms to [AU Base Address](http://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) +* an employee identifier local to an organisation, e.g. a hospital or lab, be sent with: + * a type code of 'EI' 'http://terminology.hl7.org/CodeSystem/v2-0203' + * the system will be filled with a namespace specific to the organisation, e.g. 'https://territorymedicalcentre.example.com/provider' or 'http://ns.electronichealth.net.au/id/abn-scoped/service-provider-individual/1.0/51824753556' + * the value is the actual employee identifier in the organisation's system, e.g. 'frankburns27' or '123456' - +When sending a Prescription and or Dispense Record List to the My Health Record system it is expected that: +* an HPI-I will be sent + +This profile is referenced by TBD diff --git a/pages/PrescriptionDispenseLists/_includes/practitionerrole-withpractitionerident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/practitionerrole-withpractitionerident-1-intro.md index 7864399d3..d76915f16 100644 --- a/pages/PrescriptionDispenseLists/_includes/practitionerrole-withpractitionerident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/practitionerrole-withpractitionerident-1-intro.md @@ -1,12 +1,10 @@ -#### PractitionerRole with Practitioner with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### PractitionerRole with Practitioner with Mandatory Identifier *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance +For the overarching usage scenarios in this implementation guide it is recommended that: +* PractitionerRole.code will be a value equivalent to the author's professional role, e.g. General Practitioner +* practitioner will be sent as a reference to a Practitioner resource for the author +* the organisation the author is representing (PractitionerRole.organization), e.g. family clinic, will be sent as a reference to an Organization resource +* availability information (availableTime, notAvailable, and availabilityExceptions) will not be sent -No additional guidance is suggested to support implementation of this profile for the overarching usage scenarios this implementation guide is intended to support. - -When the shared medicines list is a PSML document it is expected that: - -* PractitionerRole.code will be a value equivalent to the author's professional role, e.g. 159011008 \|Community pharmacist\| -* practitioner will be sent as a reference to a Practitioner resource for the author, e.g. the pharmacist -* the organisation the author is representing (PractitionerRole.organization), e.g. pharmacy, will be sent as a reference to an Organization resource -* availability information (availableTime, notAvailable, and availabilityExceptions) will not be sent \ No newline at end of file +This profile is referenced by TBD \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md index 28de98c45..abfc7fd5f 100644 --- a/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/provenance-list-gen-1-intro.md @@ -8,19 +8,19 @@ * A registered portal or registered repository receives a list with provenance An expected usage scenario, further scoping the above overarching scenarios is: - * Prescription and dispense view (PDV) exchanged with the My Health Record as a list with provenance Further scoping of applicable usage scenarios (e.g. point-to-point or point-to-share) is done at the referencing Composition profile. #### Implementation guidance - For the overarching usage scenarios in this implementation guide it is expected that: - * When creating a list as a filtered view of an existing list (e.g. filtering to only current medicines), the source list can be identified using the entity element with an entity.role of 'source' and entity.whatReference pointing to that source list resource * If a list has been generated from a time-based query or time-based filter it is expected that filtering dates are captured in the provenance period with the earliest filtering date provided in the period start and the latest filtering date provided in the period end -* When creating the list the list is created with a set of existing resources, e.g. AllergyIntolerance, the resources that initially populated the list may be referenced as entities with the role of 'source' and what pointing to that resource + +Provenance can record the set of the resources used for generation, e.g. the created list itself in target and the set of resources that make up the list in one or more instances of entity with entity.role as 'source'. When the list is a prescription and dispense view it is expected that: * only one instance of agent (the assembling device e.g. My Health Record system) is provided * only one instance of target (the Prescription and dispense view list resource) is provided + +This profile is referenced by [Prescription and / or Dispense List](StructureDefinition-composition-pdl-1.html) \ No newline at end of file diff --git a/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md b/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md index c01463bde..1385fcf38 100644 --- a/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/relatedperson-dh-base-1-intro.md @@ -1,6 +1,7 @@ -#### Base RelatedPerson *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* +#### Base RelatedPerson *[[Active](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. - +For the overarching usage scenarios in this implementation guide it is recommended that: +* an Australian address conforms to [AU Base Address](http://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) +This profile is referenced by TBD diff --git a/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md b/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md index e3c58ea7b..901bd7cad 100644 --- a/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md +++ b/pages/PrescriptionDispenseLists/_includes/relatedperson-ident-1-intro.md @@ -1,7 +1,7 @@ #### RelatedPerson with Mandatory Identifier *[[Draft](http://hl7.org/fhir/stu3/valueset-publication-status.html)]* #### Implementation guidance +For the overarching usage scenarios in this implementation guide it is recommended that: +* an Australian address conforms to [AU Base Address](http://build.fhir.org/ig/hl7au/au-fhir-base-stu3/StructureDefinition-au-address.html) -No additional guidance is suggested to support implementation of this profile for the expected usage scenarios of this implementation guide. - - +This profile is referenced by TBD