Difference between revisions of "FPS Ontoserver testing"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ==== FPS Health - Terminology Centre NRC ==== | + | ==== ''' FPS Health - Terminology Centre NRC''' ==== |
===== Onto server Test Atelier ===== | ===== Onto server Test Atelier ===== | ||
| Line 23: | Line 23: | ||
::* JSON parser | ::* JSON parser | ||
| − | '''For any question''', please contact [mailto: | + | ''' Issue logging''' |
| + | ::* Please create your issues identified during the BE FHIR-A-THON testing here: [https://apps.health.belgium.be/terminology-request-form/support/form/nl Belgian Health Terminology Portal - Support] | ||
| + | |||
| + | '''For any question''', please contact [mailto:terminologie@health.fgov.be NRC, FPS Health] | ||
Latest revision as of 19:08, 4 November 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
Issue logging
- Please create your issues identified during the BE FHIR-A-THON testing here: Belgian Health Terminology Portal - Support
For any question, please contact NRC, FPS Health
