FHIR Profile Page

Comments from Lloyd:

• Example table under slicing is hard to read. Perhaps change content to courier?
• I challenge whether "evidence" is in the 80%. Same for endorser. It might be used for some types of template systems, but a lot of profiling will be done that won't care about these things
• suggest changing name of Profile.profile to Profile.imports. That would be consistent with the naming of "supercedes" which also references profiles
• doesn't resourceType need to allow for "custom" resources too?
• Profile.resource.purpose: "Why describe this resource" is weak.
• I think xpath needs to be broken into a structure which includes xpath and human text
  • Need this to generate schematron output which has to be human readable
  • In some cases, xpath won't be able to do the job - e.g. vocab subsumption.
• Need to capture the rules about use of "mapping" being a further constraint, not a replacement of. At least when it applies to RIM.
• Definitions for mustSupport and mustUnderstand need serious work. Also, you mark them as optional. That implies a default, but one isn't declared anywhere. Do all booleans default to false? Even if so, being explicit would be better
• Which brings up the question of: Should FHIR support defaulting?
• No clue what you meant by Profile.extensionDefn.contextType
• You're inconsistent in how you reference re-used types. For author and endorser, you spell out the content both times. For Profile.resource.element and Profile.extensionDefn.element, you do a funky reference thing.
  • The funky reference thing should do a hyperlink in the HTML. (yes, I know this means you need to put ids on stuff.)
• Need to define the "may be required" stuff for binding elements.
• The idea of "must include all the constraints in this profile of referenced profiles" falls down in the face of versioning. If the referenced profile is updated, then what happens? That's one of the points of referencing. I think there needs to be two levels of profiles. Definitional - where constraints haven't been propagated, and Runtime - where they have.
• "The condition element must be present if the conformance value is conditional" - The thing is, the condition may be best stated at a higher level. If the condition is "may have either A or B, but not both", the constraint should appear on the common ancestor of A and B.
• Can the same resource be referenced multiple times with different sets of constraints, and if so, what would that mean? I can think of situations where Person might be referenced in different places with different cosntraints, but if you do that, then you need to be able to say for each resource that references person, which constraint set from within the profile did you want to apply?
• Extension code as the element name won't fly. Can have multiple extensions with the same name. You're going to need to be able to alias names in a profile. And the alias name is what should be used. Element names from codes is a bad scene.