| Module Name | Report |
| cisco_ios |
|
| device_manager |
|
| provision |
|
| puppetlabs-accounts |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 89 |
|
2021-03-03T01:56:10Z |
success |
| 88 |
|
2021-03-02T01:49:06Z |
success |
| 87 |
|
2021-03-01T01:22:56Z |
success |
| 86 |
|
2021-02-28T01:20:39Z |
success |
| 85 |
|
2021-02-27T01:22:46Z |
success |
| 84 |
|
2021-02-26T00:46:53Z |
success |
|
|
| puppetlabs-acl |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 114 |
|
2021-03-03T01:07:35Z |
success |
| 113 |
|
2021-03-02T01:06:02Z |
success |
| 112 |
|
2021-03-01T01:12:18Z |
success |
| 111 |
|
2021-02-28T01:11:06Z |
success |
| 110 |
|
2021-02-27T01:09:15Z |
success |
| 109 |
|
2021-02-26T01:06:55Z |
success |
|
|
| puppetlabs-apache |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 104 |
|
2021-03-03T02:14:38Z |
failure |
| 103 |
|
2021-03-02T02:07:02Z |
success |
| 102 |
|
2021-03-01T01:53:33Z |
success |
| 101 |
|
2021-02-28T01:54:12Z |
failure |
| 100 |
|
2021-02-27T01:52:45Z |
failure |
| 99 |
|
2021-02-26T01:33:47Z |
success |
|
|
| puppetlabs-apt |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 34 |
|
2021-03-03T00:57:24Z |
success |
| 33 |
|
2021-03-02T00:43:15Z |
success |
| 32 |
|
2021-02-03T00:22:23Z |
failure |
| 31 |
|
2021-02-02T00:26:39Z |
failure |
| 30 |
|
2021-02-01T00:27:56Z |
failure |
| 29 |
|
2021-01-31T00:27:15Z |
failure |
|
|
| puppetlabs-chocolatey |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 91 |
|
2021-03-03T00:54:28Z |
success |
| 90 |
|
2021-03-02T11:03:00Z |
success |
| 89 |
|
2021-03-02T11:00:44Z |
success |
| 88 |
|
2021-02-28T00:40:57Z |
success |
| 87 |
|
2021-02-27T00:40:56Z |
success |
| 86 |
|
2021-02-26T00:41:41Z |
success |
|
|
| puppetlabs-concat |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 89 |
|
2021-03-03T02:43:04Z |
success |
| 88 |
|
2021-03-02T02:27:30Z |
success |
| 87 |
|
2021-03-01T02:12:00Z |
success |
| 86 |
|
2021-02-28T02:09:04Z |
success |
| 85 |
|
2021-02-27T02:10:51Z |
success |
| 84 |
|
2021-02-26T01:50:09Z |
success |
|
|
| puppetlabs-docker |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 106 |
|
2021-03-03T01:45:18Z |
success |
| 105 |
|
2021-03-02T01:37:49Z |
success |
| 104 |
|
2021-03-01T01:33:38Z |
success |
| 103 |
|
2021-02-28T01:33:31Z |
success |
| 102 |
|
2021-02-27T01:33:32Z |
success |
| 101 |
|
2021-02-26T01:32:00Z |
success |
|
|
| puppetlabs-dsc |
|
| puppetlabs-dsc_lite |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 56 |
|
2021-03-03T01:35:32Z |
success |
| 55 |
|
2021-03-02T01:28:46Z |
failure |
| 54 |
|
2021-03-01T01:18:03Z |
success |
| 53 |
|
2021-02-28T01:19:56Z |
success |
| 52 |
|
2021-02-27T01:16:01Z |
success |
| 51 |
|
2021-02-26T01:17:12Z |
success |
|
|
| puppetlabs-exec |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T01:37:46Z |
success |
| 83 |
|
2021-03-02T01:25:44Z |
success |
| 82 |
|
2021-03-01T00:48:50Z |
success |
| 81 |
|
2021-02-28T00:49:02Z |
success |
| 80 |
|
2021-02-27T00:51:19Z |
success |
| 79 |
|
2021-02-26T00:41:16Z |
success |
|
|
| puppetlabs-facter_task |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T00:49:31Z |
success |
| 83 |
|
2021-03-02T00:58:06Z |
success |
| 82 |
|
2021-03-01T00:30:34Z |
success |
| 81 |
|
2021-02-28T00:29:12Z |
success |
| 80 |
|
2021-02-27T00:32:07Z |
success |
| 79 |
|
2021-02-26T00:19:27Z |
success |
|
|
| puppetlabs-firewall |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T01:45:31Z |
success |
| 83 |
|
2021-03-02T01:37:20Z |
success |
| 82 |
|
2021-03-01T01:24:03Z |
success |
| 81 |
|
2021-02-28T01:25:33Z |
success |
| 80 |
|
2021-02-27T01:24:23Z |
success |
| 79 |
|
2021-02-26T01:15:06Z |
success |
|
|
| puppetlabs-haproxy |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 90 |
|
2021-03-03T01:41:47Z |
success |
| 89 |
|
2021-03-02T01:27:51Z |
failure |
| 88 |
|
2021-03-01T00:39:38Z |
success |
| 87 |
|
2021-02-28T00:36:06Z |
success |
| 86 |
|
2021-02-27T00:37:08Z |
success |
| 85 |
|
2021-02-26T00:31:23Z |
success |
|
|
| puppetlabs-helm |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T00:39:25Z |
failure |
| 83 |
|
2021-03-02T00:26:04Z |
failure |
| 82 |
|
2021-03-01T00:31:50Z |
failure |
| 81 |
|
2021-02-28T00:32:48Z |
failure |
| 80 |
|
2021-02-27T00:30:55Z |
failure |
| 79 |
|
2021-02-26T00:33:03Z |
failure |
|
|
| puppetlabs-ibm_installation_manager |
|
| puppetlabs-iis |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 83 |
|
2021-03-03T01:45:47Z |
success |
| 82 |
|
2021-03-02T01:25:44Z |
success |
| 81 |
|
2021-03-02T13:39:50Z |
success |
| 80 |
|
2021-02-28T01:22:42Z |
failure |
| 79 |
|
2021-02-27T01:22:24Z |
success |
| 78 |
|
2021-02-26T01:19:16Z |
success |
|
|
| puppetlabs-inifile |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 89 |
|
2021-03-03T00:47:47Z |
failure |
| 88 |
|
2021-03-02T00:45:40Z |
success |
| 87 |
|
2021-03-01T09:39:19Z |
success |
| 86 |
|
2021-03-01T09:45:08Z |
success |
| 85 |
|
2021-02-27T00:37:46Z |
success |
| 84 |
|
2021-02-26T00:36:01Z |
success |
|
|
| puppetlabs-java |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 104 |
|
2021-03-03T01:52:53Z |
failure |
| 103 |
|
2021-03-02T01:44:58Z |
success |
| 102 |
|
2021-03-01T01:27:16Z |
success |
| 101 |
|
2021-02-28T01:21:27Z |
success |
| 100 |
|
2021-02-27T01:24:45Z |
failure |
| 99 |
|
2021-02-26T00:47:31Z |
success |
|
|
| puppetlabs-java_ks |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T02:21:19Z |
success |
| 83 |
|
2021-03-02T02:12:48Z |
failure |
| 82 |
|
2021-03-01T01:55:30Z |
success |
| 81 |
|
2021-02-28T01:52:02Z |
success |
| 80 |
|
2021-02-27T01:53:17Z |
success |
| 79 |
|
2021-02-26T01:30:29Z |
success |
|
|
| puppetlabs-kubernetes |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 57 |
|
2021-03-03T00:52:22Z |
failure |
| 56 |
|
2021-03-02T00:47:59Z |
failure |
| 55 |
|
2021-03-01T00:46:28Z |
failure |
| 54 |
|
2021-02-28T00:46:06Z |
failure |
| 53 |
|
2021-02-27T00:44:28Z |
failure |
| 52 |
|
2021-02-26T00:44:39Z |
failure |
|
|
| puppetlabs-motd |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 127 |
|
2021-03-03T01:51:13Z |
failure |
| 126 |
|
2021-03-02T01:48:59Z |
success |
| 125 |
|
2021-03-01T15:16:25Z |
success |
| 124 |
|
2021-02-28T00:41:39Z |
success |
| 123 |
|
2021-02-27T00:45:12Z |
success |
| 122 |
|
2021-02-26T00:31:09Z |
success |
|
|
| puppetlabs-mysql |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 84 |
|
2021-03-03T01:38:16Z |
success |
| 83 |
|
2021-03-02T01:29:55Z |
failure |
| 82 |
|
2021-03-01T01:17:20Z |
success |
| 81 |
|
2021-02-28T01:12:39Z |
success |
| 80 |
|
2021-02-27T01:15:28Z |
success |
| 79 |
|
2021-02-26T01:10:45Z |
success |
|
|
| puppetlabs-ntp |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 90 |
|
2021-03-03T01:55:37Z |
success |
| 89 |
|
2021-03-02T01:48:29Z |
success |
| 88 |
|
2021-03-01T01:33:17Z |
success |
| 87 |
|
2021-02-28T01:31:01Z |
success |
| 86 |
|
2021-02-27T01:32:17Z |
success |
| 85 |
|
2021-02-26T01:13:04Z |
success |
|
|
| puppetlabs-package |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 99 |
|
2021-03-03T01:47:27Z |
success |
| 98 |
|
2021-03-02T01:40:17Z |
failure |
| 97 |
|
2021-03-01T01:31:17Z |
success |
| 96 |
|
2021-02-28T01:25:00Z |
success |
| 95 |
|
2021-02-27T01:25:30Z |
success |
| 94 |
|
2021-02-26T01:03:18Z |
success |
|
|
| puppetlabs-panos |
|
| puppetlabs-postgresql |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 76 |
|
2021-03-03T01:41:38Z |
failure |
| 75 |
|
2021-03-02T01:33:42Z |
failure |
| 74 |
|
2021-03-01T01:24:47Z |
failure |
| 73 |
|
2021-02-28T01:23:59Z |
failure |
| 72 |
|
2021-02-27T01:22:12Z |
failure |
| 71 |
|
2021-02-26T01:19:11Z |
failure |
|
|
| puppetlabs-powershell |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 86 |
|
2021-03-03T00:59:22Z |
success |
| 85 |
|
2021-03-02T00:55:26Z |
success |
| 84 |
|
2021-03-01T01:00:32Z |
failure |
| 83 |
|
2021-02-28T00:43:40Z |
failure |
| 82 |
|
2021-02-27T00:45:27Z |
success |
| 81 |
|
2021-02-26T00:38:04Z |
failure |
|
|
| puppetlabs-puppet_conf |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 90 |
|
2021-03-03T01:42:09Z |
success |
| 89 |
|
2021-03-02T01:24:47Z |
success |
| 88 |
|
2021-03-01T00:53:42Z |
success |
| 87 |
|
2021-02-28T00:51:01Z |
success |
| 86 |
|
2021-02-27T00:51:31Z |
success |
| 85 |
|
2021-02-26T00:41:19Z |
success |
|
|
| puppetlabs-reboot |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 99 |
|
2021-03-03T01:10:09Z |
success |
| 98 |
|
2021-03-02T01:01:05Z |
success |
| 97 |
|
2021-03-01T00:48:34Z |
success |
| 96 |
|
2021-02-28T00:48:21Z |
success |
| 95 |
|
2021-02-27T00:45:54Z |
success |
| 94 |
|
2021-02-26T00:48:20Z |
success |
|
|
| puppetlabs-registry |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 114 |
|
2021-03-03T01:08:23Z |
success |
| 113 |
|
2021-03-02T00:58:08Z |
success |
| 112 |
|
2021-03-01T00:46:58Z |
success |
| 111 |
|
2021-02-28T00:46:35Z |
success |
| 110 |
|
2021-02-27T00:44:26Z |
success |
| 109 |
|
2021-02-26T00:44:43Z |
success |
|
|
| puppetlabs-resource_api |
|
| puppetlabs-rook |
|
| puppetlabs-satellite_pe_tools |
|
| puppetlabs-scheduled_task |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 91 |
|
2021-03-03T07:54:33Z |
success |
| 90 |
|
2021-03-02T00:25:59Z |
success |
| 89 |
|
2021-03-02T11:08:16Z |
success |
| 88 |
|
2021-02-28T00:26:35Z |
success |
| 87 |
|
2021-02-27T00:24:33Z |
success |
| 86 |
|
2021-02-26T00:29:22Z |
success |
|
|
| puppetlabs-service |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 82 |
|
2021-03-03T01:12:58Z |
success |
| 81 |
|
2021-03-02T01:08:28Z |
success |
| 80 |
|
2021-03-01T00:58:37Z |
success |
| 79 |
|
2021-02-28T00:57:21Z |
success |
| 78 |
|
2021-02-27T00:55:33Z |
success |
| 77 |
|
2021-02-26T00:53:43Z |
success |
|
|
| puppetlabs-sqlserver |
|
| puppetlabs-stdlib |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 98 |
|
2021-03-03T02:07:08Z |
success |
| 97 |
|
2021-03-02T01:57:42Z |
success |
| 96 |
|
2021-03-01T00:53:36Z |
success |
| 95 |
|
2021-02-28T00:48:44Z |
success |
| 94 |
|
2021-02-27T01:27:13Z |
success |
| 93 |
|
2021-02-26T00:44:51Z |
success |
|
|
| puppetlabs-tagmail |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 90 |
|
2021-03-03T00:35:41Z |
success |
| 89 |
|
2021-03-02T00:39:40Z |
success |
| 88 |
|
2021-03-01T00:29:41Z |
success |
| 87 |
|
2021-02-28T00:24:30Z |
success |
| 86 |
|
2021-02-27T00:25:57Z |
success |
| 85 |
|
2021-02-26T00:15:00Z |
success |
|
|
| puppetlabs-testing |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 145 |
|
2021-03-03T01:21:09Z |
success |
| 144 |
|
2021-03-02T01:10:18Z |
success |
| 143 |
|
2021-03-01T00:59:12Z |
success |
| 142 |
|
2021-02-28T00:57:38Z |
success |
| 141 |
|
2021-02-27T00:57:54Z |
success |
| 140 |
|
2021-02-26T00:54:42Z |
success |
|
|
| puppetlabs-tomcat |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 85 |
|
2021-03-03T02:00:27Z |
success |
| 84 |
|
2021-03-02T01:51:50Z |
success |
| 83 |
|
2021-03-01T01:30:31Z |
success |
| 82 |
|
2021-02-28T01:27:44Z |
failure |
| 81 |
|
2021-02-27T01:30:27Z |
failure |
| 80 |
|
2021-02-26T01:01:27Z |
success |
|
|
| puppetlabs-vcsrepo |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 79 |
|
2021-03-03T01:26:34Z |
failure |
| 78 |
|
2021-03-02T01:16:57Z |
success |
| 77 |
|
2021-03-01T01:04:04Z |
success |
| 76 |
|
2021-02-28T01:02:08Z |
success |
| 75 |
|
2021-02-27T01:02:31Z |
success |
| 74 |
|
2021-02-26T01:00:44Z |
success |
|
|
| puppetlabs-vsphere |
|
| puppetlabs-websphere_application_server |
|
| puppetlabs-wsus_client |
| Workflow | Runs |
| nightly |
| Run Number | Branch | Updated At | Conclusion |
| 57 |
|
2021-03-03T01:28:53Z |
failure |
| 56 |
|
2021-03-02T01:15:00Z |
success |
| 55 |
|
2021-03-01T09:03:48Z |
success |
| 54 |
|
2021-02-28T01:12:37Z |
failure |
| 53 |
|
2021-02-27T01:14:44Z |
success |
| 52 |
|
2021-02-26T01:15:47Z |
success |
|
|


foxconn
Businessmodel of Foxconn
Customer segment
Foxconn serves original equipment manufacturers (OEMs) either as a foundry manufacturer or supplier of components.
Among others, the company has a subsidiary called FIH Mobile that is mainly engaged in providing product development and after-sales support. FIH Mobile, which has won a contract to produce Nokia-branded devices designed HMD, a company formed by former Nokia employees, has its corporate headquarters in Cayman Islands.
Value proposition
The company strives to bring solutions that result in convenience in the everyday lives of people. It achieves that through low-cost manufacturing model that enables brands to enjoy the lowest total costs possible.
Foxconn’s areas of business focus are computer, consumer electronics, communications, digital content and auto parts. The company operates on five key tenets namely: technology, speed, quality, flexibility and cost efficiency.
Channels
The company employs multiple strategies to grow its customer roll. These strategies include participation at trade shows and conference.
The company also uses traditional media and the Internet to advertising to its products and services with the main reaching new customers and expanding the business.
In addition to these efforts, Foxconn also has direct sales team on the ground to hunt for new business deals. The company also maintains key accounts team headed by Key Account Managers.
Customer relationship
As a provider to the OEMs market, Foxconn doesn’t maintain traditional customer relationship. The company’s engineers are at the forefront of customer support because they are the ones who work closely with customers at various stages of product development and prototyping.
Key activities
Contract manufacturing: Foundry manufacturing is one of Foxconn’s main business activities. The company produces and assembles a range of electronic products such as computers, tablets and smartphones on behalf of brand OEMs. Foxconn operates manufacturing factories in several locations around the world. The plants that Foxconn operates globally enable it to produce close to customer and they also provide a channel to appeal to new customers.
Parts supply: Foxconn is also engaged in the production and supply of mostly components for electronic devices.
Diversification: In the recent times Foxconn has stepped up efforts to diversify its business at a time when it is also facing growing pressure in foundry business. For instance, the company is no longer the exclusive contract manufacturers for Apple. As such, the company can be seen diversifying into areas such as medical devices, where profit margins are greater than typical consumer electronics and where more growth is expected in the future. Foxconn is also diversifying into robotics business, with the company itself planning to deploy robot workers at its factories.
Key resources
With more than 1.3 million employees running its factories globally, Foxconn counts its workers as its greatest asset. Without them operations at Foxconn’s research centers and production plants around the world would literally grind to a screeching halt. These workers not only help with product innovation and manufacturing, but they also help to bring new customers on board to ensure that the business keeps growing.
The many manufacturing plants that Foxconn owns around the globe are also a major resource for the company. Because of them, Foxconn has the manufacturing capacity to meet the production demands of its customers. Additionally, the mega factories also enable Foxconn to enjoy greater economies of scale. That explains why Foxconn is a cost leader in contract manufacturing.
The other key resource that Foxconn can boast of is its portfolio of intellectual property. Foxconn had more than 55,000 worldwide patents by 2012. Proprietary technologies that Foxconn owns are a great source of competitive advantage.
Key partners
Foxconn’s customers are also its major partners as it works with them in areas of product innovation, testing and production.
For instance, Apple has made a number of investments in Foxconn to go toward robotics, R&D and factory expansion among others.
Cost structure
One of Foxconn’s main objectives is to increase affordability of electronic products so that every human being can have access to them. As such, the company has modeled its business to ensure that customers enjoy the lowest total cost possible in their production of consumer goods.
Labor cost is one of Foxconn’s major expenses. But the rising labor cost has seen Foxconn contemplating deploying robots on its factory floors to help with works such as welding, spraying and assembling.
But using robots in production could result in massive job losses in places where Foxconn operates factories. The company’s factories in China employ close to 1 million people.
Revenue sources
Foxconn has and continues to diversify its operations, which means it generates revenue from more than one stream. One source of Foxconn’s revenue is contract manufacturing. The company also generates revenue through the sale of branded components for computing systems and devices. The acquisition of Sharp is likely to accelerate Foxconn’s expansion into consumer market.
Foxconn generated consolidated revenue amounting to $135.6 billion in 2015, up from $133.04 billion in 2014 and $91.6 billion in 2011.


Files CCore/inc/crypton/SHA.h CCore/src/crypton/SHA.cpp
Files CCore/inc/crypton/PlatformSHA.h
The following HashFunction<....> classes implement the SHA hash algorithms:
using SHA1 = HashFunction<....> ; using SHA224 = HashFunction<....> ; using SHA256 = HashFunction<....> ; using SHA384 = HashFunction<....> ; using SHA512 = HashFunction<....> ;
SHAnnn implements the correspondent SHA-nnn algorithm.
The following KeyedHashFunction<....> classes implement the HMAC hash functions based on SHA algorithms:
using KeyedSHA1 = KeyedHashFunction<....> ; using KeyedSHA224 = KeyedHashFunction<....> ; using KeyedSHA256 = KeyedHashFunction<....> ; using KeyedSHA384 = KeyedHashFunction<....> ; using KeyedSHA512 = KeyedHashFunction<....> ;
KeyedSHAnnn implements the HMAC based on the correspondent SHA-nnn algorithm.
The file PlatformSHA.h contains stub definitions for the PlatformSHA types.
using PlatformSHA1 = SHA1 ; using PlatformSHA224 = SHA224 ; using PlatformSHA256 = SHA256 ; using PlatformSHA384 = SHA384 ; using PlatformSHA512 = SHA512 ; using PlatformKeyedSHA1 = KeyedSHA1 ; using PlatformKeyedSHA224 = KeyedSHA224 ; using PlatformKeyedSHA256 = KeyedSHA256 ; using PlatformKeyedSHA384 = KeyedSHA384 ; using PlatformKeyedSHA512 = KeyedSHA512 ;
A target may override this header file and provide its own definitions with efficient platform-dependent SHA implementation.


HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU Ballot 1 - Local Development build (v0.9.1). See the Directory of published versions
mCODE Release Notes / Change Log
mCODE 0.9.1 Release
The following are changes relative to mCODE 0.9.0.
Enhancements
- Updated to FHIR Release 4 from DSTU 2.
- Changed base class of mCODE laboratory panels (CBC and CMP) from Observation to DiagnosticReport.
- Documented mCODE compliance criteria.
- Documented preferred value sets for extensible binding and affect on US Core compliance.
- Changed HistologyMorphologyBehaviorVS value set to descendants of SCT#367651003 (Malignant neoplasm of primary, secondary, or uncertain origin (morphologic abnormality)), from descendants of SCT#108369006 (Neoplasm (morphologic abnormality)), because the latter brought in some concepts that do not represent malignant neoplasms.
Corrections and Modifications to Existing Content
- Updated code systems to new FHIR R4 base URL, http://terminology.hl7.org (previously was http://hl7.org/fhir)
- Changed profile name from GeneticMutationTested to GeneticVariantTested.
- Corrected mapping so the reference to PrimaryCancerCondition in all staging-related observations uses the existing 'focus' attribute.
- Renamed extension Orientation to AnatomicalOrientation. The associated value set was also renamed to AnatomicalOrientationVS and its enumerated content was replaced by a logical definition.
- Eliminated ClockDirection as a separate value set because values are incorporated in logically-defined SNOMED-CT AnatomicalOrientationVS.
- Re-wrote the introductory narratives to consolidate multiple pages.
- Changed clinicalStatus on PrimaryCancerCondition and SecondaryCancerCondition from 1..1 to 0..1.
- Typographical fixes to multiple documentation pages.
- Eliminated reference range from GeneticVariantTested and components of GeneticVariantFound.
- Improved the definition of "curative" and "palliative" in TreatmentIntentVS.
- Corrected the definition of TreatmentIntent.
- Improved the explanation of the relationships between the genomics-related profiles.
- Updated examples to validate against FHIR R4 and other changes to the profiles.
- Changed blood pressure test code to LNC#85354-9 "Blood pressure panel with all children optional" to align with FHIR
- Restored device attribute on TumorMarkerTest since laboratories do report it on occasion.
- Added string as an allowable datatype for TumorMarkerTest.value[x], since it is a valid datatype for some of the tests included in TumorMarkerTestVS.
- Changed cardinality of ECOGPerformanceStatus.value and KarnofskyPerformanceStatus.value to 1..1 and ECOGPerformanceStatus.dataAbsentReason and ECOGPerformanceStatus.dataAbsentReason to 0..0
- Changed cardinality of GeneticVariantTested.referenceRange to 0..0.
- Changed cardinality of referenceRange for GeneticVariantFound.component[VariantFoundIdentifier], GeneticVariantFound.component[VariantFoundHGVSName] and GeneticVariantFound.component[VariantFoundDescription] and to 0..0.
- Clarified description of HistologyMorphologyBehaviorVS regarding the use of ICD-O-3 behavior codes.
- Corrected descriptions for multiple codes in the ComorbidConditionVS.
- Updated Data Dictionary to reflect FHIR R4 and other changes to the Implementation Guide.
- Renamed PrimaryCancerConditionVS to PrimaryOrUncertainBehaviorCancerDisorderVS, for greater alignement with value set content.
- Renamed extension prefixes from `shr-core` to `obf-datatype`.
- Replaced onco-core-GeneStudied-extension with observation-geneticsGene standard extension in GeneticVariantTested.
- Corrected the definition of obf-RadiationDosePerFraction-extension.
- Renamed vital-precondition-extension to vital-preconditionCode-extension to distinguish from precondition whose datatype is Reference().
- Improved the definition for obf-RadiationFractionsDelivered-extension.
- Replaced locally defined LateralityVS with FHIR-defined laterality value set in obf-datatype-Laterality-extension.
- Improved definition of onco-core-EvidenceType-extension.
- Replaced obf-dateOfDiagnosis-extension with condition-assertedDate standard extension in PrimaryCancerCondition and SecondaryCancerCondition.
- Added logical definition to TNM-related value sets to include all codes from AJCC staging systems.
- Removed references to MedicationRequest on basedOn attribute for TNMClinicalPrimaryTumorCategory, TNMClinicalRegionalNodesCategory, TNMClinicalDistantMetastasesCategory, KarnofskyPerformanceStatus and ECOGPerformanceStatus.


THE LITTLE FOXES
May 1975 at LLT's Armory Building Playhouse
Director - Michael Howard
Assistant Director - Hilma Seefeld
THE CAST
Addie - Johnnie Ruth Collins
Birdie Hubbard - Beverly Trask
Oscar Hubbard - Jimmie Cox
Leo Hubbard - Steve Lightsey
Benjamin Hubbard - Ralph Woosley
Regina Giddens - Kathryn Anderson
Alexander Giddens - Debby Douglass
Horace Giddens - Joe Myers
William Marshall - Jim Gibbon


iOS builds via command line are much more complex as compared to Android.
Note: Builds work only for Mac users. Since Apple requires that all the builds be made on Xcode itself, iOS apps can only be built on a Mac machine.
These are the few pre-requisites to build a release ipa file.
Ideally, every app has three release variants just like a typical backend application:
Hence, we would need three different schemes
for three different variants.
A typical build process in iOS would have the following steps:
~/Library/MobileDevice/Provisioning\ Profiles/
scripts/ios/profile/XYZ.mobileprovision
scripts/ios/certs/ABC.p12
Place an exportOptions file at scripts/ios/exportOptions/exportOptions-dev.plist
Typically, an exportOptions file looks like this :
scripts/ios/exportOptions/exportOptions-dev.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>compileBitcode</key>
<false/>
<key>method</key>
<string>enterprise</string>
<key>teamID</key>
<string>ABC1234DA</string>
<key>uploadBitcode</key>
<true/>
<key>uploadSymbols</key>
<true/>
<key>manifest</key>
<dict>
<key>appURL</key>
<string>null</string>
<key>displayImageURL</key>
<string>null</string>
<key>fullSizeImageURL</key>
<string>null</string>
</dict>
</dict>
</plist>
Make sure you put all the above files in the gitignore.
Create the script:
The below script will create a new keychain ios-build
and will store the certificate in the keychain. Also, it will make ios-build
the default keychain so that Xcode picks up the certificate from it. Then it will copy the provisioning profile to the correct directory so that Xcode can pick it up.
scripts/ios/keychain.sh
#!/bin/bash
set -e
cur_dir=`dirname $0`
#Check if ios-build keychain exists
export keychainCount=`security list-keychains | grep -E 'ios-build' -c`
if [ $keychainCount == 0 ] ; then
echo "Create ios-build keychain"
# Create a custom keychain
security create-keychain -p "ios-build-password" ios-build.keychain
fi
# Add it to the list
security list-keychains -d user -s ios-build.keychain
echo "Making the ios-build keychain default, so xcodebuild will use it for signing"
security default-keychain -s ios-build.keychain
echo "Unlocking the ios-build keychain"
security unlock-keychain -p "ios-build-password" ios-build.keychain
# Set keychain timeout to 1 hour for long builds
# see http://www.egeek.me/2013/02/23/jenkins-and-xcode-user-interaction-is-not-allowed/
security set-keychain-settings -t 3600 -l ~/Library/Keychains/ios-build.keychain
echo "Importing $IOS_CERTIFICATE to keychain"
security import $cur_dir/certs/$IOS_CERTIFICATE -k ~/Library/Keychains/ios-build.keychain -P $IOS_CERTIFICATE_KEY -T "/usr/bin/codesign" -A
#Mac OS Sierra https://stackoverflow.com/questions/39868578/security-codesign-in-sierra-keychain-ignores-access-control-settings-and-ui-p
security set-key-partition-list -S apple-tool:,apple: -s -k "ios-build-password" ios-build.keychain
# Put the provisioning profile in place
echo "Copying $IOS_PROVISION_PROFILE in place"
mkdir -p ~/Library/MobileDevice/Provisioning\ Profiles
cp "$cur_dir/profile/$IOS_PROVISION_PROFILE" ~/Library/MobileDevice/Provisioning\ Profiles/
Create the script that does the build. This script will run the xcodebuild to first archive the project. Then it will generate the IPA file which can be used for installing the app onto an iPhone.
scripts/ios/builder.sh
#!/bin/bash
set -e
cur_dir=`dirname $0`
WORKING_DIR=`pwd`;
cd $cur_dir/../../ios
echo "Setting version to ${BUILD_NUMBER}, ${BUILD_NAME}"
xcrun agvtool new-version -all ${BUILD_NUMBER}
xcrun agvtool new-marketing-version ${BUILD_NAME}
cd $WORKING_DIR
echo "Archiving the project"
xcodebuild clean archive PRODUCT_BUNDLE_IDENTIFIER=${IOS_APP_ID} -project $cur_dir/../../ios/${PROJECT_NAME}.xcodeproj -scheme $IOS_SCHEME -configuration $IOS_CONFIGURATION -derivedDataPath $cur_dir/../../ios/build -archivePath $cur_dir/../../ios/build/Products/${PROJECT_NAME}.xcarchive
# or if you are not using xcodeproj and are using xcworkspace to build.. use the below code:
# echo "Archiving the project"
# xcodebuild clean archive PRODUCT_BUNDLE_IDENTIFIER=${IOS_APP_ID} -workspace $cur_dir/../../ios/${PROJECT_NAME}.xcworkspace -scheme $IOS_SCHEME -configuration $IOS_CONFIGURATION -derivedDataPath $cur_dir/../../ios/build -archivePath $cur_dir/../../ios/build/Products/${PROJECT_NAME}.xcarchive
#SIGN
# Issue : "No applicable devices found."
# Fix: https://stackoverflow.com/questions/39634404/xcodebuild-exportarchive-no-applicable-devices-found
unset GEM_HOME
unset GEM_PATH
echo "Export archive to create IPA file using $IOS_EXPORT_OPTIONS_PLIST"
xcodebuild -exportArchive -archivePath $cur_dir/../../ios/build/Products/${PROJECT_NAME}.xcarchive -exportOptionsPlist $cur_dir/../../scripts/ios/exportOptions/$IOS_EXPORT_OPTIONS_PLIST -exportPath $cur_dir/../../ios/build/Products/IPA
echo "IPA will be found at $cur_dir/../../ios/build/Products/IPA/$IOS_SCHEME.ipa"
Run the keychain.sh
to setup the certificate and provision profile like this:
IOS_CERTIFICATE='ABC.p12' IOS_CERTIFICATE_KEY='PASSWORD' IOS_PROVISION_PROFILE='ABC.mobileprovision' sh scripts/ios/keychain.sh
Now, run the build script to build the ipa file like this:
PROJECT_NAME='NoteTaker' IOS_APP_ID='com.notetaker.app.ios' BUILD_NUMBER=11 BUILD_NAME=1.1.1 IOS_SCHEME='local' IOS_CONFIGURATION='RELEASE' IOS_EXPORT_OPTIONS_PLIST='exportOptions-dev.plist' sh ./scripts/ios/builder.sh
The build should take a couple of minutes and you can find the final ipa file at
ios/build/Products/IPA/
The code till here can be found on the branch chapter/11/11.2