Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-39788

Revise the Composition-uv-epi profile

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Electronic Medicinal Product Information (FHIR)
    • 1.0.0-ballot
    • Biomedical Research & Regulation
    • STU
    • Composition (ePI)
    • Hide
      • Revise the epiType  value set leaving only the LOINC codes. Change the binding  to example
      • No additional constraints for nested sections
      • Change title and section.title cardinality to 1..1
      • Revise sectionCode value set leaving only the LOINC codes. Change the binding to example
      • No changes for orderedBy, category
      • evaluate to add invariant for section text (sections without subsections have to have text)
      Show
      Revise the epiType  value set leaving only the LOINC codes. Change the binding  to example No additional constraints for nested sections Change title and section.title cardinality to 1..1 Revise sectionCode value set leaving only the LOINC codes. Change the binding to example No changes for orderedBy, category evaluate to add invariant for section text (sections without subsections have to have text)
    • Rik Smithies/Norman Gregory : 7-0-2
    • Correction
    • Non-compatible
    • Yes

    Description

      type

      • Revise the epiType value set

      category

      • make this element required so that ePI can be searched independently on the codes used by each jurisdiction in the type .
      • Use the Loinc code that has been requested for this category when it will be assigned 

      relatesTo

      • Fix the short description "document()s)" => document(s)

      Section

      • Is there any constraint on the number of nested sections ? in case make them explicit e.g. section.section.section 0..0
       title
      • Add section.title to the profile, possible as 1..
      section.title
      • Consider to change it to 1..
       text and section.section.text
      • I suggest to make this conditional e.g. 1.. if no subsections are present
       orderedBy and section.section.orderedBy
      • Please clarify the need of having this element listed.
      • In case it is kept revise the used value set limiting it to the applicable concepts (e.g will be ever patient or event date ordered ?)
      code and section.section.code
      • fix the value set sectionCode
      • change the binding from extensible to preferred
      • add alternative value sets as needed 

      Attachments

        Activity

          People

            Unassigned Unassigned
            giorgio Giorgio Cangioli
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: