Skip to content

Commit

Permalink
Fix header levels
Browse files Browse the repository at this point in the history
  • Loading branch information
thomiz committed Dec 2, 2024
1 parent 1fefee4 commit 93341a1
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 16 deletions.
4 changes: 2 additions & 2 deletions VitalSigns/input/pages/VKP-mapping.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# VKPObservation vs NoDomainVitalSigns
### VKPObservation vs NoDomainVitalSigns

VKPObservation is another profile specification implemented by Velferdsteknologisk knutepunkt and Pasientens Måledata in the NHN infrastructure. The goal of the profiles is to support sharing and searching for vital signs observations.

## Mapping table
#### Mapping table

The table shows a the Observation.code (snomed) used in the different profiles. Other summarizes the extensions defined in NoDomainVitalSigns (that don't extist in VKP).

Expand Down
6 changes: 3 additions & 3 deletions VitalSigns/input/pages/guidance.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Use of LOINC codes
### Use of LOINC codes

In FHIR, the LOINC codes (magic value) are mandatory to indicate what category of measurement the given observation is. This is problematic in Norway as LOINC is not generally used in clinical systems in Norway. The magic value codes are to be considered as category codes and if more precise coding is needed SNOMED or other terminology are recommended to use in addition to the magic value.

# Pulse rate vs Heart rate
### Pulse rate vs Heart rate

In most cases pulse rate and heart rate values are considered to be clinically the same; pulse rate is treated as a "proxy" of the actual heart rate. However there are several cases where pulse rate and heart rate are treated as different measurements and differences have clinical importance. In most cases a general LOINC heart rate code to indicate both pulse rate and heart rate is good enough. For systems and clinical processes that need to differentiate the different concepts, the use of more specific SNOMED codes indicated in Observation.code slices in the no-domain-pulse and no-domain-heartrate profiles are recommended. Additional information about method and bodySite of the heart rate observation can also indicate pulse or heart rate observation.

## Conceptual model vs FHIR vital-signs profiles
#### Conceptual model vs FHIR vital-signs profiles

The model depicts the differences in conceptual and FHIR vital signs model, including the meaning of different use of codes for handling the complex conceptual model where pulse rate and heart rate are to be differentiated.

Expand Down
4 changes: 2 additions & 2 deletions VitalSigns/input/pages/index.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# About the Norwegian national vital signs profiles
### About the Norwegian national vital signs profiles

The *Norwegian national vital signs profiles* have been designed for exchange of the most important [vital signs](https://en.wikipedia.org/wiki/Vital_signs) between systems, devices, and healthcare organizations in the national Norwegian healthcare system.

Expand All @@ -14,7 +14,7 @@ Since the EHR system in question ([DIPS Arena](https://www.dips.com/)) uses [Ope

Other information models for these vital signs have been consulted, and while there are several different approaches none have been identified that have the capability to express any concept or relationship that the current profiles are not capable of expressing. Of particular interest here are the CIMI revised vital signs profiles [TODO: link] and the NHS profiles [TODO: link]. CIMI have entirely independently taken an approach remarkably similar to these profiles (which we take as validating this approach), while the NHS has developed their propfiles in conjunction with, and seemingly as a primary use case, profiles for the NEWS2 score [TODO: link]. NEWS2 is a standard screening tool in Norwegian hospitals and it is likely that a future revision of these profiles will need to be adapted to work well in this context.

## Vital signs profiles and terminology
#### Vital signs profiles and terminology

Information exchange defined as the scope of delivery of NoDomainVitalSigns profiles.

Expand Down
23 changes: 14 additions & 9 deletions docs/2024-12-02-notater.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,32 +21,37 @@ Lars Andreas Nystad

Guideance - Guidance

* Hvem er publisher for verdisett?
* AKSJON: Hvem er publisher for verdisett?
* Mest naturlig at det publiseres av HL7 Norge.
* HL7 Norge kan få en gratis versjon av Ontoserver.
* HL7 Norge har ikke ressurser.
* OK, konfigureres i SUSHI
* SNOMED copyright
* AKSJON: SNOMED copyright
* NOTAT Relevant i alle verdisett med SNOMED koder
* Referanse til arketypene.
* TEST
* AKSJON: Referanse til arketypene.
* Relevant i beskrivelsen av alle profilene.
* Nevnes en gang pr. profil.
* [arketype henvisning](https://arketyper.no/ckm/archetypes/1078.36.2165/sharewithcolleague)
* En linje pr. profil
* Lisens, hvilken lisens skal vi bruke, skrive det inn i konfigen sushi
* TEST
* AKSJON: Lisens, hvilken lisens skal vi bruke, skrive det inn i konfigen sushi
* OK, konfigureres i SUSHI
* Sjekk hva de bruker internasjonalt for lisens
* Gapet i tabellen må forklares https://hl7norway.github.io/no-domain/VitalSigns/TestBuild/index.html#vital-signs-profiles-and-terminology
* OK?
* AKSOJN: Gapet i tabellen må forklares https://hl7norway.github.io/no-domain/VitalSigns/TestBuild/index.html#vital-signs-profiles-and-terminology
* Forklare gapet med tekst
* Si hva SNOMED
* Heter Norsk utvidelse og engelsk extension.
* Det ser rart ut at denne ikke er i norsk ekstensjon
* Heter Norsk utvidelse og engelsk extension.
* OK
* AKSJON: Det ser rart ut at denne ikke er i norsk ekstensjon
* 4491000202105 (finnes ikke i norsk ekstensjon)
* Finnes ikke i SNOMED
* SCTID: 4501000202102 brukes istedenfor 4491000202105
* Litt om utviklingen i R6 rund bruk av LOINC koder.
* OK
* AKSJON: Litt om utviklingen i R6 rund bruk av LOINC koder.
* På Guidance siden
* Overskrifter blir veldig rare (nivåene)
* AKSJON: Overskrifter blir veldig rare (nivåene)

## Workshop

Expand Down

0 comments on commit 93341a1

Please sign in to comment.