This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Search results

Jump to navigation Jump to search
  • ...source Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] [[Category:FHIR Resource Proposal]]
    5 KB (807 words) - 22:06, 11 February 2015
  • ...source Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] [[Category:FHIR Resource Proposal]]
    6 KB (808 words) - 22:12, 11 February 2015
  • ...ource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] [[Category:FHIR Resource Proposal]]
    7 KB (1,103 words) - 05:43, 22 May 2014
  • ...d_Care_FHIR_Mini-Connectathon_201704|Return to April 2017 Value-Based Care FHIR Mini-Connectathon]] =FHIR Resource Subscription Track=
    15 KB (2,116 words) - 22:57, 9 March 2017
  • =FHIR Resource Subscription Track= ...l7.org/images/4/43/201701_FHIRConnecathon-ResourceSubscription_Report.pptx Resource Subscription Track Report]
    15 KB (2,128 words) - 19:44, 15 January 2017
  • ...ontact WG to determine whether they want GenomicVariantObservation to be a resource or a profile ...we discuss how to further engage implementers who are not members into the FHIR voting process. Clearly an FBG, TSC, and Board topic.
    7 KB (1,172 words) - 16:13, 26 August 2015
  • ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.''' ...with only knowledge of a development environment and little to no previous FHIR knowledge. If creating a server, advanced preparation will be required, but
    20 KB (3,082 words) - 15:56, 19 January 2017
  • ...sentation/d/1rXbzm9usNJvFkHnR2ummnVHuKRskk2-7--BOy3WkaFU/edit?usp=sharing FHIR Connectathon 19 Patient Track Orientation Slides] ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.'''
    20 KB (3,147 words) - 19:50, 13 January 2019
  • ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.''' ...with only knowledge of a development environment and little to no previous FHIR knowledge. If creating a server, advanced preparation will be required, but
    20 KB (3,095 words) - 10:43, 7 May 2017
  • ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.''' ...with only knowledge of a development environment and little to no previous FHIR knowledge. If creating a server, advanced preparation will be required, but
    21 KB (3,238 words) - 14:12, 29 January 2018
  • ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.''' ...with only knowledge of a development environment and little to no previous FHIR knowledge. If creating a server, advanced preparation will be required, but
    21 KB (3,238 words) - 07:08, 4 April 2018
  • ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.''' ...with only knowledge of a development environment and little to no previous FHIR knowledge. If creating a server, advanced preparation will be required, but
    21 KB (3,210 words) - 20:36, 11 September 2017
  • ...sentation/d/1rXbzm9usNJvFkHnR2ummnVHuKRskk2-7--BOy3WkaFU/edit?usp=sharing FHIR Connectathon 19 Patient Track Orientation Slides] ...ntal requirement that all FHIR servers ''SHALL'' support the [http://build.fhir.org/http.html#capabilities capabilities] interaction.'''
    21 KB (3,259 words) - 20:02, 30 September 2018
  • The focus of this track will be on the transformation from HL7v2 to FHIR (and vice versa). The testing scenarios shown below form the core of the "H #(v2 to FHIR) ADT Query - mapping a v2 query and its response
    15 KB (2,160 words) - 14:13, 18 May 2015
  • FHIR ...the FHIR core team, however, it has been changed due to the change in the FHIR core team agenda. Therefore, we will cover the core team collaboration in Q
    43 KB (5,565 words) - 20:55, 11 January 2016
  • * ISO (Hide): ISO: Audit trail discussions (27789 Audit Trail for EHR) Change proposal to keep conformance with ATNA, etc. Some vocabulary, such as purpose of us 5. FHIR Security Report out - John Moehrke
    15 KB (2,266 words) - 05:45, 1 June 2018
  • ...of the standard that might need to be updated with the NTE segment as per proposal # 839.<br/> The proposal is asking to add to A01, A03, A04, A05, A08, A28.<br/>
    44 KB (5,693 words) - 21:05, 11 January 2016
  • 2018-08-10: All substantive reconciliation applied. FHIR Core is frozen, limited QA process for content subject to ballot only <br/> https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677<br/>
    19 KB (2,629 words) - 14:52, 7 August 2018
  • ...re are things here... model creation, OMG/AML... CIMI activities with SHN, FHIR... and then membership, policies... etc. We can discuss now, but best if al ...cture - Auditing. There are 24 things that can happen to a record, such as deleted. Destroyed...
    25 KB (4,231 words) - 20:56, 11 February 2017