Abstract parameter in Operation Validate code is confusing

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • Normative
    • CodeSystem
    • Hide

      Change to:

      If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is fase, abstract codes are not considered to be valid.

      Note that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in a actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.

      Show
      Change to: If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is fase, abstract codes are not considered to be valid. Note that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in a actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.
    • Rob Hausam/Grahame Grieve: 15-0-1
    • Correction
    • Non-substantive
    • STU3

      The In Parameter "abstract" documentation is very confusing and needs to be clarified or perhaps a better approach instituted. The doc:

      if true, then an abstract code is allowed to be used in the context of the code that is being validated. Typically, abstract codes are allowed to be used in value set specifications (e.g. any code that is subsumed by an abstract code), but not in an actual recrod. If false (which is the default value), then only concrete codes as defined by the code system are allowed.

      1) It is very unclear what is meant by "...an abstract code is allowed to be used in the context of the code that is being validated." There is not a good reason to differentiate this operation based on the code system designating a concept as "abstract". Few code systems (other than HL7 ones) do this and the concept is a valid member of the code system in any case. If a user wants to know a propert of the concept (such as "abstract" then they should obtain that information using the $lookup operation. Given my understanding I think this parameter should be removed.

      2) a typo exists record. should be record

            Assignee:
            Unassigned
            Reporter:
            Rob McClure
            Rob McClure
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: