| Package | nw-gmsa.github.io |
| Resource Type | OperationDefinition |
| Id | ProcessMessage |
| FHIR Version | R4 |
| Source | https://nw-gmsa.github.io/https://build.fhir.org/ig/nw-gmsa/R4/OperationDefinition-ProcessMessage.html |
| URL | https://nw-gmsa.github.io/OperationDefinition/ProcessMessage |
| Version | 0.0.7 |
| Status | draft |
| Date | 2025-08-12T13:52:16+00:00 |
| Name | ProcessMessage |
| Title | Process Message |
| Realm | uk |
| Description | This is documentation on the version of [HL7 FHIR process-message](https://hl7.org/fhir/R4/messageheader-operation-process-message.html) to be used for regional FHIR Messaging, this HL7 FHIR definition **SHALL** be followed. |
| Type | false |
| Kind | operation |
| CapabilityStatement | |
| RegionalIntegrationEngine | CapabilityStatement for NW GMSA Regional Integration Engine for Genomics |
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: OperationDefinition ProcessMessage
URL: [base]/$process-message
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | content | 1..1 | Bundle | The message to process (or, if using asynchronous messaging, it may be a response message to accept) | ||
| OUT | return | 0..1 | Bundle | A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value |
This event message differs from traditional NHS England definitions of this operation is that this operation is designed to be an interface to a mix of broker and event consumer actors, and so other standards they suport.
This is NOT intended to be a method of transferring health records or data between computer systems (i.e. it is not a health record type).
FHIR{
"resourceType": "OperationDefinition",
"id": "ProcessMessage",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"url": "https://nw-gmsa.github.io/OperationDefinition/ProcessMessage",
"version": "0.0.7",
"name": "ProcessMessage",
"title": "Process Message",
"status": "draft",
"kind": "operation",
"date": "2025-08-12T13:52:16+00:00",
"publisher": "NHS North West GMSA",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "https://www.nw-gmsa.nhs.uk/contact-us"
}
]
}
],
"description": "This is documentation on the version of [HL7 FHIR process-message](https://hl7.org/fhir/R4/messageheader-operation-process-message.html) to be used for regional FHIR Messaging, this HL7 FHIR definition **SHALL** be followed.",
"jurisdiction": [
{
"coding": [
{
"system": "urn:iso:std:iso:3166",
"code": "GB",
"display": "United Kingdom of Great Britain and Northern Ireland"
}
]
}
],
"code": "process-message",
"comment": "\nThis `event message` differs from traditional NHS England definitions of this operation is that this operation is designed to be an interface to a mix of broker and event consumer actors, and so other standards they suport.\n\nThis is **NOT** intended to be a method of transferring health records or data between computer systems (i.e. it is not a health record type).\n",
"resource": [
"MessageHeader"
],
"system": true,
"type": false,
"instance": false,
"parameter": [
{
"name": "content",
"use": "in",
"min": 1,
"max": "1",
"documentation": "The message to process (or, if using asynchronous messaging, it may be a response message to accept)",
"type": "Bundle"
},
{
"name": "return",
"use": "out",
"min": 0,
"max": "1",
"documentation": "A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value",
"type": "Bundle"
}
]
}