Handle narrative description slicing in more robust fashion

[eyuasa]

There are a few edge cases within the MADFSH narrative description generation that have not been handled because they require some more investigation. These edge cases include:

• Slicing of elements - an example of this occurs in us-core-conditions-problems-health-concerns where there are two slices for .category. As a result, MADFSH says that the narrative mapping does not contain an entry for .category (because we instead have category:screening-assessment and category:us-core. Create a generalized way for the tool to handle situations where there are multiple definitions for a given attribute due to slicing.
• There are profiles that make use of the [x] syntax for denoting choice data types. Examples are in the Observation profile (which makes use of effective[x] and value[x]. Right now, our mappings include the [x] choice type, but the application throws an error that effective and value are not supported. Create a generalized solution for handling whether we want to document the choice types or if we want to omit them, or if we want to include mappings both with and without the choice type included as entries.