Survey of Required Coded Elements

All Required Bindings for Required Coded Elements:

1. CareTeam.status

   • base cardinality= 0..1
   • base valueSet = http://hl7.org/fhir/ValueSet/care-team-status|4.0.0
   • base binding strength = required
   • http://hl7.org/fhir/ValueSet/care-team-status ( entered-in-error, inactive, active, suspended, proposed)

   Proposal is to make 0..1 Must Support

2. MedicationStatement.status

   • base cardinality= 1..1
   • base valueSet = http://hl7.org/fhir/ValueSet/medication-statement-status|4.0.0
   • base binding strength = required
   • http://hl7.org/fhir/ValueSet/medication-statement-status ( completed, active, entered-in-error, on-hold, unknown, stopped, intended, not-taken)

   No Change needed

3. Patient.telecom.system

   • base cardinality= ..
   • http://hl7.org/fhir/ValueSet/contact-point-system ( phone, pager, url, fax, other, sms, email)

   No Change needed

4. Patient.gender

   • base cardinality= 0..1
   • base valueSet = http://hl7.org/fhir/ValueSet/administrative-gender|4.0.0
   • base binding strength = required
   • http://hl7.org/fhir/ValueSet/administrative-gender ( male, female, other, unknown)

   No Change needed

5. Immunization.status

   • base cardinality= 1..1
   • base valueSet = http://hl7.org/fhir/ValueSet/immunization-status|4.0.0
   • base binding strength = required
   • http://hl7.org/fhir/ValueSet/immunization-status ( completed, not-done, entered-in-error)

   Discuss whether there are use cases where the status is not known in and whether the resource has any worth if status is absent or unknown

6. Observation.status

   • base cardinality= ..
   • http://hl7.org/fhir/ValueSet/observation-status ( corrected, amended, final, registered, entered-in-error, preliminary, cancelled, unknown)

   No Change needed

7. DocumentReference.status

   • base cardinality= 1..1
   • base valueSet = http://hl7.org/fhir/ValueSet/document-reference-status|4.0.0
   • base binding strength = required
   • http://hl7.org/fhir/ValueSet/document-reference-status ( entered-in-error, superseded, current)

   Discuss whether there are use cases where the status is not known in and whether the resource has any worth if status is absent or unknown

8. DocumentReference.type

   • base cardinality= 0..1
   • base valueSet = http://hl7.org/fhir/ValueSet/c80-doc-typecodes
   • base binding strength = preferred
   • http://hl7.org/fhir/ValueSet/c80-doc-typecodes ( 36325-9, 39337-1, 42473-9, 47522-8, 43458-9, 39920-4, 34751-8, 37393-6, 38019-6, 46349-7, 57177-8, 39670-5, 30688-6, 24659-5, 37764-8, 58744-4, 24909-4, 39336-3, 43791-3, 51392-9)

   *Already discussed for US Core ballot will keep as required and change valueset from c80 to "all LOINC values whose SCALE is DOC in the LOINC database." *

9. DocumentReference.content.attachment.contentType

   • base cardinality= ..
   • http://hl7.org/fhir/ValueSet/mimetypes|4.0.0

   No Change needed

10. DiagnosticReport.status

    • base cardinality= ..
    • http://hl7.org/fhir/ValueSet/diagnostic-report-status ( registered, cancelled, partial, entered-in-error, unknown, appended, final, preliminary, corrected, amended)

    No Change needed

11. MedicationRequest.status

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/medicationrequest-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/medicationrequest-status ( stopped, active, entered-in-error, cancelled, completed, draft, unknown, on-hold)

    No Change needed

12. DiagnosticReport.status

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/diagnostic-report-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/diagnostic-report-status ( registered, cancelled, partial, entered-in-error, unknown, appended, final, preliminary, corrected, amended)

    No Change needed

13. Condition.verificationStatus

    • base cardinality= 0..1
    • base valueSet = http://hl7.org/fhir/ValueSet/condition-ver-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/condition-ver-status ( differential, entered-in-error, unconfirmed, confirmed, refuted, provisional)

    Proposal is to make 0..1 Must Support

14. Encounter.status

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/encounter-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/encounter-status|4.0.0 ( planned, unknown, in-progress, finished, cancelled, triaged, arrived, onleave, entered-in-error)

    No Change needed

15. Procedure.status

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/event-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/event-status ( completed, unknown, not-done, stopped, entered-in-error, on-hold, preparation, in-progress)

    No Change needed

16. PractitionerRole.telecom.system

    • base cardinality= ..
    • http://hl7.org/fhir/ValueSet/contact-point-system|4.0.0 ( phone, pager, url, fax, other, sms, email)

    No Change needed

17. CarePlan.text.status

    • base cardinality= ..
    • http://hl7.org/fhir/us/core/ValueSet/us-core-narrative-status

    Discuss whether there are use cases where the status is not known in and whether the resource has any worth if status is absent or unknown

18. CarePlan.status

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/request-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/request-status ( active, draft, completed, entered-in-error, unknown, on-hold, revoked)

    No Change needed

19. CarePlan.intent

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/care-plan-intent|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/care-plan-intent ( proposal, option, plan, order)

    No Change needed

20. Goal.lifecycleStatus

    • base cardinality= 1..1
    • base valueSet = http://hl7.org/fhir/ValueSet/goal-status|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/goal-status ( active, completed, rejected, cancelled, planned, entered-in-error, accepted, on-hold, proposed)

    Discuss whether there are use cases where the status is not known in and whether the resource has any worth if status is absent or unknown

21. AllergyIntolerance.verificationStatus

    • base cardinality= 0..1
    • base valueSet = http://hl7.org/fhir/ValueSet/allergyintolerance-verification|4.0.0
    • base binding strength = required
    • http://hl7.org/fhir/ValueSet/allergyintolerance-verification ( confirmed, refuted, entered-in-error, unconfirmed)

    Proposal is to make 0..1 Must Support