STARS Implementation Guide
0.1.0 - ci-build
STARS Implementation Guide - Local Development build (v0.1.0). See the Directory of published versions
Official URL: https://acdp.csiro.au/starsapi-sandbox/fhir-ig/stars/ValueSet/submission-category-value-set | Version: 0.1.0 | |||
Draft as of 2023-04-26 | Computable Name: SubmissionCategoryValueSet |
the thing to pick from
References
https://acdp.csiro.au/starsapi-sandbox/fhir-ig/stars/CodeSystem/legacy-submission-category-code-system
This value set contains 3 concepts
Expansion based on STARS Legacy Submission Category Code System v0.1.0 (CodeSystem)
Code | System | Display |
1 | https://acdp.csiro.au/starsapi-sandbox/fhir-ig/stars/CodeSystem/legacy-submission-category-code-system | Routine testing no suspicion of emergency disease |
2 | https://acdp.csiro.au/starsapi-sandbox/fhir-ig/stars/CodeSystem/legacy-submission-category-code-system | Exclusion of emergency disease low priority |
3 | https://acdp.csiro.au/starsapi-sandbox/fhir-ig/stars/CodeSystem/legacy-submission-category-code-system | Identification of emergency disease high priority |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |