This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Editing Tasks"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
 
*Ballot closes: '''May 7, 2018'''
 
*Ballot closes: '''May 7, 2018'''
  
== To Do Items May 2018 Cycle ==
+
== To Do Items for June ==
  
* EntryDefinition: Change "purpose" element (1..1, CodeableConcept) to an element called "orderable" (1..1, boolean)
+
* EntryDefinition: Rename purpose (1..1, CodeableConcept) to orderable (1..1, boolean)
* EntryDefinition: Change datatype of "status" from CodeableConcept to code, change cardinality to 1..1, and assign FHIR value set [http://build.fhir.org/valueset-publication-status.html PublicationStatus](required), (values: draft | active | retired | unknown).
+
* EntryDefinition.status: Change datatype from CodeableConcept to code, change cardinality to 1..1, and assign FHIR value set [http://build.fhir.org/valueset-publication-status.html PublicationStatus](required), (values: draft | active | retired | unknown).
* EntryDefinition: Change datatype of relatedEntry.relationType from CodeableConcept to code, and define FHIR value set (required) with these values:
+
* EntryDefinition.relatedEntry.relationType: Change datatype from CodeableConcept to code, and define FHIR value set (required) with these values:
 
** has-input: the related entry represents an item to be provided as input to the current item
 
** has-input: the related entry represents an item to be provided as input to the current item
 
** has-output: the related entry represents an item produced as out put of the current item
 
** has-output: the related entry represents an item produced as out put of the current item
Line 21: Line 21:
 
** triggers: the related entry represents an activity that may be triggered by the current item
 
** triggers: the related entry represents an activity that may be triggered by the current item
 
** is-replaced-by: the related entry represents an item that replaces the current retired item
 
** is-replaced-by: the related entry represents an item that replaces the current retired item
 +
* EntryDefinition.type: Assign value set. The content of type represents the type of resource referenced by referencedItem (Medication, Device, Observation, ActivityDefinition, ...) How can we enforce that?
 
* ActivityDefinition timingTiming (Timing) - confirm ability to carry a performance schedule as in eDos
 
* ActivityDefinition timingTiming (Timing) - confirm ability to carry a performance schedule as in eDos
 
** an example of a performance schedule is "every Monday & Wednesday"  
 
** an example of a performance schedule is "every Monday & Wednesday"  
 
** Yes, this is confirmed. The datatype Timing supports quite complex performance schedules, if needed.
 
** Yes, this is confirmed. The datatype Timing supports quite complex performance schedules, if needed.
 
** --> Done
 
** --> Done
 +
 +
== Other to dos ==
 +
 
* Review all value sets and value set bindings
 
* Review all value sets and value set bindings
 
** Add Knowledge Artifact and Order Set to the value set for type
 
** Add Knowledge Artifact and Order Set to the value set for type

Revision as of 16:16, 8 June 2018

Return to Orders & Observations Work Group

Return to Ordering Service Project Page

Return to Catalog Project Page

Deadlines

  • Substantive content freeze : March 4, 2018
  • Final Content freeze: March 11, 2018
  • Ballot opens: April 6, 2018
  • Ballot closes: May 7, 2018

To Do Items for June

  • EntryDefinition: Rename purpose (1..1, CodeableConcept) to orderable (1..1, boolean)
  • EntryDefinition.status: Change datatype from CodeableConcept to code, change cardinality to 1..1, and assign FHIR value set PublicationStatus(required), (values: draft | active | retired | unknown).
  • EntryDefinition.relatedEntry.relationType: Change datatype from CodeableConcept to code, and define FHIR value set (required) with these values:
    • has-input: the related entry represents an item to be provided as input to the current item
    • has-output: the related entry represents an item produced as out put of the current item
    • uses: the related entry represents an item (product or material or substance) used by the current item
    • triggers: the related entry represents an activity that may be triggered by the current item
    • is-replaced-by: the related entry represents an item that replaces the current retired item
  • EntryDefinition.type: Assign value set. The content of type represents the type of resource referenced by referencedItem (Medication, Device, Observation, ActivityDefinition, ...) How can we enforce that?
  • ActivityDefinition timingTiming (Timing) - confirm ability to carry a performance schedule as in eDos
    • an example of a performance schedule is "every Monday & Wednesday"
    • Yes, this is confirmed. The datatype Timing supports quite complex performance schedules, if needed.
    • --> Done

Other to dos

  • Review all value sets and value set bindings
    • Add Knowledge Artifact and Order Set to the value set for type
    • review relationshipType value set - also look at similar one from Task
  • Review element definitions
  • Add search parameters to each resource - see connectathon report for suggestions for EntryDefinition
  • Prepare design summary in preparation for meeting with Lloyd
  • Add examples from connectathon to build
  • Review and prepare dispositions for comments from January ballot

Items for Future Cycles

Define Implementation Guide resource and content to contain the appropriate StructureDefinitions and Resources