2015May core #913 - Allow structures in notes, make 0..*

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology
    • (NA)
    • Hide

      Will define a common data type?called "Annotation". ?We will update the build tool to require that elements named "note", "notes", "comment" or "comments" be validated as follows:

      "notes" or "comments" produces an error.

      "note" must be 0..* with a data type of Annotation

      "comment" must be 0..1 with a type of string and generates a warning message "MnM must have confirmed this should not be an Annotation". ?(We can suppress these warnings on a case-by-case basis.)

      Datatype definition: A structured note capturing information about who made the statement and when

      Usage Note: For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. ?This element may need to be included in narrative because of the potential for modifying information. ?Annotations SHOULD NOT?be used to communicate "modifying" information that could be computable. ?(We use SHOULD because enforcing user behavior is nearly impossible.)

      The data type will have 3 properties:

      author (0..1) Reference(Practitioner|Patient|RelatedPerson)|string

      Definition: The individual responsible for making the annotation.

      time (0..1) dateTime

      Definition: Indicates when this particular annotation was made

      text (1..1) string

      Definition: The text of the annotation

      Show
      Will define a common data type?called "Annotation". ?We will update the build tool to require that elements named "note", "notes", "comment" or "comments" be validated as follows: "notes" or "comments" produces an error. "note" must be 0..* with a data type of Annotation "comment" must be 0..1 with a type of string and generates a warning message "MnM must have confirmed this should not be an Annotation". ?(We can suppress these warnings on a case-by-case basis.) Datatype definition: A structured note capturing information about who made the statement and when Usage Note: For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. ?This element may need to be included in narrative because of the potential for modifying information. ?Annotations SHOULD NOT?be used to communicate "modifying" information that could be computable. ?(We use SHOULD because enforcing user behavior is nearly impossible.) The data type will have 3 properties: author (0..1) Reference(Practitioner|Patient|RelatedPerson)|string Definition: The individual responsible for making the annotation. time (0..1) dateTime Definition: Indicates when this particular annotation was made text (1..1) string Definition: The text of the annotation
    • Bill de Beaubien/Michelle Miller: 10-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: Global - notes (e.g., Condition.notes)

      Comment:

      Recommend allowing for structures in notes that contain an optional type. Generally, should be 0..* when used rather than 0..1. If the cardinality is 0..1, and there are multiple notes, the receiving application will be responsible for parsing them.

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Claude Nanjo (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: