Editing Tasks

Return to Orders & Observations Work Group

Return to Ordering Service Project Page

Return to Catalog Project Page

Deadlines

• Substantive content freeze : August 10, 2018
• Final Content freeze:
• Ballot opens: August 24, 2018
• Ballot closes: September 24, 2018

To Do for September Connectathon

• rename EntryDefinition to CatalogEntry --> Done by Claude
• Add scope and boundary text to resource -- Done by Claude
• Relationships from Activity Definition to SpecimenDefinition and ObservationDefinition (NEED TO DISCUSS WITH CDS WG)
• Tracker items from ballot - François prepared proposed resolutions for block vote. (DONE)
• review value set bindings and definitions (CLAUDE CANNOT DO)
• review relationship types in Catalog Entry (CLAUDE CANNOT DO)
  • remove has-input, has-output and uses from the list --> Done by Claude (Assuming these will be defined in profiles on ActivityDefinition)
• ObservationDefinition cleanup:
  • Replace Coding by CodeableConcept on category and code (DONE - PENDING CHECK IN)
  • Add element identifier (discovered as useful for Quest, and probably to most labs for internal identifier) (DONE - PENDING CHECK IN)
  • I think element permittedDatatype should be of type code, with fhir value-set {quantity, time, string, CodeableConcept, ...etc) (CANNOT DO. NEED PRECISE REQUIREMENTS)
  • Correct value set binding of quantitativeDetail.qualifiedRange.category: This is not a category of observation. An example value set would be: {"reference", "critical", "absolute"} (CANNOT FIND IN RESOURCE)
  • qualifiedInterval.range: Correct the description from "Low bound of reference range, if relevant" to "range of the interval" (DONE. ALSO CHANGED LONG DESCRIPTION TO REFECT MEANING)
• SpecimenDefinition: Apply resolutions of trackers listed here (DONE)
• Connectathon proposal
  • François to flesh out use cases with Quest --> DONE
• Claude to re-set up to add to build
• Coverage on examples: medication, devices, (CLAUDE CANNOT DO)
  • we should discuss Human Services use cases - look at our example use cases
  • Profile on ActivityDefinition (NEED REQUIREMENTS)

Done Items (June)

• EntryDefinition: Rename purpose (1..1, CodeableConcept) to orderable (1..1, boolean) ---> Done!
• 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). ---> Done!
• 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

---> Done! Thanks Jose!

To Do Items for June

• ObservationDefinition: various corrections
  • Correct datatype of elements category and code: from Coding to CodeableConcept
  • bind category to value set http://hl7.org/fhir/ValueSet/observation-category (preferred)
  • Correct datatype of element permittedDataType from Coding to code, with the binding to the FHIR value set {Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period} (required)
  • Correct the definition of ObservationDefinition.qualifiedInterval from "Reference range for ordinal and continuous observations." to "Reference range for ordinal and quantity measurement observations."

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? [NOTE: WE DECIDED TO DEFER THIS UNTIL WE HAVE A CONCRETE USE CASE THAT WARRANT ITS USE.]

• ActivityDefinition timingTiming (Timing) - confirm ability to carry a performance schedule as in eDos ---> Done!
  • an example of a performance schedule is "every Monday & Wednesday"
  • Yes, this is confirmed. The datatype Timing supports quite complex performance schedules, if needed.

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