Skip to content

NBRS-4931 changed more CodeSystem/dos-id into Id/dos-service-id #436

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
cda69 merged 1 commit into from
Mar 26, 2025
Merged

NBRS-4931 changed more CodeSystem/dos-id into Id/dos-service-id #436

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion ...-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 @@ -63,7 +63,7 @@ A Receiver's MessageDefinitions will contain several identifiers that will allow

* 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
* Service in MessageDefinition.useContext.code[]: <div style="display: inline">https://fhir.nhs.uk/Id/dos-service-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
2 changes: 1 addition & 1 deletion ...nGuide-BaRS/Home/About-BaRS/Content-Negotiation/Sender-MessageDefiniton.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ MessageDefinition Content_Negotiation_Client_MessageDefinition()
{compatible = true;}
else{compatible = false; break;}

if(Identifier.system == "https://fhir.nhs.uk/CodeSystem/dos-id" && Identifier.code == Service)
if(Identifier.system == "https://fhir.nhs.uk/Id/dos-service-id" && Identifier.code == Service)
{compatible = true;}
else{compatible = false; break;}
}
Expand Down
2 changes: 1 addition & 1 deletion ...ary/Payload-Library/ServiceRequest---Request/Payload-Message-Definition.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This Message Definition is built with the following specific values:
| status | 1..1 | active | |
| date | 1..1 | Date last changed | |
| useContext | 1..1 | | We are expecting the UseContext to be a DOS ID |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/CodeSystem/dos-id | |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/Id/dos-service-id | |
| useContext.code.code | 1..1 | dos-id | |
| event.system | 1..1 | https://fhir.nhs.uk/CodeSystem/message-events-bars | |
| event.code | 1..1 | servicerequest-request | |
Expand Down
2 changes: 1 addition & 1 deletion ...Guide-BaRS/Home/TEMP-HOLDING-AREA/All-Payloads/Referral-Request-Payload.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ This Message Definition is built with the following specific values:
| status | 1..1 | active | |
| date | 1..1 | Date last changed | |
| useContext | 1..1 | | We are expecting the UseContext to be a DOS ID |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/CodeSystem/dos-id | |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/Id/dos-service-id | |
| useContext.code.code | 1..1 | dos-id | |
| event.system | 1..1 | https://fhir.nhs.uk/CodeSystem/message-events-bars | |
| event.code | 1..1 | servicerequest-request | |
Expand Down
2 changes: 1 addition & 1 deletion guides/Training-guide-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 @@ -63,7 +63,7 @@ A Receiver's MessageDefinitions will contain several identifiers that will allow

* 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
* Service in MessageDefinition.useContext.code[]: https://fhir.nhs.uk/Id/dos-service-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
2 changes: 1 addition & 1 deletion ...-guide-BARS/Home/About-BaRS/Content-Negotiation/Sender-MessageDefiniton.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ MessageDefinition Content_Negotiation_Client_MessageDefinition()
{compatible = true;}
else{compatible = false; break;}

if(Identifier.system == "https://fhir.nhs.uk/CodeSystem/dos-id" && Identifier.code == Service)
if(Identifier.system == "https://fhir.nhs.uk/Id/dos-service-id" && Identifier.code == Service)
{compatible = true;}
else{compatible = false; break;}
}
Expand Down
2 changes: 1 addition & 1 deletion ...ary/Payload-Library/ServiceRequest---Request/Payload-Message-Definition.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This Message Definition is built with the following specific values:
| status | 1..1 | active | |
| date | 1..1 | Date last changed | |
| useContext | 1..1 | | We are expecting the UseContext to be a DOS ID |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/CodeSystem/dos-id | |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/Id/dos-service-id | |
| useContext.code.code | 1..1 | dos-id | |
| event.system | 1..1 | https://fhir.nhs.uk/CodeSystem/message-events-bars | |
| event.code | 1..1 | servicerequest-request | |
Expand Down
2 changes: 1 addition & 1 deletion ...guide-BARS/Home/TEMP-HOLDING-AREA/All-Payloads/Referral-Request-Payload.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ This Message Definition is built with the following specific values:
| status | 1..1 | active | |
| date | 1..1 | Date last changed | |
| useContext | 1..1 | | We are expecting the UseContext to be a DOS ID |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/CodeSystem/dos-id | |
| useContext.code.system | 1..1 | https://fhir.nhs.uk/Id/dos-service-id | |
| useContext.code.code | 1..1 | dos-id | |
| event.system | 1..1 | https://fhir.nhs.uk/CodeSystem/message-events-bars | |
| event.code | 1..1 | servicerequest-request | |
Expand Down
Loading