Difference between revisions of "FPS Ontoserver testing"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==== FPS Health - Terminology Centre NRC ==== | ==== FPS Health - Terminology Centre NRC ==== | ||
| − | ===== | + | ===== Onto server Test Atelier ===== |
''' Target audience:''' | ''' Target audience:''' | ||
| Line 7: | Line 7: | ||
::* value set consumers | ::* value set consumers | ||
| − | |||
''' Test case 1 – Consume BE SCT edition (binary files) | ''' Test case 1 – Consume BE SCT edition (binary files) | ||
''' | ''' | ||
Latest revision as of 13:09, 7 October 2024
FPS Health - Terminology Centre NRC
Onto server Test Atelier
Target audience:
- technical implementers & healthcare software providers from first and second line (general practitioners, nurses, hospitals …)
- health vaults
- value set consumers
Test case 1 – Consume BE SCT edition (binary files)
- Connect to Ontoserver
- Put in place configuration to subscribe to BE edition of SNOMED CT
- Use Ontoserver Syndication API to
- Consume BE edition of SNOMED CT
- Update BE edition of SNOMED CT
Test case 2 – Consume BE SCT value lists (codes + labels)
- Use Ontoserver FHIR API to
- Expand value lists
Prerequisites
- Tool for querying (Postman, cURL, …)
- JSON parser
For any question, please contact David Op de Beeck
