LOINC Template - Quality Observable - 99 - 1 - Archived
Status | Archived |
|---|---|
Version | 0.9 |
Descriptions:
Term | description type | Language/acceptability | Langauge/acceptability | Case significance |
|---|---|---|---|---|
LOINC FSN + (Observable entity) | FSN | US:PT | GB:PT | CS |
LOINC FSN | PT | US:PT | GB:PT | CS |
LOINC unique ID | SYN | US:A | GB:A | CS |
Published UUID | SYN | US:A | GB:A | CS |
Correlation ID | SYN | US:PT | GB:PT | CS |
Concept model:
Attribute | Value | role group number |
|---|---|---|
{"timestamp":1789231933260,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1789231933277,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
{"timestamp":1789231933235,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1789231933283,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
{"timestamp":1789231933282,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1789231933297,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
{"timestamp":1789231933286,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1789231933272,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
|
| 0 |
|
| 0 |
|
| 0 |
Definition status:
Rules for description generation:
N/A
Comments
@Kai Kewley all values specified in the table for concept model are constraints. They should already be covered by the MRCM rules for LOINC.
The descriptions covers the information that are needed for exporting expression refset as I mentioned in the requirements. Should we integrate Peter's script as part of template based import? So, we can have a single consistent batch import function.
@Yongsheng Gao I'm just chatting with Peter. Do we expect the LOINC content to adhere to the SCA MRCM? Although we are able to disable MRCM for an SCA project this means the project can not be promoted which will affect the release process.
@Yongsheng Gao The template service we have in place can only take batch files containing values which relate to relationship slots within a template. Looking at the descriptions on this template they seem to be custom values from the batch file?
CC: @Former user (Deleted)