From 1d0662ab430ffa63ea9931d0ab64bac45f516d2f Mon Sep 17 00:00:00 2001 From: Janne Heikkinen Date: Fri, 6 Sep 2024 13:21:16 +0300 Subject: [PATCH 1/5] Move ServiceEvent extension to base profiles. --- input/fsh/extensions/serviceEvent.fsh | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 input/fsh/extensions/serviceEvent.fsh diff --git a/input/fsh/extensions/serviceEvent.fsh b/input/fsh/extensions/serviceEvent.fsh new file mode 100644 index 0000000..df2ff86 --- /dev/null +++ b/input/fsh/extensions/serviceEvent.fsh @@ -0,0 +1,5 @@ +Extension: ServiceEvent +Id: service-event +Description: "Extension for service event id (*palvelutapahtuman tunniste*)." +* value[x] 1.. +* value[x] only oid \ No newline at end of file From 996debd2336e4326f913f296bfdf3e5528dba237 Mon Sep 17 00:00:00 2001 From: Janne Heikkinen Date: Fri, 6 Sep 2024 13:21:16 +0300 Subject: [PATCH 2/5] Move ServiceEvent extension to base profiles. --- input/fsh/extensions/serviceEvent.fsh | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 input/fsh/extensions/serviceEvent.fsh diff --git a/input/fsh/extensions/serviceEvent.fsh b/input/fsh/extensions/serviceEvent.fsh new file mode 100644 index 0000000..df2ff86 --- /dev/null +++ b/input/fsh/extensions/serviceEvent.fsh @@ -0,0 +1,5 @@ +Extension: ServiceEvent +Id: service-event +Description: "Extension for service event id (*palvelutapahtuman tunniste*)." +* value[x] 1.. +* value[x] only oid \ No newline at end of file From 78d22623e0cb9654a3bd1b7573627acb83b7fc94 Mon Sep 17 00:00:00 2001 From: Janne Heikkinen Date: Thu, 12 Sep 2024 15:08:29 +0300 Subject: [PATCH 3/5] Move ServiceEvent extension intro file to base profiles. --- .../pagecontent/StructureDefinition-service-event-intro.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 input/pagecontent/StructureDefinition-service-event-intro.md diff --git a/input/pagecontent/StructureDefinition-service-event-intro.md b/input/pagecontent/StructureDefinition-service-event-intro.md new file mode 100644 index 0000000..e177555 --- /dev/null +++ b/input/pagecontent/StructureDefinition-service-event-intro.md @@ -0,0 +1,7 @@ +### Scope and Usage + +ServiceEvent extension defines related service event identifier (*palvelutapahtuman tunniste*). When the service event id is included into the resource, it SHALL be done with this extension. + +The scope of *palvelutapahtuma* is described in [base profiles](https://hl7.fi/fhir/finnish-base-profiles/StructureDefinition-fi-base-encounter.html#relation-to-finnish-palvelutapahtuma). + +There are other mechanisms for communicating this information as well, like including it into the Provenance, as Kanta does, or referring to the Appointment resource from the Encounter. \ No newline at end of file From 87ccbadb19db1f7b8bc439e12babdf7cbb85fe5e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikael=20Rinnetm=C3=A4ki?= Date: Sat, 19 Oct 2024 08:27:43 +0300 Subject: [PATCH 4/5] Add info on service event extension --- ...ctureDefinition-fi-base-encounter-intro.md | 23 ++++++++++++------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/input/pagecontent/StructureDefinition-fi-base-encounter-intro.md b/input/pagecontent/StructureDefinition-fi-base-encounter-intro.md index 252c0a9..afd779e 100644 --- a/input/pagecontent/StructureDefinition-fi-base-encounter-intro.md +++ b/input/pagecontent/StructureDefinition-fi-base-encounter-intro.md @@ -41,20 +41,27 @@ and will archive lab results directly to Kanta. It receives encounter id in SMAR context. Laboratory system can resolve *palvelutapahtuma*'s OID identifier by fetching the encounter resource. -##### How to communicate palvelutapahtuma via FHIR encounter? +##### How to communicate the *palvelutapahtuma* via the Encounter resource -First thing is to identify the appropriate aggregation level of encounter. If encounter is not -representing a *palvelutapahtuma*, but is a lower level encounter (some systems call these -*prosessitapahtuma*), `partOf` should be used to point to upper level encounter (up until -*palvelutapahtuma* level is reached). +This method is applicable for resources that have a direct link to Encounter. -A *palvelutapahtuma* encounter is identified by an identifier. When encounter has an identifier -with `use=official` it is considered to be a *palvelutapahtuma* and that identifier SHALL be the -OID of a *palvelutapahtuma*. +An Encounter that is a *palvelutapahtuma* SHALL have an identifier with `use=official` and the +value of that identifier SHALL be the OID of a *palvelutapahtuma*. Other levels of encounter that are not a *palvelutapahtuma*, MUST NOT contain an identifier with `use=official`. +The resource referring to the Encounter, may link to the *palvelutapahtuma* Encounter directly, or +to a lower level Encounter (some systems call these +*prosessitapahtuma*). In this case, the lower level Encounters SHALL have a chain of `.partOf` +links eventually leading to the *palvelutapahtuma* Encounter. + +##### How to communicate the *palvelutapahtuma* without an Encounter resource + +When the resource does not have a direct link to Encounter or if the chaining of Encounter +resources is considered too complex, the +[ServiceEvent extension](StructureDefinition-service-event.html) can be used instead. + #### Organizational responsibility The unit responsible for the encounter SHOULD be communicated using the `serviceProvider` property. From 05b0da3f6e6d5a3fc9b11de35ea98e1064366c5f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikael=20Rinnetm=C3=A4ki?= Date: Sat, 19 Oct 2024 08:44:30 +0300 Subject: [PATCH 5/5] Enhance the description Use local links to this IG. We're in the base profiles ig now. (This extension was copied from scheduling-specific ig's.) Don't mention Kanta yet. There is nothing authoritative we can link to. --- .../StructureDefinition-service-event-intro.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/input/pagecontent/StructureDefinition-service-event-intro.md b/input/pagecontent/StructureDefinition-service-event-intro.md index e177555..e21b16b 100644 --- a/input/pagecontent/StructureDefinition-service-event-intro.md +++ b/input/pagecontent/StructureDefinition-service-event-intro.md @@ -1,7 +1,11 @@ ### Scope and Usage -ServiceEvent extension defines related service event identifier (*palvelutapahtuman tunniste*). When the service event id is included into the resource, it SHALL be done with this extension. +ServiceEvent extension defines related service event identifier (*palvelutapahtuman tunniste*). +When the service event id is included into the resource, it SHALL be done with this extension. -The scope of *palvelutapahtuma* is described in [base profiles](https://hl7.fi/fhir/finnish-base-profiles/StructureDefinition-fi-base-encounter.html#relation-to-finnish-palvelutapahtuma). +The scope of *palvelutapahtuma* is described in the description pf the +[Fi Base Encounter](StructureDefinition-fi-base-encounter.html#relation-to-finnish-palvelutapahtuma) +profile. -There are other mechanisms for communicating this information as well, like including it into the Provenance, as Kanta does, or referring to the Appointment resource from the Encounter. \ No newline at end of file +The Fi Base Encounter profile also describes how the *palvelutapahtuma* Encounter can be referred +to using the link from the resource.