Fracture of [bone structure] (disorder) - v1.0

Hi @Yongsheng Gao @Kai Kewley   I'd like to add a section to these pages, something like "Application" or "Applies To" and then have a list of concepts, from which point down this template can be applied.    So in this case that would be << 125605004 |Fracture of bone (disorder)|   

I don't think it's possible to determine that information from this page as it stands?   I'd also like to represent that in the JSON.    The immediate use case is to allow automation of checking for template conformance in the appropriate sub-hierarchies.     A secondary use case would be in the form of Author Decision Support so that we could offer the user the appropriate template(s) for what they're working on once we know the parent (interesting workflow / UI implication there that we'd need to be told the immediate parent but the template will assert the proximal primitive eg Disorder).

I didn't want to just make that change because I heard Yong say there was already some code to generate the JSON from these confluence pages?

Hi @Peter Williams . Yes please that would be useful.

We can just update the template generation code which has just really a workflow helper for me:

https://git.ihtsdotools.org/ihtsdo/snomed-template-service/blob/master/src/test/java/org/ihtsdo/otf/authoringtemplate/TemplateAuthoringHelper.java

Example input - https://gist.github.com/kaicode/16916275b80b4d9b1859cc7258f28716 (I copy the contents of a 'Concept model:' table not including the header).

@Peter Williams, It sounds good and convenient.   

Yes, this concept can be determined from the template as it stands. It is fully defined as |Disease|:{|associated morphology = fracture, |finding site| = |bone structure|}. It is possible that a precordinated concept might not exist for a template. For example, the template created by Jim for pathologic fracture of bone structure due to a disorder.