FHIR Chat · Looking for Help

Stream: conformance

Topic: Looking for Help

Grahame Grieve (Feb 15 2018 at 10:56):

I need some help. I'm working on GF#13065, and I have added isModifierReason. Now, somebody has to go through a bunch of elements and sort out the documentation:

Missing IsModifierReason on Definition.status
Missing IsModifierReason on Definition.experimental
Missing IsModifierReason on Request.intent
Missing IsModifierReason on Request.doNotPerform
Missing IsModifierReason on FiveWs.status
Missing IsModifierReason on Resource.implicitRules
Missing IsModifierReason on DomainResource.modifierExtension
Missing IsModifierReason on MetadataResource.status
Missing IsModifierReason on MetadataResource.experimental
Missing IsModifierReason on AllergyIntolerance.clinicalStatus
Missing IsModifierReason on AllergyIntolerance.verificationStatus
Missing IsModifierReason on Basic.code
Missing IsModifierReason on BodyStructure.active
Missing IsModifierReason on CarePlan.intent
Missing IsModifierReason on CarePlan.activity.detail.status
Missing IsModifierReason on CarePlan.activity.detail.prohibited
Missing IsModifierReason on Condition.clinicalStatus
Missing IsModifierReason on Condition.verificationStatus
Missing IsModifierReason on DetectedIssue.status
Missing IsModifierReason on DeviceRequest.intent
Missing IsModifierReason on DiagnosticReport.status
Missing IsModifierReason on Composition.confidentiality
Missing IsModifierReason on Composition.section.mode
Missing IsModifierReason on DocumentReference.relatesTo
Missing IsModifierReason on Encounter.status
Missing IsModifierReason on Group.characteristic.exclude
Missing IsModifierReason on Immunization.isPotent
Missing IsModifierReason on ImmunizationRecommendation.recommendation.forecastStatus
Missing IsModifierReason on List.mode
Missing IsModifierReason on List.entry.deleted
Missing IsModifierReason on Location.status
Missing IsModifierReason on MedicationRequest.intent
Missing IsModifierReason on MedicationRequest.substitution.allowed
Missing IsModifierReason on Medication.amount
Missing IsModifierReason on NutritionOrder.intent
Missing IsModifierReason on Observation.status
Missing IsModifierReason on OperationOutcome.issue.severity
Missing IsModifierReason on Organization.active
Missing IsModifierReason on Patient.active
Missing IsModifierReason on Patient.deceased[x]
Missing IsModifierReason on Patient.animal
Missing IsModifierReason on Patient.link
Missing IsModifierReason on ServiceRequest.intent
Missing IsModifierReason on ServiceRequest.doNotPerform
Missing IsModifierReason on Questionnaire.item.enableWhen
Missing IsModifierReason on RelatedPerson.active
Missing IsModifierReason on ValueSet.compose.include.filter
Missing IsModifierReason on ConceptMap.group.element.target.equivalence
Missing IsModifierReason on Schedule.active
Missing IsModifierReason on AppointmentResponse.participantStatus
Missing IsModifierReason on HealthcareService.active
Missing IsModifierReason on Person.active
Missing IsModifierReason on SupplyRequest.status
Missing IsModifierReason on Consent.scope
Missing IsModifierReason on Task.status
Missing IsModifierReason on ActivityDefinition.doNotPerform
Missing IsModifierReason on RequestGroup.intent
Missing IsModifierReason on ResearchStudy.status
Missing IsModifierReason on ResearchSubject.status
Missing IsModifierReason on AdverseEvent.actuality
Missing IsModifierReason on ProductPlan.status
Missing IsModifierReason on OccupationalData.status
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\capabilitystatement\capabilitystatement-extensions-spreadsheet.xml, sheet "Extensions", row 3
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\questionnaire\questionnaire-extensions-spreadsheet.xml, sheet "Extensions", row 17
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\questionnaire\questionnaire-extensions-spreadsheet.xml, sheet "Extensions", row 20
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\device\device-extensions-spreadsheet.xml, sheet "Extensions", row 3
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\codesystem\codesystem-extensions-spreadsheet.xml, sheet "Extensions", row 4
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\observation\observation-extensions-spreadsheet.xml, sheet "Extensions", row 4
Missing IsModifierReason on extension @ c:\work\org.hl7.fhir\build\source\observation\observation-extensions-spreadsheet.xml, sheet "Extensions", row 7

Grahame Grieve (Feb 15 2018 at 10:56):

any ideas on process for this?

Alexander Henket (Feb 15 2018 at 10:59):

Send out to respective WGs just like stuff that comes from QA? In fact you could put it on the QA list for processing so it follows the same route?

Grahame Grieve (Feb 15 2018 at 11:59):

well, typically what happens is I write a business rule that requires this. Then the build fails. Then I comment it out. Then, a couple of years later, I ask Lloyd whether we'll ever get serious about it

Grahame Grieve (Feb 15 2018 at 11:59):

unless I or some of us go through and make comments that the committees don't like. then they'll fix them

Alexander Henket (Feb 15 2018 at 12:01):

Cynical? :-) I remember PA being pretty diligent on those QA things. Can't speak for every group obviously. Is it possible to not have the build fail but get the thing in QA anyway? Sounds like a proper start.

Grahame Grieve (Feb 15 2018 at 12:02):

yes some committees are not recalcitrant. But others are seriously determined about it

Alexander Henket (Feb 15 2018 at 12:04):

Gotcha. Well let's at least follow the regular route for the coalition of the willing and start encouraging people less likely to do this in a timely fashion through the lists and FHIR facilitators (even if that role goes by a different name)

Alexander Henket (Feb 15 2018 at 12:05):

If it is on the QA list, that is at least a regular source for WG input and FHIR Facilitators already look at it, rather than creating a new one. Unless you want to script a ticket for each resource in GForge which also puts it on the radar.

Ewout Kramer (Feb 15 2018 at 13:06):

Want me to put this on my list for the FHIR-I resources?

Grahame Grieve (Feb 15 2018 at 13:15):

that would be great

Eric Haas (Feb 15 2018 at 17:39):

I don't think we should let each WG decide what words to use for the same elements ( e.g. active, status) I hate Is-mod and may be snarky in my version. so we need some canned text here for the common elements...

Eric Haas (Feb 15 2018 at 17:44):

e.g. status: "enteredInError changes the interpretation of the entire resource" Lloyd's words not mine

Eric Haas (Feb 15 2018 at 17:48):

e.g. active "a active value of false changes how this resource is interpreted "

Grahame Grieve (Feb 15 2018 at 20:16):

in fact, mostly you won't see status on that list, since I pre-canned text for that.

Grahame Grieve (Feb 15 2018 at 20:16):

I missed a few with spelling variations, and active

Grahame Grieve (Feb 15 2018 at 22:14):

Revised list:

Grahame Grieve (Feb 15 2018 at 22:14):

Eric Haas (Feb 16 2018 at 18:59):

for intent "these values change where the request fits into the workflow chain" [or some cleverer text from Lloyd]

Eric Haas (Feb 16 2018 at 19:02):

for doNotPerform "if true this negates the specified action"

Eric Haas (Feb 16 2018 at 19:03):

If these are ok I can go ahead and fill in the missing blanks across the board to get us started. The rest need to be divied out to the workgroups Thoughts on this plan?

Grahame Grieve (Feb 16 2018 at 19:53):

that'd be great thanks

Lloyd McKenzie (Feb 16 2018 at 21:25):

For "intent": "This element changes the interpretation of all descriptive attributes. For example "the time the request is recommended to occur" vs. "the time the request is authorized to occur" or "who is recommended to perform the request" vs. "who is authorized to perform the request"".

Eric Haas (Feb 16 2018 at 23:44):

Eric Haas (Feb 17 2018 at 02:55):

Except for a few datatypes, it looks like the spreadsheets never got updated to include the column "Modifier Reason". Did you want me to do that?

Grahame Grieve (Feb 17 2018 at 06:36):

yes you'll need to add the column where you need to provide a value

Eric Haas (Feb 20 2018 at 05:42):

just committed but the metatdataresource is not showing up for the confomance resources. Still getting

"Is Modifier true (Reason: null)"

Grahame Grieve (Feb 20 2018 at 05:46):

hmm I might to look at that

Last updated: Apr 12 2022 at 19:14 UTC

Main menu

FHIR Chat · Looking for Help · conformance

Stream: conformance

Topic: Looking for Help

Grahame Grieve (Feb 15 2018 at 10:56):

Grahame Grieve (Feb 15 2018 at 10:56):

Alexander Henket (Feb 15 2018 at 10:59):

Grahame Grieve (Feb 15 2018 at 11:59):

Grahame Grieve (Feb 15 2018 at 11:59):

Alexander Henket (Feb 15 2018 at 12:01):

Grahame Grieve (Feb 15 2018 at 12:02):

Alexander Henket (Feb 15 2018 at 12:04):

Alexander Henket (Feb 15 2018 at 12:05):

Ewout Kramer (Feb 15 2018 at 13:06):

Grahame Grieve (Feb 15 2018 at 13:15):

Eric Haas (Feb 15 2018 at 17:39):

Eric Haas (Feb 15 2018 at 17:44):

Eric Haas (Feb 15 2018 at 17:48):

Grahame Grieve (Feb 15 2018 at 20:16):

Grahame Grieve (Feb 15 2018 at 20:16):

Grahame Grieve (Feb 15 2018 at 22:14):

Grahame Grieve (Feb 15 2018 at 22:14):

Eric Haas (Feb 16 2018 at 18:59):

Eric Haas (Feb 16 2018 at 19:02):

Eric Haas (Feb 16 2018 at 19:03):

Grahame Grieve (Feb 16 2018 at 19:53):

Lloyd McKenzie (Feb 16 2018 at 21:25):

Eric Haas (Feb 16 2018 at 23:44):

Eric Haas (Feb 17 2018 at 02:55):

Grahame Grieve (Feb 17 2018 at 06:36):

Eric Haas (Feb 20 2018 at 05:42):

Grahame Grieve (Feb 20 2018 at 05:46):