Skip to content

Updates for Jiras 3757, 3868 and change logs for App4 and App6 #399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luci-davies merged 5 commits into from
Mar 19, 2025
Merged

Updates for Jiras 3757, 3868 and change logs for App4 and App6 #399

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
49e7b15
Added change log items for App4 and App6
luci-davies Mar 18, 2025
e236dfe
Content negotiation page fixes
luci-davies Mar 18, 2025
747eb76
Amended link for Appointment
luci-davies Mar 18, 2025
f9d4736
Update Mechanism.page.md
luci-davies Mar 18, 2025
3dd0ae5
BaRS Applications add to site map
luci-davies Mar 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...-ImplementationGuide-BaRS/Home/About-BaRS/Content-Negotiation/Mechanism.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,15 +55,15 @@ Another capability described within the CapabilityStatement is the definition of

### The receivers responsibility

The receiver at this level only needs to evaluate the Accept Header to ensure there is no major version discrepancy. A 406 HTTP response with the appropriate OprationOutcome should be given if this is the case.
The receiver at this level only needs to evaluate the Accept Header to ensure there is no major version discrepancy. A 406 HTTP response with the appropriate OperationOutcome should be given if this is the case.

## Identifying MessageDefinitions

A Receiver's MessageDefinitions will contain several identifiers that will allow a Sender to ascertain whether their use-case workflow can be completed, beyond what the CapabilityStatement has already confirmed, supporting Content negotiation. The Message Definition will also contain a version number for version negotiation, along with the fundamental intent of the MessageDefinitions, defining the construct of the message (payload) a Sender must build. Example of identifiers are as follows:

* Name or URL in MessageDefinition.url / MessageDefinition.name : https://fhir.nhs.uk/MessageDefinition/bars-message-servicerequest-request
* Use case in MessageDefinition.useContext.code[]: https://fhir.nhs.uk/CodeSystem/usecases-categories-bars.
* Service in MessageDefinition.useContext.code[]: https://fhir.nhs.uk/CodeSystem/dos-id
* Name or URL in MessageDefinition.url / MessageDefinition.name : <div style="display: inline">https://fhir.nhs.uk/MessageDefinition/bars-message-servicerequest-request
* Use case in MessageDefinition.useContext.code[]: <div style="display: inline">https://fhir.nhs.uk/CodeSystem/usecases-categories-bars
* Service in MessageDefinition.useContext.code[]: <div style="display: inline">https://fhir.nhs.uk/CodeSystem/dos-id
* Version in MessageDefinition.version

The Name or URL define the type of message being sent. The Service id is confirmation of the correct Service. The Use Case Category code(s) define the care setting context required to ensure the message is actionable by the service. The Version allows for Version negotiation. All of these items need to be checked. There may be variations of the same message definition for a given service based on these variables.
Expand Down
5 changes: 3 additions & 2 deletions ...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/1.2.2.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,9 @@ This is a minor "patch" with clarifications to limited areas of the Implementati

| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |

| encounter.class.display | | | Update | Validation Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |
| encounter.class.display | | | Update | Interim Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |
| encounter.class.display | | | Update | Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |


<br>
Expand Down
3 changes: 1 addition & 2 deletions .../Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.4.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |

| encounter.class.display | | | Update | Referral Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | <mark style="background-color: Yellow">Addition</mark> |


<br>
<hr>

Expand Down
5 changes: 5 additions & 0 deletions ...Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Index.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
topic: Applications
---

## {{page-title}}
2 changes: 1 addition & 1 deletion ...e-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Cancellation.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ This payload is used to transmit all the necessary information that is required

| Data Item | Implementation Guidance | Necessity | Profile Cardinality | Example Value(s) |
|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------|------------------------------------------------------------------------------------------|
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcoreappointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcore-appointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment.id | This MUST only be populated with an id generated by the Receiver in the synchronous HTTP response. | MUST | 0..1 | 3713c8fc-dbcf-4f90-bacf-89d99e434e9b |
| Appointment.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 1..1 | |
| Appointment.meta.profile | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | https://fhir.hl7.org.uk/StructureDefinition/UKCore-Appointment |
Expand Down
2 changes: 1 addition & 1 deletion ...e-BaRS/Home/Core/1.1.6/Standard-Pattern-Composite-Messages/Cancellation.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ This payload is used to transmit all the necessary information that is required

| Data Item | Implementation Guidance | Necessity | Profile Cardinality | Example Value(s) |
|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------|------------------------------------------------------------------------------------------|
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcoreappointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcore-appointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment.id | This MUST only be populated with an id generated by the Receiver in the synchronous HTTP response. | MUST | 0..1 | 3713c8fc-dbcf-4f90-bacf-89d99e434e9b |
| Appointment.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 1..1 | |
| Appointment.meta.profile | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | https://fhir.hl7.org.uk/StructureDefinition/UKCore-Appointment |
Expand Down
2 changes: 1 addition & 1 deletion ...e-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/Cancellation.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ This payload is used to transmit all the necessary information that is required

| Data Item | Implementation Guidance | Necessity | Profile Cardinality | Example Value(s) |
|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------|------------------------------------------------------------------------------------------|
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcoreappointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment | https://simplifier.net/hl7fhirukcorer4/ukcore-appointment <br><br>This resource will be used to communicate information about an appointment. | | 1..1 | |
| Appointment.id | This MUST only be populated with an id generated by the Receiver in the synchronous HTTP response. | MUST | 0..1 | 3713c8fc-dbcf-4f90-bacf-89d99e434e9b |
| Appointment.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 1..1 | |
| Appointment.meta.profile | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | https://fhir.hl7.org.uk/StructureDefinition/UKCore-Appointment |
Expand Down
Loading