-
Notifications
You must be signed in to change notification settings - Fork 61
JSON "schema" for SEG metadata
Andrey Fedorov edited this page May 10, 2016
·
9 revisions
Summary of the elements being communicated as implemented for the Iowa use case conversion process.
On the high level,it might be nice to use JSON-LD for describing this, to include references to all definitions of the concepts used, but it is not completely clear how that should be done in practice ... See a very initial attempt to get started with this here: https://gist.github.com/fedorov/10dc46e160a615ea187c0b838205eb0f
TODO: investigate the joint use of JSON-LD and JSON Schema!
{
"seriesAttributes": {
"ReaderID": <PN - string>,
"ClinicalTrialSeriesID": <LO - string>,
"ClinicalTrialTimePointID": <LO - string>,
"SeriesDescription": <LO - string>,
"SeriesNumber": <IS - int>,
"InstanceNumber": <IS - int>,
"BodyPartExamined": <CS - string>
},
"segmentAttributes": {
<int>: {
"LabelID": <int>, # required
"SegmentedPropertyCategory": <code_tuple>, # required
"SegmentedPropertyType": <code_tuple>, # required
"SegmentedPropertyTypeModifier": <code_tuple>, # optional
"SegmentAlgorithmType": {AUTOMATIC,MANUAL,SEMIAUTOMATIC}, # required
"SegmentAlgorithmName": <string>, # required if not MANUAL
"RecommendedDisplayRGBValue": (<int>,<int>,<int>) # optional
}
}