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

Use of separate Signs and Symptoms profiles

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Highest Highest

    Description

      I'm not a big fan of separate profiles for the presence and absence of particular Signs and Symptoms. Given that Condition.verificationStatus is Must Support is US Core and is a Modifier element, it feels like systems should be about to use this element to clearly distinguish between presence and absence. It may be less of a lift for systems to use this standard data element than to look for a profile identifier or a library specific extension. 

      At the very least, should the profiles have guidance on appropriate values to put in .verificationStatus for each of the profiles?

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: