FHIR Breaking changes between DSTU 2 ballot and final

From HL7Wiki
Jump to: navigation, search

A list of all the changes made to DSTU 2 after DSTU 2 ballot that were labelled 'non-compatible':

  • 2865 Clarify the functionality of GET [base]/[compartment]/[id]/?
  • 3011 CarePlan.activity.note needs further explanation
  • 3249 Profile.date should have a more meaningful name
  • 3361 Message endpoints should be associated with the event protocol
  • 3627 Value set - define/concept[0..*] needs additional wording
  • 3633 Change .expansion.timestamp datatype to dateTime
  • 3855 search param naming is inconsistent
  • 4003 Resource Encounter Content
  • 5165 Jan 2015 Ballot Comment #32
  • 5444 Jan 2015 Ballot Comment #337
  • 5457 Jan 2015 Ballot Comment #396
  • 5561 Composition.type and Composition.class defintions should be improved according to the improvements made to DocumentReference.
  • 5678 List.flag vocabulary
  • 5680 order of common resource elements not consistent
  • 5695 Medication should be required in MedicationStatement
  • 5698 Appointment.order can't work at present
  • 5701 MedicationStattement.wasNotGiven should notTaken
  • 5760 $translate does not suport dependsOn
  • 5895 is Order.authority part of 80%?
  • 5940 allow MedicationStatement.quantity to be either a quantity or range
  • 5947 Relationship between child concepts and subsumption needs clarification
  • 5951 Timing doesn't allow an overall duration
  • 5961 Change DiagnosticReport.name to .code
  • 5997 Rename Provenance.agent.reference[x]
  • 5998 ImagingStudy should use CodeableConcept, not Coding
  • 6029 More precise definitions of some concept map equivalence codes
  • 6040 StructureDefinition/ElementDefinition overlaps
  • 6067 Split Supply into SupplyRequest and SupplyDispense
  • 6079 StructureDefinition needs a target type property
  • 6089 Telecom doesn't allow for alternate systems
  • 6094 change 'subject' search parameter
  • 6104 Tooling should enforce coding capitalization consistency
  • 6118 409 status code
  • 6122 Support non-atomic transactions/batches in RESTful API
  • 6129 Change the Procedure attribute type to code
  • 6130 Change attribute name for Quantiy.code, Quantity.units, Quantity.system
  • 6171 Flag.patient should be [0..1]
  • 6215 roll up CarePlan.activity.detail.note into CarePlan.activity.notes
  • 6216 Goal.concern reference list
  • 6242 ImagingStudy.clinicalInformation shoiuld choice of string or Condition resource and possbile code?
  • 6253 body site should be a datatype - but used consisitantly throughout the standrard.
  • 6269 AuditEvent needs a Participant userId type code to explain how to understand the value in userId (e.g. Patient ID in CX form)
  • 6304 Abstract for Action Who/What/When/Where/Why across Resources
  • 6309 Allow reference to medication to be either a code or a Medication Resource Reference
  • 6310 Add MedicationStatementStatus for planned future medications
  • 6311 Need better explanation of DataElement Slicing
  • 6331 Clarify whether conditional operations in a transaction include [base]
  • 6336 "Executing an Operation Asynchronously" should be removed
  • 6343 The /Mailbox endpoint is no longer needed, given FHIR's "operations" framework
  • 6637 Add modifier to string parameters to indicate what kind of partial match is required
  • 6793 2015May sdc #10 - Use stringency, not specificity
  • 6868 2015May sdc #85 - Why unassessible?
  • 6913 2015May sdc #136 - How are "append" relationships handled?
  • 6922 2015May sdc #145 - Request that max count be unbounded
  • 6944 2015May core #9 - Make reason 0..*
  • 7018 2015May core #83 - Response: Specifying paging support would be a welcome addition and would further increase interoperability.
  • 7123 2015May core #182 - What's difference between Procedure.category and type?
  • 7127 2015May core #186 - Procedure.relatedItem is too complicated - make it extension
  • 7154 2015May core #213 - Explain reliability
  • 7347 2015May core #537 - Schedule.actor has resource type of "Any"
  • 7366 2015May core #556 - Why not avoid this problem by requiring contained resources to explicitly state their subject? Why allow this degree of optionality?
  • 7404 2015May core #594 - Is narrative the same for documents vs. other mechanisms?
  • 7428 2015May core #716 - Using of Snomed CT
  • 7431 2015May core #719 - AuditEvent source identifier
  • 7454 2015May core #742 - Can only one be declared as primary? Can none?
  • 7457 2015May core #745 - should allow for multiple Coding returned, with at most one marked as primary
  • 7460 2015May core #748 - Allow non-resources to be focus of Provenance
  • 7483 2015May core #778 - consistency of FamilyMemberHistory's condition with the Condition resource
  • 7511 2015May core #802 - Make names consistent between Procedure and Encounter
  • 7515 2015May core #806 - rename MedicationStatement.dosage.schedule to MedicationStatement.dosage.timing
  • 7517 2015May core #808 - Bring back Observation.component
  • 7518 2015May core #809 - Immunization.protocol cardinality
  • 7521 2015May core #812 - ICD-9 system URLs
  • 7525 2015May core #816 - MedicationStatement.status definitions
  • 7530 2015May core #821 - remove ElementDefinition.binding.name
  • 7541 2015May core #832 - Simply conditional create header
  • 7543 2015May core #834 - include transitiveness
  • 7545 2015May core #836 - transaction and base interaction
  • 7550 2015May core #841 - AllergyIntolerance negation
  • 7581 2015May core #872 - How do we specify an "active" or "resolved" problem?
  • 7583 2015May core #874 - We need a status to specify whether the med is "active" vs. "discontinued" meds?
  • 7585 2015May core #876 - GMDN FDA guidance: http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM369248.pdf
  • 7587 2015May core #878 - body site is overly complicated (Observation)
  • 7613 2015May core #904 - How is encounter diagnosis handled?
  • 7617 2015May core #908 - Is Working vs. Confirmed in the 80%?
  • 7621 2015May core #912 - Aren't these all similar items? Shouldn't they all be called target or detail?
  • 7622 2015May core #913 - Allow structures in notes, make 0..*
  • 7629 2015May core #920 - Suggest renaming to 'bodySite' or 'affectedSite'
  • 7631 2015May core #922 - Procedure.device -> targetDevice
  • 7633 2015May core #924 - Procedure has evolved since ProcedureRequest was drafted. Suggest re-aligning the two resources to account for changes in one, relevant to the other.
  • 7636 2015May core #927 - Should 'applies' be renamed to 'physiologicallyRelevant[x]'. While short names are good, they must also be more descriptive.
  • 7639 2015May core #930 - What's difference between has component and has member?
  • 7651 2015May core #942 - Need to categroize re-admissions
  • 7655 2015May core #946 - Recommend renaming this to referralRequestFulfilled
  • 7693 2015May core #984 - Who or what should sign a bundle and how is this used? RBAC? What happens if a transaction is not signed?
  • 7702 2015May core #993 - Can signature be captured by blob?
  • 7751 2015May core #1072 - Replace Provenance extension
  • 7753 2015May core #1074 - The use of the DocumentReference.confidentiality element is not conformant with the HCS requirements on Security Labels. This needs to be fixed.
  • 7760 2015May core #1081 - Add dependsOn element as an input Parameter with parts, and product as an output Parameter with parts.
  • 7761 2015May core #1082 - Allow ConceptMap/$translate to have multiple outcomes
  • 7859 2015May core #1179 - Condition.dateAsserted definition clarification
  • 7864 2015May core #1184 - Condition.clinicalStatus should not convey both record status (in error) and confirmation Status (working, confirmed, refuted)
  • 7867 2015May core #1187 - Add a record status to communicate active, in error, cancelled
  • 7894 2015May core #1214 - Rename AllergyIntolerance.event
  • 7897 2015May core #1217 - Should immunization be searchable by subject since there is no subject parameter (if yes, should AllergyIntollerance be searchable by subject?)
  • 7906 2015May core #1226 - Encounter condition relationship
  • 7913 2015May core #1233 - MedicationStatement.status clarification
  • 7924 2015May core #1244 - Clarify content-location for Reads without Versioning support
  • 7954 2015May core #1274 - Remove _language query parameter support
  • 7957 2015May core #1277 - Alternative suggestion for Date Ranges
  • 7961 2015May core #1281 - Modify Name of Substance.Type Property
  • 8002 2015May core #1326 - Add mode parameters as a value set.
  • 8043 2015May core #1368 - Change  Resource Contraindication to DetectedIssue
  • 8045 2015May core #1370 - Medication Prescription Status Values
  • 8105 DocumentReference.format needs to be type Codeing
  • 8107 Update the definition of "status" for the MedicationStatement
  • 8112 Recommend adding 'On-Hold' to MedicationStatement.status
  • 8120 Consider Location.status "present"
  • 8123 AuditEvent constraints are too tight
  • 8142 2015May daf #96 - Modify Content Search Parameters
  • 8163 Transaction processing sequence should reflect bundle entry sequence
  • 8172 transaction-operation coding system doesn't correspond to transaction-operation value set
  • 8184 Add reference to Condition
  • 8188 ConceptMap structure doesn't make sense
  • 8198 MAY2015 QICore#70 - Change CommunciationRequest.orderedOn to requestedOn
  • 8204 URI for Medical Device Codes defined in ISO 11073-10101 is wrong
  • 8210 2015MAY QICore#85 Goal.patient cardinality
  • 8226 ValueSet.url should be ValueSet.uri
  • 8230 Display for filter-operator "=" code is " "
  • 8236 terminology system URL syntax
  • 8246 Signature.who can have every dataType in fhir-single.xsd
  • 8265 ValueSet.compose.include should have codes or filters, but not both
  • 8281 Rename ProcedureRequest.timing[x] to scheduled[x]
  • 8313 Change terminology for AllergyIntolerance.type
  • 8343 j.equivalence definition and valueset detfinition contradict each other
  • 8354 ValueSet.define should be renamed to ValueSet.codeSystem
  • 8355 valueOrdinal should be decimal, not integer
  • 8363 No place for a displayname in SearchParameter
  • 8370 We're ambiguous about allowing relative urls for reference-type search parameters
  • 8372 Support multiple discharge diagnoses
  • 8379 Observation indirect target is confusing
  • 8386 LOINC copyright query should not allow "All" as a value
  • 8416 Remove batch operations now that we have a batch interaction
  • 8418 Add Period to Group Characteristic
  • 8437 Remove Social Security Number from the Identifier type value set and improve definition
  • 8440 Change references from Supply to SupplyRequest
  • 8441 Provide support for a CodeableConcept for answer to question
  • 8449 OperationOutcome.issue.code is either extendable CodeableConcept or not Code - Prefer extendable
  • 8450 OperationOutcome.issue.location is unfriendly to JSON based applications only using HTTP Get parameters
  • 8498 DocumentReference.format belongs inside content
  • 8504 change DR.requestdetail to DR.request to harmonize with PC resources
  • 8509 Conformance should have a "kind"
  • 8510 Rename NamingSystem.type to NamingSystem.kind
  • 8511 NamingSystem.country and .category should become useContext
  • 8512 NamingSystem.category should have same binding as Identifier.type
  • 8514 change name of element serviveCategory to category
  • 8521 Questionnaire Extension defaultasfixed - clarification
  • 8551 create and extension for O.refrange to allow for ...or equal to

All tasks (inclduing the list above)


  • 2840 Address can't differentiate physical and postal
  • 2865 Clarify the functionality of GET [base]/[compartment]/[id]/?
  • 3006 4.15.6 Resource Observation - Examples need to show related propert in use for panel and calculated measurement
  • 3011 CarePlan.activity.note needs further explanation
  • 3063 Simplification of Schemas #4 - use the
  • 3090 Conformance SearchParams should be more powerful
  • 3123 CarePlan.participant.role needs a value set
  • 3129 Profile.structure.element.definition.type.profile should repeat
  • 3151 Parent concept in medication-form-codes and medication-package-form-codes is wrong
  • 3228 Need rules for tags invalidated by an update
  • 3249 Profile.date should have a more meaningful name
  • 3297 Add a warning about the safety implications of not conforming to the specification
  • 3317 Patient/RelatedPerson/Organization search key 'phonetic' lacks path definition
  • 3342 contained resources overrepresented in examples
  • 3358 Need to clarify what's in-scope for resources vs. profiles
  • 3361 Message endpoints should be associated with the event protocol
  • 3478 Add DateTime to the Attachment data type
  • 3501 Practitioner address data model not rich enough to capture needed information in all countries
  • 3511 Add detail to Value Set Expansion Definition
  • 3534 Need a formal support mechanism for i18n and l10n of schemas and schematrons
  • 3598 Add support for multiple designations on concepts
  • 3624 Add a property for comments to the JSON format
  • 3625 Create "best practice" guide for creating a "system URI" for Coding
  • 3627 Value set - define/concept[0..*] needs additional wording
  • 3633 Change .expansion.timestamp datatype to dateTime
  • 3655 Need to allow for Patient's where there's no indication of human vs. animal
  • 6206 display text is wrong fro example
  • 3760 Clarify when OperationOutcome rather than another resource is appropriate
  • 3792 FHIR ebook not valid
  • 3800 $validate and $translate should allow multiple repetitions
  • 3802 Specify what it means for a search parameter to matches a complex datatype
  • 3807 Should add rationale to Invariant
  • 3810 Resource package/profile list should link directly to profile if only one is defined for unique id
  • 3819 Need to allow Observation.related.target to be QuestionnaireAnswers in addition to Observation
  • 3820 Need to add support for message polling and message querying
  • 3836 Add constraining base node searches through ConformanceProfile
  • 3855 search param naming is inconsistent
  • 3873 Explicitly specify resource/element types throughout?
  • 3874 Referenced system vakue "http://hl7.org/fhir/message-type" seems incorrect
  • 3918 usability issues with "address" as a search parameter for patient
  • 4003 Resource Encounter Content
  • 4038 Expand the definition of CarePlan.concern
  • 4872 Communication support for phone calls
  • 5164 Jan 2015 Ballot Comment #30
  • 5165 Jan 2015 Ballot Comment #32
  • 5182 Jan 2015 Ballot Comment #56
  • 5194 Jan 2015 Ballot Comment #69
  • 5308 Jan 2015 Ballot Comment #187
  • 5313 Jan 2015 Ballot Comment #192
  • 5319 Jan 2015 Ballot Comment #199
  • 5368 Jan 2015 Ballot Comment #254
  • 5369 Jan 2015 Ballot Comment #255
  • 5371 Jan 2015 Ballot Comment #257
  • 5374 Jan 2015 Ballot Comment #261
  • 5378 Jan 2015 Ballot Comment #265
  • 5381 Jan 2015 Ballot Comment #268
  • 5383 Jan 2015 Ballot Comment #270
  • 5384 Jan 2015 Ballot Comment #271
  • 5386 Jan 2015 Ballot Comment #273
  • 5387 Jan 2015 Ballot Comment #274
  • 5388 Jan 2015 Ballot Comment #275
  • 5395 Jan 2015 Ballot Comment #284
  • 5444 Jan 2015 Ballot Comment #337
  • 5457 Jan 2015 Ballot Comment #396
  • 5458 Jan 2015 Ballot Comment #397
  • 5459 Jan 2015 Ballot Comment #398
  • 5460 Jan 2015 Ballot Comment #399
  • 5461 Jan 2015 Ballot Comment #400
  • 5471 Jan 2015 Ballot Comment #407
  • 5473 Jan 2015 Ballot Comment #409
  • 5474 Jan 2015 Ballot Comment #410
  • 5479 Jan 2015 Ballot Comment #416
  • 5480 Jan 2015 Ballot Comment #417
  • 5483 Jan 2015 Ballot Comment #420
  • 5495 Jan 2015 Ballot Comment #432
  • 5509 Jan 2015 Ballot Comment #446
  • 5518 Update example f201 to use dose, timing, and medication (remove the todos)
  • 5520 Clarify the relationship of Medication.package and Medication.product
  • 5535 Include common resource elements in resource profile definitions
  • 5541 Add best practice narrative on suppressing data for client access of a resource
  • 5549 Expansion and compose should allow for caseSensitive or define should loose the attribute
  • 5553 Resource Ownership
  • 5561 Composition.type and Composition.class defintions should be improved according to the improvements made to DocumentReference.
  • 5624 create UDI examples for device
  • 5633 Consider choice of code|Reference(Medication) or code|Reference(Medication|Substance)
  • 5644 Follow up on #3600 Change MedAdmin.dosage.site to .bodySite choice of codeableConcept|reference(BodySite)
  • 5652 Be specific that JSON format must be UTF-8 just like XML
  • 5661 Add 'active' On Practitioner Resource
  • 5665 To add new datatype for multichannel recording data
  • 5666 .identifier - bring consistency to the cardinality and type across resources
  • 5672 maintaining order within FHIR resources for list items
  • 5678 List.flag vocabulary
  • 5680 order of common resource elements not consistent
  • 5690 Patient Entered/Reported Data
  • 5694 Request for new security label for when content is removed from a resource for operational reasons
  • 5695 Medication should be required in MedicationStatement
  • 5701 MedicationStattement.wasNotGiven should notTaken
  • 5713 Add "proposed" status to the Appointment resource
  • 5720 MedicationAdministration.status should be marked as a modifier
  • 5721 MedicationStatement.status should be marked as a modifier
  • 5732 Add Organization reference to Order.source
  • 5749 Need extensions for capturing formal mapping paths for data elements
  • 5759 Jan 2015 Ballot Comment #455
  • 5760 $translate does not suport dependsOn
  • 5761 Consider Adding Precondition to MedicationStatement
  • 5762 Dosage Instructions on Medication Dispense
  • 5786 Are there other ways of doing UI hinting than a heirarchy in the expansion
  • 5787 Do we need support for active/inactive in expansions?
  • 5789 can we be more specific about date and filter parameters on expansion
  • 5790 Improve documentation around value set expansion currency
  • 5794 Define "all known value sets" magic URI as part of the spec
  • 5800 Server Validation of CodeSystem.define.system
  • 5801 Should code system name be a service provider specific identifer?
  • 5802 How should display text case be handled on validate - case sensitive or not?
  • 5803 Add concept map link extension
  • 5806 Administration of medication to a patient
  • 5820 AllergyIntolerance.event.description vs AllergyIntolerance.event.comment
  • 5826 FamilyHistory negation
  • 5829 Specimen needs status code
  • 5844 Identification of Value Sets Used in a Profile
  • 5846 typo in MedicationAdministration.dosage.rate
  • 5847 MedicationAdministration.dosage.rate where no duration is needed
  • 5861 MedicationPrescription.dosageInstruction.scheduled[x] naming inconsistency
  • 5870 Alert should have encounter
  • 5872 Add extension to link OperationOutcome and Contraindication
  • 5880 Recognition in FHIR specificaiton of profiles from other organizations
  • 5882 Value set should explain how master files are handled
  • 5892 Medication Package Form Codes wrong?
  • 5893 Note Immunization Resource Can Record Historical Immunizations
  • 5895 is Order.authority part of 80%?
  • 5896 Name of MedicationPrescription
  • 5911 Consider 'dateEnded' for MedicationPrescription
  • 5912 Consider 'reasonEnded' codeable concept for MedicationPrescription
  • 5916 Clarify MedicationStatement usage
  • 5926 Invariants should be on MedicationStatement
  • 5928 FHIR specification and build system must be refactored
  • 5935 "Break the Glass" Method Description in Security Labels Section is Very Limiting
  • 5940 allow MedicationStatement.quantity to be either a quantity or range
  • 5941 Clarify boundary between MedicationAdministration and MedicationStatement
  • 5944 Clarify what elements of valueSet constitute the Content Logical Definition
  • 5946 hostname instead of URL for LOINC
  • 5947 Relationship between child concepts and subsumption needs clarification
  • 5949 relationship between dosage.text and dosage.Scheduled[x]
  • 5951 Timing doesn't allow an overall duration
  • 5956 Additional Questionnaire layout hints - horizontal, autocomplete and select
  • 5961 Change DiagnosticReport.name to .code
  • 5965 Status values for MedicationStatement can conflict with effective[x]
  • 5966 Composition section content should come before a nested section
  • 5972 Weird-looking flags
  • 5973 Superseded is misspelled
  • 6336 "Executing an Operation Asynchronously" should be removed
  • 5981 Need to be able to specify a value set identity by reference to a binding (e.g. element definition) in value set operations
  • 5982 mixing of dates and versioning
  • 5983 Unexpected behaviour specifyiing binding strength
  • 5987 remove isSummary from Resource Definintion
  • 5992 Wrong VS expansion: http://hl7.org/fhir/vs/medication-form-codes
  • 5993 Wrong VS expansion: http://hl7.org/fhir/vs/medication-package-form-codes
  • 5994 MedicationAdministration.medication description misleading
  • 5996 Proposal to add _narrative parameter to REST api
  • 5997 Rename Provenance.agent.reference[x]
  • 5998 ImagingStudy should use CodeableConcept, not Coding
  • 6019 Need a common extension to allow goals to be referenced from other resources
  • 6022 Change short description of .perfomer
  • 6023 Minimum cardinality of ProcedureRequest.subject should be 0
  • 6025 Need rules for stringency
  • 6032 Too many things 1..x in DocumentReference
  • 6034 NDF-RT link on Named Systems List page 404s
  • 6040 StructureDefinition/ElementDefinition overlaps
  • 6041 durationMax not present in Repeat element of Timing resource
  • 6042 Terminology services page: validate-code replaces validate
  • 6043 Questionnaire.$populate - subject parameter type should be Reference(Any) not Any
  • 6044 Questionnaire - needs a subject type element
  • 6045 Sort - specification is unclear about whether sort is case sensitive or not
  • 6046 Questionnaire.$populate - content parameter type should be Any, not string
  • 6048 Signature should allow device resources
  • 6060 Documentation of extensions for simple types
  • 6061 Typos
  • 6066 Expand [x] type element in profile unspecified types in the snapshot
  • 6067 Split Supply into SupplyRequest and SupplyDispense
  • 3791 create examples tab for extensions
  • 6077 Complex extensions aren't rendering properly
  • 6078 LOINC mappings for data element should be to database columns
  • 6079 StructureDefinition needs a target type property
  • 6080 CAP example isn't showing up in ballot
  • 6084 MedicationPrescription misspelled as MedicationPescription in several places
  • 6085 Add discussion of profile consistency to profile page
  • 6087 No way to specify multiple bindings (with different strengths)?
  • 6088 We still need Physical vs. Postal address
  • 6089 Telecom doesn't allow for alternate systems
  • 6091 Add Device.note
  • 6092 Individual Resource pages do not align with Resource names
  • 6093 Differential element[x] is expanded to element
  • 6094 change 'subject' search parameter
  • 6096 Bundle resource has no elements that are marked as "in summary"
  • 6097 Conceptmaps are not part of validation.zip
  • 6098 Extension Initial presumed answer for question - request for more detail surrounding
  • 6099 Should have style and markup on Question.text and Group.text
  • 6100 change enternalFormula.rate to type quantity
  • 6101 Miove .enteralformula.schduled next to .quantity
  • 6102 move enrteraformula.administrationinstruction to end
  • 6103 provide guidance in notes section on how to use the resource for a continuous vs a bolus enteral feeding
  • 6104 Tooling should enforce coding capitalization consistency
  • 6105 Appointment notes section could use a diagram or two
  • 6106 add a entry for a single file containing all the structure definition datatype and resource
  • 6107 broken link in patient example
  • 6108 Clarify FHIR server behavior (http codes, body, outcome etc) while CREATE with id, UPDATE without id
  • 6109 HTTP codes ValueSet
  • 6111 change type for rate change trom quatnity to rate
  • 6113 Summary needs to be updated
  • 6115 add elements to Address data type
  • 6116 Parameters resource is missing in listings
  • 6118 409 status code
  • 6121 Content-Type,_format,accept,Accept-Charset
  • 6122 Support non-atomic transactions/batches in RESTful API
  • 6125 Profiling should document rules for documentation & mappings
  • 6126 Make clear that RelatedPerson and Practitioner can be animals
  • 6127 ValueSet profile should support additional instruction on codes
  • 6128 Change vaccineType to vaccineCode
  • 6129 Change the Procedure attribute type to code
  • 6130 Change attribute name for Quantiy.code, Quantity.units, Quantity.system
  • 6131 CarePlan could benefit from a reference to EpisodeOfCare
  • 6132 Add Problem to ConditionCategory
  • 6133 change "list" to "see List of Resources"
  • 6134 Change 'This resource is extends resource" to 'This resource is extends the base Resource'
  • 6135 move hyperlink to resources adn Capitalize
  • 6136 change "concept" to "concept code" or "code"
  • 6138 Validator not handling references to contained resources
  • 6139 Resource.Id and Resource.meta not in summary
  • 6140 Schema error for Age, Count, etc.
  • 6144 remove table showing conformance/extensibility combinations
  • 6145 typo in example
  • 6147 Typo in text for DomainResource Resource
  • 6148 Typo in text for searhc parameter
  • 6149 missing text? in bundle transaction discussion
  • 6151 structureDefintion notes section does not apply - typo?
  • 6152 typo in 6.17.5.2
  • 6153 Conformance.rest.security.service should be extensible
  • 6154 Does Conformence need a RevIinclude list?
  • 6155 Refers to StructureDefinition wheras much of the discussion is about ElementDefinition
  • 6156 should this section refer to the section on revinclude?
  • 6157 replace this section or refer to Bundle text from 6.8.3.5
  • 6158 fix link
  • 6159 correct typo
  • 6160 fix typo
  • 6162 fix typo
  • 6163 no example of JSON comments found -need explicit example references or shown
  • 6164 fix uml for timing datatype
  • 6166 when and how to use AppointmentResponse.participantType
  • 6167 need more clear clarification
  • 6169 vsd 1 expansion.value for is wrong
  • 6170 Clarify use of flag.category
  • 6171 Flag.patient should be [0..1]
  • 6172 no example for named query
  • 6173 Parameters resource not listed on resource page
  • 6174 add link
  • 6175 change text to avoid using term 'list'
  • 6176 clarfiy what is meant by 'subject resource '
  • 6177 fix typo
  • 6178 provide claricifaction to profile tags
  • 6179 Narrow down composition.section.code value set
  • 6180 Bining types need to be updated in this section
  • 6181 Code restriction regex is wrong
  • 6184 BCP-13 and BCP-47 should be in the coding system list
  • 6187 need to also refer to both SturctureDefinition and ElementDefintion
  • 6188 differnec between profile types is unclear
  • 6189 differential view should only show what is different
  • 6190 There are two Clinical Document profiles in Spec?
  • 6191 broken links
  • 6193 change name of section
  • 6194 remove the parenthetical resources
  • 6195 Include reference to fulfillment of referral request
  • 6196 propose boundaries for DO
  • 6199 add boundaries section to DR
  • 6200 remove background and context section from DR
  • 6201 Add referral creation date
  • 6202 redo Background and Context section
  • 6205 refer to .neme which is missing
  • 6207 Improve the description for .event.detail
  • 6208 Allow Organization in flag.author
  • 6209 Unclear how to represent non-medical devices
  • 6212 create at least example binding
  • 6214 detail.product what about diet/ nutrional suppliements
  • 6215 roll up CarePlan.activity.detail.note into CarePlan.activity.notes
  • 6216 Goal.concern reference list
  • 6218 change name to sodium and 'fluid' restircted
  • 6219 medication form bound to dosage route VS
  • 6223 why not have a reference to the MedicationDispense Resource for reference to dosing details
  • 6226 Search summary table misses entry for _query
  • 6229 extension definition still very hard to read
  • 6233 AuditEvent confusion on 'idenfier' elements that are actually strings. Affects understanding as well as search (which should not be token)
  • 6234 suggestion to add a feature like _fields
  • 6235 Invalid namespace prefix xs:xs:gYear in primitive profile XML
  • 6238 Is WADO-RS equivalent to " DICOM contexts " and "DICOM constructs"
  • 6239 many descritiption contain paranthetical ids - a legend would be nice to explain what they mean
  • 6240 with identifier.type does is make sense to roll up multiple identifier or keep as separate idenetifiers
  • 6241 Retrieve URI (0008,1190) is confusing name
  • 6242 ImagingStudy.clinicalInformation shoiuld choice of string or Condition resource and possbile code?
  • 6243 .procedure needs at least an example binding and should there be a choice with procedure resource
  • 6244 ImagingStudy.series.instance.content comment is wrong
  • 6245 Suggest hyperlinks to referenced standards WADO and DICOM
  • 6246 add choice ImagingObjectSelection to DiagnosticReport.imagingStudy
  • 6248 add unkown to Value Set http://hl7.org/fhir/vs/animal-genderstatus and make required
  • 6251 Communication.payload.content[x] definition is too narrow
  • 6252 Timing.repeat.count must support ranges and decimal type.
  • 6253 body site should be a datatype - but used consisitantly throughout the standrard.
  • 6256 define entity and how is different from agent
  • 6257 Need additional prefixes for date search parameters
  • 6258 Extension Reference to the DeviceMetric resource - Definition not needed
  • 6259 constrain out Device from .device in DeviceMetricObservation profile
  • 6266 Please Clarify "Data Element vs. Codes" section
  • 6269 AuditEvent needs a Participant userId type code to explain how to understand the value in userId (e.g. Patient ID in CX form)
  • 6271 Subject of flag
  • 6272 IHE multiple extension point review request
  • 6273 fix typo
  • 6277 Minor editorial fix
  • 6279 Modifier listing should be consistent all be listed in one place (split up)
  • 6298 unable to review adverse event dus to pub issues
  • 6302 ValueSetCategory has no values listed yet is a required binding
  • 6304 Abstract for Action Who/What/When/Where/Why across Resources
  • 6307 Specify dot-notation for element name
  • 6029 More precise definitions of some concept map equivalence codes
  • 6308 Wording improvement for Extensible binding
  • 6309 Allow reference to medication to be either a code or a Medication Resource Reference8112
  • 6310 Add MedicationStatementStatus for planned future medications
  • 6311 Need better explanation of DataElement Slicing
  • 6312 Body Site used to collect specimen is part of Specimen resource not Observation
  • 6313 Distinction between Observation and QuestionnaireAnswers unclear
  • 6318 Bundle.entry.search.mode only captures one status
  • 6320 Clarify distinction between ElementDefinition.defaultValue vs. ElementDefinition.meaningWhenMissing
  • 6321 Improve the mechanism for auto-generating StructureDefinition ids in build tool
  • 6324 JSON views: "canonical form" links broken
  • 6325 ElementDefinition.short should not refer to "generated XML format"
  • 6326 How does OperationOutcome communicate limitations imposed by security?
  • 6327 Descriptions of multiple-cardinality fields should be uniformly expressed in the singular (or plural)
  • 6328 Bundle.entry.resource should be defined as "Resource" (not "Resources")
  • 6329 Clarify description of Bundle.entry.transaction.url
  • 6330 Need a consistent way to refer to quoted values in FHIR spec
  • 6331 Clarify whether conditional operations in a transaction include [base]
  • 6332 Clarify the justification for requiring a "transaction" in history bundle entries
  • 6333 Example reference to Binary content should use a capital "B"
  • 6334 Why do Condition.onset and Condition.abatement have different datatypes?
  • 6335 OperationDefinition should distingush parameters that are Resourecs vs. References
  • 6337 elementdefinition-examples.html should link to structuredefinition-examples.html
  • 6338 Missing "raw" link for some JSON pages
  • 6339 Are slicing discriminators compatible with `pattern[x]` constraints in ElementDefinition?
  • 6340 How do StructureDefinitions treat [x] values?
  • 6341 Slicing examples need to be updated (Observation.name no longer exists)
  • 6342 Clarify the "literal" vs "logical" behavior of :in modifier for search
  • 6343 The /Mailbox endpoint is no longer needed, given FHIR's "operations" framework
  • 6344 Explain how to achieve the behavior or "valueBoolean" for Observations
  • 6345 Clarify how DocumentReference.type and DocumentReference.class differ
  • 6346 DocumentReference should have a reference to Encounter
  • 6347 Timing examples should break "period+units" into two columns
  • 6354 Provenance mapping to W3C specification
  • 6355 Requirements column in profile spreadsheet does not get filled in for generated profile
  • 6365 Improve documentation about element
  • 6578 NamingSystem bundle for FHIR distibution
  • 6629 Define system URIs for common coding systems
  • 6630 Patient.deceased search parameter has wrong xpath
  • 6637 Add modifier to string parameters to indicate what kind of partial match is required
  • 6783 Add a bundle of NamingSystems for known code systems/identifiers
  • 6784 2015May sdc #1 - Can answer lists be independent of questions?
  • 6785 2015May sdc #2 - Multi-code system value sets are bad
  • 6793 2015May sdc #10 - Use stringency, not specificity
  • 6797 2015May sdc #14 - Show the actual data type for References
  • 6798 2015May sdc #15 - Explain usefulness in other jurisdictions
  • 6799 2015May sdc #16 - Warn about schema-centric implementation.
  • 6801 2015May sdc #18 - Explain different id types
  • 6803 2015May sdc #20 - Explain how ConceptMap works better
  • 6807 2015May sdc #24 - Explain usage of value sets in SDC-context
  • 6809 2015May sdc #26 - 404 on link to SDC wiki
  • 6810 2015May sdc #27 - Explain what "options" means
  • 6811 2015May sdc #28 - Can type be a code?
  • 6815 2015May sdc #32 - Can root group be non-required?
  • 6817 2015May sdc #34 - Add invariant on cardinality extensions to repeat
  • 6818 2015May sdc #35 - Duplicate extensions
  • 6821 2015May sdc #38 - Reference to Questionnaire should be profile-specific
  • 6823 2015May sdc #40 - Fix indirect link
  • 6826 2015May sdc #43 - Change referenced QuestionnaireAnswer resource to "QuestionnaireAnswers".
  • 6827 2015May sdc #44 - Fix page numberings
  • 6828 2015May sdc #45 - Define terminology for Questionnaire category extension
  • 6829 2015May sdc #46 - Declare references as Reference(x)
  • 6831 2015May sdc #48 - Missing/bad links
  • 6832 2015May sdc #49 - JSON template not in All view
  • 6833 2015May sdc #50 - Links to structure definitions don't resolve
  • 6834 2015May sdc #51 - XML representation for last "value*" element should have the entire element crossed out not just its description.
  • 6836 2015May sdc #53 - Missing publisher
  • 6837 2015May sdc #54 - Consistent in use of terms. For example, CCDA and C-CDA.
  • 6838 2015May sdc #55 - TOC did not list all sections.
  • 6839 2015May sdc #56 - remove extra "/" at end and relace with "."
  • 6840 2015May sdc #57 - Labels on different tabs should be different
  • 6841 2015May sdc #58 - change FHIR version from 0.2 to 0.5.0
  • 6846 2015May sdc #63 - Diagram references "template"
  • 6850 2015May sdc #67 - What's behavior for modifier extensions?
  • 6853 2015May sdc #70 - Add authorization qualifier to 'read'
  • 6862 2015May sdc #79 - Small XSD facets issue.
  • 6868 2015May sdc #85 - Why unassessible?
  • 6882 2015May sdc #99 - data types inconsistent
  • 6883 2015May sdc #100 - Cardinality change from 0..1 to 0..*
  • 6885 2015May sdc #102 - Change the term EMR to EHR.
  • 6886 2015May sdc #103 - Change CER to PCOR
  • 6887 2015May sdc #104 - Change to PCOR use case
  • 6888 2015May sdc #105 - Reword introduction section
  • 6889 2015May sdc #106 - Forms are not part of an EHR
  • 6893 2015May sdc #110 - Correct link
  • 6895 2015May sdc #112 - Make endpoint 1..*
  • 6897 2015May sdc #114 - Resource is impenetrable
  • 6898 2015May sdc #115 - Repetition spelled incorrectly
  • 6899 2015May sdc #116 - Add pre-population
  • 6901 2015May sdc #118 - Explain signatures of forms with Provenance
  • 6904 2015May sdc #126 - Why are extensions needed for answer list?
  • 6905 2015May sdc #127 - Why is options a reference rather than a list of embedded content
  • 6906 2015May sdc #128 - How do you nest questions under answers?
  • 6907 2015May sdc #130 - Valueset could not be expanded
  • 6910 2015May sdc #133 - why does the sentences states value set has 0 concepts?
  • 6911 2015May sdc #134 - Duplicate "used in"
  • 6912 2015May sdc #135 - Episodes of Care can overlap and reference the same encounter
  • 6913 2015May sdc #136 - How are "append" relationships handled?
  • 6914 2015May sdc #137 - removal of the sentence, removes the issue.
  • 6917 2015May sdc #140 - Simply wording about Narrative
  • 6918 2015May sdc #141 - What's relationship between class and type
  • 6919 2015May sdc #142 - Assert no context flow
  • 6920 2015May sdc #143 - Add Author to list
  • 6922 2015May sdc #145 - Request that max count be unbounded
  • 6923 2015May sdc #146 - Request that max count be unbounded
  • 6925 2015May sdc #148 - Inclusion of pagers for contact
  • 6927 2015May sdc #150 - A requested fix for profiling.
  • 6928 2015May sdc #151 - Make Race and Ethnicity core
  • 6931 2015May sdc #154 - Distinguish primary contact
  • 6934 How does escaping work in composite URI searches?
  • 6935 Provide example post requests for complex operations such as the different variants of $validate-code
  • 6937 2015May core #2 - Add description to AllergyIntolerance
  • 6938 2015May core #3 - Appointment/Encounter Referencing
  • 6944 2015May core #9 - Make reason 0..*
  • 6945 2015May core #10 - Makre reasonReference 0..*
  • 6946 2015May core #11 - Typo on goal
  • 6947 2015May core #12 - Add CarePlan.description
  • 6949 2015May core #14 - Expand on potential uses
  • 6950 2015May core #15 - Message can be sent to many receipient (recipient 0..*). How will the sender know if the message was received by all of them?
  • 6952 2015May core #17 - Explain contraindication.author
  • 6954 2015May core #19 - Clarification needed - is this who authored the documents in the set? Or is this who authored the document manifest?
  • 6955 2015May core #20 - Typo - throuh needs a g
  • 6956 2015May core #21 - Typo - change my to by
  • 6958 2015May core #23 - Need to identify generic maternal/paternal relationships without specific family member
  • 6960 2015May core #25 - Typo - remove "for use"
  • 6969 2015May core #34 - typo - fix location of opening parenthesis.
  • 6972 2015May core #37 - Make address 0..*
  • 6975 2015May core #40 - GET should be POST, name changed
  • 6977 2015May core #42 - GET should be POST, name is wrong
  • 6983 2015May core #48 - Missing www
  • 6984 2015May core #49 - Unabreviate name
  • 6985 2015May core #50 - No detail regarding the Risk Assessment issue
  • 6963 2015May core #28 - ?Typo - Change note to list
  • 6986 2015May core #51 - Typo: missing closing bracket
  • 6987 2015May core #52 - In the notes, the incorrect line is stated in reference to the resource's id
  • 6988 2015May core #53 - Make last updated match last-modified
  • 6989 2015May core #54 - Add HTTP headers to example
  • 6990 2015May core #55 - Change "SearchResults" -> Bundle
  • 6991 2015May core #56 - Incorrect line number for meta.lastUpdated
  • 6992 2015May core #57 - Incorrect line number for base
  • 6993 2015May core #58 - Incorrect line number for total
  • 6994 2015May core #59 - Incorrect line number for link
  • 6995 2015May core #60 - "item" should be "entry" with correct line number
  • 6996 2015May core #61 - Typo in word "exist"
  • 6997 2015May core #62 - Incorrect line number for id
  • 6998 2015May core #63 - It would be useful to have the Update Response return an HTTP Location header with the Updated Resource's new location on the service.
  • 6999 2015May core #64 - Spelling typo
  • 7000 2015May core #65 - Unclosed bracket typo.
  • 7001 2015May core #66 - "[Missing]" suggests the spec is incomplete.
  • 7002 2015May core #67 - Use "individual resource level"
  • 7003 2015May core #68 - Invariants Section content missing
  • 7004 2015May core #69 - Table contains a number of values under Status with "Unknown - not stated by committee"
  • 7005 2015May core #70 - Typo in word "that"
  • 7006 2015May core #71 - Typo in word "is"
  • 7007 2015May core #72 - TBD in table of registries
  • 7008 2015May core #73 - Missing section on Canonical XML
  • 7009 2015May core #74 - todo - develop this at top of section
  • 7011 2015May core #76 - remove references to value set from Coding
  • 7013 2015May core #78 - Missing introduction or no introduction?
  • 7014 2015May core #79 - Content is "todo"
  • 7015 2015May core #80 - Missing link
  • 7016 2015May core #81 - Response: Happy with mandatory SSL/TLS+Server Certificate, and optional client certificate authentication.
  • 7017 2015May core #82 - Spelling typo
  • 7018 2015May core #83 - Response: Specifying paging support would be a welcome addition and would further increase interoperability.
  • 7019 2015May core #84 - Spelling typo
  • 7020 2015May core #85 - Grammar around "the criteria is expressed.".
  • 7021 2015May core #86 - Typo around "On"
  • 7022 2015May core #87 - client makes the call, not the server
  • 7023 2015May core #88 - It would be useful and informative to demonstrate how this process fulfills the original problem statement in the beginning of this section.
  • 7024 2015May core #89 - Typo around "if they are do not"
  • 7025 2015May core #90 - Missing content / TODO
  • 7026 2015May core #91 - Disagree with timezone approach
  • 7027 2015May core #92 - Missing content / TODO
  • 7030 2015May core #95 - State whether translation codes are allowed and evaluated
  • 7031 2015May core #96 - State whether translation codes are allowed and evaluated
  • 7032 2015May core #97 - Reference to feed.category is incorrect.
  • 7033 2015May core #98 - More documentation for "cert"
  • 7034 2015May core #99 - Content comes from SDC
  • 7036 2015May core #101 - Specification generation/tooling error
  • 7038 2015May core #103 - Missing content
  • 7039 2015May core #104 - List includes "Other" instead of "Basic"
  • 7041 2015May core #106 - It would be helpful if this value set had a code to indicate a List is accurate within the context it is used in
  • 7042 2015May core #107 - Missing content / TODO
  • 7043 2015May core #108 - Add constraint around Locked Date wrt referenced versions
  • 7044 2015May core #109 - Is the code list complete and sufficient?
  • 7047 2015May core #112 - Explain relationship between AllergyIntolerance and RiskAssessment
  • 7052 2015May core #117 - Agree, this isn't necessary.
  • 7053 2015May core #118 - What is the recommended approach for recording alerts?
  • 7054 2015May core #119 - Typo
  • 7055 2015May core #120 - Explain how No Known Allergies is handled
  • 7056 2015May core #122 - Did you consider making the status mandatory (1..1)? What does it mean when an AllergyIntolerance is retunred with this field empty?
  • 7058 2015May core #124 - The movement of sunlight out of this resource directly is different than the design in C-CDA design.
  • 7059 2015May core #125 - Remove sentence on 5%
  • 7040 2015May core #105 - Spelling typo
  • 7060 2015May core #126 - Typo
  • 7061 2015May core #127 - Add mime type list
  • 7069 2015May core #128 - Is the person that Authored the plan always the one responsible for the plan? Would it better to say who 'wrote' the plan?
  • 7070 2015May core #129 - Please add a suggested value set
  • 7072 2015May core #131 - Did you consider making the title 1..1 if the section is present?
  • 7073 2015May core #132 - What is the use case for not having a title?
  • 7075 2015May core #134 - there's is misspelled
  • 7076 2015May core #135 - Remove "are"
  • 7077 2015May core #136 - resource misspelled
  • 7078 2015May core #137 - whether should not be capitalized
  • 7079 2015May core #138 - Copy and paste from 1.12.2
  • 7080 2015May core #139 - Copy and paste from 1.12.2
  • 7081 2015May core #140 - "that" should be "than"
  • 7082 2015May core #141 - "an" should be "a"
  • 7083 2015May core #142 - Missing "IDs"?
  • 7084 2015May core #143 - Is there a need for a non-bulleted list? list-style-type:none
  • 7086 2015May core #145 - Should communcation also include a prefered method such as sign language, Braille, email, telephone, etc.
  • 7087 2015May core #146 - Is the priority property the patient's priority or the practicioner's priority? Shouldn't both be represented as they may not be the same?
  • 7088 2015May core #147 - Both example links return 404.
  • 7089 2015May core #148 - "activity" should be "activites"
  • 7090 2015May core #149 - "A" should be "An"
  • 7091 2015May core #150 - Remove "a"
  • 7092 2015May core #151 - Remove the phrase "consumer level" from the introduction.
  • 7093 2015May core #152 - Remove the first occurrence of the word "a" in this sentence.
  • 7094 2015May core #153 - Change semicolon to a colon, correct spelling of "differently," and add a period at the end of the sentence.
  • 7095 2015May core #154 - Move the sentence to section 1.23.6.3.1, and consider expanding it.
  • 7096 2015May core #155 - Change "a code" in the first sentence" to "codes."
  • 7097 2015May core #156 - Capitalize the abbreviation "URI."
  • 7103 2015May core #162 - Wording is over complex
  • 7107 2015May core #166 - Request that max count be unbounded
  • 7118 2015May core #177 - Explain whether Contraindication is definition or instance
  • 7121 2015May core #180 - Statuses aren't sufficient
  • 7123 2015May core #182 - What's difference between Procedure.category and type?
  • 7124 2015May core #183 - Use approach site, not target
  • 7125 2015May core #184 - Don't make Procedure.outcome codes
  • 7126 2015May core #185 - Procedure.complication should be narrative
  • 7127 2015May core #186 - Procedure.relatedItem is too complicated - make it extension
  • 7129 2015May core #188 - Procedure.device is too vague
  • 7133 2015May core #192 - Differentiate placer & filler ids
  • 7134 2015May core #193 - Rename clinicalNotes to reason or indication
  • 7135 2015May core #194 - supporting information isn't clear, includes errors
  • 7137 2015May core #196 - Declare relationship with IEEE 11073
  • 7141 2015May core #200 - What unit codes are to be used?
  • 7143 2015May core #202 - needs more description. Doubt they are talking about color as in the light spectrum, so need something that ordinary folks can understand
  • 7144 2015May core #203 - Believe this is really the sampling rate of a signal. If so that should be stated more clearly
  • 7148 2015May core #207 - Explain Apgar example
  • 7149 2015May core #208 - very unclear. is this in case it is Coded with exceptions variable gets a free text answer.. Need an example
  • 7150 2015May core #209 - test not done was reported as part of the status in V2. Would make sense to stay with that both for continuity and because it is NOT really an answer
  • 7152 2015May core #211 - to whom. Think it is usually when made available to the clinical providers. It may be available earlier within lab but not yet "verified"
  • 7154 2015May core #213 - Explain reliability
  • 7155 2015May core #214 - add "instance" to end after "observation". Might comment on the scope of uniqueness. globally unique or unique in the context of the sources
  • 7156 2015May core #215 - insert "donor" after fetus
  • 7157 2015May core #216 - Subject can be communicated within Observation.code
  • 7158 2015May core #217 - change "are often" to "may be"
  • 7160 2015May core #219 - Explain grouping more
  • 7161 2015May core #220 - Related type is unneeded complexity
  • 7167 2015May core #226 - Clarify purpose of MedicationStatement
  • 7168 2015May core #227 - Loosen who can capture MedicationStatement
  • 7170 2015May core #229 - would help in the US to say this would usually be the RxNorm clinical drug code as mandated by MU regulation
  • 7172 2015May core #231 - Does NutritionOrder include hyperalimentation?
  • 7175 2015May core #234 - How to handle confusion between intolerance vs. preference
  • 7176 2015May core #235 - How to handle confusion between intolerance vs. preference vs. excludeFood
  • 7178 2015May core #237 - Distinguish what's in internal order vs. provider order (amount)
  • 7184 2015May core #243 - Use route rather than enteral formula
  • 7187 2015May core #246 - Add reference to panels & batteries
  • 7191 2015May core #250 - add " (revised) " for clarity after updated.
  • 7193 2015May core #253 - Overlap of Procedure and Observation is going to be a problem
  • 7202 2015May core #262 - Explain how terminology works with local vs. standard code sets.
  • 7204 2015May core #264 - Typo - "and" misspelled in second sentence
  • 7205 2015May core #265 - Don't understand code system and value set distinction
  • 7207 2015May core #267 - Don't use ValueSet for answer lists
  • 7210 2015May core #270 - Errors in examples
  • 7211 2015May core #271 - Don't use both SNOMED and LOINC
  • 7212 2015May core #272 - no one would do this. Further the oral temperature does not literally measure any thing about the body as a whole
  • 7213 2015May core #273 - no one would do this either if the measure is called oral temperature
  • 7214 2015May core #274 - Narrative doesn't reflect how data would be reported
  • 7219 2015May core #279 - Need phase abnormal flag
  • 7220 2015May core #280 - what are these symbols?
  • 7222 2015May core #282 - Which are master files vs. patient-specific elements. ClinicalImpression is problematic
  • 7223 2015May core #283 - should be distinguished as a master file or knowledge base not patient specific
  • 7224 2015May core #284 - Use MedicationOrder rather than MedicationRequest
  • 7226 2015May core #286 - more often this will be data about a dispensing . The distinction based on how it arrived is not good
  • 7227 2015May core #287 - This is described as an issues at to whether it should be separate
  • 7229 2015May core #289 - Use MedicationOrder rather than MedicationRequest
  • 7230 2015May core #290 - the LOINC code for blood culture is 600-7 Bacteria identified in Blood by Culture
  • 7231 2015May core #291 - Don't use both SNOMED and LOINC
  • 7232 2015May core #292 - "entire body" is a bad example
  • 7233 2015May core #293 - Fix examples to show pre-coordinated formula
  • 7234 2015May core #294 - Use LOINC instead of SNOMED
  • 7237 2015May core #297 - Errors in examples
  • 7243 2015May core #303 - Don’t know what is included
  • 7244 2015May core #304 - presume this relates to the so called segmented privacy, that will be a nightmare and could be glue to the wheels of care. Would try to avoid it.
  • 7249 2015May core #309 - Need more background on parallels of messaging w/ v2
  • 7257 2015May core #447 - No content is provieded in this section
  • 7259 2015May core #449 - The error code and any recommendations on OperationOutcome should be specified
  • 7261 2015May core #451 - No content is provieded in this section
  • 7262 2015May core #452 - No content is provieded in this section
  • 7265 2015May core #455 - contains route codes instead of the intended medication form codes
  • 7266 2015May core #456 - contains routce codes instead of the intended package codes
  • 7269 2015May core #459 - Need a definition from Lloyd
  • 7270 2015May core #460 - The link is critical in order to know what the requirement is.
  • 7256 2015May core #446 - Typo
  • 7271 2015May core #461 - I am unsure as to the intention of this note, but it does not seem to match the example
  • 7272 2015May core #462 - The line number references in the notes do not seem to match the example
  • 7273 2015May core #463 - Typo
  • 7274 2015May core #464 - Missing closing paraenthesis at end
  • 7275 2015May core #465 - Line number reference is incorrect
  • 7276 2015May core #466 - lastUpdated (line 12) - if present, this must match the value in the HTTP header
  • 7277 2015May core #467 - server is spelled wrong
  • 7278 2015May core #468 - Typo
  • 7279 2015May core #469 - How is resource contention handled on delete?
  • 7280 2015May core #470 - More explanation on client-assigned ids8082
  • 7282 2015May core #472 - Typo
  • 7284 2015May core #474 - No content is provieded in this section
  • 7285 2015May core #475 - No content is provieded in this section
  • 7288 2015May core #478 - No content is provieded in this section
  • 7289 2015May core #479 - Verify security risks are handled in stylesheet
  • 7290 2015May core #480 - Content is needed
  • 7301 2015May core #491 - Make birthDate a dateTime
  • 7303 2015May core #493 - There may be more than one dietary preference/restriction
  • 7304 2015May core #494 - There may be more than one diagnosis on discharge
  • 7305 2015May core #495 - admit diagnoses are important, particularly in the cases where the patient may have not be discharged yet.
  • 7307 2015May core #497 - Consider adding birthDate dateTime to resource, just as it is in the Person resource. Ager of the individual involved in the care could be important
  • 7311 2015May core #501 - Keep birthDate data type consistent with the Person resource
  • 7313 2015May core #503 - No guidance provided on Messaging subscription
  • 7340 2015May core #530 - Example links are broken.
  • 7345 2015May core #535 - Require server behavior for merged patients.
  • 7346 2015May core #536 - Make the address search parameter its own type with subdivisions rather than simply a string.
  • 7347 2015May core #537 - Schedule.actor has resource type of "Any"
  • 7348 2015May core #538 - participant.actor should be required
  • 7349 2015May core #539 - Not ALL of CCDA has been incorporated yet.
  • 7351 2015May core #541 - Add ambulatory care to list of contexts
  • 7352 2015May core #542 - Merge first paragraph of 1.7.2.2 into 1.7.2.1. and eliminate second paragraph
  • 7353 2015May core #543 - Use a better comparison than folders
  • 7354 2015May core #544 - Typo extraneous "is." Also suggest capitalizing and making the link more explicit (to Base Resource).
  • 7355 2015May core #545 - Wording is confusing on common properties
  • 7356 2015May core #546 - Don't use "may not"
  • 7357 2015May core #547 - Typo
  • 7358 2015May core #548 - Don't list CCD, say "implementation guide" instead of profile
  • 7359 2015May core #549 - What is the answer then? Shouldn't there be testing tools that can check complete conformance to the FHIR spec, as well as to specific FHIR Profiles?
  • 7360 2015May core #550 - Need to see isModifer=true in the instance
  • 7361 2015May core #551 - Clarify some confusion that cropped up when people looked at "aborted" vs "cancelled" in mapping efforts
  • 7362 2015May core #552 - Expand on life-cylc
  • 7363 2015May core #553 - Use "life cycle" instead of "pattern"
  • 7364 2015May core #554 - Drop life-cycle table until there are more definitions
  • 7365 2015May core #555 - Change "from" to "to"
  • 7366 2015May core #556 - Why not avoid this problem by requiring contained resources to explicitly state their subject? Why allow this degree of optionality?
  • 7367 2015May core #557 - Clarify use of "Medication" as non-patient-specific
  • 7368 2015May core #558 - Narrative should contain all human-relevant discrete data
  • 7370 2015May core #560 - How is list narrative made non-redundant if generated?
  • 7371 2015May core #561 - Narrative only shouldn't be a List
  • 7372 2015May core #562 - See my comment on 6.1.5 -- it does not make sense to call these types of narrative a "List."
  • 7373 2015May core #563 - Is "instant" needed?
  • 7374 2015May core #564 - Clarify reference to contained extension
  • 7375 2015May core #565 - Typo
  • 7376 2015May core #566 - MedicationPrescription "anti-prescription" example has a typo in its first tag, and has as the ending tag.
  • 7377 2015May core #567 - Typo
  • 7378 2015May core #568 - Rename "Specification Map" to "Table of Contents"
  • 7379 2015May core #569 - Be explicit that Composition doesn't contain content. Also note that it establishes context.
  • 7380 2015May core #570 - Typo
  • 7381 2015May core #571 - How are lawn mowing services healthcare related?
  • 7382 2015May core #572 - "a single" is too limiting and does not fit the examples.
  • 7384 2015May core #574 - I think it's important to be explicit about how to know the difference between proposals and actual orders, so I suggested the additional wording.
  • 7385 2015May core #575 - From previous ballot, enter something about 162, 176, 177, 183, 187
  • 7386 2015May core #576 - Differentiate "doesn't have" from "refuted"
  • 7387 2015May core #577 - Add link to documents from Resources page under "Documents & Structure" heading
  • 7388 2015May core #578 - Soften language on presentation of the document changing.
  • 7392 2015May core #582 - Reword definition
  • 7393 2015May core #583 - Remove "final mode" and clarify description of changes list.
  • 7394 2015May core #584 - Where is narrative found in a resource?
  • 7395 2015May core #585 - Saying "base" resource could be confusing since there is a specifical "Base Resource" section (1.10) in the FHIR spec.
  • 7396 2015May core #586 - Typo
  • 7397 2015May core #587 - Remove (or deprecate) this from the Basic Resource Types value set because Slot is already a FHIR resource in the Scheduling/Ordering category.
  • 7398 2015May core #588 - Link is broken, sentence is confusing
  • 7399 2015May core #589 - Typo
  • 7401 2015May core #591 - Distinguish "element" vs. "backbone element"
  • 7402 2015May core #592 - The URL does not work, produces an HTTP 404 error.
  • 7403 2015May core #593 - Description of the rules on human-readable text aren't completely accurate
  • 7404 2015May core #594 - Is narrative the same for documents vs. other mechanisms?
  • 7405 2015May core #595 - Example implies MedicationStatement is a summary, when summary is List
  • 7407 2015May core #597 - CarePlanActivityCategory shouldn't be required
  • 7408 2015May core #598 - Typo
  • 7410 2015May core #600 - Suggest providing a clarification to explicitly allow deprecation (sometimes it just makes sense).
  • 7411 2015May core #601 - Typo
  • 7412 2015May core #602 - ToC links to wrong page
  • 7413 2015May core #603 - Typo, phrase is vague
  • 7414 2015May core #604 - How does OperationOutcome represent business issues?
  • 7415 2015May core #605 - ToC links to wrong page
  • 7417 2015May core #607 - ToC links to wrong page
  • 7418 2015May core #608 - Contradication in definition of Device.location
  • 7420 2015May core #610 - ToC links to wrong page
  • 7421 2015May core #611 - Typo
  • 7422 2015May core #612 - Typo
  • 7423 2015May core #613 - Typo
  • 7426 2015May core #714 - Reference any resource in Document manifest
  • 7427 2015May core #715 - Reference any resources in Document manifest
  • 7428 2015May core #716 - Using of Snomed CT
  • 7400 2015May core #590 - It does not say where to submit the request for a new code. FHIR Management Group? Vocabulary WG? Where? I suggest that be included in the text.
  • 7429 2015May core #717 - Using of Snomed CT
  • 7430 2015May core #718 - Harmonization with ISO EN 13606
  • 7431 2015May core #719 - AuditEvent source identifier
  • 7438 2015May core #726 - Provide help text for flags column
  • 7439 2015May core #727 - Typo
  • 7440 2015May core #728 - hyperlink is to #modifier, but that does not exist on this page….probably should be to #1.16.0.2
  • 7441 2015May core #729 - hyperlink is to seatch.html#mustSupport, but that does not exist on this page….probably should be to #2.1.1.4.7
  • 7444 2015May core #732 - …except… except what? Seems like there is something missing from the sentence
  • 7445 2015May core #733 - nice file cabinet, folder, versioning analogy, but think that read needs to specify it gets the paper from the top of the folder
  • 7446 2015May core #734 - missing a space between appropriate and cabinet
  • 7447 2015May core #735 - resource instead of reosurce
  • 7448 2015May core #736 - Need life-cycle declared everywhere
  • 7450 2015May core #738 - How is unknown extensions support declareD?
  • 7452 2015May core #740 - How do we avoid duplicate extensions?
  • 7454 2015May core #742 - Can only one be declared as primary? Can none?
  • 7456 2015May core #744 - The existing text seems to have a sentence fragment and the meaning is unclear.
  • 7457 2015May core #745 - should allow for multiple Coding returned, with at most one marked as primary
  • 7459 2015May core #747 - Why are_text and _filter missing?
  • 7460 2015May core #748 - Allow non-resources to be focus of Provenance
  • 7463 2015May core #751 - patient compartment should be lowercase patient, not uppercase Patient, which would be the resource.
  • 7464 2015May core #752 - "patient" has wrong case
  • 7466 2015May core #754 - Don't snip narrative
  • 7468 2015May core #756 - Explain issues around cross-origin resource sharing
  • 7469 2015May core #764 - Typo-Binding Definitions
  • 7470 2015May core #765 - Finding the Table of Contents and Section numbers
  • 7471 2015May core #766 - Clinical Resources vs. Administrative Resource
  • 7472 2015May core #767 - Problems with the section "Mixing Custom and Standard Terminologies"
  • 7473 2015May core #768 - Permit a code for a MedicationStatement's Medication
  • 7476 2015May core #771 - Rendering of choice cardinalities
  • 7477 2015May core #772 - Guide to Resources needed
  • 7479 2015May core #774 - 5.1 isn't referenced in TOC correctly
  • 7480 2015May core #775 - These appear to be the same value set but are referenced with different names.
  • 7481 2015May core #776 - Value set link broken
  • 7482 2015May core #777 - This comment appears to be left over from when dosage was 0..* and is no longer appropriate now that dosage is 0..1.
  • 7483 2015May core #778 - consistency of FamilyMemberHistory's condition with the Condition resource
  • 7484 2015May core #779 - Clarify Data Element Boundaries and Relationships
  • 7485 2015May core #780 - Typos in Data Elements vs. Codes
  • 7487 2015May core #782 - Suggested grammar fix in 6.21.8.1
  • 7488 2015May core #783 - Clarification needed on the use of Data Element with other resources
  • 7489 2015May core #784 - Typo in 1.23.0.0.1
  • 7490 2015May core #785 - Grammar in 1.23.0.1
  • 7491 2015May core #786 - Typo in 1.23.0.1
  • 7492 2015May core #787 - Typo in 1.23.1.1.5
  • 7493 2015May core #788 - Sentence re-write is needed.
  • 7494 2015May core #789 - Appropriateness of each coded data type
  • 7495 2015May core #790 - Typo in 1.23.0.2.1
  • 7496 2015May core #791 - Clarify preferred
  • 7497 2015May core #792 - Omitted words in Discriminator discussion
  • 7498 2015May core #793 - Fix incomplete sentence in Discriminator examples.
  • 7499 2015May core #794 - Fix numbering of extensions in Slicing Examples
  • 7500 2015May core #795 - DiagnosticReport.issued -- change to instant?
  • 7502 2015May core #797 - Question about ordering
  • 7503 2015May core #798 - Nested lists?
  • 7504 2015May core #799 - History of
  • 7505 2015May core #800 - FamilyMemberHistory search parameters needed
  • 7506 2015May core #801 - Enforce identifier search parameter
  • 7511 2015May core #802 - Make names consistent between Procedure and Encounter
  • 7513 2015May core #804 - MedicationStatement should allow dose range
  • 7514 2015May core #805 - MedicationStatement- medication as code not Reference(Medication)
  • 7515 2015May core #806 - rename MedicationStatement.dosage.schedule to MedicationStatement.dosage.timing
  • 7517 2015May core #808 - Bring back Observation.component
  • 7518 2015May core #809 - Immunization.protocol cardinality
  • 7519 2015May core #810 - Immunization.protocol.does* cardinality
  • 7521 2015May core #812 - ICD-9 system URLs
  • 7522 2015May core #813 - URL for National Provider
  • 7524 2015May core #815 - URL for NDC
  • 7525 2015May core #816 - MedicationStatement.status definitions
  • 7527 2015May core #818 - Communication.party role type not known?
  • 7528 2015May core #819 - DocumentManifest.recipient role type not known?
  • 7529 2015May core #820 - ElementDefinition should support quaantities too
  • 7530 2015May core #821 - remove ElementDefinition.binding.name
  • 7534 2015May core #825 - remove page toc
  • 7535 2015May core #826 - change driver's license to naming systems
  • 7536 2015May core #827 - Document xml:lang system URI
  • 7537 2015May core #828 - fix json description
  • 7538 2015May core #829 - sort out xml atrribute whitespace
  • 7539 2015May core #830 - PATCH operation
  • 7540 2015May core #831 - Fetch by profile
  • 7541 2015May core #832 - Simply conditional create header
  • 7542 2015May core #833 - registry URLS
  • 7543 2015May core #834 - include transitiveness
  • 7544 2015May core #835 - improve tranasction documentation
  • 7545 2015May core #836 - transaction and base interaction
  • 7547 2015May core #838 - Observation.value= true|false
  • 7549 2015May core #840 - MedicationAdministration.dosage.method duplication
  • 7550 2015May core #841 - AllergyIntolerance negation
  • 7551 2015May core #842 - Current Problem List
  • 7552 2015May core #843 - Spelling error in 1.23.6.3
  • 7553 2015May core #844 - Spelling error in 1.23.6.11
  • 7554 2015May core #845 - Spelling error in 6.21.6
  • 7555 2015May core #846 - Spelling error in 6.21.7
  • 7556 2015May core #847 - Missing entries in table in section 6.21.7.1
  • 7557 2015May core #848 - Spelling error in
  • 7558 2015May core #849 - militaryservice extension isn't useful
  • 7564 2015May core #855 - AuditEvent.event value set is a mess
  • 7565 2015May core #856 - Fix link
  • 7566 2015May core #857 - Use the correct term for the AuditEvent.object.sensitivity. This should be AuditEvent.object.confidentiality.
  • 7572 2015May core #863 - Explain business-specific details of update
  • 7574 2015May core #865 - Add conformance keywords to allow more precision and improve testability. "S" for mandatory is insufficient.
  • 7575 2015May core #866 - Support profiling a profile
  • 7581 2015May core #872 - How do we specify an "active" or "resolved" problem?
  • 7582 2015May core #873 - How do we specify an "active" or "resolved" allergy?
  • 7583 2015May core #874 - We need a status to specify whether the med is "active" vs. "discontinued" meds?
  • 7585 2015May core #876 - GMDN FDA guidance: http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM369248.pdf
  • 7587 2015May core #878 - body site is overly complicated (Observation)
  • 7588 2015May core #879 - body site is overly complicated (Procedure)
  • 7589 2015May core #880 - body site is overly complicated (Condition)
  • 7590 2015May core #881 - Require GMDN as device kind
  • 7591 2015May core #882 - Don't allow local/proprietary codes
  • 7592 2015May core #883 - This binding strengths would allow for gaps in value sets to persist.
  • 7600 2015May core #891 - Wording should be updated to reflect the appropriate SNOMED CT concept.
  • 7601 2015May core #892 - Wording should be updated to reflect the appropriate SNOMED CT concept.
  • 7608 2015May core #899 - Typo
  • 7609 2015May core #900 - The definition is ambiguous. What does "nominated care provider" mean? Is it the primary care provider?
  • 7610 2015May core #901 - Make managing organization 0..*?
  • 7613 2015May core #904 - How is encounter diagnosis handled?
  • 7614 2015May core #905 - Condition.encounter -> firstEncounter
  • 7615 2015May core #906 - If wish to capture date first asserted, should add a sibling attributed called dateFirstAsserted.
  • 7617 2015May core #908 - Is Working vs. Confirmed in the 80%?
  • 7618 2015May core #909 - Please clarify when/how Range is supposed to be used for Condition.range, abatement
  • 7620 2015May core #911 - Are Condition.stage, evidence, dueTo and occurredFollowing in the 80%?
  • 7621 2015May core #912 - Aren't these all similar items? Shouldn't they all be called target or detail?
  • 7622 2015May core #913 - Allow structures in notes, make 0..*
  • 7626 2015May core #917 - ContactPoint should provide a 'rank' attribute
  • 7629 2015May core #920 - Suggest renaming to 'bodySite' or 'affectedSite'
  • 7630 2015May core #921 - Suggest renaming to 'targetBodySite'. There may be other body sites associated with procedure (e.g., approachBodySite)
  • 7631 2015May core #922 - Procedure.device -> targetDevice
  • 7633 2015May core #924 - Procedure has evolved since ProcedureRequest was drafted. Suggest re-aligning the two resources to account for changes in one, relevant to the other.
  • 7634 2015May core #925 - Procedure.notes is 0..1. ProcedureRequest.notes is 0..*. Suggest updating both resources based on comment number 19.
  • 7636 2015May core #927 - Should 'applies' be renamed to 'physiologicallyRelevant[x]'. While short names are good, they must also be more descriptive.
  • 7639 2015May core #930 - What's difference between has component and has member?
  • 7640 2015May core #931 - Align prescription.status with other resources (e.g. Planned, proposed)
  • 7647 2015May core #938 - Recommend renaming to administrationSite
  • 7650 2015May core #941 - Typo
  • 7651 2015May core #942 - Need to categroize re-admissions
  • 7652 2015May core #943 - Extra 'is'.
  • 7653 2015May core #944 - Bindings aren't mutually exclusive
  • 7654 2015May core #945 - Dietary preference to 0..*
  • 7655 2015May core #946 - Recommend renaming this to referralRequestFulfilled
  • 7659 2015May core #950 - Where are the present-on-admission diagnoses?
  • 7660 2015May core #951 - Why is this 0...1? Are all the other discharge diagnoses supposed to be elsewhere, e.g., under reason?
  • 7662 2015May core #953 - How is a diagnostic report not a diagnostic report?
  • 7663 2015May core #954 - Explain most common types of data exchange
  • 7669 2015May core #960 - Reading through the resource description, it's still unclear how to represent an appointment request. Please clarify.
  • 7670 2015May core #961 - Differentiate ReferralRequest and AppointmentRequest
  • 7672 2015May core #963 - Please populate the actual value set or at least provide a good set of examples based on the logical specification of the value set.
  • 7678 2015May core #969 - The text says the contextType shall always be populated, but the definition has it as optional
  • 7679 2015May core #970 - Please update use case. From a clinical perspective performing a CT scan for further investigation of an elevated PSA level would be unusual.
  • 7681 2015May core #972 - In three cases Retrieve URL maps to the DICOM attribute (0008,1190). Do we really neet 4 Retrieve URLs for the ImagingObjectSelection resource?
  • 7682 2015May core #973 - Need to reference key images too
  • 7684 2015May core #975 - Need to distinguish pathologist from technologist comments
  • 7687 2015May core #978 - Add authorization qualifier to 'history'
  • 7693 2015May core #984 - Who or what should sign a bundle and how is this used? RBAC? What happens if a transaction is not signed?
  • 7694 2015May core #985 - Summary says 9 mandatory elements, but only see 1
  • 7696 2015May core #987 - Please write this section.
  • 7702 2015May core #993 - Can signature be captured by blob?
  • 7729 2015May core #1020 - Suggest updating the name of this grouping so it does not conflict with the proper grouping for Medications and Immunizations.
  • 7731 2015May core #1022 - Possible additional text for improved understanding.
  • 7732 2015May core #1023 - Clarification
  • 7733 2015May core #1024 - Missing attribute?
  • 7734 2015May core #1025 - Suggest update definition.
  • 7735 2015May core #1026 - Clarification
  • 7736 2015May core #1027 - Seeking clarification.
  • 7737 2015May core #1028 - Suggest adding more info in the comment.
  • 7739 2015May core #1030 - If a system wants to communicate the manufacturer, brand, form, packaging, etc., they Should use the full Medication Resource.
  • 7743 2015May core #1034 - Suggest updating this introduction text and fixing the link to the example SNOMED CT value set.
  • 7744 2015May core #1035 - Suggested edit removed parens.
  • 7745 2015May core #1036 - Fix typo
  • 7746 2015May core #1037 - Fix the link
  • 7750 2015May core #1071 - Rationalize the design of Provenance Resource and decouple from AuditEvent.
  • 7751 2015May core #1072 - Replace Provenance extension
  • 7753 2015May core #1074 - The use of the DocumentReference.confidentiality element is not conformant with the HCS requirements on Security Labels. This needs to be fixed.
  • 7757 2015May core #1078 - Add David Hays excellent description of the Operations Framework to the top of operations.html.
  • 7759 2015May core #1080 - It is not clear where CORE extensions begin, DAF extensions begin and QICore extensions begin
  • 7760 2015May core #1081 - Add dependsOn element as an input Parameter with parts, and product as an output Parameter with parts.
  • 7761 2015May core #1082 - Allow ConceptMap/$translate to have multiple outcomes
  • 7765 2015May core #1086 - Harmonize AllergyIntollerance.event, Contraindication and Immunization.reaction
  • 7779 2015May core #1100 - Epub is corrupted
  • 7782 2015May core #1103 - Default cardinality of ElementDefintion min and max is undefined
  • 7785 2015May core #1106 - Make sections of the full table of contents expandable/contractible
  • 7786 2015May core #1107 - Need best-practice documentation for creating profiles
  • 7787 2015May core #1108 - Need to create and document processes for achieving interoperability using FHIR
  • 7788 2015May core #1109 - The normative information on a profile needs to be separable from the rest of FHIR
  • 7795 2015May core #1117 - In profiles, a better way to constrain resource references is needed.
  • 7796 2015May core #1118 - No way to restrict Resource(Any)
  • 7797 2015May core #1119 - Concept look up operation may duplicate functionality
  • 7799 2015May core #1121 - Need to list complete rules of what is allowed/not allowed for overrides in derived profiles (cardinality, type, etc.)
  • 7800 2015May core #1122 - Tools aren't checking cardinality alignment
  • 7801 2015May core #1123 - Need to list complete rules of what is allowed/not allowed for overrides in derived profiles with respect to binding and conformance strength.
  • 7802 2015May core #1124 - Tools aren't checking binding strength alignment
  • 7804 2015May core #1126 - Better documentation and examples for extensions both simple primitive and more complex structures.
  • 7851 2015May core #1170 - Condition.clinicalStatus HL7v2 mapping
  • 7854 2015May core #1174 - Encounter.type HL7v2 mapping
  • 7855 2015May core #1175 - Condition.asserter definition clarification
  • 7856 2015May core #1176 - Introducing HL7 FHIR page needs to update its Patient example
  • 7857 2015May core #1177 - Base Resource Definition page has a misspelled word (resource)
  • 7858 2015May core #1178 - Patient Cause of Death
  • 7859 2015May core #1179 - Condition.dateAsserted definition clarification
  • 7864 2015May core #1184 - Condition.clinicalStatus should not convey both record status (in error) and confirmation Status (working, confirmed, refuted)
  • 7866 2015May core #1186 - Add comments or notes to the Immunization resource
  • 7867 2015May core #1187 - Add a record status to communicate active, in error, cancelled
  • 7868 2015May core #1188 - Add Encounter to Risk Assessment
  • 7870 2015May core #1190 - Add Goal.Informant
  • 7873 2015May core #1193 - Period dates in the future
  • 7874 2015May core #1194 - Patient.careProvider HL7v2 mapping
  • 7875 2015May core #1195 - Appointment.reason HL7v2 mapping
  • 7876 2015May core #1196 - Questionnaire.name
  • 7878 2015May core #1198 - Attachment.contentType has conflicting documentation
  • 7883 2015May core #1203 - Add encounter to list
  • 7884 2015May core #1204 - Add Goal.category
  • 7885 2015May core #1205 - Add Goal.startDate
  • 7886 2015May core #1206 - Communication support for phone calls
  • 7887 2015May core #1207 - Immunization.date optional
  • 7888 2015May core #1208 - Encounter.participant definition
  • 7889 2015May core #1209 - Using Codes in Resources typo correction
  • 7891 2015May core #1211 - Search-specific page needs to clarify what URL POST should be supported against.
  • 7892 2015May core #1212 - Under “identity”, it states that if ports differ, the identity of the resource differs, but specifically mentions that http is equivalent to https. This conflicts.
  • 7894 2015May core #1214 - Rename AllergyIntolerance.event
  • 7895 2015May core #1215 - "related things" to "Related identifiers or resources associated with the DocumentReference"
  • 7896 2015May core #1216 - Encounter Status Management typos
  • 7897 2015May core #1217 - Should immunization be searchable by subject since there is no subject parameter (if yes, should AllergyIntollerance be searchable by subject?)
  • 7898 2015May core #1218 - More clarification is needed around how to query for a subset of observations (vitals, labs, social history, etc.).
  • 7902 2015May core #1222 - Clarify the purpose of FHIR Core Profiles
  • 7903 2015May core #1223 - Clarify boundary and relationships between Communication and Encounter
  • 7906 2015May core #1226 - Encounter condition relationship
  • 7907 2015May core #1227 - RESTful special characters
  • 7908 2015May core #1228 - Add AllergyIntolerance.severity
  • 7909 2015May core #1229 - Flag Summary Search broken hyperlink
  • 7911 2015May core #1231 - MedicationStatement updates
  • 7912 2015May core #1232 - More timing examples
  • 7913 2015May core #1233 - MedicationStatement.status clarification
  • 7914 2015May core #1234 - IV Infusion timing
  • 7915 2015May core #1235 - These concepts need to be split. CRFs is a reserved word in context to clinical trial, data collection.
  • 7921 2015May core #1241 - Require 403 Response for Unauthorized Access.
  • 7924 2015May core #1244 - Clarify content-location for Reads without Versioning support
  • 7925 2015May core #1245 - Clarification on Resource + OperationOutcome responses
  • 7926 2015May core #1246 - Remove support for conditional updates.
  • 7927 2015May core #1247 - Remove support for conditional deletes.
  • 7928 2015May core #1248 - Remove support for conditional creates.
  • 7929 2015May core #1249 - Make version metadata support on Creates conditional on version support by servers
  • 7931 2015May core #1251 - Further clarification for variant searches within compartments
  • 7932 2015May core #1252 - Make Etag support for Conformance optional
  • 7933 2015May core #1253 - Remove Transaction requirement for History interaction
  • 7934 2015May core #1254 - Remove SHOULD stipulation for Server Content Manipulation
  • 7935 2015May core #1255 - Transaction Integrity Guidelines in Read and Search
  • 7941 2015May core #1261 - Unclear wording in field requirements in ReferralRequest
  • 7944 2015May core #1264 - Change Asynchronous Operation execution to use Callback URLs
  • 7946 2015May core #1266 - Clarify Document Immutability for Indirect Resource References
  • 7953 2015May core #1273 - Only support POST for FHIR RESTful Search
  • 7954 2015May core #1274 - Remove _language query parameter support
  • 7955 2015May core #1275 - Modifiers should modify content, not names.
  • 7957 2015May core #1277 - Alternative suggestion for Date Ranges
  • 7961 2015May core #1281 - Modify Name of Substance.Type Property
  • 7962 2015May core #1282 - Add class property tosubstance.
  • 7968 2015May core #1288 - Limit Scope of Composition Resource to Documents
  • 7971 2015May core #1291 - Overlap of elements in DocumentReference and Provenance
  • 7972 2015May core #1292 - add code for 'legalAuthentuicator
  • 7973 2015May core #1293 - The value set for .entity.type is listed as Required and is composed of FHIR resources, I think this is an error and should be "extensible"
  • 7974 2015May core #1294 - Add organization to reference types
  • 7975 2015May core #1295 - Add 'entity' and 'entitytype' as query parameters for provenance.
  • 7976 2015May core #1296 - Add option for a receiver to send responses to mailbox endpoint of the source
  • 7980 2015May core #1300 - The phrase literal isn't used until the "Business Identifier" section and it's unclear whether the spec is referring to id or identifier.
  • 7981 2015May core #1301 - Typo
  • 7982 2015May core #1302 - A simple example, or reference to search, on howto acces by business identifier rather than literal resource id might help the new reader.
  • 7983 2015May core #1303 - Please spell PI out. Protected information?
  • 7984 2015May core #1304 - Does this mean OperationOutcome .issue.severity cannot = error? Why?
  • 7985 2015May core #1305 - Typo
  • 7986 2015May core #1306 - If possible, add link also.
  • 7988 2015May core #1312 - Did you consider creating a diagram for this section?
  • 7989 2015May core #1313 - Which status corresponds to admitted?
  • 7990 2015May core #1314 - Clarify search returns
  • 7991 2015May core #1315 - Does including this in a ballot upgrade the status to proposed? Where can folks track the discusision on this resource?
  • 7992 2015May core #1316 - The examples in other spots are very helpful
  • 7993 2015May core #1317 - The examples in other spots are very helpful
  • 7994 2015May core #1318 - How did the authors decide to include 'to 2 significant figures'? In the next row it states 'to 4 significant figures'.
  • 7995 2015May core #1319 - Allow a codeableConcept in addition to the ability to reference Medication Resource. It's very common to just record the medication code.
  • 7997 2015May core #1321 - Please add an example.
  • 7998 2015May core #1322 - The other sections use the first sentence to define the parameter -- would be great to follow pattern here.
  • 7999 2015May core #1323 - Just trying to highlight difference with parallel sentences.
  • 8001 2015May core #1325 - Typo
  • 8002 2015May core #1326 - Add mode parameters as a value set.
  • 8003 2015May core #1327 - Add examples for FHIR operations
  • 8004 2015May core #1328 - Add example for code:in
  • 8013 2015May core #1338 - When would you ever record a MedicationStatement without a patient?
  • 8014 2015May core #1339 - Where would you put a free text SIG? Please include guidance somewhere on this page: /medicationstatement-definitions.html#MedicationStatement.note
  • 8015 2015May core #1340 - Did you consider allowing a link between MedicationPrescriptions when the status is superceded?
  • 8019 2015May core #1344 - Typo
  • 8020 2015May core #1345 - Please add detail on when you expect to just use the MedicationPrescription.dispense vs the full MedicationDispense resource.
  • 8022 2015May core #1347 - The value set appears to be route codes. Please update to be medication codes. Linked to the page from Medication.code: /medication.html
  • 8023 2015May core #1348 - How did you decided to include this field? Isn't this available through the Medication.code and/or Medication.package?
  • 8024 2015May core #1349 - Not clear what framework is referenced here?
  • 8026 2015May core #1351 - Clarify resource inclusion in document bundle
  • 8027 2015May core #1352 - How would a stylesheet render a document unsafe if it doesn’t alter the presentation? Is a common stylesheet supplied?
  • 8028 2015May core #1353 - Link to "Profile Tags" is incorrect - takes you to compartment based access Why wouldn't you use the meta tag in the composition resource?
  • 8032 2015May core #1357 - Code inconsistent
  • 8034 2015May core #1359 - Occurrence misspelling
  • 8041 2015May core #1366 - Add "and extended with metadata in the HL7 Value Set Definition specification"
  • 8042 2015May core #1367 - Do not understand the use case driving this, nor the need for the recursive containment. Remove.
  • 8043 2015May core #1368 - Change  Resource Contraindication to DetectedIssue
  • 8044 2015May core #1369 - effective date range for the communication
  • 8045 2015May core #1370 - Medication Prescription Status Values
  • 8046 2015May core #1371 - Add URI for NDC (National Drug Code)
  • 8047 2015May core #1372 - Add UIR for NPI (National Provider ID)
  • 8049 2015May core #1374 - Support XHTML narrative in extensions
  • 8051 2015May core #1376 - Link broken
  • 8053 2015May core #1378 - Link broken
  • 8054 2015May core #1434 - Why is the patient reference called patient in some resources and subject in others? Should be consistent where possible.
  • 8055 2015May core #1435 - Typo
  • 8056 2015May core #1436 - Typo
  • 8057 2015May core #1437 - Make Composition.class and DocumentReference.class extensions
  • 8058 2015May core #1438 - Make clear that Procedure.device includes implanted devices
  • 8060 2015May core #1440 - Re-word for clarity
  • 8061 2015May core #1441 - MedicationFormalRepresentation - Link to valueset for medication codes points to value set contents for route of administration.
  • 8062 2015May core #1442 - MedicationForm - Link to valueset for medication codes points to value set contents for route of administration.
  • 8063 2015May core #1443 - MedicationContainer - Link to valueset for medication codes points to value set contents for route of administration.
  • 8064 2015May core #1444 - Medication.code - Reference points to value set contents for route of administration.
  • 8065 2015May core #1445 - Medication.product.form- Reference points to value set contents for route of administration.
  • 8066 2015May core #1446 - Medication.package.container - Reference points to value set contents for route of administration.
  • 8067 2015May core #1447 - medicine -> medication
  • 8074 2015May core #1454 - Concerns for FamilyMemberHistory
  • 8079 2015May core #1461 - More structured approach to conformance resource
  • 8080 2015May core #1462 - FHIR section 6.16.3 does not describe all UML classes
  • 8081 2015May core #1463 - The concept of profile needs further consolidation
  • 8082 2015May core #1464 - What is difference between a profile and implementation guide
  • 8086 Create best practice wording on how to deal with large scale OID URI strategy
  • 8102 Fix description of Timing datatype components: frequency and frequencyMax
  • 8105 DocumentReference.format needs to be type Codeing
  • 8107 Update the definition of "status" for the MedicationStatement7913
  • 8110 When "To many codes to display (>10000)" , show *some* of them
  • 8111 Clarify description of OperationDefinition.idempotent
  • 8112 Recommend adding 'On-Hold' to MedicationStatement.status
  • 8113 Need additional documentation on List resource about List semantics
  • 8114 FamilyMemberHistory.deceased[x] documentation typo
  • 8116 "Example" appears on the description of the Condition-Category valueset even though the values are required if used
  • 8118 Correct typos in Service Root URL
  • 8120 Consider Location.status "present"
  • 8121 Allow additional search results when an advanced search algorithm is available
  • 8122 Definition of neutered only covers male animals
  • 8123 AuditEvent constraints are too tight
  • 8124 Clinical Resource categories
  • 8125 2015May daf #5 - Missing Concept Display Name
  • 8128 2015May daf #26 - Expand value set
  • 8129 2015May daf #27 - Profile title suggestion
  • 8130 2015May daf #28 - Profile title suggestion
  • 8136 2015May daf #36 - Profile title suggestion
  • 8137 2015May daf #45 - Profile title suggestion
  • 8138 2015May daf #48 - Duplicate Section Titles
  • 8142 2015May daf #96 - Modify Content Search Parameters
  • 8143 2015May daf #106 - MedicationPrescription.dispense.numberOfRepeatsAllowed
  • 8146 2015May daf #166 - Provide wording to distinguish severity & criticality
  • 8147 2015May daf #167 - Notes should be 0..* rather than 0..1
  • 8150 2015May daf #181
  • 8154 2015May daf #192 - Incorrect encoding of units in SCT
  • 8155 2015May daf #210
  • 8156 2015May daf #211 - Broken link: http://www.hl7.org/FHIR/2015May/QICoreMedicationCodes.html#1.23.2.1.2088
  • 8158 Brokent Link on extensibility Page.
  • 8159 word clarify
  • 8160 Procedure missing value sets
  • 8162 "Complete Conformance Statement" is incomplete
  • 8163 Transaction processing sequence should reflect bundle entry sequence
  • 8164 allow batch delete for conditional DELETE operation if multiple match
  • 8165 2015May core #975b - Add authorization qualifier to 'read'
  • 8166 Order should have a search parameter "identifier"
  • 8167 What to do when I encounter unknown elements in a FHIR payload?
  • 8168 Small typo in ConceptMap detailed description
  • 8171 Profile HTML pages should have default values from base resources grayed out if missing in differential
  • 8172 transaction-operation coding system doesn't correspond to transaction-operation value set
  • 8174 Typo on REST/API page
  • 8175 xsd:decimal precludes implied precision
  • 8176 Typo on REST/API page, conformance operation
  • 8177 change administrationinstructions to administrationinstruction (remove s)
  • 8178 fix dangling references to web categories in security labels page
  • 8179 also change .scheduled to schedule for consistency (remove d)
  • 8180 schedule[x] (dateTime|Period|Timing) can be just schedule (Timing)
  • 8183 Add mode of encounter
  • 8184 Add reference to Condition
  • 8185 Change DO .item.code and DR .name valueset binding to Example
  • 8186 Identifier Type needs to use internally defined codes
  • 8187 Correct Language about outcome of translation operation
  • 8188 ConceptMap structure doesn't make sense
  • 8189 Dead link to Profile Tags
  • 8190 BindingStrength of FamilyMemberHistory.condition.outcome is UNKNOWN
  • 8194 May2015 QICore #34 - Unreadable documentation page
  • 8196 MAY2015-QICore#61- Broken "link-to-here"
  • 8197 MAY2015-QICore #62-63 - Show value set and strength instead of binding name
  • 8198 MAY2015 QICore#70 - Change CommunciationRequest.orderedOn to requestedOn
  • 8200 MAY2015-QICore#84 - Null values for modifying attributes?
  • 8202 Questionnaire.group.question missing validation
  • 8203 The MedicationPrescription resource does not specifically state that it includes the ability to order total parenteral nutrition.
  • 8204 URI for Medical Device Codes defined in ISO 11073-10101 is wrong
  • 8210 2015MAY QICore#85 Goal.patient cardinality
  • 8216 Make clear separation of recommendation and plan in CarePlan
  • 8220 Add unavailable as list empty reason
  • 8222 Device Scope nad Usage needs editing
  • 8226 ValueSet.url should be ValueSet.uri
  • 8228 How to represent a range of infusion rates?
  • 8230 Display for filter-operator "=" code is " "
  • 8232 Add ImagingStudy element to ImagingObjectSelection
  • 8233 Add searchRevInclude to Conformance
  • 8234 What are "the standard search parameters"
  • 8235 Return behaviour of named queries: Bundle or Parameters
  • 8236 terminology system URL syntax
  • 8238 MedicationAdministration.dosage.rate clarification
  • 8239 fix typo in updates page
  • 8244 2015May daf #104 - Update Data Types Timing.code value set
  • 8245 2015May daf #94 - Add preferred binding to condition.severity
  • 8246 Signature.who can have every dataType in fhir-single.xsd
  • 8247 Invariants not showing up on Element
  • 8248 CliniciansonFHIR: Care Plan status value set
  • 8249 CliniciansonFHIR: Care Plan reference Care Plan
  • 8252 CliniciansonFHIR: Care Plan roles
  • 8254 CliniciansonFHIR: Goal - link to goal observation
  • 8256 CliniciansonFHIR: Goal Status Value
  • 8258 iniciansonFHIR: Goal with computable < and >
  • 8261 Procedure Resource need to reference referral
  • 8262 2015May daf #50 - FHIR Version Number
  • 8263 2015May daf #54 -Title: Extension: Data Absent Reason
  • 8265 ValueSet.compose.include should have codes or filters, but not both
  • 8270 ValueSet observation-values has no codes as defined
  • 8271 Value set specimen-collection-priority references nonsensical code system www.example.com
  • 8272 CarePlan Definition - how zero or more providers in a team with the person/patient intend to guide care.
  • 8277 Add a value for Clinical Research Sponsor to Organization type Value Set
  • 8281 Rename ProcedureRequest.timing[x] to scheduled[x]
  • 8283 Typos on Inter-Version Compatibilty page
  • 8284 Profile vs StructureDefinition on Conformance rules
  • 8285 Profiling examples are still DSTU1
  • 8286 Slicing entry needs to repeat full definition, not only root
  • 8287 Profile to StructureDefinition
  • 8288 Profile still used as example
  • 8289 Typo in Life Cycle page
  • 8290 Typo in narrative page
  • 8291 Typo overview clinical page
  • 8293 Typo in overview page
  • 8295 Typo on profiling page
  • 8296 New explanation for discriminator
  • 8297 Typo in references page
  • 8298 Typo on references page
  • 8300 unclear about language tag on resource page
  • 8301 Typo on updates page
  • 8303 Valueset expansion in parameters clarification
  • 8306 Change binding of EnteralRouteOfAdministration from required to extensible
  • 8307 Canonical url name clash "http://hl7.org/fhir/StructureDefinition/cda-inFulFillmentOf"
  • 8308 Add FMM gradings, and give all resources a FMM level
  • 8309 Constraints can be used to constrain extensions too
  • 8310 Constraining to max=1 in profile loses information
  • 8311 Small errors in StructureDefinitions for primitives
  • 8313 Change terminology for AllergyIntolerance.type
  • 8314 Logical table icon for Bundle incorrect
  • 8315 Guidance on "Care Team"
  • 8319 adjust wording for bundle.entry.transaction.url
  • 8321 Extensibility documentation should explain representation for primitive data types in JSON
  • 8322 Bad Link
  • 8323 DiagnosticReport vs Composition - How are they related/different?
  • 8324 Add "component" to ValueSet http://hl7.org/fhir/goal-relationship-type
  • 8325 Add reference from Communication --> CommunicationRequest
  • 8326 Example uses an invalid element name 'dob'
  • 8327 2015May QICore #56 - Make Procedure.status field isModifier
  • 8328 value-set code generator creates duplicate line for the profile within the meta tag
  • 8329 Refine explanation of $translate for non-map assertions
  • 8333 Missing Examples for other usage identified
  • 8337 Value set manifestation-c-cda-codes has no codes as defined
  • 8338 Description of Condition/Problem/Diagnosis Codes off Condition.category has redundant "condition"
  • 8339 Allow a server to specify that eTags are required for updates
  • 8341 conformance versioning detail not consistent
  • 8342 include the option for a client to specify whether the updated resource is to be included in a transaction response
  • 8343 j.equivalence definition and valueset detfinition contradict each other
  • 8345 Support MedicationPrescription.dosageInstruction.rate as a Quantity
  • 8352 2015May QICore #65 - Copyright Statement not appearing in generated valueset HTML page
  • 8353 Non-resource-specific pages should include responsible WG
  • 8354 ValueSet.define should be renamed to ValueSet.codeSystem
  • 8355 valueOrdinal should be decimal, not integer
  • 8356 Add a note about ordinals and reference to extension on Questionnaire
  • 8357 Extension display doesn't show cardinality for extension
  • 8359 ATNA REST action codes do not cover DSTU2 operations
  • 8360 Clarify Condition.code and evidence
  • 8363 No place for a displayname in SearchParameter
  • 8365 Relative URLs in reference search parameter
  • 8366 "it's" vs "its"
  • 8370 We're ambiguous about allowing relative urls for reference-type search parameters
  • 8371 content-type=application/x-www-form-urlencoded
  • 8372 Support multiple discharge diagnoses
  • 8376 Encounter participant type value set - add addtl V3 ParticipationType codes
  • 8379 Observation indirect target is confusing
  • 8381 Extend OrganizationType to include other commercial types
  • 8382 Incorrect code in patient-example.xml
  • 8386 LOINC copyright query should not allow "All" as a value
  • 8388 doc-typecodes filter value for LOINC should match case with LOINC db
  • 8389 Create codes in special value code system for "L" (below detection limit) and "U" (above detection limit)
  • 8393 Operations defined on profiles do not work
  • 8394 Conformance.security search param path is wrong
  • 8395 Error First child element must be of type... when defining a nested complex type extension
  • 8396 json-edge-cases.json is invalid
  • 8397 MedAdmin clarifications needed
  • 8399 observation-methods includes an invalid filter for LOINC
  • 8401 Add ConceptMap search parameter for sourceUri
  • 8403 Need 21090 ordinal extension on Coding
  • 8407 Add AllergyIntolerance.onset
  • 8408 Add identifier field to search parameters for Procedure resource
  • 8416 Remove batch operations now that we have a batch interaction
  • 8417 Concept Designation Use binding - clarify SCT licensing issues
  • 8418 Add Period to Group Characteristic
  • 8419 adjust binding strength of DocumentReference value sets
  • 8421 Conflicting advide in ValueSet expansion and define/compose
  • 8423 Care Plan Status missing draft and cancelled(or similar)
  • 8426 What is the effect of operations on _history?
  • 8427 Custodian of a Resource should be accessible through Provenance
  • 8429 $everything operation support _include directive?
  • 8430 Clarify how non-transaction/batch Bundle posts work when sent to the base URL
  • 8431 add Signature to the datatype graphic on the top of the datatype page
  • 8432 Add Encounter to MedicationStatement
  • 8433 Add "logical" to StructureDefinition.kind
  • 8434 Document content expectations too tight
  • 8437 Remove Social Security Number from the Identifier type value set and improve definition
  • 8438 Add identifier systems to the system list
  • 8439 Add a value set for yes/no/don't know (common questionnaire combination)
  • 8440 Change references from Supply to SupplyRequest
  • 8441 Provide support for a CodeableConcept for answer to question
  • 8444 Test Script should note relationship to other resources
  • 8446 typo in narrative for mode = create
  • 8449 OperationOutcome.issue.code is either extendable CodeableConcept or not Code - Prefer extendable
  • 8450 OperationOutcome.issue.location is unfriendly to JSON based applications only using HTTP Get parameters
  • 8452 Add StructureDefinition.invariants
  • 8454 Support for multiple authors and sections they've completed
  • 8455 Provide support for other roles involved in questionnaire/assessment completion
  • 8456 Inconsistent extension element links
  • 8457 Add section on IP considerations
  • 8466 Allow Communication resource to have Group as a recipient
  • 8469 StructureDefinition notes refer to "type" instead of "contextType"
  • 8470 Rendering of extensions includes a "Summary" with no content
  • 8471 StructureDefinition.context needs a clearer definition
  • 8473 When StructureDefinition.contextType is 'extension', rules are unclear
  • 8474 Condition laterality
  • 8479 Remove Observation.value[x] binding
  • 8480 Rename QuestionnaireAnswers to QuestionnaireResponse
  • 8481 Don't force use of ValueSet for questionnaire question choices
  • 8482 Criticality terminology for AllergyIntolerance resource
  • 8483 Update element description for ElementDefinition.type.profile
  • 8485 published xml extensions misslng "-->'
  • 8486 DataElement should have stringency as a search criteria
  • 8487 Need a system url for mime type
  • 8488 The presentation of Goal is not clear
  • 8490 Timing documentation is out of date
  • 8492 Searching for codes by valueset should use ValueSet.url
  • 8494 QI-Core and CQF are two non-names for QICore
  • 8495 HealthcareService missing Identifier search property
  • 8497 valueset-c80-doc-classcodes should include four missing C-CDA document-level codes
  • 8498 DocumentReference.format belongs inside content
  • 8499 DocumentReference: "Document Formats" section is out of date
  • 8500 Profile schematron rules do not trigger
  • 8501 Document the "system" for Patient.communication.language
  • 8502 MedicationAdministration rate changes
  • 8504 change DR.requestdetail to DR.request to harmonize with PC resources
  • 8505 add choice of ProcedureReequest and ReferralRequest to DR.requestDetail
  • 8508 Invariant rules in profiles not populated in schematron files
  • 8509 Conformance should have a "kind"
  • 8510 Rename NamingSystem.type to NamingSystem.kind
  • 8511 NamingSystem.country and .category should become useContext
  • 8512 NamingSystem.category should have same binding as Identifier.type
  • 8514 change name of element serviveCategory to category
  • 8520 Duplicate profile ids overwrite
  • 8521 Questionnaire Extension defaultasfixed - clarification
  • 8532 The Questionnaire parameter on the $populate operation should permit by reference
  • 8535 Search documentation missing anchor for "_security"
  • 8539 StructureDefinition invariants mention non-existent f:type
  • 8540 Primitive types have f:element/f:type/f:code which violates binding
  • 8541 How interpret StructureDefinition differential?
  • 8542 Extension example - value[x]
  • 8543 Request multi-level extension example
  • 8544 Duplicate search parameter "familymemberhistory-daf-FamilyMemberHistory-condition"
  • 8547 Complex extensions not showing proper icon
  • 8549 Reject modifiers inside complex extensions
  • 8551 create and extension for O.refrange to allow for ...or equal to
  • 8553 Remove Medication.name from Medication Resource
  • 8555 Need enableWhen to work for non-answered questions too
  • 8556 Clean up profile list
  • 8561 Profie examples not published in IG section.
  • 8562 Bad link generated in pubished pages to raw XML of IG-defined valuesets
  • 8568 Need example valueset on ProcedureRequest.asNeeded[x] and indication elements
  • 8582 Define MPI search for patient resource
  • 8584 Erroneous warnings on path being generated by build
  • 8586 Elements repeating in differential view
  • 8589 QA: All properties are included in the Summary
  • 8590 Questionnaire Summary items missing "name" of the Questionnaire
  • 8594 ElementDefinition.type.code values not in data-type valueset
  • 8595 add two codes to provenance-participant-role for assembler and composer
  • 8596 profile element comments not displaying in element details
  • 8597 clarification for identifer.system
  • 8598 typo for comparators in inclusive extension -fix = instead of =< and =>
  • 8599 AllergyIntolerance.status value set
  • 8605 Datatype Boolean - explanation required
  • 8607 Don't require use of data elements for $populate w/ SDC
  • 8613 change EPUB link to readable version of FHIR Book
  • 8606 Clarify description of slicing, not limited to element lists
  • 8622 validation.zip's dataelements.xml contains duplicate fullUrl and canonical urls
  • 8623 validation.zip conceptmap.xml contains incorrect canonical url
  • 8624 Clarify that Subscription.criteria should not have a leading "/"
  • 8625 Fix missing Provenance HL7 Extension
  • 8626 build not expanding Provenance valueset v3 Value Set ProvenanceEventCurrentState
  • 8628 some slice members lack f:name
  • 8629 The schema for Parameter resource is missing.
  • 8631 Extensions missing in differential view
  • 8633 Description of string search w/ :exact is slightly ambiguous
  • 8635 Search Parameter Crossmap w/ Data Types Missing All Number Types
  • 8636 Quantity Search Needs Clarification Regarding Quantities With Comparators
  • 8637 Quantity Search Needs Clarification Regarding Value Semantics

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.