FHIR Breaking changes between DSTU 2 ballot and final

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
• 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