This wiki has undergone a migration to Confluence found Here
Editing Tasks
Revision as of 01:40, 17 October 2018 by Francoismacary (talk | contribs) (→To Do post September Connectathon)
Return to Orders & Observations Work Group
Return to Ordering Service Project Page
Return to Catalog Project Page
Contents
Deadlines
- Substantive content freeze : August 10, 2018
- Final Content freeze:
- Ballot opens: August 24, 2018
- Ballot closes: September 24, 2018
To Do post September Connectathon
- ObservationDefinition:
- CatalogEntry
- SpecimenDefinition:
- change patientPreparation from string 0..1 to CodeableConcept 0..*. An example value set is: < 703763000 |Precondition value (qualifier value)| from SNOMED CT. Multiple pre-conditions or preparations can be specified, hence the cardinalities 0..*. In case there is no coded concept, the text element of CodeableConcept can be used. --> RT 19419
- Correct value set of container.type to: < 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)| SNOMED CT --> RT 19422
- Provide value set for container.material (glass, plastic, metal ... see Specimen DAM) --> RT 19425
- Provide value set for collection (binding strength Example) --> RT 19426
- Sometimes, the minimum volume may appear as a textual instruction. Therefore change minimumVolume from SimpleQuantity to a choice {SimpleQuantity, string} --> RT 19423
- Challenge the usefulness of isDerived boolean element. In V2 OM4-2 “Derived specimen” uses table 0170 to specify whether the specimen is parent (e.g. blood culture) or child (e.g. pure colony isolate). Do we really need this element in SpecimenDefinition?
- Coverage on examples: François provided for SpecimenDefinition and ObservationDefinition. Needed for other kinds of catalogs (medications, devices)
- we should discuss Human Services use cases - look at our example use cases --> NEED TO ASSIGN TO SOMEONE
- Profile on ActivityDefinition (NEED TO ASSIGN TO SOMEONE AFTER SEPT) --> François
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 --> DONE by Bryn
- Tracker items from ballot - François prepared proposed resolutions for block vote. --> DONE
- review value set bindings and definitions (François to do) --> DONE, review the proposals in the Post September Connectathon section above.
- review relationship types in Catalog Entry (François to do): remove has-input, has-output and uses from the list --> DONE
- ObservationDefinition cleanup:
- Replace Coding by CodeableConcept on category and code --> DONE
- Add element identifier (discovered as useful for Quest, and probably to most labs for internal identifier) --> DONE
- I think element permittedDatatype should be of type code, with fhir value-set {quantity, time, string, CodeableConcept, ...etc) (Waiting to get core value set reference from Lorraine) --> DONE
- Correct value set binding of qualifiedInterval.category: This is not a category of observation. An example value set would be: {"reference", "critical", "absolute"} --> DONE
- Fix definitions for qualifiedInterval.category and qualifiedInterval.type (Actually, review all definitions for clarity and completeness) (FRANCOIS) --> DONE, see left over in section "Post September Connectathon" above.
- qualifiedInterval.range: Correct the description from "Low bound of reference range, if relevant" to "range of the interval", also changed long description --> DONE
- 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 --> DONE
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
