argonautproject/implementation-program issues and pull requests

#70 - SNOMED 160244002 for NKA, which is no longer active. Should reference 716186003

Issue - State: open - Opened by Healthedata1 almost 8 years ago
Labels: data.allergies

#70 - SNOMED 160244002 for NKA, which is no longer active. Should reference 716186003

Issue - State: open - Opened by Healthedata1 almost 8 years ago
Labels: data.allergies

#69 - Add instructions on how to lodge issues/trackers

Issue - State: open - Opened by Healthedata1 almost 8 years ago

#69 - Add instructions on how to lodge issues/trackers

Issue - State: open - Opened by Healthedata1 almost 8 years ago

#68 - Care team category cardinality should be less restrictive

Issue - State: closed - Opened by torresdrew about 8 years ago - 4 comments

#68 - Care team category cardinality should be less restrictive

Issue - State: closed - Opened by torresdrew about 8 years ago - 4 comments

#67 - Valueset for the formatcode being used is missing CCDA R2.1 value

Issue - State: closed - Opened by torresdrew about 8 years ago - 2 comments

#67 - Valueset for the formatcode being used is missing CCDA R2.1 value

Issue - State: closed - Opened by torresdrew about 8 years ago - 2 comments

#66 - Update Search "date' Parameter modifiers

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#66 - Update Search "date' Parameter modifiers

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#65 - Clarify DocumentReference conformance section

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#65 - Clarify DocumentReference conformance section

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#64 - Should we move there server response codes from Quick Start to a common location?

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#64 - Should we move there server response codes from Quick Start to a common location?

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment

#63 - Oxygen sat inspired O2

Issue - State: open - Opened by Healthedata1 about 8 years ago - 10 comments
Labels: data.vitals

#63 - Oxygen sat inspired O2

Issue - State: open - Opened by Healthedata1 about 8 years ago - 10 comments
Labels: data.vitals

#62 - Should the slicing be removed from Observation Results Structuredefinition.

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment
Labels: data.lab

#62 - Should the slicing be removed from Observation Results Structuredefinition.

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment
Labels: data.lab

#61 - DocuementReference masterIdentifier required?

Issue - State: closed - Opened by daliboz about 8 years ago - 1 comment

#61 - DocuementReference masterIdentifier required?

Issue - State: closed - Opened by daliboz about 8 years ago - 1 comment

#60 - GForge #11974

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment
Labels: data.problems, data.concerns

#59 - Loosen up requirements on DiagnosticReport.result

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 1 comment
Labels: data.lab

#58 - Proper Argonaut extension code system

Issue - State: closed - Opened by brettmarquard about 8 years ago - 5 comments

#57 - How to handle required binding for CodeableConcept when all you have is free text?

Issue - State: closed - Opened by Healthedata1 about 8 years ago - 3 comments
Labels: data.everything

#56 - What to do when a required code is not available?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 2 comments

#55 - What if system only has text for a required binding

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 1 comment

#54 - Procedure terminology and cardinality should be flexible.

Issue - State: closed - Opened by torresdrew over 8 years ago - 9 comments

#53 - Immunization code cardinality should be flexible

Issue - State: closed - Opened by torresdrew over 8 years ago - 1 comment

#52 - CarePlan date support

Issue - State: closed - Opened by torresdrew over 8 years ago - 2 comments
Labels: data.plan and assessment

#51 - Is DocumentReference the right resource for the Job?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 26 comments
Labels: data.MHD

#50 - Whether to change effectiveDateTime/Period from a required to a must-support element?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 3 comments
Labels: data.medications

#49 - Whether the Immunization.status value-set should be constrained

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 5 comments
Labels: data.immunizations

#48 - Time of Current Smoking Status Observation

Issue - State: closed - Opened by brettmarquard over 8 years ago - 1 comment
Labels: data.smoking

#47 - Whether to exchange the UDI string ("udi carrier") or DI + PI

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 2 comments
Labels: data.udi

#46 - Whether both medicationCodeableConcept and medicationReference are both mandatory data elements

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 9 comments
Labels: data.medications

#45 - Whether the search for Patient Document's should be limited to current (active) documents?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 5 comments

#44 - What value set should be bound to CarePlan.participant.role

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 8 comments
Labels: data.careteam

#43 - Oxygen Saturation - 59408-5 (Pulse Oximetry) vs 2708-6 (no method)

Issue - State: closed - Opened by brettmarquard over 8 years ago - 7 comments
Labels: data.vitals

#42 - Multiple races and ethnicities for patient

Issue - State: closed - Opened by torresdrew over 8 years ago - 19 comments
Labels: data.patient

#41 - Whether CareTeam needs to support search by status and/or date?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 8 comments
Labels: data.careteam

#40 - Whether to search Assessment and Plan of Treatment and Goals by status = 'active'

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 3 comments
Labels: data.goals, data.plan and assessment

#39 - What syntax for search must servers support?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 8 comments
Labels: data.patient

#38 - How to search for codes?

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 1 comment
Labels: data.vitals

#37 - Whether to combine Problems and Health Concerns

Issue - State: closed - Opened by Healthedata1 over 8 years ago - 1 comment
Labels: data.problems, data.concerns

#36 - Category Code discrepency

Issue - State: closed - Opened by avinashshanbhag almost 9 years ago - 5 comments
Labels: data.problems, data.concerns

#35 - Should Problems be limited by category?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 11 comments
Labels: data.problems, data.concerns

#34 - How to resolve the difference between the MU sex codes and FHIR gender codes

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 4 comments
Labels: data.patient

#33 - How to limit or minimize overly broad search for Patient?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 4 comments
Labels: data.patient

#32 - What are the ONC Guidelines regarding approach to Date and Date range based searches?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 3 comments
Labels: data.everything

#31 - DAF Substance Value Set is not aligned with Allergies code guidelines

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 8 comments
Labels: data.allergies

#30 - Whether to remove the values ‘unknown’ and ‘not-asked from the Smoking Status results value set

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 1 comment
Labels: data.smoking, regulatory.decision

#29 - Should SNOMED CT be preferred over UNII for food and environmental allergens?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 2 comments
Labels: data.allergies

#28 - Should Problem Search criteria include both all Problems and all Active Problems?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 2 comments
Labels: data.problems

#27 - What is the status of an implantable device that is no longer in the patient?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 2 comments
Labels: data.udi

#26 - Should a DiagnosticOrder reference be mandatory element for DiagnosticReport as it is in the DAF profile

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 3 comments
Labels: data.lab

#25 - What is a consistent pattern for grouping Observations into panels?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 1 comment
Labels: data.vitals, data.lab

#24 - Should Category based search for Vitals and Lab IG be mandatory?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 2 comments
Labels: data.vitals

#23 - Do we need an extension for Argonaut Vitals IG for Observation.component.interpretation ?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 1 comment
Labels: data.vitals

#22 - How to resolve the inconsistencies between CCDA, MU3, and the Argonaut Vital Signs IG?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 3 comments
Labels: data.vitals

#21 - For the Vitals IG should Mean BP be a standalone or component Observation?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 1 comment
Labels: data.vitals

#20 - How to resolve the inconsistencies between DAF and the Argonaut Observation based profiles?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 2 comments
Labels: data.vitals, data.lab, data.smoking, data.DAF, data.procedures

#19 - What is the behavior or guidance if units are wrong or missing?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 6 comments
Labels: data.vitals, data.lab

#18 - Should success criteria support fetching data by date?

Issue - State: closed - Opened by Healthedata1 almost 9 years ago - 1 comment
Labels: duplicate, data.everything